ntoskrnl.exe BSOD coming out of sleep

Toggle sidebar Toggle sidebar
A

alexjustdoit

Distinguished
Dec 21, 2008
11
0
18,510
My new laptop, fresh Win 8 install a few days ago, BSODs whenever coming out of sleep. Hibernate works fine.

Crash dumps always indicate ntoskrnl.exe

Typically the error is CRITICAL_PROCESS_DIED or something like that. Once in a while it gives KERNEL_DATA_INPAGE_ERROR. Both report ntoskrnl.exe EXCEPT once it gave CRITICAL_PROCESS_DIED and reported cng.sys as the culprit.

Sometimes it goes straight to BSOD, sometimes it shows the logon background for a few seconds (just background image, no logon or user) then BSODS.

Here is the minidump file, hope it is ok that I uploaded it externally and linked it here. Wasn't sure how else to do it.
http://s000.tinyupload.com/?file_id=09160426164690038761





 
Sort by date Sort by votes
A

alz_solstice

Honorable
Jul 3, 2013
364
0
10,960
Hello Alex,

First, this cng.sys is part of Windows and should not remove or delete. If this file is corrupted, then it will show the same blue screen as stated.

Try fixing this by the following in safe mode since BSOD occurs when running Windows.

1. Start-up Repair
- Turn On PC
- Press F8 repeat to open Advanced Startup Options
- Select Repair Your Computer and then Startup Repair.

2. Install Intel Chipset Driver(skip if you are not using Intel Based Motherboards)
- Look for another PC and download this Intel Chipset Driver
http://downloadcenter.intel.com/confirm.aspx?httpDown=http://downloadmirror.intel.com/23215/eng/INF_9.4.0.1027.exe&lang=eng&Dwnldid=23215&ProductID=3604
- On your PC, open Safe Mode
- Run INF_9.4.0.1027.exe

3. Run SFC /scannow
- While in safe mode, click the Start Button
- Type Command Prompt, right click the Command Prompt and select Run as administrator
- Type sfc /scannow and press Enter
 
Upvote 0 Downvote
A

alexjustdoit

Distinguished
Dec 21, 2008
11
0
18,510
The command returned "No integrity errors found" or something like that. Chipset drivers seem to have installed no problem (note, I already have installed intel chipset drivers).

It seems to have helped somewhat though. Whereas before I would get the logon background and then the crash, now I get the background and the rest of the logon screen. Once I press a button to make the password prompt appear however, it freezes again and BSODs a few seconds later, with the same error message.
 
Upvote 0 Downvote
A

alexjustdoit

Distinguished
Dec 21, 2008
11
0
18,510
The WhoCrashed app doesn't point toward any specific drivers, and basically just gives me the same information we have discovered so far.

I'm trying to get a more in depth driver verifier tool to work, but as of yet, it won't start upon reboot as it should. Theoretically, this program should identify which third party driver (assuming it is a 3rd party driver) is causing the problem.
 
Upvote 0 Downvote
A

alexjustdoit

Distinguished
Dec 21, 2008
11
0
18,510
Well it just shows the same information that the BSODViewer app was giving me when reading the dump files, pointing to ntoskrnl.exe but saying that another driver might be at fault but it is unidentifiable. So as far as which specific driver, no such luck.

But

While running verifier, one crash dump pointed to netwew00.sys, but after running it a few times that dump somehow vanished. Regardless, I tried rolling back my wireless drivers, uninstalling them, and installing new ones, all with no luck.
 
Upvote 0 Downvote
A

alz_solstice

Honorable
Jul 3, 2013
364
0
10,960
Seems I can't find a solution with this. Have you tried repairing your Windows using the Windows Installation CD? It does fix these kinds of problem. But if the problem really persists, then you might need to do a fresh install of Windows. For the drivers, try using a driver update utility or something like that. I've been using this Driver Finder and it helps me install the latest updates.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom