Waking From Sleep Problem

Discussion in 'Windows 7 Help and Support' started by Turnitdown, May 25, 2010.

  1. Turnitdown

    Turnitdown New Member

    Joined:
    May 25, 2010
    Messages:
    8
    Likes Received:
    0
    Hey

    Just installed W7 on my new build.
    Everythings working perfectly apart from Sleep mode.

    As soon as I wake the computer from sleep the USB devices stop working after 40 seconds of coming back from sleep and then I get BSOD. I have no idea why this is happening.
    The devices still get power but for example the mouse and keyboard no longer work.

    Has anyone got a fix for this?
    Its really bugging me.
     
  2. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Welcome to the forums.

    Some of your device drivers may conflict and may need to be updated. Make sure to get system updates as well. Attach you crash dumps if possible.
     
  3. Turnitdown

    Turnitdown New Member

    Joined:
    May 25, 2010
    Messages:
    8
    Likes Received:
    0
    Thanks for the reply.
    I've got all system updates. Drivers will be the problem then.
    Could you tell me where to find the crash dump files and where to upload them to.

    Thank you so much :)
     
  4. Turnitdown

    Turnitdown New Member

    Joined:
    May 25, 2010
    Messages:
    8
    Likes Received:
    0
    Attached the minidump file :)
     

    Attached Files:

  5. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    1. Test your RAM (Memtest86+ - Advanced Memory Diagnostic Tool)
    2. Update your drivers






























    Your minidumps read:


    Code:
    052310-17955-01.dmp
    
    
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DD\AA\Minidump\052310-17955-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c5ae50
    Debug session time: Sun May 23 19:26:10.499 2010 (GMT+3)
    System Uptime: 0 days 7:45:04.383
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {44428c40694d, 2, 0, fffff80002b3fa8f}
    
    Probably caused by : memory_corruption ( nt!MiIdentifyPfn+23f )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 000044428c40694d, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002b3fa8f, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc50e0
     000044428c40694d 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!MiIdentifyPfn+23f
    fffff800`02b3fa8f 4c8b7500        mov     r14,qword ptr [rbp]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  svchost.exe
    
    TRAP_FRAME:  fffff880077db4b0 -- (.trap 0xfffff880077db4b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000005 rbx=0000000000000000 rcx=0600000000000020
    rdx=000000000002aaaa rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002b3fa8f rsp=fffff880077db640 rbp=000044428c40694d
     r8=000000000002aab2  r9=0000000000000001 r10=0000000000000042
    r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!MiIdentifyPfn+0x23f:
    fffff800`02b3fa8f 4c8b7500        mov     r14,qword ptr [rbp] ss:0018:00004442`8c40694d=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a8e469 to fffff80002a8ef00
    
    STACK_TEXT:  
    fffff880`077db368 fffff800`02a8e469 : 00000000`0000000a 00004442`8c40694d 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`077db370 fffff800`02a8d0e0 : 00000000`42506650 0a050a04`39080411 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`077db4b0 fffff800`02b3fa8f : 00000000`00000000 02000000`00117bcb 00000000`000018c0 fffff800`02d53c8f : nt!KiPageFault+0x260
    fffff880`077db640 fffff800`02b4076b : 00000000`00000000 00000000`00000004 fffffa80`049b0778 fffffa80`049b0000 : nt!MiIdentifyPfn+0x23f
    fffff880`077db6e0 fffff800`02ea00f5 : fffffa80`049b0000 fffff880`077dbc60 fffff880`077db7b8 00000000`00000000 : nt!MmQueryPfnList+0xbb
    fffff880`077db720 fffff800`02de4f78 : 00000000`00000006 00000000`00000000 fffffa80`049b0000 fffff800`02a1d001 : nt!PfpPfnPrioRequest+0x115
    fffff880`077db770 fffff800`02d89cb3 : 00000000`00000000 fffff800`02a1d000 fffffa80`06098000 00000000`00000201 : nt! ?? ::NNGAKEGL::`string'+0x4853d
    fffff880`077db800 fffff800`02d8ae49 : 00000000`01a1bb68 00000000`00000001 00000000`01a1bbc0 00000000`02f68f08 : nt!ExpQuerySystemInformation+0x11c2
    fffff880`077dbba0 fffff800`02a8e153 : 00000000`00000000 00000000`02f9f4e0 00000000`02f9f401 00000000`01a1c8c0 : nt!NtQuerySystemInformation+0x4d
    fffff880`077dbbe0 00000000`77c2021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`01a1ba98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77c2021a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiIdentifyPfn+23f
    fffff800`02b3fa8f 4c8b7500        mov     r14,qword ptr [rbp]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  nt!MiIdentifyPfn+23f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+23f
    
    BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+23f
    
    Followup: MachineOwner
    ---------
    
    ---------------------------------------------
    ---------------------------------------------
    
    
    
    
    
    
    
    052310-21122-01.dmp
    
    
    
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DD\AA\Minidump\052310-21122-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
    Debug session time: Mon May 24 00:51:44.752 2010 (GMT+3)
    System Uptime: 0 days 0:13:46.012
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................
    Loading User Symbols
    Loading unloaded module list
    .............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff80002a9aa5f, 0, ffffffffffffffff}
    
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002a9aa5f, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
    
    FAULTING_IP: 
    nt!MiReplenishPageSlist+100
    fffff800`02a9aa5f f00fba6b1000    lock bts dword ptr [rbx+10h],0
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cad0e0
     ffffffffffffffff 
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  dinotify.exe
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff88004f1d5d8 -- (.exr 0xfffff88004f1d5d8)
    ExceptionAddress: fffff80002a9aa5f (nt!MiReplenishPageSlist+0x0000000000000100)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff88004f1d680 -- (.trap 0xfffff88004f1d680)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8000000000 rbx=0000000000000000 rcx=fdffffffffffffff
    rdx=000000000000004f rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a9aa5f rsp=fffff88004f1d810 rbp=fffffa8004200708
     r8=fffff80002caf400  r9=fffffa8004200000 r10=fffffa8004200728
    r11=fffff88004f1d868 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!MiReplenishPageSlist+0x100:
    fffff800`02a9aa5f f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:f000:00000000`00000010=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002aaf929 to fffff80002a75600
    
    STACK_TEXT:  
    fffff880`04f1ce08 fffff800`02aaf929 : 00000000`0000001e ffffffff`c0000005 fffff800`02a9aa5f 00000000`00000000 : nt!KeBugCheckEx
    fffff880`04f1ce10 fffff800`02a74c42 : fffff880`04f1d5d8 fffef280`00000000 fffff880`04f1d680 00000000`0000000b : nt!KiDispatchException+0x1b9
    fffff880`04f1d4a0 fffff800`02a7354a : fffffa80`07587a18 fffffa80`07587800 fffffa80`00000104 00000000`001ca000 : nt!KiExceptionDispatch+0xc2
    fffff880`04f1d680 fffff800`02a9aa5f : fffff880`00001000 fffff880`00000104 fffffa80`057919f0 00000000`0009bc00 : nt!KiGeneralProtectionFault+0x10a
    fffff880`04f1d810 fffff800`02a9af8f : fffff800`02caf400 00000000`0000002d fffffa80`00868470 fffffa80`00806070 : nt!MiReplenishPageSlist+0x100
    fffff880`04f1d870 fffff800`02a93197 : 00000000`00000002 fffff880`00000002 fffffa80`07587b98 00000000`00000002 : nt!MiRemoveAnyPage+0x24f
    fffff880`04f1d990 fffff800`02a8f8a6 : 00000000`00000001 00000000`00306000 fffff880`04f1dbe0 fffff680`00001830 : nt!MiResolveDemandZeroFault+0x577
    fffff880`04f1da80 fffff800`02a736ee : 00000000`00000001 00000000`00000000 00000000`77b93501 fffffa80`00000000 : nt!MmAccessFault+0x5c6
    fffff880`04f1dbe0 00000000`77ab1afe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`001cd268 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ab1afe
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReplenishPageSlist+100
    fffff800`02a9aa5f f00fba6b1000    lock bts dword ptr [rbx+10h],0
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nt!MiReplenishPageSlist+100
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100
    
    BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100
    
    Followup: MachineOwner
    ---------
    
    ------------------------------------
    ------------------------------------
    
    
    
    
    
    
    
    
    052410-17191-01.dmp
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DD\AA\Minidump\052410-17191-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02a1f000 PsLoadedModuleList = 0xfffff800`02c5ce50
    Debug session time: Mon May 24 09:59:14.596 2010 (GMT+3)
    System Uptime: 0 days 0:27:45.075
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff80002ab4a5f, 0, ffffffffffffffff}
    
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002ab4a5f, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
    
    FAULTING_IP: 
    nt!MiReplenishPageSlist+100
    fffff800`02ab4a5f f00fba6b1000    lock bts dword ptr [rbx+10h],0
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc70e0
     ffffffffffffffff 
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff88009c386c8 -- (.exr 0xfffff88009c386c8)
    ExceptionAddress: fffff80002ab4a5f (nt!MiReplenishPageSlist+0x0000000000000100)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff88009c38770 -- (.trap 0xfffff88009c38770)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8000000000 rbx=0000000000000000 rcx=fdffffffffffffff
    rdx=000000000000004f rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002ab4a5f rsp=fffff88009c38900 rbp=fffffa80042003c0
     r8=fffff80002cc9400  r9=fffffa8004200000 r10=fffffa80042003e0
    r11=fffff88009c38958 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!MiReplenishPageSlist+0x100:
    fffff800`02ab4a5f f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ac9929 to fffff80002a8f600
    
    STACK_TEXT:  
    fffff880`09c37ef8 fffff800`02ac9929 : 00000000`0000001e ffffffff`c0000005 fffff800`02ab4a5f 00000000`00000000 : nt!KeBugCheckEx
    fffff880`09c37f00 fffff800`02a8ec42 : fffff880`09c386c8 fffef280`00000000 fffff880`09c38770 00000000`0000000b : nt!KiDispatchException+0x1b9
    fffff880`09c38590 fffff800`02a8d54a : 00000000`00000006 00000000`00000000 fffff800`02bc4205 fffff800`02a9b202 : nt!KiExceptionDispatch+0xc2
    fffff880`09c38770 fffff800`02ab4a5f : 00000ecf`000000c8 00000000`6d646156 00000000`00000000 fffff960`00094db4 : nt!KiGeneralProtectionFault+0x10a
    fffff880`09c38900 fffff800`02ab4f8f : fffff800`02cc9400 00000000`00000018 fffffa80`003ff480 fffffa80`00410880 : nt!MiReplenishPageSlist+0x100
    fffff880`09c38960 fffff800`02aaa97a : fffff680`000290a8 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
    fffff880`09c38a80 fffff800`02a8d6ee : 00000000`00000001 00000000`0000001a 00000000`00000001 fffffa80`071f68f0 : nt!MmAccessFault+0x169a
    fffff880`09c38be0 00000000`6bd737ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0030e990 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6bd737ed
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReplenishPageSlist+100
    fffff800`02ab4a5f f00fba6b1000    lock bts dword ptr [rbx+10h],0
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nt!MiReplenishPageSlist+100
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100
    
    BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100
    
    Followup: MachineOwner
    ---------
    
    ------------------------------------
    ------------------------------------
    
    
    
    
    
    052510-16863-01.dmp
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\DD\AA\Minidump\052510-16863-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
    Machine Name:
    Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c4ce50
    Debug session time: Wed May 26 01:10:41.410 2010 (GMT+3)
    System Uptime: 0 days 6:15:37.361
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000005, fffff80002aa4a5f, 0, ffffffffffffffff}
    
    Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002aa4a5f, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
    
    FAULTING_IP: 
    nt!MiReplenishPageSlist+100
    fffff800`02aa4a5f f00fba6b1000    lock bts dword ptr [rbx+10h],0
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb70e0
     ffffffffffffffff 
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  2
    
    EXCEPTION_RECORD:  fffff8800828d6c8 -- (.exr 0xfffff8800828d6c8)
    ExceptionAddress: fffff80002aa4a5f (nt!MiReplenishPageSlist+0x0000000000000100)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff
    
    TRAP_FRAME:  fffff8800828d770 -- (.trap 0xfffff8800828d770)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8000000000 rbx=0000000000000000 rcx=fdffffffffffffff
    rdx=000000000000004f rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002aa4a5f rsp=fffff8800828d900 rbp=fffffa80042006e0
     r8=fffff80002cb9400  r9=fffffa8004200000 r10=fffffa8004200700
    r11=fffff8800828d958 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na pe nc
    nt!MiReplenishPageSlist+0x100:
    fffff800`02aa4a5f f00fba6b1000    lock bts dword ptr [rbx+10h],0 ds:00000000`00000010=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ab9929 to fffff80002a7f600
    
    STACK_TEXT:  
    fffff880`0828cef8 fffff800`02ab9929 : 00000000`0000001e ffffffff`c0000005 fffff800`02aa4a5f 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0828cf00 fffff800`02a7ec42 : fffff880`0828d6c8 fffef280`00000000 fffff880`0828d770 00000000`00000008 : nt!KiDispatchException+0x1b9
    fffff880`0828d590 fffff800`02a7d54a : fffffa80`0400a1f0 fffff880`0828d7f0 00000000`00000009 00000000`00000006 : nt!KiExceptionDispatch+0xc2
    fffff880`0828d770 fffff800`02aa4a5f : 00000980`00000000 fffffa80`04201480 fffff880`0828dbe0 00000000`0019de20 : nt!KiGeneralProtectionFault+0x10a
    fffff880`0828d900 fffff800`02aa4f8f : fffff800`02cb9400 00000000`0000002c fffffa80`01380840 fffffa80`03c91440 : nt!MiReplenishPageSlist+0x100
    fffff880`0828d960 fffff800`02a9a97a : fffff680`0003f780 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x24f
    fffff880`0828da80 fffff800`02a7d6ee : 00000000`00000001 00000000`00000030 fffff880`0828db01 fffffa80`04d18e60 : nt!MmAccessFault+0x169a
    fffff880`0828dbe0 00000000`68d037dd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`0040e7f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x68d037dd
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiReplenishPageSlist+100
    fffff800`02aa4a5f f00fba6b1000    lock bts dword ptr [rbx+10h],0
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nt!MiReplenishPageSlist+100
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100
    
    BUCKET_ID:  X64_0x1E_nt!MiReplenishPageSlist+100
    
    Followup: MachineOwner
    ---------
    
    
    
     
  6. Turnitdown

    Turnitdown New Member

    Joined:
    May 25, 2010
    Messages:
    8
    Likes Received:
    0
    Just finished the memtest.
    No errors were found on it.

    [​IMG]

    The problem is still happening though.

    Sorry if this is a silly question. But what drivers do you mean I should update?
     
  7. Chrisboy

    Chrisboy New Member

    Joined:
    May 27, 2010
    Messages:
    14
    Likes Received:
    4

Share This Page

Loading...