Toshiba Satellite Laptop BSOD

A while back cybercore helped me solve a really frustrating recurring BSOD. It helped a lot, but I couldn't find all the driver updates I needed, and now I think some new problems may be surfacing.

My webcam has never worked properly, and some of the Bugcodes seem to point to that, but I'm pretty illiterate in these areas, so maybe I'm reading it wrong.

Talked to Toshiba support, and he thinks everything comes down to the kernel in the system 32, and that I probably have a virus and need to reformat the computer and start from scratch. Not really stoked about that solution, but want to do what needs to be done.

Is there a way to contribute to the forum? You guys are really helpful, and I appreciate it.

Here's the original thread: https://www.sevenforums.com/crashes-d...hiba-p500.html

fordlikethecar said:

A while back cybercore helped me solve a really frustrating recurring BSOD. It helped a lot, but I couldn't find all the driver updates I needed, and now I think some new problems may be surfacing.

My webcam has never worked properly, and some of the Bugcodes seem to point to that, but I'm pretty illiterate in these areas, so maybe I'm reading it wrong.

Talked to Toshiba support, and he thinks everything comes down to the kernel in the system 32, and that I probably have a virus and need to reformat the computer and start from scratch. Not really stoked about that solution, but want to do what needs to be done.

Is there a way to contribute to the forum? You guys are really helpful, and I appreciate it.

Here's the original thread: https://www.sevenforums.com/crashes-d...hiba-p500.html

most of your crashes (from 3/2 till present) are caused by usbccgp.sys which is a generic usb composite driver (probably the webcams). Is that web cam supported under win 7? is the driver win 7 or earlier?

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\031611-14820-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`03267000 PsLoadedModuleList = 0xfffff800`034a4e50
Debug session time: Wed Mar 16 16:00:14.411 2011 (GMT-4)
System Uptime: 0 days 2:07:50.660
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff800032ce860, fffff8800357e1b8, fffff8800357da20}

Probably caused by : usbccgp.sys ( usbccgp!PrepareParentFDOForRemove+c5 )

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

7: 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: fffff800032ce860, The address that the exception occurred at
Arg3: fffff8800357e1b8, Exception Record Address
Arg4: fffff8800357da20, 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!memcmp+90
fffff800`032ce860 488b01          mov     rax,qword ptr [rcx]

EXCEPTION_RECORD:  fffff8800357e1b8 -- (.exr 0xfffff8800357e1b8)
ExceptionAddress: fffff800032ce860 (nt!memcmp+0x0000000000000090)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048

CONTEXT:  fffff8800357da20 -- (.cxr 0xfffff8800357da20)
rax=0000000000000000 rbx=fffff8a0001cafc8 rcx=0000000000000048
rdx=fffff8a0001cafc8 rsi=0000000000000000 rdi=fffff800034843a0
rip=fffff800032ce860 rsp=fffff8800357e3f8 rbp=0000000000000048
 r8=0000000000000010  r9=0000000000000002 r10=0000000000000000
r11=fffff88003386180 r12=fffff8a015295b50 r13=fffff88006778110
r14=fffffa8007457110 r15=fffff88006778110
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!memcmp+0x90:
fffff800`032ce860 488b01          mov     rax,qword ptr [rcx] ds:002b:00000000`00000048=????????????????
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:  0000000000000048

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350f0e0
 0000000000000048 

FOLLOWUP_IP: 
usbccgp!PrepareParentFDOForRemove+c5
fffff880`067670f1 85c0            test    eax,eax

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff80003546e2f to fffff800032ce860

STACK_TEXT:  
fffff880`0357e3f8 fffff800`03546e2f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!memcmp+0x90
fffff880`0357e400 fffff800`036a473b : 00000000`00000048 00000000`00000002 00000000`00000048 fffff880`0357e518 : nt!WmipFindGEByGuid+0x3f
fffff880`0357e430 fffff800`036a4a43 : 00000000`00000048 00000000`00000002 00000000`00000048 fffff8a0`15295b28 : nt!WmipDisableCollectionForRemovedGuid+0x2b
fffff880`0357e4a0 fffff800`036a4ab3 : 00000000`00000001 fffff8a0`15295b28 00000000`00000040 fffff8a0`1544dc00 : nt!WmipGenerateRegistrationNotification+0x83
fffff880`0357e500 fffff800`036a4af2 : 00000000`00000000 00000000`00000001 fffffa80`0cd1d110 fffffa80`07457110 : nt!WmipRemoveDataSourceByDS+0x13
fffff880`0357e530 fffff800`0353fe0e : fffffa80`0cd1d110 fffffa80`00000001 fffffa80`0cd1d110 00000000`00000000 : nt!WmipRemoveDataSource+0x22
fffff880`0357e560 fffff800`036fde14 : 00000000`00000005 00000000`00000005 fffffa80`0cd1d110 fffff880`06771000 : nt! ?? ::NNGAKEGL::`string'+0x1dff9
fffff880`0357e5a0 fffff800`0370367e : fffffa80`07457268 00000000`00000000 00000000`00000000 00000000`a0000003 : nt!WmipDeregisterDevice+0x64
fffff880`0357e5d0 fffff880`067670f1 : fffffa80`07457268 00000000`00000001 fffffa80`0a6ce010 00000000`00000002 : nt!IoWMIRegistrationControl+0xde
fffff880`0357e600 fffff880`0676959d : fffffa80`0794b060 fffffa80`07457268 fffffa80`0a6ce320 fffffa80`0a6ce010 : usbccgp!PrepareParentFDOForRemove+0xc5
fffff880`0357e650 fffff880`067690f0 : fffffa80`0a6ce002 fffffa80`0a6ce010 fffffa80`07457268 badbadba`badbadba : usbccgp!FdoRemoveDevice+0x5d
fffff880`0357e680 fffff880`0677aae1 : fffffa80`0a6ce010 fffffa80`07457260 fffffa80`07457268 fffffa80`07457268 : usbccgp!DispatchFdoPnp+0x298
fffff880`0357e6f0 fffff880`06766683 : 00000000`0000001b fffffa80`07457260 fffffa80`0000021b fffffa80`0a6ce010 : usbccgp!USBC_PnP+0x89
fffff880`0357e730 fffff800`03542a09 : fffffa80`07457110 00000000`c0000000 fffff880`0357e801 fffffa80`0a6ce010 : usbccgp!USBC_Dispatch+0x233
fffff880`0357e7b0 fffff800`036c2161 : fffffa80`0781d440 00000000`00000000 fffffa80`0dc4aaf0 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`0357e820 fffff800`033d8c13 : fffff8a0`1527d6f0 fffff8a0`1527d6f0 00000000`00000018 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`0357e8e0 fffff800`036c1cb4 : fffffa80`0dc4aaf0 00000000`00000000 00000000`00000002 00000000`00000000 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`0357e930 fffff800`036c1dc0 : 00000000`00000000 fffffa80`0781d400 fffff8a0`13cf4c30 fffff800`034db300 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`0357e960 fffff800`036c1eb9 : fffffa80`0750fb02 fffffa80`0750fb40 00000000`00000001 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`0357e9d0 fffff800`036c2031 : fffffa80`0750fb40 00000000`00000000 fffffa80`0750fb40 00000000`00000002 : nt!PnpDelayedRemoveWorker+0x79
fffff880`0357ea20 fffff800`033d8e39 : 00000000`00000001 fffffa80`0cdf5ad8 00000000`00000001 00000000`00000001 : nt!PnpChainDereferenceComplete+0x131
fffff880`0357ea60 fffff800`03752690 : 00000000`00000000 fffffa80`0dc4aa00 fffff8a0`02dfa8f0 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffff880`0357eae0 fffff800`0375292c : fffff880`0357ecb8 00000000`00000000 fffff8a0`15305000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xff0
fffff880`0357ec20 fffff800`0363da1c : 00000000`00000000 fffffa80`0cbb5780 fffff8a0`0f158cb0 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`0357ec50 fffff800`032e4961 : fffff800`035424f0 fffff8a0`02dfa8f0 fffff800`0347c5f8 fffff800`0347c5f8 : nt! ?? ::NNGAKEGL::`string'+0x58b2b
fffff880`0357ecb0 fffff800`0357a7c6 : 00000000`10000000 fffffa80`06d3cb60 00000000`00000080 fffffa80`06ca6840 : nt!ExpWorkerThread+0x111
fffff880`0357ed40 fffff800`032b5c26 : fffff880`03386180 fffffa80`06d3cb60 fffff880`033910c0 00000000`10000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0357ed80 00000000`00000000 : fffff880`0357f000 fffff880`03579000 fffff880`0357e320 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  usbccgp!PrepareParentFDOForRemove+c5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbccgp

IMAGE_NAME:  usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc15

STACK_COMMAND:  .cxr 0xfffff8800357da20 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_usbccgp!PrepareParentFDOForRemove+c5

BUCKET_ID:  X64_0x7E_usbccgp!PrepareParentFDOForRemove+c5

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

7: kd> lmvm usbccgp
start             end                 module name
fffff880`06765000 fffff880`06782000   usbccgp    (pdb symbols)          c:\symbols\usbccgp.pdb\C1EC39F29955479EBFF892E12884C0FC1\usbccgp.pdb
    Loaded symbol image file: usbccgp.sys
    Mapped memory image file: C:\Symbols\usbccgp.sys\4A5BCC151d000\usbccgp.sys
    Image path: \SystemRoot\system32\DRIVERS\usbccgp.sys
    Image name: usbccgp.sys
    Timestamp:        Mon Jul 13 20:06:45 2009 (4A5BCC15)
    CheckSum:         000274D7
    ImageSize:        0001D000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    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:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  USB Common Class Generic Parent Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Sorry, like I said, I'm pretty illiterate here. How do I change that usbccgb driver? It came with the computer as far as I can tell. It's a built in webcam running a pre-installed version of Windows 7.