BSOD on start up, Error 1000007e

Page 3 of 3 FirstFirst 123

  1. Posts : 15,026
    Windows 10 Home 64Bit
       #21

    Seemed to have crashed on Etron USB 3.0 Extensible Host Controller Driver. Try updating its drivers.
    Code:
    *** WARNING: Unable to verify timestamp for EtronXHCI.sys
    *** ERROR: Module load completed but symbols could not be loaded for EtronXHCI.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff88005363db1, fffff880031943d8, fffff88003193c30}
    
    Probably caused by : EtronXHCI.sys ( EtronXHCI+9db1 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88005363db1, The address that the exception occurred at
    Arg3: fffff880031943d8, Exception Record Address
    Arg4: fffff88003193c30, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    EtronXHCI+9db1
    fffff880`05363db1 8b8174400000    mov     eax,dword ptr [rcx+4074h]
    
    EXCEPTION_RECORD:  fffff880031943d8 -- (.exr 0xfffff880031943d8)
    ExceptionAddress: fffff88005363db1 (EtronXHCI+0x0000000000009db1)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000004074
    Attempt to read from address 0000000000004074
    
    CONTEXT:  fffff88003193c30 -- (.cxr 0xfffff88003193c30)
    rax=0000000000000001 rbx=fffffa800ebc8000 rcx=0000000000000000
    rdx=fffff88000e1c001 rsi=0000000000000002 rdi=fffffa800ea5b500
    rip=fffff88005363db1 rsp=fffff88003194610 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000002 r10=0000000000000002
    r11=0000000000000000 r12=fffffa800ea5b060 r13=0000000000000000
    r14=fffff8a003f30d00 r15=0000000000000001
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    EtronXHCI+0x9db1:
    fffff880`05363db1 8b8174400000    mov     eax,dword ptr [rcx+4074h] ds:002b:00000000`00004074=????????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000004074
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003704100
    GetUlongFromAddress: unable to read from fffff800037041c0
     0000000000004074 Nonpaged pool
    
    FOLLOWUP_IP: 
    EtronXHCI+9db1
    fffff880`05363db1 8b8174400000    mov     eax,dword ptr [rcx+4074h]
    
    BUGCHECK_STR:  0x7E
    
    LAST_CONTROL_TRANSFER:  from fffffa800ebc8000 to fffff88005363db1
    
    STACK_TEXT:  
    fffff880`03194610 fffffa80`0ebc8000 : 00000000`00000002 fffffa80`0ea5b060 fffffa80`0ea5b1b0 fffffa80`0ea5b1b0 : EtronXHCI+0x9db1
    fffff880`03194618 00000000`00000002 : fffffa80`0ea5b060 fffffa80`0ea5b1b0 fffffa80`0ea5b1b0 fffffa80`0ea5b478 : 0xfffffa80`0ebc8000
    fffff880`03194620 fffffa80`0ea5b060 : fffffa80`0ea5b1b0 fffffa80`0ea5b1b0 fffffa80`0ea5b478 fffffa80`0ea5b060 : 0x2
    fffff880`03194628 fffffa80`0ea5b1b0 : fffffa80`0ea5b1b0 fffffa80`0ea5b478 fffffa80`0ea5b060 fffff880`0535bdb6 : 0xfffffa80`0ea5b060
    fffff880`03194630 fffffa80`0ea5b1b0 : fffffa80`0ea5b478 fffffa80`0ea5b060 fffff880`0535bdb6 fffffa80`00001b6f : 0xfffffa80`0ea5b1b0
    fffff880`03194638 fffffa80`0ea5b478 : fffffa80`0ea5b060 fffff880`0535bdb6 fffffa80`00001b6f 00000000`00007023 : 0xfffffa80`0ea5b1b0
    fffff880`03194640 fffffa80`0ea5b060 : fffff880`0535bdb6 fffffa80`00001b6f 00000000`00007023 00000000`0c033001 : 0xfffffa80`0ea5b478
    fffff880`03194648 fffff880`0535bdb6 : fffffa80`00001b6f 00000000`00007023 00000000`0c033001 00000000`00000000 : 0xfffffa80`0ea5b060
    fffff880`03194650 fffffa80`00001b6f : 00000000`00007023 00000000`0c033001 00000000`00000000 fffff880`009b3180 : EtronXHCI+0x1db6
    fffff880`03194658 00000000`00007023 : 00000000`0c033001 00000000`00000000 fffff880`009b3180 00000000`00000000 : 0xfffffa80`00001b6f
    fffff880`03194660 00000000`0c033001 : 00000000`00000000 fffff880`009b3180 00000000`00000000 00000000`00000000 : 0x7023
    fffff880`03194668 00000000`00000000 : fffff880`009b3180 00000000`00000000 00000000`00000000 00000000`00000000 : 0xc033001
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  EtronXHCI+9db1
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: EtronXHCI
    
    IMAGE_NAME:  EtronXHCI.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4e2de090
    
    STACK_COMMAND:  .cxr 0xfffff88003193c30 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_EtronXHCI+9db1
    
    BUCKET_ID:  X64_0x7E_EtronXHCI+9db1
    
    Followup: MachineOwner
    ---------
    
    4: kd> lmvm EtronXHCI
    start             end                 module name
    fffff880`0535a000 fffff880`0536d500   EtronXHCI T (no symbols)           
        Loaded symbol image file: EtronXHCI.sys
        Image path: \SystemRoot\System32\Drivers\EtronXHCI.sys
        Image name: EtronXHCI.sys
        Timestamp:        Tue Jul 26 03:30:56 2011 (4E2DE090)
        CheckSum:         00020826
        ImageSize:        00013500
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    How many sticks of RAM do you have? You need to test them individually in different slots
    as mentioned in my post 13.
      My Computer


  2. Posts : 25
    64 bit Windows 7 Home premium
    Thread Starter
       #22

    I have 4 sticks that are 4GB each. And I have done the Memtest 86 test on each stick of RAM in different places and let it go to 5 or 6 passes each time and didn't get an error. I will look into updating the Etron drivers again but the last time I looked there were no updates.
      My Computer


  3. Posts : 15,026
    Windows 10 Home 64Bit
       #23

    Do you get BSOD-s in safe mode?
      My Computer


  4. Posts : 25
    64 bit Windows 7 Home premium
    Thread Starter
       #24

    No. The only time I blue screen is right after the 4 elements collide when loading up regular windows. It does it at random times. The only other information I have left that I doubt will help is the Txt I made to record every time that I have blue screened.
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #25

    Weird thing is they come with the same bug check.

    Lets enable driver verifier.

    Driver Verifier

    Use verifier for 36 hours. Then send us the BSOD reports

    Driver Verifier
    I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

    In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

    Then, here's the procedure:
    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.

    Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because [/B][B]Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

    If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
    Driver Verifier - Enable and Disable
      My Computer


  6. Posts : 25
    64 bit Windows 7 Home premium
    Thread Starter
       #26

    Sorry about getting back to this so late. I've been having other problems that overshadowed this one. I have not used Driver Verifier yet, but my computer hasn't blue screened from 4 weeks ago. Maybe I'm on a lucky streak or something I did without knowing fixed it, but I will report here if it happens again.
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #27

    No problem.
      My Computer


 
Page 3 of 3 FirstFirst 123

  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:26.
Find Us