BSOD after waking from sleep often ntoskrnl.exe

Arc · 08 Jul 2014

As memtest86+ is not showing any error, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

anubisvic · 15 Jul 2014

Hi All,

I've turned on driver verifier and ran it for a few days.

It crashed twice due to gdrv.sys.
It is something inserted by Gigabyte App Center.

After remove all Gigabyte apps (had to manually remove the gdrv.sys), and remove Daemon Tool Lite, no BSOD for the last 7 days (kept on sleeping and waking without shutting down completely) It seems that the Gigabyte drivers might be the main issue. What I am curious about is why these driver issues were not caught be the crash dumps...

I will run it for another week or two to see whether it has really solved the problems.
Really really appreciate all the help ICit2lol and Arc!

Arc · 15 Jul 2014

All the best. :)

anubisvic · 19 Aug 2014

Hi All,

Apology for the late response. After a few more weeks of testing, I had more crashes (similar issues, but on ntkrnlmp.exe, ntfs.sys now ... rather than ntoskrnl.exe).

Since I still could not figure out what is wrong, I attempted to negotiated with the retail store and Gigabyte and tried to get an exchange, but they refuse to do it right the way without sending it to repair and will take at least 3~4 weeks. Since I can't have a PC without a board, I want to try a few more things out before getting to that ...

Interesting enough, I found a post recently mentioning how Samsung SSD does not recommend Sleep function at all.
Samsung Magician + RAPID Mode + 840 EVO SSD = can't sleep - AnandTech Forums and I wonder whether that could be my problem.

Near the bottom is Samsung supports claim:

Please note that you are not supposed to put a computer with an SSD to sleep and this is what is causing the issue. It creates a read and write on the SSD, which will degrade its performance and length of use of the drive.

I am now enabling and disabling some SSD functions using Samsung Magician including:
- Hibernation Mode (Magician disable it by default)
- Power Option (Samsung has its own Windows Power profile)
to see how it goes ...

Has anyone heard that Samsung SSD is not good to sleep?
Or is that claim totally not true?