Windows 10: BSOD - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED on boot, even safe mode.

Hi, I'm getting a BSOD with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED every time I try to boot. I even get this BSOD when trying to get into safe mode. There's no sys file specified. OS is Windows 10 Pro x64 (10.0.10586)

Attachment 56647

I can get to it the command prompt from the Win 10 troubleshooter -> Advanced Options menu. I tried running the dm_log_collector.exe from here, and it says "The sub system needed to support the image type is not present.". Is there another way I can gather the logs?

This all happened after a pop-up message offering me to upgrade to Kaspersky Internet Security 2016, from KIS 2015. That installed and said Windows needed to restart, which I did.

:)

 

Lenovo Yoga 12 Windows 10 BSOD after Synaptic driver installed

Hi,

I am able to go to safe mode only with advanced repairing options>startup options...

In Safe mode seems that everything working fine... touch pad is fully functional.

I`m try to set clean boot in Safe mode and windows still reboots with BSOD.

First i did clean install of windows 10 pro created with Mediacreationtoolx64.

Then i check for updates and windows install all updates.

After reboot all devices works ok... synaptics pointing device is working with all his features...

Then i did another reboot and then i get BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED > reboot

then:

- BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED > reboot

- BSOD PNP_DETECTED_FATAL_ERROR > reboot

- BSOD PNP_DETECTED_FATAL_ERROR > reboot

- BSOD PAGING_IN_NONPAGED_AREA (win32kbase.sys) >reboot

- BSOD PNP_DETECTED_FATAL_ERROR > reboot

- advanced repair opt. > safe mode

- it boot in Safe mode and everything works fine, touch pad fully works > reboot

- boot in normal mode, everything works fine, touch pad fully works > reboot

- BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED > reboot

- BSOD PNP_DETECTED_FATAL_ERROR > reboot

- BSOD PNP_DETECTED_FATAL_ERROR > reboot

- advanced repair opt. > safe mode , all works fine

- setup clean boot > reboot

- BSOD PNP_DETECTED_FATAL_ERROR > reboot

- BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED > reboot

- advanced repair opt. > safe mode , all works fine

- uninstall Synaptics app and driver > reboot

- boot in normal mode is ok now but there is no touchpad at all

- update pointing device drviver from device manager > reboot

- BSOD PNP_DETECTED_FATAL_ERROR > reboot

- BSOD SYSTEM_THREAD_EXCEPTION_NOT_HANDLED > reboot

- advanced repair opt. > safe mode , all works fine

- uninstall Synaptics app and driver > reboot

- boot in normal mode - touchpad works with base windows driver (not fully functional but works like after clean installation of Windows 10) > reboot

- normal boot ok again > disable clean boot (restore to normal) > reboot

- boot normal, everything is fine (touchpad works with windows base driver) > reboot

- boot normal, everything is fine (touchpad works with windows base driver) > reboot

..... and again and again... boot normal...

i try to clean install windows... disable automatic update in gpedit.msc, use wushowhide to hide synaptics driver hrom update, check and install all other updates, and windows works fine (except pointing device, is not fully functional)

same issues i face with Synaptics driver from Lenovo support page... there is driver ver. 19.0.12. 61 7/9/2015 for windows 10...

Sorry for long post but it`s obvious that there is a problem with pointing device driver.

It`s very annoying...

The laptop is Lenovo ThinkPad Yoga 12 20DK001XCX

Please help

 

Cortana broken after an upgrade

System restore causes BSOD 0xc000021a. Can’t even boot safe mode

 

Hi anders,

Do you have a restore point prior to updating Kaspersky?

 

Hi, no sadly when I went to that option, there were no restore points at all. The automatic repair also does not help.

 

Ok, lets try a few things based on the usual causes for this error.
Please start with testing your memory, with your amount of memory it'll likely take a day to reach the requirements.






Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

 

Thanks. I've just started Memtest86+ having just finished a complete virus check with Kaspersky Rescue Disc.

 

Memtest is still running and on pass 6 after 24 hours. Suspect pass 8 will complete when I'm asleep. I'm away with work until Wednesday evening, so will report back then. Perhaps you could let me know the next step/test please? Assuming all 8 passes complete okay, so I can hit the floor running when I'm back. Thanks.

 

A next step would be to strip down the hardware to try to get your system booting again to remove Kaspersky.
Thus, remove the graphics card, every ram stick until 1 is left and remove anything else like peripherals that isn't required for boot.

 

Ended up being away longer than I expected. 8 passes of Memtest did complete without error.

I've now removed everything I think I can, leaving my boot SSD, 1 stick of RAM, keyboard and mouse. I borrowed an old Nvidia graphic card from a good friend, which I swapping in for my Radeon.

Win 10 still shows the same error, can't get into safe mode. *cry

 

You don't need a GPU to boot, please remove it and try to boot again in any way.

 

How will I know if it boots without a monitor? I don't have on board graphics.

 

The GPU is a hardware component that is NOT active in safe mode.
The GPU isn't used in safe mode, because Windows uses its own display drivers.

You really don't need a graphics card to get display, Windows will use its own display drivers.

 

Sorry, I'm probably being very dense here. So I need to try booting my machine with no graphics card (and therefore no monitor). What do I do then? Hit the power button after a reasonable period of time, and plug back in my graphic card.

 

Like I said, remove the GPU and try to boot.
Do NOT put the GPU back in yet.