BSOD SYSTEM_THREAD_EXEPTION_NOT_HANDLED_M (1000007e)

modemo

New Member
Messages
4
Hi to everyone,

for last 2 days I have had 2 BSOD, both SYSTEM_THREAD_EXEPTION_NOT_HANDLED, both on system startup. The system was power down correctly before it.
On BSOD screen I get to 100% of gathering infos, but no restart, I had to force notebook to power down.
Someone to help? Thanks a lot.

Laco
 

My Computer

System One

  • OS
    Win 8
    Computer type
    Laptop
    System Manufacturer/Model
    HP
The BSOD seems to be caused by your FTDI USB to Serial adapter.

You may want to unplug/remove/uninstall any device/software related to it and see how things go.

Code:
*** WARNING: Unable to verify timestamp for ftdibus.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdibus.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff801a0907c70, fffff88007348b98, fffff880073483d0}

Probably caused by : ftdibus.sys ( ftdibus+a886 )

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

6: 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: fffff801a0907c70, The address that the exception occurred at
Arg3: fffff88007348b98, Exception Record Address
Arg4: fffff880073483d0, 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: 
nt!IofCallDriver+10
fffff801`a0907c70 fe4a43          dec     byte ptr [rdx+43h]

EXCEPTION_RECORD:  fffff88007348b98 -- (.exr 0xfffff88007348b98)
ExceptionAddress: fffff801a0907c70 (nt!IofCallDriver+0x0000000000000010)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000043
Attempt to write to address 0000000000000043

CONTEXT:  fffff880073483d0 -- (.cxr 0xfffff880073483d0)
rax=0000000000000000 rbx=fffffa800bf021a0 rcx=fffffa8007cfd6a0
rdx=0000000000000000 rsi=0000000000000004 rdi=fffffa8016c00000
rip=fffff801a0907c70 rsp=fffff88007348dd0 rbp=fffffa800ccd3a70
 r8=00000000000078f0  r9=0000000000000000 r10=fffff88003040000
r11=0000000000000306 r12=00000000fffff880 r13=0000000000000004
r14=fffffa8007cfd6a0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!IofCallDriver+0x10:
fffff801`a0907c70 fe4a43          dec     byte ptr [rdx+43h] ds:002b:00000000`00000043=??
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:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000043

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff801a0bc6168
GetUlongFromAddress: unable to read from fffff801a0bc61f8
 0000000000000043 Nonpaged pool

FOLLOWUP_IP: 
ftdibus+a886
fffff880`2d4a5886 ??              ???

BUGCHECK_STR:  AV

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff8802d4a5886 to fffff801a0907c70

STACK_TEXT:  
fffff880`07348dd0 fffff880`2d4a5886 : fffff880`07348e50 fffffa80`0ccd3a70 00000000`00000000 00000000`00000700 : nt!IofCallDriver+0x10
fffff880`07348e00 fffff880`07348e50 : fffffa80`0ccd3a70 00000000`00000000 00000000`00000700 fffffa80`16c00000 : ftdibus+0xa886
fffff880`07348e08 fffffa80`0ccd3a70 : 00000000`00000000 00000000`00000700 fffffa80`16c00000 00000000`fffff880 : 0xfffff880`07348e50
fffff880`07348e10 00000000`00000000 : 00000000`00000700 fffffa80`16c00000 00000000`fffff880 00000000`00000000 : 0xfffffa80`0ccd3a70


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ftdibus+a886

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ftdibus

IMAGE_NAME:  ftdibus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50fea16d

STACK_COMMAND:  .cxr 0xfffff880073483d0 ; kb

FAILURE_BUCKET_ID:  AV_ftdibus+a886

BUCKET_ID:  AV_ftdibus+a886

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

6: kd> lmvm ftdibus
start             end                 module name
fffff880`2d49b000 fffff880`2d4ac400   ftdibus  T (no symbols)           
    Loaded symbol image file: ftdibus.sys
    Image path: \SystemRoot\system32\drivers\ftdibus.sys
    Image name: ftdibus.sys
    Timestamp:        Tue Jan 22 20:25:49 2013 (50FEA16D)
    CheckSum:         0001FDE7
    ImageSize:        00011400
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
 

My Computer

System One

  • OS
    Windows 7 Home Premium 64 Bit
    Computer type
    PC/Desktop
Thank you.
Yes, I am using new FTDI USB to serial converter for few days. I download latest drivers from FTDI website, hope it helps. I wil give feedback after some time.
 

My Computer

System One

  • OS
    Win 8
    Computer type
    Laptop
    System Manufacturer/Model
    HP
So I get next BSOD :confused:
I am using latest FTDI driver (2.08.28) and usually getting BSOD when turning on computer with FTDI cable/chip already connected.
Any ideas?

Thanks, Laco.


Code:
*******************************************************************************
*                        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: fffff8033ceaac70, The address that the exception occurred at
Arg3: fffff8802ace5b98, Exception Record Address
Arg4: fffff8802ace53d0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP: 
nt!IofCallDriver+10
fffff803`3ceaac70 fe4a43          dec     byte ptr [rdx+43h]

EXCEPTION_RECORD:  fffff8802ace5b98 -- (.exr 0xfffff8802ace5b98)
ExceptionAddress: fffff8033ceaac70 (nt!IofCallDriver+0x0000000000000010)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000000000043
Attempt to write to address 0000000000000043

CONTEXT:  fffff8802ace53d0 -- (.cxr 0xfffff8802ace53d0)
rax=0000000000000000 rbx=fffffa800c21b1a0 rcx=fffffa8007b80040
rdx=0000000000000000 rsi=0000000000000004 rdi=fffffa8016400000
rip=fffff8033ceaac70 rsp=fffff8802ace5dd0 rbp=fffffa80082aea10
 r8=00000000000078f0  r9=0000000000000000 r10=fffff88003240000
r11=0000000000000306 r12=00000000fffff880 r13=0000000000000004
r14=fffffa8007b80040 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!IofCallDriver+0x10:
fffff803`3ceaac70 fe4a43          dec     byte ptr [rdx+43h] ds:002b:00000000`00000043=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  0000000000000043

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8033d169168
GetUlongFromAddress: unable to read from fffff8033d1691f8
 0000000000000043 Nonpaged pool

FOLLOWUP_IP: 
ftdibus+a886
fffff880`2d07f886 ??              ???

BUGCHECK_STR:  AV

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff8802d07f886 to fffff8033ceaac70

STACK_TEXT:  
fffff880`2ace5dd0 fffff880`2d07f886 : fffff880`2ace5e50 fffffa80`082aea10 00000000`00000000 00000000`00000700 : nt!IofCallDriver+0x10
fffff880`2ace5e00 fffff880`2ace5e50 : fffffa80`082aea10 00000000`00000000 00000000`00000700 fffffa80`16400000 : ftdibus+0xa886
fffff880`2ace5e08 fffffa80`082aea10 : 00000000`00000000 00000000`00000700 fffffa80`16400000 00000000`fffff880 : 0xfffff880`2ace5e50
fffff880`2ace5e10 00000000`00000000 : 00000000`00000700 fffffa80`16400000 00000000`fffff880 00000000`00000000 : 0xfffffa80`082aea10


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ftdibus+a886

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ftdibus

IMAGE_NAME:  ftdibus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50fea16d

STACK_COMMAND:  .cxr 0xfffff8802ace53d0 ; kb

FAILURE_BUCKET_ID:  AV_ftdibus+a886

BUCKET_ID:  AV_ftdibus+a886

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

My Computer

System One

  • OS
    Win 8
    Computer type
    Laptop
    System Manufacturer/Model
    HP
Maybe you should just disable that software.
 

My Computer

System One

  • OS
    Windows 7 Home Premium 64 Bit
    Computer type
    PC/Desktop
Back
Top