BSOD

[yahskaraghu]

Well, for the first time in 8 or 9-odd months, I had a BSOD pop up randomly. So I installed and ran the debugger, and this is what I got. Unfortunately I have no clue how to interpret the results, so any assistance here would be greatly appreciated. Thanks!
By the way, my Laptop's an HP G60 64-bit, and has been running Windows 7 for nearly 6 months now, with no major problems until today.


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


Loading Dump File [C:\Windows\Minidump\053110-40841-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c4c0?
Symbol search path is: srv*DownstreamStore*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Mon May 31 15:24:10.057 2010 (UTC - 4:00)
System Uptime: 0 days 6:47:45.085
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80064d3060, fffff80000b9c4d8, fffffa8007bbb0e0}

Probably caused by : usbccgp.sys

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80064d3060, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa8007bbb0e0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc15

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff8800606d000 usbccgp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c488 fffff800`02ef81b3 : 00000000`0000009f 00000000`00000003 fffffa80`064d3060 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`02e956a6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c530 fffff800`02e94a26 : fffff800`03039700 00000000`0017ee08 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02e9557e : 00000038`f653d82e fffff800`00b9cc18 00000000`0017ee08 fffff800`03006388 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02e94d97 : 0000000b`365a68c1 0000000b`0017ee08 0000000b`365a680e 00000000`00000008 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02e91dfa : fffff800`03003e80 fffff800`03011c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys

BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80064d3060, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa8007bbb0e0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc15

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff8800606d000 usbccgp

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c488 fffff800`02ef81b3 : 00000000`0000009f 00000000`00000003 fffffa80`064d3060 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`02e956a6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c530 fffff800`02e94a26 : fffff800`03039700 00000000`0017ee08 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02e9557e : 00000038`f653d82e fffff800`00b9cc18 00000000`0017ee08 fffff800`03006388 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02e94d97 : 0000000b`365a68c1 0000000b`0017ee08 0000000b`365a680e 00000000`00000008 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02e91dfa : fffff800`03003e80 fffff800`03011c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys

BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys

Followup: MachineOwner

 

[yahskaraghu]

I've attached the MiniDump File itself here as well. Thanks again in advance!

 

[CarlTR6]

STOP 0x0000009F: DRIVER_POWER_STATE_FAILURE

Usual causes: Device driver
BSOD Index

When I ran bugcheck, I found your dump shows the above device driver problem and points to usbvideo.sys as the cause. Your dmp analysis points to usbccgp.sys. Both of these are Microsoft drivers and may not be the cause unless they are corrupted.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80064d3060, fffff80000b9c4d8, fffffa8007bbb0e0}

Probably caused by : usbvideo.sys

Followup: MachineOwner

I did find you have a very obsolete driver, SSPORT.sys Aug 11 2005. This is a pre Vista driver. The process 32bit Port Contention Driver or SSPORT belongs to the software SSPORT or Port Contention Driver by Samsung Electronics.

I recommend that you update the driver or uninstall the program it is associated with. A driver this old can definitely cause problems.

I also recommend that you uninstall Norton. Norton is known to cause conflicts on some systems. It it is not the cause, you can always install it again.

Once you have done so, reboot and see if the problem persists. It it does, we will take another step.

 

[yahskaraghu]

Well, I tried googling and searching for SSPORT.sys on both Samsung and Microsoft's websites and found nothing but other references to people who've found the same badly out of date driver. The only Samsung product I have installed is a Samsung ML-2010 Printer, so should I just uninstall everything for that printer, then reinstall everything afterwards?

 

[CarlTR6]

Going through your drivers again, I found another old driver that I missed the first time:

mdmxsdk.sys Jun 19 2006 - mdmxsdk is a driver file from the company Conexant belonging to product Diagnostic Interface.

Suggest you update the driver or uninstall the program it is associated with.

 

[CarlTR6]

Go the Samsung website, and look for your printer model. See if there are updated drivers available for it. If not, it may be time for a new printer.

Here is a link I tried. I did not see any driver downloads; but I noticed they have updated manuals. Maybe you can find something there.

http://www.samsung.com/us/support/d...1&prd_ia_cd=&prd_mdl_cd=&prd_mdl_name=ML-2010

 

[yahskaraghu]

I tried googling and searching for all 4 drivers, usbccgp.sys, usbvideo.sys, SSPORT.sys, and mdmxsdk.sys, and didn't find a single legitimate update or anything like that for any of them. I'm not even sure what the Conexant Diagnostic Interface does, to be quite honest.
What do you recommend I do about each of these 4; Uninstall, leave them alone and hope that it was a one-time thing, or something else altogether? Thanks for your help!

 

[yahskaraghu]

Well, I went there and clicked the "Drivers" mini-tab, and a list of drivers popped up, so I installed the first one for Windows 7, so hopefully that takes care of any issues. This laptop was originally a Vista laptop, so that may be the reason for the old driver, though I haven't had any problems with this printer in the 6 months I've been running Win7 until now. In any case, I hope that takes care of it, though I'll certainly post back here if the BSoD shows up again.

 

[CarlTR6]

Don't worry for now about usbccgp.sys and usbvideo.sys. These are windows systems drivers.

Look Control Panel > Programs and Features and see if there is a diagnostic program by Coexant there. If there is uninstall out. Another option is to download and use [FONT=&quot]Revo Uninstaller[/FONT]

If you can't find the program, do a search for mdmxsdk.sys using Widows Explorer. Create a system restore point first and rename this file to mdmxsdk.bak. Then reboot. You can do the same procedure for SSPORT.sys. But keep in mind, you printer might not work without this driver. I think you probably will end up buying a new printer as there seem to be no updated drivers for it.

You can use SFC to check your existing system drivers. Click on the link for the tutorial.

It may have been a one time thing and you can see if it occurs again. I'm betting it will because of those obsolete drivers. Win 7 does not like obsolete drivers.

Let us know what you do and what works for the benefit of others. Good luck!

 

[yahskaraghu]

I ran the SFC scan, and it found no integrity violations. So, I'm going to wait a few days at least, and see what happens. Given that I've used this printer a number of times since installing Win7 without a single problem until today, I feel like it may have just been a one-time thing. However, if it does happen again, then I'll definitely try changing those drivers to .bak, and perhaps uninstalling this printer entirely and switching to my backup.

 

[CarlTR6]

Very good; let us know how everything turns out.

 

[sandeep1234]

Carl,

===
[/code]I did find you have a very obsolete driver, SSPORT.sys Aug 11 2005. This is a pre Vista driver. The process 32bit Port Contention Driver or SSPORT belongs to the software SSPORT or Port Contention Driver by Samsung Electronics.
===

I arrived at this post by googling when I had the same problem as was originally reported. I am wondering how you deduced on the obsolete driver ssport.sys from DMP file.

I looked into the DMP file and did not find anything other than usbccgp.sys in the bugcheck.