SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Windows 10 boot loop

2009/2010 Acer Aspire 5738DZG
Intel Pentium T4400
ATI Mobility Radeon HD 4570
15.6" screen
Windows 10 x64

When the laptop is turned on, a BSOD appears with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.

It automatically restarts after around 5 seconds.

F8 does nothing.

I have booted with a Windows 10 USB flash drive and it shows Preparing automatic repairbefore showing the BSOD again.

Any ideas?

Hi King Mustard,

Please provide system specs about the laptop.
F8 only works with desktops, laptops have a specific key (combination) to get in safe mode.

Is the USB recovery media? If so, boot from it, go to the advanced troubleshooting options and open command prompt
In the command prompt enter following command

Code:

start msconfig

In msconfig, go to the boot tab and click safe mode.
Click apply > ok and reboot when asked.
See if that helps.

Hi King Mustard,

Please provide system specs about the laptop.
F8 only works with desktops, laptops have a specific key (combination) to get in safe mode.

Is the USB recovery media? If so, boot from it, go to the advanced troubleshooting options and open command prompt
In the command prompt enter following command

Code:

start msconfig

In msconfig, go to the boot tab and click safe mode.
Click apply > ok and reboot when asked.
See if that helps.

Most of what you asked is in the first post.

Laptop specifications:
2009/2010 Acer Aspire 5738DZG
Intel Pentium T4400
ATI Mobility Radeon HD 4570
15.6" screen
Windows 10 x64

It's Windows 10 that is on the bootable USB flash drive.

When I boot from it, I only see Preparing automatic repairbefore the system shows the same BSOD and restarts, so I can't type anything in anywhere, or get into Safe Mode.

Can you get in the BIOS?

I read on the t'Internet that pulling the battery out and then back in and re-turning it on would make the system boot.

I definitely didn't think it would work but for some reason, it did!

I've found a temporary solution. After pressing F8, run windows in Debug Mood, it didn't show this error and seams like normal.

I have just registered to answer to this thread. Oh my f.king god I was trying to solve the same problem and I have watched every stupid youtube video then I saw the last comment above. Oh god why, i removed the battery and bammm the comp. is back. This was the most rideculous problem i have ever met as a 17 years of windows user. Thank you dude, thanks everybody. Nothing else works bisedes this, i was nearly throwing out the laptop, oh my f.king god i still cant believe it. Thanks everybody, good day.

I have just registered to answer to this thread. Oh my f.king god I was trying to solve the same problem and I have watched every stupid youtube video then I saw the last comment above. Oh god why, i removed the battery and bammm the comp. is back. This was the most rideculous problem i have ever met as a 17 years of windows user. Thank you dude, thanks everybody. Nothing else works bisedes this, i was nearly throwing out the laptop, oh my f.king god i still cant believe it. Thanks everybody, good day.

As a nerd, I was shocked, too.

Sometimes it's the simplest things, eh!

You know why it is best to start with the basics and move slowly to more advanced methods