BSOD everytime after sleeping.


  1. Posts : 18
    Windows 7 Ultimate x64
       #1

    BSOD everytime after sleeping.


    Hi guys,

    I am having a problem with my computer BSODing everytime I resume it from sleep.

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 1e
    BCP1: FFFFFFFFC0000046
    BCP2: FFFFF80001EC8B80
    BCP3: 0000000000000000
    BCP4: FFFFFA800771C5A0
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\111312-18876-01.dmp
    C:\Users\Tom\AppData\Local\Temp\WER-20966-0.sysdata.xml

    I have uploaded the .dmp file for you to view here - http://puu.sh/1pW6R

    Really hope someone can help me out, as this is turning into a real nightmare!
    I'm not sure if it's related but I now frequently hear something crackling/ticking inside my computer, particularly when it's under some sort of load. Could it be a PSU problem? I recently moved house so I wonder if something got knocked.

    Your help will be much appreciated, cheers in advance.
    Tom
      My Computer


  2. Posts : 18
    Windows 7 Ultimate x64
    Thread Starter
       #2

    In my haste I didn't read the BSOD - Posting Instructions, so I missed the SF logs. Please find them attached below:
      My Computer


  3. Posts : 18
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Bump
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    It is causwd by Etron USB 3.0 Extensible Host Controller Driver.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1E, {ffffffffc0000046, fffff80001ec8b80, 0, fffffa800771c5a0}
    
    *** WARNING: Unable to verify timestamp for EtronXHCI.sys
    *** ERROR: Module load completed but symbols could not be loaded for EtronXHCI.sys
    Probably caused by : EtronXHCI.sys ( EtronXHCI+e656 )
    
    Followup: MachineOwner
    ---------
    Update it from Etron Technology Inc..
    For the port, first, uninstall and reinstall the USB ports drivers.

    1. Right click on Computer icon > manage. It will open the computer management window.
    2. Click on "Device Manager" in the left pane, it will list all installed devices up.
    3. Expand "USB Serial Bus Controllers" by clicking on the triangle in front of it.
    4. Click on one item to select, then right click and uninstall.
    5. Do the same for all.
    6. Restart the computer.
    7. At restart, windows will auto configure the appropriate drivers.

    And, Disable USB Selective Suspense too.
    USB Selective Suspend - Turn On or Off

    For the devices, first, detach all the USB devices other than the keyboard and mouse.
    Then, Update the drivers for them all, including the keyboard and mouse, if any third party drivers are installed for them.

    As a caution, do it:
    ► 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, per RAM module per slot.

    Let us know the results.
      My Computer


  5. Posts : 18
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Thanks for your response Arc.

    So I uninstalled all the Etron USB Controllers, like you explained above.

    I then disabled USB Selective Suspense.

    Restarted twice, and still getting the same problem.

    Attached new logs.
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {0, 2, 1, fffffa8000000000}
    
    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffffa8000000000, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800020b8100
    GetUlongFromAddress: unable to read from fffff800020b81c0
     0000000000000000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    +0
    fffffa80`00000000 0000            add     byte ptr [rax],al
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TAG_NOT_DEFINED_c000000f:  FFFFF800037FFFB0
    
    TRAP_FRAME:  fffff800037ff890 -- (.trap 0xfffff800037ff890)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff800037ff9e0
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffffa8000000000 rsp=fffff800037ffa20 rbp=fffff800037ffaa0
     r8=0000000000000000  r9=0000000000000000 r10=0000000000007800
    r11=fffffa80070b60a0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    fffffa80`00000000 0000            add     byte ptr [rax],al ds:00000000`00000000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80001e88569 to fffff80001e88fc0
    
    STACK_TEXT:  
    fffff800`037ff748 fffff800`01e88569 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff800`037ff750 fffff800`01e871e0 : fffffa80`0c19cb50 fffff800`01e8c387 00000000`0968ade5 fffffa80`00000001 : nt!KiBugCheckDispatch+0x69
    fffff800`037ff890 fffffa80`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
    fffff800`037ffa20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000007 : 0xfffffa80`00000000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!KiPageFault+260
    fffff800`01e871e0 440f20c0        mov     rax,cr8
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiPageFault+260
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
    
    FAILURE_BUCKET_ID:  X64_0xD1_nt!KiPageFault+260
    
    BUCKET_ID:  X64_0xD1_nt!KiPageFault+260
    
    Followup: MachineOwner
    ---------
    In such a situation, 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.

    Also, 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, per RAM module per slot.

    Let us know the results, with the subsequent crash dumps, if any.
      My Computer


  7. Posts : 18
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Hi Arc,

    Thanks for your help. Problem is sorted now.

    I deleted, and then reinstalled the Etron drivers/controllers, but the problem carried on.

    I have now moved all my USB's to the USB 2.0 slots instead, and it's fixed my problem. Not the best case scenario but certainly alot better.

    Cheers for all your help, much appreciated!
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    Well done, best of luck :)
      My Computer


 

  Related Discussions
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 18:17.
Find Us