Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

USB device disconnects causing Blue screen issues.


  • Please log in to reply
1 reply to this topic

#1 hofadomma

hofadomma

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:33 AM

Posted 28 August 2009 - 03:54 PM

I read a post while not registered about debugging, and did it and here is the information, can anyone look at this and help me trouble shoot why when i disconnect any USB device, my computer crash's to Bluescreen. Brand new dell computer, and two devices that have caused issues so far are external usb hard drive, and usb dongle linksys wireless card.


Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Fatty\Desktop\Mini082609-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.22477.amd64fre.vistasp1_ldr.090722-0700
Machine Name:
Kernel base = 0xfffff800`01a12000 PsLoadedModuleList = 0xfffff800`01bd4db0
Debug session time: Wed Aug 26 06:14:26.540 2009 (GMT-6)
System Uptime: 0 days 3:06:03.269
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80001e423aa, fffffa60017e07d8, fffffa60017e01b0}

Probably caused by : ntkrnlmp.exe ( nt!PnpDelayedRemoveWorker+2a )

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

1: 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: fffff80001e423aa, The address that the exception occurred at
Arg3: fffffa60017e07d8, Exception Record Address
Arg4: fffffa60017e01b0, 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!PnpDelayedRemoveWorker+2a
fffff800`01e423aa 498b8238010000 mov rax,qword ptr [r10+138h]

EXCEPTION_RECORD: fffffa60017e07d8 -- (.exr 0xfffffa60017e07d8)
ExceptionAddress: fffff80001e423aa (nt!PnpDelayedRemoveWorker+0x000000000000002a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffffa60017e01b0 -- (.cxr 0xfffffa60017e01b0)
rax=fffffa80036aa001 rbx=fffffa80062120f0 rcx=fffff80001c0ad20
rdx=fffffa80036aa001 rsi=fffffa8008030060 rdi=0000000000000000
rip=fffff80001e423aa rsp=fffffa60017e0a10 rbp=0000000000000001
r8=fffffa80062120f0 r9=5000c00dca000000 r10=005c00730077006f
r11=00000000000007ff r12=fffff80001c0ab20 r13=fffffa80047b5c10
r14=0000000000000000 r15=0000000000000002
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!PnpDelayedRemoveWorker+0x2a:
fffff800`01e423aa 498b8238010000 mov rax,qword ptr [r10+138h] ds:002b:005c0073`007701a7=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_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: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c37080
ffffffffffffffff

FOLLOWUP_IP:
nt!PnpDelayedRemoveWorker+2a
fffff800`01e423aa 498b8238010000 mov rax,qword ptr [r10+138h]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff80001e42555 to fffff80001e423aa

STACK_TEXT:
fffffa60`017e0a10 fffff800`01e42555 : fffffa80`062120f0 fffffa80`047b5c18 fffffa80`047b5c10 00000000`00000001 : nt!PnpDelayedRemoveWorker+0x2a
fffffa60`017e0a60 fffff800`01b3dc69 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`06f10be0 : nt!PnpChainDereferenceComplete+0x115
fffffa60`017e0aa0 fffff800`01e46d79 : 00000000`00000000 fffffa80`08030000 fffffa80`0761dbb0 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffffa60`017e0b20 fffff800`01e46ffc : fffffa60`017e0cf8 00000000`00000000 fffff880`0d47bc00 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xf99
fffffa60`017e0c70 fffff800`01d476c7 : 00000000`00000001 fffffa80`0800f180 fffff880`0ba06170 00000000`4b706e50 : nt!PnpProcessTargetDeviceEvent+0x4c
fffffa60`017e0ca0 fffff800`01a6be4a : fffff800`01c73494 fffff880`0d3885c0 fffff800`01ba18f8 fffffa80`036aa040 : nt! ?? ::NNGAKEGL::`string'+0x4a314
fffffa60`017e0cf0 fffff800`01c83573 : fffffa80`0800f180 00000000`00000000 fffffa80`036aa040 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`017e0d50 fffff800`01a9aff6 : fffffa60`005ec180 fffffa80`036aa040 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`017e0d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!PnpDelayedRemoveWorker+2a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a67e1a0

STACK_COMMAND: .cxr 0xfffffa60017e01b0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_nt!PnpDelayedRemoveWorker+2a

BUCKET_ID: X64_0x7E_nt!PnpDelayedRemoveWorker+2a

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

BC AdBot (Login to Remove)

 


#2 ShIzNiT1707

ShIzNiT1707

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:12:33 AM

Posted 29 August 2009 - 10:15 PM

You may have been hit by the same error that thousands (or hundreds of thousand) of others have...

Try the steps located here: http://www.techerator.com/2009/08/fix-wind...indows-updates/

I read a post while not registered about debugging, and did it and here is the information, can anyone look at this and help me trouble shoot why when i disconnect any USB device, my computer crash's to Bluescreen. Brand new dell computer, and two devices that have caused issues so far are external usb hard drive, and usb dongle linksys wireless card.


Microsoft Windows Debugger Version 6.11.0001.404 X86
Copyright Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Fatty\Desktop\Mini082609-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 Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.22477.amd64fre.vistasp1_ldr.090722-0700
Machine Name:
Kernel base = 0xfffff800`01a12000 PsLoadedModuleList = 0xfffff800`01bd4db0
Debug session time: Wed Aug 26 06:14:26.540 2009 (GMT-6)
System Uptime: 0 days 3:06:03.269
Loading Kernel Symbols
...............................................................
................................................................
............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80001e423aa, fffffa60017e07d8, fffffa60017e01b0}

Probably caused by : ntkrnlmp.exe ( nt!PnpDelayedRemoveWorker+2a )

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

1: 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: fffff80001e423aa, The address that the exception occurred at
Arg3: fffffa60017e07d8, Exception Record Address
Arg4: fffffa60017e01b0, 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!PnpDelayedRemoveWorker+2a
fffff800`01e423aa 498b8238010000 mov rax,qword ptr [r10+138h]

EXCEPTION_RECORD: fffffa60017e07d8 -- (.exr 0xfffffa60017e07d8)
ExceptionAddress: fffff80001e423aa (nt!PnpDelayedRemoveWorker+0x000000000000002a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffffa60017e01b0 -- (.cxr 0xfffffa60017e01b0)
rax=fffffa80036aa001 rbx=fffffa80062120f0 rcx=fffff80001c0ad20
rdx=fffffa80036aa001 rsi=fffffa8008030060 rdi=0000000000000000
rip=fffff80001e423aa rsp=fffffa60017e0a10 rbp=0000000000000001
r8=fffffa80062120f0 r9=5000c00dca000000 r10=005c00730077006f
r11=00000000000007ff r12=fffff80001c0ab20 r13=fffffa80047b5c10
r14=0000000000000000 r15=0000000000000002
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!PnpDelayedRemoveWorker+0x2a:
fffff800`01e423aa 498b8238010000 mov rax,qword ptr [r10+138h] ds:002b:005c0073`007701a7=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_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: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001c37080
ffffffffffffffff

FOLLOWUP_IP:
nt!PnpDelayedRemoveWorker+2a
fffff800`01e423aa 498b8238010000 mov rax,qword ptr [r10+138h]

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff80001e42555 to fffff80001e423aa

STACK_TEXT:
fffffa60`017e0a10 fffff800`01e42555 : fffffa80`062120f0 fffffa80`047b5c18 fffffa80`047b5c10 00000000`00000001 : nt!PnpDelayedRemoveWorker+0x2a
fffffa60`017e0a60 fffff800`01b3dc69 : 00000000`00000001 00000000`00000001 00000000`00000000 fffffa80`06f10be0 : nt!PnpChainDereferenceComplete+0x115
fffffa60`017e0aa0 fffff800`01e46d79 : 00000000`00000000 fffffa80`08030000 fffffa80`0761dbb0 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffffa60`017e0b20 fffff800`01e46ffc : fffffa60`017e0cf8 00000000`00000000 fffff880`0d47bc00 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xf99
fffffa60`017e0c70 fffff800`01d476c7 : 00000000`00000001 fffffa80`0800f180 fffff880`0ba06170 00000000`4b706e50 : nt!PnpProcessTargetDeviceEvent+0x4c
fffffa60`017e0ca0 fffff800`01a6be4a : fffff800`01c73494 fffff880`0d3885c0 fffff800`01ba18f8 fffffa80`036aa040 : nt! ?? ::NNGAKEGL::`string'+0x4a314
fffffa60`017e0cf0 fffff800`01c83573 : fffffa80`0800f180 00000000`00000000 fffffa80`036aa040 00000000`00000080 : nt!ExpWorkerThread+0x11a
fffffa60`017e0d50 fffff800`01a9aff6 : fffffa60`005ec180 fffffa80`036aa040 fffffa60`005f5d40 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`017e0d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!PnpDelayedRemoveWorker+2a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a67e1a0

STACK_COMMAND: .cxr 0xfffffa60017e01b0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_nt!PnpDelayedRemoveWorker+2a

BUCKET_ID: X64_0x7E_nt!PnpDelayedRemoveWorker+2a

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






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users