locked
BSOD windows8.1 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    Please please help..

    three times in the past 48 hours i have received this message:

    system_thread_exception_not_handled (usb ethernet adapter)

    after mich research and looking on yours site i read a wiki article  (on your site about how to begin addressing the problem)

    As instructed i have uploaded the dmp files. 

    For further information: i have a dell XPS 12.

    see link below. thank you.

    https://onedrive.live.com/redir?resid=772CB958885E0EC8!1290&authkey=!AG_EDX-E5fM90Co&ithint=file%2crar

    Wednesday, February 4, 2015 4:13 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote 
    WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 7 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff800`f3281000 PsLoadedModuleList = 0xfffff800`f3557370
Debug session time: Wed Feb  4 10:37:37.823 2015 (UTC - 5:00)
System Uptime: 0 days 0:07:26.758
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image \SystemRoot\system32\DRIVERS\USB_Ethernet_Adaptor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USB_Ethernet_Adaptor.sys
*** ERROR: Module load completed but symbols could not be loaded for USB_Ethernet_Adaptor.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800a0bb758a, ffffd000a5567358, ffffd000a5566b60}

Probably caused by : USB_Ethernet_Adaptor.sys ( USB_Ethernet_Adaptor+358a )

Followup: MachineOwner
---------

2: 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: fffff800a0bb758a, The address that the exception occurred at
Arg3: ffffd000a5567358, Exception Record Address
Arg4: ffffd000a5566b60, 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: 
USB_Ethernet_Adaptor+358a
fffff800`a0bb758a 410fb6442404    movzx   eax,byte ptr [r12+4]

EXCEPTION_RECORD:  ffffd000a5567358 -- (.exr 0xffffd000a5567358)
ExceptionAddress: fffff800a0bb758a (USB_Ethernet_Adaptor+0x000000000000358a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000004
Attempt to read from address 0000000000000004

CONTEXT:  ffffd000a5566b60 -- (.cxr 0xffffd000a5566b60)
rax=0000000000000000 rbx=ffffe001719ee470 rcx=0000000000000000
rdx=0000000000006ce1 rsi=0000000000000005 rdi=ffffe00174346000
rip=fffff800a0bb758a rsp=ffffd000a5567590 rbp=ffffe00169574d00
 r8=0000000000000000  r9=ffffe00174346000 r10=0000000000000005
r11=ffffd000a55674e0 r12=0000000000000000 r13=ffffe0016cbb40b0
r14=0000000000000000 r15=0000000000000088
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
USB_Ethernet_Adaptor+0x358a:
fffff800`a0bb758a 410fb6442404    movzx   eax,byte ptr [r12+4] ds:002b:00000000`00000004=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

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:  0000000000000004

READ_ADDRESS: fffff800f3544d80: Unable to get special pool info
fffff800f3544d80: Unable to get special pool info
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 0000000000000004 

FOLLOWUP_IP: 
USB_Ethernet_Adaptor+358a
fffff800`a0bb758a 410fb6442404    movzx   eax,byte ptr [r12+4]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from ffffe001719ee470 to fffff800a0bb758a

STACK_TEXT:  
ffffd000`a5567590 ffffe001`719ee470 : 00000000`00006ce1 00000000`00000088 00000000`00000088 ffffd000`ffffffff : USB_Ethernet_Adaptor+0x358a
ffffd000`a5567598 00000000`00006ce1 : 00000000`00000088 00000000`00000088 ffffd000`ffffffff ffffd000`ffffffff : 0xffffe001`719ee470
ffffd000`a55675a0 00000000`00000088 : 00000000`00000088 ffffd000`ffffffff ffffd000`ffffffff 00000000`ffffffff : 0x6ce1
ffffd000`a55675a8 00000000`00000088 : ffffd000`ffffffff ffffd000`ffffffff 00000000`ffffffff ffffe001`6ce1d180 : 0x88
ffffd000`a55675b0 ffffd000`ffffffff : ffffd000`ffffffff 00000000`ffffffff ffffe001`6ce1d180 ffffe001`6ce1d188 : 0x88
ffffd000`a55675b8 ffffd000`ffffffff : 00000000`ffffffff ffffe001`6ce1d180 ffffe001`6ce1d188 00000000`00000000 : 0xffffd000`ffffffff
ffffd000`a55675c0 00000000`ffffffff : ffffe001`6ce1d180 ffffe001`6ce1d188 00000000`00000000 80000300`000b0088 : 0xffffd000`ffffffff
ffffd000`a55675c8 ffffe001`6ce1d180 : ffffe001`6ce1d188 00000000`00000000 80000300`000b0088 fffff800`9ea4b84a : 0xffffffff
ffffd000`a55675d0 ffffe001`6ce1d188 : 00000000`00000000 80000300`000b0088 fffff800`9ea4b84a ffffe001`6d2cd060 : 0xffffe001`6ce1d180
ffffd000`a55675d8 00000000`00000000 : 80000300`000b0088 fffff800`9ea4b84a ffffe001`6d2cd060 ffffe001`6ce1d160 : 0xffffe001`6ce1d188


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  USB_Ethernet_Adaptor+358a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USB_Ethernet_Adaptor

IMAGE_NAME:  USB_Ethernet_Adaptor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50bf1d43

STACK_COMMAND:  .cxr 0xffffd000a5566b60 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_USB_Ethernet_Adaptor+358a

BUCKET_ID:  X64_0x7E_USB_Ethernet_Adaptor+358a

Followup: MachineOwner
---------

2: kd> lmvm USB_Ethernet_Adaptor
start             end                 module name
fffff800`a0bb4000 fffff800`a0bbe000   USB_Ethernet_Adaptor T (no symbols)           
    Loaded symbol image file: USB_Ethernet_Adaptor.sys
    Image path: \SystemRoot\system32\DRIVERS\USB_Ethernet_Adaptor.sys
    Image name: USB_Ethernet_Adaptor.sys
    Timestamp:        Wed Dec 05 05:09:07 2012 (50BF1D43)
    CheckSum:         00011E8B
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    The crash was caused by USB_Ethernet_Adaptor.sys. See if you can find an updated version of the driver.


    • Edited by XP ROCKS Thursday, February 5, 2015 3:51 AM
    • Proposed as answer by ZigZag3143x Thursday, February 5, 2015 4:23 AM
    • Marked as answer by FangZhou Chen Thursday, February 19, 2015 1:20 AM
    Thursday, February 5, 2015 3:49 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote 
    WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 7 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
Machine Name:
Kernel base = 0xfffff800`f3281000 PsLoadedModuleList = 0xfffff800`f3557370
Debug session time: Wed Feb  4 10:37:37.823 2015 (UTC - 5:00)
System Uptime: 0 days 0:07:26.758
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image \SystemRoot\system32\DRIVERS\USB_Ethernet_Adaptor.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for USB_Ethernet_Adaptor.sys
*** ERROR: Module load completed but symbols could not be loaded for USB_Ethernet_Adaptor.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800a0bb758a, ffffd000a5567358, ffffd000a5566b60}

Probably caused by : USB_Ethernet_Adaptor.sys ( USB_Ethernet_Adaptor+358a )

Followup: MachineOwner
---------

2: 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: fffff800a0bb758a, The address that the exception occurred at
Arg3: ffffd000a5567358, Exception Record Address
Arg4: ffffd000a5566b60, 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: 
USB_Ethernet_Adaptor+358a
fffff800`a0bb758a 410fb6442404    movzx   eax,byte ptr [r12+4]

EXCEPTION_RECORD:  ffffd000a5567358 -- (.exr 0xffffd000a5567358)
ExceptionAddress: fffff800a0bb758a (USB_Ethernet_Adaptor+0x000000000000358a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000004
Attempt to read from address 0000000000000004

CONTEXT:  ffffd000a5566b60 -- (.cxr 0xffffd000a5566b60)
rax=0000000000000000 rbx=ffffe001719ee470 rcx=0000000000000000
rdx=0000000000006ce1 rsi=0000000000000005 rdi=ffffe00174346000
rip=fffff800a0bb758a rsp=ffffd000a5567590 rbp=ffffe00169574d00
 r8=0000000000000000  r9=ffffe00174346000 r10=0000000000000005
r11=ffffd000a55674e0 r12=0000000000000000 r13=ffffe0016cbb40b0
r14=0000000000000000 r15=0000000000000088
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
USB_Ethernet_Adaptor+0x358a:
fffff800`a0bb758a 410fb6442404    movzx   eax,byte ptr [r12+4] ds:002b:00000000`00000004=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

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:  0000000000000004

READ_ADDRESS: fffff800f3544d80: Unable to get special pool info
fffff800f3544d80: Unable to get special pool info
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 0000000000000004 

FOLLOWUP_IP: 
USB_Ethernet_Adaptor+358a
fffff800`a0bb758a 410fb6442404    movzx   eax,byte ptr [r12+4]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from ffffe001719ee470 to fffff800a0bb758a

STACK_TEXT:  
ffffd000`a5567590 ffffe001`719ee470 : 00000000`00006ce1 00000000`00000088 00000000`00000088 ffffd000`ffffffff : USB_Ethernet_Adaptor+0x358a
ffffd000`a5567598 00000000`00006ce1 : 00000000`00000088 00000000`00000088 ffffd000`ffffffff ffffd000`ffffffff : 0xffffe001`719ee470
ffffd000`a55675a0 00000000`00000088 : 00000000`00000088 ffffd000`ffffffff ffffd000`ffffffff 00000000`ffffffff : 0x6ce1
ffffd000`a55675a8 00000000`00000088 : ffffd000`ffffffff ffffd000`ffffffff 00000000`ffffffff ffffe001`6ce1d180 : 0x88
ffffd000`a55675b0 ffffd000`ffffffff : ffffd000`ffffffff 00000000`ffffffff ffffe001`6ce1d180 ffffe001`6ce1d188 : 0x88
ffffd000`a55675b8 ffffd000`ffffffff : 00000000`ffffffff ffffe001`6ce1d180 ffffe001`6ce1d188 00000000`00000000 : 0xffffd000`ffffffff
ffffd000`a55675c0 00000000`ffffffff : ffffe001`6ce1d180 ffffe001`6ce1d188 00000000`00000000 80000300`000b0088 : 0xffffd000`ffffffff
ffffd000`a55675c8 ffffe001`6ce1d180 : ffffe001`6ce1d188 00000000`00000000 80000300`000b0088 fffff800`9ea4b84a : 0xffffffff
ffffd000`a55675d0 ffffe001`6ce1d188 : 00000000`00000000 80000300`000b0088 fffff800`9ea4b84a ffffe001`6d2cd060 : 0xffffe001`6ce1d180
ffffd000`a55675d8 00000000`00000000 : 80000300`000b0088 fffff800`9ea4b84a ffffe001`6d2cd060 ffffe001`6ce1d160 : 0xffffe001`6ce1d188


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  USB_Ethernet_Adaptor+358a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USB_Ethernet_Adaptor

IMAGE_NAME:  USB_Ethernet_Adaptor.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50bf1d43

STACK_COMMAND:  .cxr 0xffffd000a5566b60 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_USB_Ethernet_Adaptor+358a

BUCKET_ID:  X64_0x7E_USB_Ethernet_Adaptor+358a

Followup: MachineOwner
---------

2: kd> lmvm USB_Ethernet_Adaptor
start             end                 module name
fffff800`a0bb4000 fffff800`a0bbe000   USB_Ethernet_Adaptor T (no symbols)           
    Loaded symbol image file: USB_Ethernet_Adaptor.sys
    Image path: \SystemRoot\system32\DRIVERS\USB_Ethernet_Adaptor.sys
    Image name: USB_Ethernet_Adaptor.sys
    Timestamp:        Wed Dec 05 05:09:07 2012 (50BF1D43)
    CheckSum:         00011E8B
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    The crash was caused by USB_Ethernet_Adaptor.sys. See if you can find an updated version of the driver.


    • Edited by XP ROCKS Thursday, February 5, 2015 3:51 AM
    • Proposed as answer by ZigZag3143x Thursday, February 5, 2015 4:23 AM
    • Marked as answer by FangZhou Chen Thursday, February 19, 2015 1:20 AM
    Thursday, February 5, 2015 3:49 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the same exact problem.

    The only driver i can find is through windows update. Nothing else works.

    does anyone have any working solution?

    you will never walk alone

    Friday, July 31, 2015 9:00 AM