BSoD when coming out of sleep or undocking


  1. DeaconFrost
    Posts : 5,795
    Windows 7 Ultimate x64 SP1
       New #1

    BSoD when coming out of sleep or undocking


    A user of mine is telling me she gets a BSoD often when she wakes up her laptop from sleep, or if she tries to undock it. My free tools for analyzing the dump file aren't giving me anything useful, so I figured I'd post it here in case someone with better tools would give it a shot.

    Thanks!
      My Computer
    Quote Quote

  3. z3r010
    Posts : 51,479
    Windows 11 Workstation x64
       New #2

    I've just had a quick look and the dump is blaming memory corruption, it would be worth doing some memory tests while you wait for the BSOD folks to take a good look at the dump.

    RAM - Test with Memtest86+

    Code:
    *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {c0415e08, c0000185, 46c58860, 82bc15f3}

GetPointerFromAddress: unable to read from 82b74830
Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0415e08, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 46c58860, current process (virtual address for lock type 3, or PTE)
Arg4: 82bc15f3, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

Debugging Details:
------------------


ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  8ab13b88 -- (.trap 0xffffffff8ab13b88)
ErrCode = 00000010
eax=8ab13c20 ebx=00000000 ecx=8ab13c6c edx=82a46bcd esi=00000002 edi=00000002
eip=82bc15f3 esp=8ab13bfc ebp=8ab13c64 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt!EtwWriteStartScenario:
82bc15f3 0000            add     byte ptr [eax],al          ds:0023:8ab13c20=5c
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82aaedd8 to 82ae9e9c

STACK_TEXT:  
8ab139ec 82aaedd8 0000007a c0415e08 c0000185 nt!KeBugCheckEx+0x1e
8ab13a5c 82ab26b9 8ab13ab0 82b75300 8ab13ad0 nt!MiWaitForInPageComplete+0x302
8ab13aec 82a9b91b 82b75300 82bc15f3 84bb97b0 nt!MiIssueHardFault+0x3b3
8ab13b70 82a4c468 00000008 82bc15f3 00000000 nt!MmAccessFault+0x2656
8ab13b70 82bc15f3 00000008 82bc15f3 00000000 nt!KiTrap0E+0xdc
8ab13c64 82c9b43d 00000000 00000004 00000002 nt!EtwWriteStartScenario
8ab13cac 82c9b72f 00000000 00000002 00000004 nt!PopIssueActionRequest+0x187
8ab13ce8 82ad10de 82b4d060 848c1a70 82b463bc nt!PopPolicyWorkerAction+0x45
8ab13d00 82a88a6b 00000000 00000000 848c1a70 nt!PopPolicyWorkerThread+0x64
8ab13d50 82c14056 00000001 aa35f07d 00000000 nt!ExpWorkerThread+0x10d
8ab13d90 82abc1a9 82a8895e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    82bc1001-82bc105e  94 bytes - nt!SmQueryStoreInformation+178
    [ 90 90 90 90 90 8b ff 55:00 00 00 00 00 00 00 00 ]
    82bc1060-82bc106f  16 bytes - nt!WdipSemQueryScenarioTable+5a (+0x5f)
    [ 90 90 90 90 90 8b ff 55:00 00 00 00 00 00 00 00 ]
    82bc1072-82bc107c  11 bytes - nt!WdipSemEnableScenario+d (+0x12)
    [ 53 56 57 33 f6 33 ff 66:00 00 00 00 00 00 00 00 ]
    82bc1080-82bc1082  3 bytes - nt!WdipSemEnableScenario+1b (+0x0e)
    [ c6 45 ff:00 00 00 ]
    82bc1084-82bc10a7  36 bytes - nt!WdipSemEnableScenario+1f (+0x04)
    [ 6a 11 bb 64 b5 b4 82 59:00 00 00 00 00 00 00 00 ]
    82bc10aa-82bc10d6  45 bytes - nt!WdipSemEnableScenario+45 (+0x26)
    [ c0 be a8 66 a5 82 56 ff:00 00 00 00 00 00 00 00 ]
    82bc10d8-82bc10de  7 bytes - nt!WdipSemEnableScenario+73 (+0x2e)
    [ 85 ff 74 05 e8 76 30:00 00 00 00 00 00 00 ]
    82bc10e1-82bc10f1  17 bytes - nt!WdipSemEnableScenario+7c (+0x09)
    [ 8b 0d 64 b5 b4 82 8b c1:00 00 00 00 00 00 00 00 ]
    82bc10f5-82bc10f9  5 bytes - nt!WdipSemEnableScenario+90 (+0x14)
    [ 8d 41 f0 e9 84:00 00 00 00 00 ]
    82bc10fd-82bc1107  11 bytes - nt!WdipSemEnableScenario+98 (+0x08)
    [ 39 75 10 74 a2 80 3d 28:00 00 00 00 00 00 00 00 ]
    82bc1109-82bc110e  6 bytes - nt!WdipSemEnableScenario+a4 (+0x0c)
    [ 75 09 c7 45 f8 01:00 00 00 00 00 00 ]
    82bc1111-82bc1116  6 bytes - nt!WdipSemEnableScenario+ac (+0x08)
    [ c0 eb 97 e8 a2 1d:00 00 00 00 00 00 ]
    82bc1119-82bc113b  35 bytes - nt!WdipSemEnableScenario+b4 (+0x08)
    [ 3b c6 89 45 f8 7d 06 c6:00 00 00 00 00 00 00 00 ]
    82bc113e-82bc1146  9 bytes - nt!WdipSemEnableScenario+d9 (+0x25)
    [ 8b f8 3b fe 74 c7 e8 bd:00 00 00 00 00 00 00 00 ]
    82bc1149-82bc1171  41 bytes - nt!WdipSemEnableScenario+e4 (+0x0b)
    [ 39 75 f8 0f 8c 59 ff ff:00 00 00 00 00 00 00 00 ]
    82bc1174-82bc1176  3 bytes - nt!WdipSemEnableScenario+10f (+0x2b)
    [ 57 e8 f2:00 00 00 ]
    82bc117a-82bc119f  38 bytes - nt!WdipSemEnableScenario+115 (+0x06)
    [ e9 62 ff ff ff 33 c0 f6:00 00 00 00 00 00 00 00 ]
    82bc11a2-82bc11a4  3 bytes - nt!WdipSemEnableScenario+13d (+0x28)
    [ 8d 81 84:00 00 00 ]
    82bc11a8-82bc11a9  2 bytes - nt!WdipSemEnableScenario+143 (+0x06)
    [ 66 ff:00 00 ]
    82bc11ab-82bc11ac  2 bytes - nt!WdipSemEnableScenario+146 (+0x03)
    [ 0f b7:00 00 ]
    82bc11ae-82bc11b6  9 bytes - nt!WdipSemEnableScenario+149 (+0x03)
    [ 66 85 c0 75 16 8d 41 40:00 00 00 00 00 00 00 00 ]
    82bc11b8-82bc11bd  6 bytes - nt!WdipSemEnableScenario+153 (+0x0a)
    [ 74 0f 66 83 b9 86:00 00 00 00 00 00 ]
    82bc11c2-82bc11c4  3 bytes - nt!WdipSemEnableScenario+15d (+0x0a)
    [ 75 05 e8:00 00 00 ]
    82bc11c6-82bc11cb  6 bytes - nt!WdipSemEnableScenario+161 (+0x04)
    [ 23 e7 ff 80 7d ff:00 00 00 00 00 00 ]
    82bc11cd-82bc11cf  3 bytes - nt!WdipSemEnableScenario+168 (+0x07)
    [ 0f 84 8a:00 00 00 ]
    82bc11d3-82bc11d6  4 bytes - nt!WdipSemEnableScenario+16e (+0x06)
    [ 64 a1 24 01:00 00 00 00 ]
    82bc11d9-82bc11dc  4 bytes - nt!WdipSemEnableScenario+174 (+0x06)
    [ 66 ff 88 84:00 00 00 00 ]
    82bc11e0-82bc11e5  6 bytes - nt!WdipSemEnableScenario+17b (+0x07)
    [ 8b c3 f0 0f ba 28:00 00 00 00 00 00 ]
    82bc11e7-82bc11f5  15 bytes - nt!WdipSemEnableScenario+182 (+0x07)
    [ 73 07 8b cb e8 36 c9 ed:00 00 00 00 00 00 00 00 ]
    82bc11f7-82bc11fc  6 bytes - nt!WdipSemEnableScenario+192 (+0x10)
    [ 74 05 e8 f9 66 14:00 00 00 00 00 00 ]
    82bc11fe-82bc1233  54 bytes - nt!WdipSemEnableScenario+199 (+0x07)
    [ 8b 0d 64 b5 b4 82 8b c1:00 00 00 00 00 00 00 00 ]
    82bc1236-82bc1238  3 bytes - nt!WdipSemEnableScenario+1d1 (+0x38)
    [ 8d 81 84:00 00 00 ]
    82bc123c-82bc123d  2 bytes - nt!WdipSemEnableScenario+1d7 (+0x06)
    [ 66 ff:00 00 ]
    82bc123f-82bc1240  2 bytes - nt!WdipSemEnableScenario+1da (+0x03)
    [ 0f b7:00 00 ]
    82bc1242-82bc124a  9 bytes - nt!WdipSemEnableScenario+1dd (+0x03)
    [ 66 85 c0 75 16 8d 41 40:00 00 00 00 00 00 00 00 ]
    82bc124c-82bc1251  6 bytes - nt!WdipSemEnableScenario+1e7 (+0x0a)
    [ 74 0f 66 83 b9 86:00 00 00 00 00 00 ]
    82bc1256-82bc1265  16 bytes - nt!WdipSemEnableScenario+1f1 (+0x0a)
    [ 75 05 e8 6c 22 e7 ff 8b:00 00 00 00 00 00 00 00 ]
    82bc1267-82bc1274  14 bytes - nt!WdipSemEnableScenario+202 (+0x11)
    [ 90 90 90 90 90 8b ff 55:00 00 00 00 00 00 00 00 ]
    82bc1277-82bc127a  4 bytes - nt!WdipSemActivateInstance+b (+0x10)
    [ 66 ff 88 84:00 00 00 00 ]
    82bc127e-82bc128a  13 bytes - nt!WdipSemActivateInstance+12 (+0x07)
    [ 56 57 be 7c b5 b4 82 8b:00 00 00 00 00 00 00 00 ]
    82bc128c-82bc129a  15 bytes - nt!WdipSemActivateInstance+20 (+0x0e)
    [ 73 07 8b ce e8 91 c8 ed:00 00 00 00 00 00 00 00 ]
    82bc129c-82bc12d1  54 bytes - nt!WdipSemActivateInstance+30 (+0x10)
    [ 8b 0d 7c b5 b4 82 8b c1:00 00 00 00 00 00 00 00 ]
    82bc12d4-82bc12d6  3 bytes - nt!WdipSemActivateInstance+68 (+0x38)
    [ 8d 81 84:00 00 00 ]
    82bc12da-82bc12db  2 bytes - nt!WdipSemActivateInstance+6e (+0x06)
    [ 66 ff:00 00 ]
    82bc12dd-82bc12de  2 bytes - nt!WdipSemActivateInstance+71 (+0x03)
    [ 0f b7:00 00 ]
    82bc12e0-82bc12e8  9 bytes - nt!WdipSemActivateInstance+74 (+0x03)
    [ 66 85 c0 75 16 8d 41 40:00 00 00 00 00 00 00 00 ]
    82bc12ea-82bc12ef  6 bytes - nt!WdipSemActivateInstance+7e (+0x0a)
    [ 74 0f 66 83 b9 86:00 00 00 00 00 00 ]
    82bc12f4-82bc12ff  12 bytes - nt!WdipSemActivateInstance+88 (+0x0a)
    [ 75 05 e8 ce 21 e7 ff 5f:00 00 00 00 00 00 00 00 ]
    82bc1301-82bc1318  24 bytes - nt!WdipSemActivateInstance+95 (+0x0d)
    [ 90 90 90 90 90 8b ff 55:00 00 00 00 00 00 00 00 ]
    82bc131a-82bc131c  3 bytes - nt!WdipSemEnableContextProviders+14 (+0x19)
    [ 83 7e 28:00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3749 errors : !nt (82bc1001-82bc1fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
      My Computers
    Quote Quote

  4. DeaconFrost
    Posts : 5,795
    Windows 7 Ultimate x64 SP1
    Thread Starter
       New #3

    Hmmm...could very well be possible. I searched for the error code and saw common suggestions to check the HDD, which I did and found no issues. I also ran several malware scans that came up clean.
      My Computer
    Quote Quote

  6. richc46
    Posts : 17,796
    Windows 10, Home Clean Install
       New #4

    Hi
    As John pointed out that one dmp points to memory; it also suggests an I/O error, which is input, output, which can suggest many things, but its usually the Hard Drive. As you mentioned you took a hard drive test. I do not know what you did but the most accurate would be the test that is given by your hard drive manufacurer, which can be taken from the website. Most computers have self diagnostic tests, which can be done right from the computer, check the manual for how this is done the information is probably online, too. If you did the chkdsk test, thats worthless.
    In addition regarless of what that one dmp says, one dmp is never enough.
    When you get more post and we will have more clues
    Until then
    Take memtest, as suggested.Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
    If one dmp were definitive, this is a definite point toward hardware; memory is hardware and I/O technically means input/output problem due to hardware.
    Post any additional BSODS, to give us more clues.
    Last edited by richc46; 28 Sep 2012 at 16:00.
      My Computer
    Quote Quote

 

  Related Discussions
BSOD coming off of sleep
in BSOD Help and Support

The windows system is less than a year old and it was a full retail pro 64bit windows 7 if you have any questions about the system feel free to ask.
BSoD when coming out of sleep
in BSOD Help and Support

I keep getting BSoD when my computer comes out of sleep. This started after I did some over clocking. It's a x64 win7 OS on a top of the line system. Thanks in advance!
BSOD coming out of sleep
in BSOD Help and Support

Hi all, I just put together a new computer this weekend. Specs are below. It appeared to be fine when gaming and browsing the internet. However it soon started to BSOD. It would do this when loading Youtube. I traced this to an apparent problem between ATI drivers and Flash. Changing...
Bsod When coming out of sleep
in BSOD Help and Support

Whenever i come out of sleep mode i get a bsod, i have win 7 pro on a toshiba l350, any ideas their is nothing glaringly obvious in the windows device manager cheers for ur help
BSOD when coming out of sleep!
in BSOD Help and Support

I recently did a clean install of Windows 7 Professional and EVERY time I put the computer to sleep it crashes with coming back. Any ideas on what it could be? I'm not completely computer illiterate, but I don't know much about finding error codes and what not. This is pretty annoying but at...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 08:07.
Find Us