BSOD after waking from sleep often ntoskrnl.exe

[anubisvic]

Hi All,

I've had experience with random BSOD for the past few months and it was mostly coming after waking the PC up after sleep. I've tried many thinks such as memtest memory, install only vendor drivers, driver verifier etc but no luck ( I am keen to run them over again if anyone have any suggestions ). So I decided to re-install everything again from scratch. After installing all the basic drivers and software I need, the BSOD started again and I could not figure out why. The BSOD are 90% after wake from sleep, and sometime it will crash after an hour or a few hours.

Any assistance would be great! Many thanks in advance.
Attached zip contains the latest 4 dmp files after the os re-install.

 

[ICIT2LOL]

Hello and welcome Anubis mate some system specs would be good as I personally do not understand what looks like the Chinese language in msinfo for example.
http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

 

[Arc]

Hi anubisvic.

All the recent BSODs are of different bugcheck codes without any finite probable cause. It gives a good hint of failing memory.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.
_________________________________

BugCheck 4E, {99, 1e3023, 2, 2dbe22}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

BugCheck 19, {20, fffff8a012725f40, fffff8a012725f80, 5040204}

GetPointerFromAddress: unable to read from fffff80004afe100
GetUlongFromAddress: unable to read from fffff80004afe1c0

fffff8a012725040 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

GetUlongFromAddress: unable to read from fffff80004a6ca38
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+c4 )

Followup: MachineOwner
---------

BugCheck 24, {1904fb, fffff88008638bf8, fffff88008638450, fffff800049be6c7}

Probably caused by : ntkrnlmp.exe ( nt!CcMapData+117 )

Followup: MachineOwner
---------

BugCheck 3B, {c0000005, fffff8000497042c, fffff8800a205f80, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObReferenceObjectByHandleWithTag+10c )

Followup: MachineOwner
---------

 

[anubisvic]

ICit2lol: My apology! I've updated my system spec.
Arc: I will run memtest overnight and post results afterward.

Not sure whether this will help but just had another crash this morning after computer wake from sleep.

 

[anubisvic]

Attached is the memtest so far after 12 hours. I will continue to run for another 6 hours. However, based on the fact that I've run 8 passes before on these memory modules 2 months ago, I suspect that they are okay.

The BSOD only comes after PC wakes, what would be other possible causes?
Please advise on the next step of actions after memtest. Many thanks.

 

[ICIT2LOL]

Am guessing here but am wondering if the memory problem is linked to theGPU's? as that error states memory shared - I could be quite wrong but it wouldbe a good idea to make sure the drivers for the GPU's are up to date forstarters. I have had a look for these but have got nowhere - most unusual for NVidia.
The other thing you could check out is the PSU > Run HW Info HWiNFO, HWiNFO32/64 - Download
close the right hand panel > hit Sensors > in the window that drops down scroll down until you get to the section which gives you the PSU voltages (it may come up with a title that is unfamiliar) In my pic is my laptop which does not really show what I mean but you will see the rail voltages when you get to the right part of that window. Now the volts that show will need to be within +/- 5% of the required voltage - nay variance and the PSU is not functioning ok.

 

[anubisvic]

Just attached a screen for 21 hrs of memtest without any errors.

ICit2lol: Thanks for trying! I am not sure how I can test the PSU since the BSOD usually come right after I wake the PC from sleep then die right after and reboot. But I will give it a go.

 

[anubisvic]

Attached is the HWiNFO32 sensor readings. It appears to be okay ... nothing out of the ordinary.
Any other thoughts?

 

[ICIT2LOL]

Ok mate this is an alternative way of testing it - just remember to use a digital multimeter like in the pics as an analogue one injects volts to test and they usually have 9 volt batteries in them so injecting that into a 3.3 rail is not a good idea
http://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html

 

[ICIT2LOL]

Attached is the HWiNFO32 sensor readings. It appears to be okay ... nothing out of the ordinary.
Any other thoughts?

Yes nothing out of the ordinary although correct volts does not necessarily mean correct current. Having said that I reckon the PSU can be eliminated.

 

[Arc]

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]

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]

All the best.

 

[anubisvic]

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?