BSOD when waking PC up from sleep mode

[aussiepride]

Hi everyone!
I recently experienced a blue screen of death when waking up my PC from sleep mode and do not know what has caused it. I've followed the instructions by using the DM log collector and would greatly appreciate anyone's help. If you require any more info please do not hesitate to ask. Thanks!

 

[ICIT2LOL]

Hello AP mate that dump contains a fault that is or can be down to many things and we need to check out a few things before we go any further.

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80003249000 nt
DEBUG_FLR_IMAGE_TIMESTAMP:  55afca65
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000000 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt+86739
fffff800`032cf739 44893498        mov     dword ptr [rax+rbx*4],r14d
BUGCHECK_STR:  0x1E_c0000005_R
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  [COLOR=red]WIN7_DRIVER_FAULT[/COLOR]
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff8000333d832 to fffff800032bc5c0
STACK_TEXT:  
fffff880`08626cc8 fffff800`0333d832 : 00000000`0000001e ffffffff`c0000005 fffff800`032cf739 00000000`00000000 : nt+0x735c0
fffff880`08626cd0 00000000`0000001e : ffffffff`c0000005 fffff800`032cf739 00000000`00000000 ffffffff`ffffffff : nt+0xf4832
fffff880`08626cd8 ffffffff`c0000005 : fffff800`032cf739 00000000`00000000 ffffffff`ffffffff fffff880`014d7b01 : 0x1e
fffff880`08626ce0 fffff800`032cf739 : 00000000`00000000 ffffffff`ffffffff fffff880`014d7b01 fffffa80`0978f1b0 : 0xffffffff`c0000005
fffff880`08626ce8 00000000`00000000 : ffffffff`ffffffff fffff880`014d7b01 fffffa80`0978f1b0 fffff8a0`14de3140 : nt+0x86739

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt+86739
fffff800`032cf739 44893498        mov     dword ptr [rax+rbx*4],r14d
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  nt+86739
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  [COLOR=red]ntoskrnl.exe[/COLOR]
BUCKET_ID:  WRONG_SYMBOLS
FAILURE_BUCKET_ID:  [COLOR=red]WRONG_SYMBOLS[/COLOR]
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:wrong_symbols
FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner

Have you made any major changes to the machine recently ? new hardware ? software.

I think it would not be a bad idea to at least run these

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2 >in safe mode if need be

then these

https://www.malwarebytes.org/mwb-download/index.html

http://www.superantispyware.com/

http://www.bleepingcomputer.com/download/adwcleaner/

ADW download from bleepingcomputer delete any rubbish found with the malware scans

NB If anyone is runningKaspersky security it may rant about ADW - just ignore it or disable it for awhile

 

[aussiepride]

Hello AP mate that dump contains a fault that is or can be down to many things and we need to check out a few things before we go any further.

ADDITIONAL_DEBUG_TEXT:  
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80003249000 nt
DEBUG_FLR_IMAGE_TIMESTAMP:  55afca65
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000000 
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
nt+86739
fffff800`032cf739 44893498        mov     dword ptr [rax+rbx*4],r14d
BUGCHECK_STR:  0x1E_c0000005_R
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  [COLOR=red]WIN7_DRIVER_FAULT[/COLOR]
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff8000333d832 to fffff800032bc5c0
STACK_TEXT:  
fffff880`08626cc8 fffff800`0333d832 : 00000000`0000001e ffffffff`c0000005 fffff800`032cf739 00000000`00000000 : nt+0x735c0
fffff880`08626cd0 00000000`0000001e : ffffffff`c0000005 fffff800`032cf739 00000000`00000000 ffffffff`ffffffff : nt+0xf4832
fffff880`08626cd8 ffffffff`c0000005 : fffff800`032cf739 00000000`00000000 ffffffff`ffffffff fffff880`014d7b01 : 0x1e
fffff880`08626ce0 fffff800`032cf739 : 00000000`00000000 ffffffff`ffffffff fffff880`014d7b01 fffffa80`0978f1b0 : 0xffffffff`c0000005
fffff880`08626ce8 00000000`00000000 : ffffffff`ffffffff fffff880`014d7b01 fffffa80`0978f1b0 fffff8a0`14de3140 : nt+0x86739

STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt+86739
fffff800`032cf739 44893498        mov     dword ptr [rax+rbx*4],r14d
SYMBOL_STACK_INDEX:  4
SYMBOL_NAME:  nt+86739
FOLLOWUP_NAME:  MachineOwner
IMAGE_NAME:  [COLOR=red]ntoskrnl.exe[/COLOR]
BUCKET_ID:  WRONG_SYMBOLS
FAILURE_BUCKET_ID:  [COLOR=red]WRONG_SYMBOLS[/COLOR]
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:wrong_symbols
FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner

Have you made any major changes to the machine recently ? new hardware ? software.

I think it would not be a bad idea to at least run these

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2 >in safe mode if need be

then these

https://www.malwarebytes.org/mwb-download/index.html

http://www.superantispyware.com/

http://www.bleepingcomputer.com/download/adwcleaner/

ADW download from bleepingcomputer delete any rubbish found with the malware scans

NB If anyone is runningKaspersky security it may rant about ADW - just ignore it or disable it for awhile

Hi! Thank you for helping me! I've done both the scans you recommended and it showed that everything was fine. I haven't made any recent changes to my machine recently but after my BSOD I did notice that I needed to install a few windows updates and did so accordingly. Do you think this BSOD could have been caused by not having the latest updates installed?

 

[ICIT2LOL]

Possible but not in any way definite this fault can as I said before have a multitude of causes software and hardware we just need to work through the machine to find if anything is out of whack. As you may recall I did mark WIN DRIVERS in red which could be just anything from drives to graphics.

Now run those malware scans as well - if you haven't already and please to make life a tad easier do this as we need to know what it is we are working with.

SYSTEM SPECS ADD IN

Can we have some systemspecs please as what you have posted gives us not that much (or anythingat all with some folks) to work with and given there are so many manufacturersof components and configurations that do influence what goes on within anygiven machine and OS.
System Info - See YourSystem Specs

The do this for starters



Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right handwindow select Sensors and scroll down to the power section where you will seewhat the volts are doing see my pic. Now the section you want will be labeled -for example Asus boards usually have "Nuvoton" and Gigabyte boards"ITE" in any case the section you want will have Vbatt or VBAT in it(dead give away)
The original right hand window shows the machine running and is handy for thatbut for looking at the components in some detail close it and use the main lefthand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in andthen click on the individual component/s (it will highlight in blue) - in theright hand side will appear all sorts of details including brands speeds andother essential info that particular device. See pic for example.

I ask because the PSU is very overlooked when tracking down a fault and is maybe in a lot of cases the primary faulter.

When we get the specs back we can go on from there

 

[aussiepride]

Possible but not in any way definite this fault can as I said before have a multitude of causes software and hardware we just need to work through the machine to find if anything is out of whack. As you may recall I did mark WIN DRIVERS in red which could be just anything from drives to graphics.

Now run those malware scans as well - if you haven't already and please to make life a tad easier do this as we need to know what it is we are working with.

SYSTEM SPECS ADD IN

Can we have some systemspecs please as what you have posted gives us not that much (or anythingat all with some folks) to work with and given there are so many manufacturersof components and configurations that do influence what goes on within anygiven machine and OS.
System Info - See YourSystem Specs

The do this for starters



Using HW Info
PART A:
You can test the volts on the PSU with HW Info HWiNFO, HWiNFO32/64 - Download < download the right bit version and close the right handwindow select Sensors and scroll down to the power section where you will seewhat the volts are doing see my pic. Now the section you want will be labeled -for example Asus boards usually have "Nuvoton" and Gigabyte boards"ITE" in any case the section you want will have Vbatt or VBAT in it(dead give away)
The original right hand window shows the machine running and is handy for thatbut for looking at the components in some detail close it and use the main lefthand side panel
FOR OTHER COMPONENTS
PART B:
Open each small square with + in it on the section the components are in andthen click on the individual component/s (it will highlight in blue) - in theright hand side will appear all sorts of details including brands speeds andother essential info that particular device. See pic for example.

I ask because the PSU is very overlooked when tracking down a fault and is maybe in a lot of cases the primary faulter.

When we get the specs back we can go on from there

Hi! I've added in my specs using that program that you recommended. Obviously, the program doesn't provide the info to fill in all of the fields in the spec page, so if you require anymore feel free to let me know.

 

[ICIT2LOL]

Sorry late reply mate had to be off line yesrday.


Now that is good stuff at least we know what we are working with and all I need for the moment is that info as per the HW Info

 

[aussiepride]

Sorry late reply mate had to be off line yesrday.


Now that is good stuff at least we know what we are working with and all I need for the moment is that info as per the HW Info

No worries! Thanks for the help! Is this what you are after? If not feel free to let me know and Ill do my best to get the info that you need. Thanks!

 

[ICIT2LOL]

Ok mate that is good we are on he same page What you need to do is scroll down that right hand panel until you get to a section that has that reference to Vbatt or VBATT in it and it will usually be in a section titled as per my pic that title changes from brand to brand the important thing is that you see that Vbatt info it is the CMOS battery and it will show you the voltage on the different rails.

Post back pic of that section.

 

[aussiepride]

Ok mate that is good we are on he same page What you need to do is scroll down that right hand panel until you get to a section that has that reference to Vbatt or VBATT in it and it will usually be in a section titled as per my pic that title changes from brand to brand the important thing is that you see that Vbatt info it is the CMOS battery and it will show you the voltage on the different rails.

Post back pic of that section.

Isn't that already in the pic that I attached?

 

[ICIT2LOL]

No mate if I am seeing what you posted it is only showing me the CPU details I need that section as in this pic - you need to scroll down that right hand panel until you get to that section that has either Vbatt VBATT or something very similar. If you look it will show two different refs to the 3.3v rail - one is the CMOS battery hence Vbatt etc and the 3.3v rail that goes to the motherboard.

In my pic I have snipped out the scroll bar so at the very right hand side just like any window you open so use that to get to the refs I want. I've changed the pic to show you where that scroll bar will be found.

 

[aussiepride]

No mate if I am seeing what you posted it is only showing me the CPU details I need that section as in this pic - you need to scroll down that right hand panel until you get to that section that has either Vbatt VBATT or something very similar. If you look it will show two different refs to the 3.3v rail - one is the CMOS battery hence Vbatt etc and the 3.3v rail that goes to the motherboard.

In my pic I have snipped out the scroll bar so at the very right hand side just like any window you open so use that to get to the refs I want. I've changed the pic to show you where that scroll bar will be found.

Hang on..the version of HWiNFO I'm using is different to yours. I don't have the option up the top to select sensors like you do. Where did you get the version you are using? I'm using a 64-bit version of windows.

 

[ICIT2LOL]

Ok mate in post #4 click on the link I have included in that and use the correct bit version.

But just to be sure this is the link you want to use HWiNFO, HWiNFO32/64 - Download

In the pics is what you should see on clicking the site open and what to choose in bit version and then go to the bottom and find the downloader you want open it out and choose the US version - I always use this link on any machine I install this valuable tool on

 

[aussiepride]

Ok mate in post #4 click on the link I have included in that and use the correct bit version.

But just to be sure this is the link you want to use HWiNFO, HWiNFO32/64 - Download

In the pics is what you should see on clicking the site open and what to choose in bit version and then go to the bottom and find the downloader you want open it out and choose the US version - I always use this link on any machine I install this valuable tool on

Yep that's the exactly what I did and the exact program that I downloaded. I just don't have that option to select sensors like you did; I did however select "sensors only option" when running the the program. In the screenshots I've enclosed in this post, I've included everything that my HW info program is displaying for me. I'm guessing what your after just has to be in there somewhere! lol

 

[ICIT2LOL]

That is odd mate but however I have snipped and marked the section that you need the title is marked in red (motherboard) the rails in blue and the Vbat ref I kept on about in black (CMOS / BIOS battery).

From those readouts you can see a lot of other useful info ie CPU temps the average rails volts core frequencies RAM usage etc etc a lot of info that you can use for diagnosing for example so in all a very useful tool.

What I shall do is to uninstall mine and reinstall it to see if I get the same problem that you are having if I do then I shall ask in the HW Info forum I belong to find an answer but even so I might just ask anyway

 

[aussiepride]

That is odd mate but however I have snipped and marked the section that you need the title is marked in red (motherboard) the rails in blue and the Vbat ref I kept on about in black (CMOS / BIOS battery).

From those readouts you can see a lot of other useful info ie CPU temps the average rails volts core frequencies RAM usage etc etc a lot of info that you can use for diagnosing for example so in all a very useful tool.

What I shall do is to uninstall mine and reinstall it to see if I get the same problem that you are having if I do then I shall ask in the HW Info forum I belong to find an answer but even so I might just ask anyway

No problems! How did you go with it?

 

[ICIT2LOL]

No problems mate I even went into the registry in CURRENT USER and found the leftover reg entry for HW Info and deleted that. Now I ma thinking maybe it might have been a crooked install install and that it would be worth trying the install again.

While I am thinking of it that is something I always check out after uninstalling softwares as many like some of the AV programs and Norton (Symantec) is a classic - leave registry entries in both CURRENT USER & LOCAL MACHINE > Software even when - and I suspect - those remover tools are mean to deliberately do that but it may be me being paranoid and cynical

 

[aussiepride]

No problems mate I even went into the registry in CURRENT USER and found the leftover reg entry for HW Info and deleted that. Now I ma thinking maybe it might have been a crooked install install and that it would be worth trying the install again.

While I am thinking of it that is something I always check out after uninstalling softwares as many like some of the AV programs and Norton (Symantec) is a classic - leave registry entries in both CURRENT USER & LOCAL MACHINE > Software even when - and I suspect - those remover tools are mean to deliberately do that but it may be me being paranoid and cynical

Its funny you say that because I already have tried uninstalling and reinstalling the program. In any case, do you think that this program is likely to reveal the main cause of my BSOD problem?

 

[ICIT2LOL]

No mate absolutely not I use it to track down hardware problems ie testing out the voltage rails in desktop PSU's and laptop battery status as (for example ) power supplies are very overlooked as a source of computer problems. So in addition to that one can see the very detailed info on RAM sticks hard drives network adaptors GPU' s etc etc
It is in other words an excellent tool for trying to find faults within those dedicated components.

ie you can see what the normal operating functions are in say a RAM stick and then also see what it is operating at now again for example the frequencies being put through them.

When you look at BSOD's again for example the faults can be soft or hardware based and have so many different interactions between the two basic form of "wares" it sorta makes you spin out thinking about them

 

[aussiepride]

No mate absolutely not I use it to track down hardware problems ie testing out the voltage rails in desktop PSU's and laptop battery status as (for example ) power supplies are very overlooked as a source of computer problems. So in addition to that one can see the very detailed info on RAM sticks hard drives network adaptors GPU' s etc etc
It is in other words an excellent tool for trying to find faults within those dedicated components.

ie you can see what the normal operating functions are in say a RAM stick and then also see what it is operating at now again for example the frequencies being put through them.

When you look at BSOD's again for example the faults can be soft or hardware based and have so many different interactions between the two basic form of "wares" it sorta makes you spin out thinking about them

oh I get you now! Ok so whats the next step and where to from here? Would you like me to try uninstalling and reinstalling that program again?

 

[ICIT2LOL]

Yep takes no time at all - as for where we head next will have to trawl backthrough and see where we have been already.

Now I do remember there was a reference to ntoskrnl.exe and that is related to just about anything including updates so will just have to plod through the hardware stuff first. If I get stuck then we can always ask for help.