Windows 10: BSOD on startup (ntoskrnl.exe)

When I started up windows, the little white dotted circle in the black screen stopped spinning for a good minute, then had to reboot again, and I got a dump file. I read it, and had an issue with ntoskrnl.exe. I looked it up, and read that most of the time, it means bad RAM. I did the windows memory diagnostic, and got no problems detected. So, whats the issue?

:)

 

Since the Windows 1709 update my PC randomly crashes/restarts once a day

Hi, i have same ntoskrnl.exe+759faf problem since 1709 update.

Try to turn off "Fast Startup" in settings. It helped me. Almost 2 weeks without BSOD since i turned off fast startup.

 

BSOD: IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_NOT_HANDLED

Greetings,

last week i made some hardware changes to my laptop (lenovo z70-80). I installed a new ssd and upgraded my 4gb RAM to 16 gb RAM . The next day i experienced some BSOD errors (only at a cold startup, after the reboot of the system everything works just fine).
Most commonly the cause of BSOD was SYSTEM_THREAD_NOT_HANDLED and just lately the IRQL_NOT_LESS_OR_EQUAL. I post the info from the last BSOD as got from blue screen viewer :

Bug Check String;

IRQL_NOT_LESS_OR_EQUAL

Bug Check Code: 0x0000000a

Parameter1: 00000000`00060001

Parameter2: 00000000`000000ff

Parameter3: 00000000`00000000

Parameter4: fffff802`8266bf72

Caused by Driver: ntoskrnl.exe

Caused by Address: ntoskrnl.exe+16c580

File Description: NT Kernel & System

thanks in advance.

 

Hi jonathan4210,

Welcome to the 10forums *Smile

Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to install as less as possible software using custom/advanced options, you can use this tutorial for the installation part *Arrow AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums
Attachment 100324
Code: 6: kd> lmvm atikmdag Browse full module list start end module name fffff801`28080000 fffff801`297dc000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: atikmdag.sys Image name: atikmdag.sys Browse all global symbols functions data Timestamp: Wed Feb 10 04:25:15 2016 (56BAAD9B) CheckSum: 016E3C29 ImageSize: 0175C000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

Last time I had a BSOD, the issue was related to atikmdag.sys, for which I had used DDU, and this was roughly 2 weeks ago. Only difference is that I reinstalled the drivers with the catalyst package. Now I followed the link you provided, and only installed the correct drivers (and set auto driver installation to No). Only time will tell if my problem has actually been fixed this time. So for now, thanks *Smile

Also, I noticed that the last 2 times it crashed, it happened after I cleaned my registry (not right away, after shutting down and booting up again). Is this a coincidence or can it be related to the issue?

 

Keep me posted on how it goes please *Smile

 

Would you recommend me trying the Windows Driver Verifier? It looks like it can tell me if the driver is good right away instead of waiting for a BSOD (cause I dont get them often), but I also read it can be dangerous.

 

I wouldn't until I'm certain it would be necessary to catch a driver.