BSOD after waking from sleep often ntoskrnl.exe

anubisvic · 06 Jul 2014

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 · 06 Jul 2014

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.
System Info - See Your System Specs

Arc · 06 Jul 2014

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.
_________________________________

Code:

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

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

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

Code:

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
---------

Code:

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

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

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

Code:

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

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

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

anubisvic · 07 Jul 2014

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 · 07 Jul 2014

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 · 08 Jul 2014

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 · 08 Jul 2014

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 · 08 Jul 2014

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

ICIT2LOL · 08 Jul 2014

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
PSU - Test DC Output Voltage

ICIT2LOL · 08 Jul 2014

anubisvic said:

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.