ntoskrnl.exe is responsible for memory management and other kernel based services. It could be a driver causing the issue.
Check your event logs for any error or critical problems when the BSOD occurred to see what the issue is.
Also I would start up verifier.exe (Included Windows tool) and create a custom setting for non-Windows based services/drives. It'll throw up a BSOD when a violation is detected and should help determine what driver has caused the issue.
Then check the mini dumps again, remember to delete the settings after you're done with them.
NOTE: If you BSOD before you log in just means that driver is set to load at boot up. Just restart into safe mode.


LinkBack URL
About LinkBacks
Reply With Quote
. I clicked restart to allow the windows updates to install completely however it just hung as the force restart option came up. Anyway, I will follow your advice now @mikeo01. I will let you know what I come up with ASAP.

