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

Blue Screen (of Death?)


  • Please log in to reply
6 replies to this topic

#1 A20

A20

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:03:23 AM

Posted 10 November 2006 - 01:27 AM

Hi,

I have encountered a blue screen (Blue Screen of Death, I think) by either logging off users or shutting down my computer. I had a suspicion it was a Logitech Driver, so I went to their website and downloaded and installed a newer version of their software for my web camera (had to install new version of Windows Installer to do this). It must not have worked, since the screen showed again.

This last time the stop message was:

STOP: 0x0000007E (0xc0000005, 0x00000000, 0xF8987A6c, 0xF8987768)

I've looked online but nothing is making any sense.

Thanks,
A

BC AdBot (Login to Remove)

 


m

#2 projectfocus

projectfocus

  • Members
  • 474 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Brighton
  • Local time:11:23 AM

Posted 10 November 2006 - 08:52 AM

If it is crashing everytime then I would say it is likely to be a driver. If the system has not successfully shut down since then start XP with Last Known Good configuration.
Press F8 on startup to reveal this option.
Posted Image

#3 notsotechie

notsotechie

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:04:23 AM

Posted 10 November 2006 - 10:49 AM

Also there could be a conflict with the video card? possible. Check the device manager see if there are any yellow ! or a red x on any devices
another way u can try is this

start>run>cmd>sfc/scannow please have your window os handy in the drive as there may be a problem with the protected system file area?
Have A Great Day;-D[font=Century Gothic]

#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:23 AM

Posted 10 November 2006 - 05:21 PM

Here's a link to a description of the error: http://aumha.org/win5/kbestop.php#0x7e

Was there a filename mentioned in the BSOD? This often leads to a quick solution.

If you can't recall - try looking for the error in your Event Viewer (How To here: http://www.bleepingcomputer.com/forums/t/40108/how-to-use-event-viewer/ )

If you can't find it there, you may be able to search your hard drive for files ending in .dmp or .mdmp. If you find them, you can use this procedure to generate an analysis and then post it here for us to look at: http://forums.majorgeeks.com/showthread.php?t=35246

On the "down" side, often the errors will cite filenames belonging to Windows system files. This indicates where the error occurred - not what caused it. If that's the case, then the troubleshooting is a bit more complex.

Finally, the best thing to do is to sit down, grab a beer (or other beverage) and have a long think about what might have caused this. Just consider the things that you've done to the system recently - and you may come up with the clue that will lead to a speedy fix.

Also, don't forget to visit Windows Update and ensure that you've got the latest updates for the latest fixes that you've downloaded.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#5 A20

A20
  • Topic Starter

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:03:23 AM

Posted 11 November 2006 - 04:04 PM

Hi,

The BSoD is not occuring everytime I log off or restart, so I haven't tried the first suggestion, yet. I have checked the device manager, and everything seems to be running fine. I have also used Microsoft Debugger, and it appears to be an issue with the the USB Generic Parent Driver, but I am unsure what to do about it. Here is a copy of the info from my Debugging file, in case this would be useful for someone to help with:

Microsoft ® Windows Debugger Version 6.6.0007.5
Copyright © 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 again, for all your suggestions,
Andrea

#6 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,077 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:05:23 AM

Posted 12 November 2006 - 08:34 AM

From your description in the first post - I'd assume that you're using a Logitech webcam that plugs into the USB ports. If so, this correlates well with the error message analysis (which also points to your USB ports).

I suspect that the Logitech driver may have caused some corruption in your USB drivers and that's causing the file usbccgp.sys to crash.

Since a reinstall of the USB camera drivers didn't fix the problem, then I'd suggest updating your motherboard/chipset drivers from the manufacturer's website. This should fix the problem for you.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#7 Enthusiast

Enthusiast

  • Members
  • 5,898 posts
  • OFFLINE
  •  
  • Location:Florida, USA
  • Local time:05:23 AM

Posted 12 November 2006 - 08:41 AM

Have you updated to SP2? Or are you still running with SP1?
Composite USB devices whose interfaces are not sequentially numbered do not work in Windows XP (and SP1)
http://support.microsoft.com/kb/814560

Probably caused by : usbccgp.sys






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users