BSoD

Hi,

I have recently been getting a Blue Screen Of Death upon either logging off or shutting down. Not everytime, but enough.

I have looked at my devices and everything seems to be working. I have tried to find my specific STOP ERROR messages online with nothing specifically applying to my situation. I finally found the Microsoft Debugging Tools and the problem seems to lie with the USB Common Class Generic Parent Driver. Unfortunately, I am unsure what to do next. I thought I would paste the copy of the Debugger information on here and see if anyone could help:

Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini110906-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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu Nov 9 15:01:25.875 2006 (GMT-7)
System Uptime: 5 days 5:42:41.461
Loading Kernel Symbols
...........................................................................................................................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 0, f8987a6c, f8987768}

Probably caused by : usbccgp.sys ( usbccgp!USBC_PnP+12f )

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: c0000005, The exception code that was not handled
Arg2: 00000000, The address that the exception occurred at
Arg3: f8987a6c, Exception Record Address
Arg4: f8987768, 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:
+0
00000000 ?? ???

EXCEPTION_RECORD: f8987a6c -- (.exr fffffffff8987a6c)
ExceptionAddress: 00000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000000
Attempt to read from address 00000000

CONTEXT: f8987768 -- (.cxr fffffffff8987768)
eax=81fffa48 ebx=00000000 ecx=00000003 edx=81b5fee0 esi=81fffb00 edi=81bc10e8
eip=00000000 esp=f8987b34 ebp=f8987b60 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210286
00000000 ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

READ_ADDRESS: 00000000

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f86ec6ff to 00000000

FAILED_INSTRUCTION_ADDRESS:
+0
00000000 ?? ???

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f8987b30 f86ec6ff 00000000 68627375 70646f52 0x0
f8987b60 f86f3661 81fffa48 81bc10e8 81b5fe28 usbhub!USBH_PdoRemoveDevice+0x41
f8987b80 f86ec952 81fffb00 81b5fe28 00000002 usbhub!USBH_PdoPnP+0x5b
f8987ba4 f86ea1d8 01fffb00 81b5fe28 f8987c0c usbhub!USBH_PdoDispatch+0x5a
f8987bb4 804e13d9 81fffa48 81b5fe28 81bff7b8 usbhub!USBH_HubDispatch+0x48
f8987bc4 f88fdcef 81ffb028 00000000 00000002 nt!IopfCallDriver+0x31
f8987c0c f88f85e5 81dd2330 81b5fe28 0000001b usbccgp!USBC_PnP+0x12f
f8987c48 804e13d9 81dd2278 81b5fe28 f8987cd4 usbccgp!USBC_Dispatch+0x195
f8987c58 8059e86e 81fffa48 81fffa48 00000002 nt!IopfCallDriver+0x31
f8987c84 805aa766 81dd2278 f8987cb0 00000000 nt!IopSynchronousCall+0xb7
f8987cd8 8050e5a9 81fffa48 00000002 00000000 nt!IopRemoveDevice+0x93
f8987d00 805ab78e e31893c8 00000018 e1ac68b8 nt!IopRemoveLockedDeviceNode+0x160
f8987d18 805aaa3c 81cbd008 00000002 e1ac68b8 nt!IopDeleteLockedDeviceNode+0x34
f8987d4c 805abc78 81fffa48 02ac68b8 00000002 nt!IopDeleteLockedDeviceNodes+0x3f
f8987d7c 804e23b5 814d6d98 00000000 823c6b30 nt!IopDelayedRemoveWorker+0x4b
f8987dac 80574128 814d6d98 00000000 00000000 nt!ExpWorkerThread+0xef
f8987ddc 804efc81 804e22f1 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
usbccgp!USBC_PnP+12f
f88fdcef 8945f4 mov dword ptr [ebp-0Ch],eax

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: usbccgp!USBC_PnP+12f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbccgp

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 41107d6d

STACK_COMMAND: .cxr 0xfffffffff8987768 ; kb

FAILURE_BUCKET_ID: 0x7E_NULL_IP_usbccgp!USBC_PnP+12f

BUCKET_ID: 0x7E_NULL_IP_usbccgp!USBC_PnP+12f

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

1: kd> lmvm usbccgp
start end module name
f88f8000 f88ffb80 usbccgp (pdb symbols) c:\symbols\usbccgp.pdb\8EDE1D867980486FA4F62FD3D84E97AC1\usbccgp.pdb
Loaded symbol image file: usbccgp.sys
Mapped memory image file: c:\symbols\usbccgp.sys\41107D6D7b80\usbccgp.sys
Image path: usbccgp.sys
Image name: usbccgp.sys
Timestamp: Tue Aug 03 23:08:45 2004 (41107D6D)
CheckSum: 00013C1C
ImageSize: 00007B80
File version: 5.1.2600.2180
Product version: 5.1.2600.2180
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: USBCCGP.SYS
OriginalFilename: USBCCGP.SYS
ProductVersion: 5.1.2600.2180
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
FileDescription: USB Common Class Generic Parent Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.

Thanks for any help you can give,

Andrea

 

Ummmm i dont know what to do i would say try to reinstall the driver but i am not sure if you should do that it may make it worse try to google it for more info

 

This is a USB device error, I would say disconnect all USB devices from your pc and try to narow down which one is causing the issue

 

http://www.memtest.org/download/1.65/memtest86+-1.65.iso.zip

Unzip, burn it on cd, reboot with the cd, let it have 5-30 passes & post the # of errors here.