BSOD with

[affeking]

I recently added a Hauppauge Colossus capture card to my HTPC, and since then have been encountering BSODs.

I'm already gone through quite a lot of troubleshooting, to the point that I opted to reinstall windows, primarily with the assumption that old drivers were causing problems. Turns out - they weren't. Right now I'm running a fresh install with nothing more than my video card and the Colossus installed, and I'm getting BSODs that appare to occur when the Colossus is being used.

I should also note that Windows froze at one point while installing updates (post install) and gave a BSOD, but no minidump. It was a random security patch, and it installed with no issue later. However, I have to wonder if it or the other updates it was working on may have some problems. Granted, the BSOD appeared on this fresh copy, so it's likely the Colossus was the root cause.

Here is what I'm running:

Motherboard: Gigabyte 965P-DS3 (rev 2.0)
Video Card: GIGABYTE GV-NX86T256H GeForce 8600 GT 256MB 128-bit GDDR3 PCI Express x16
Capture Card: Hauppauge Colossus
Other: HDHR (HD Homerun) netwokred ATSC tuner; external MC IR blaster (which I have now disconnected, but hasn't made a difference)
OS: Windows 7 Premium

Again, this happens when running Media Center.

I'm attaching two logs. I don't remember the specifics on when the first appeared, but the second was when I attempted to tune a channel in MC that was using the Collosus.

Appreciate any help you can provide!

Jeff

 

[Ace]

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.

(Error: 0x9F)

This would be your hcwD1cap.sys driver which is your Hauppauge Colossus driver. If I were you I would just uninstall it. Open Windows Media Center to test.

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

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

*** WARNING: Unable to verify timestamp for hcwD1cap.sys
*** ERROR: Module load completed but symbols could not be loaded for hcwD1cap.sys

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: cf9b4ae0

DEVICE_OBJECT: 863a4538

DRIVER_OBJECT: 863a4720

IMAGE_NAME: hcwD1cap.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e1b21de

MODULE_NAME: hcwD1cap

FAULTING_MODULE: 9235e000 hcwD1cap

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 82856054 to 828f6e34

STACK_TEXT:
82940a94 82856054 0000009f 00000003 8519ac40 nt!KeBugCheckEx+0x1e
82940b00 828558e8 82940bb8 00000000 8294d280 nt!PopCheckIrpWatchdog+0x1f5
82940b38 8288418d 8295ba20 00000000 0509bfb5 nt!PopCheckForIdleness+0x73
82940b7c 82884131 82943d20 82940ca8 00000002 nt!KiProcessTimerDpcTable+0x50
82940c68 82883fee 82943d20 82940ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82940cdc 8288234e 000bfe12 875e1c48 8294d280 nt!KiTimerExpiration+0x25c
82940d20 82882178 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82940d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_hcwD1cap.sys

BUCKET_ID: 0x9F_IMAGE_hcwD1cap.sys

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

0: kd> lmvm hcwD1cap
start end module name
9235e000 9238d000 hcwD1cap T (no symbols)
Loaded symbol image file: hcwD1cap.sys
Image path: \SystemRoot\system32\DRIVERS\hcwD1cap.sys
Image name: hcwD1cap.sys
Timestamp: Mon Jul 11 10:16:30 2011 (4E1B21DE)
CheckSum: 00034BA9
ImageSize: 0002F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[affeking]

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.

(Error: 0x9F)

This would be your hcwD1cap.sys driver which is your Hauppauge Colossus driver. If I were you I would just uninstall it. Open Windows Media Center to test.

Thanks Ace!

I agree that the issue is definitely caused by the Colossus. When I pull it out of there, everything works just fine. I'm not sure the dump really helps to clarify this, but what I'm now trying to determine is whether this is faulty hardware, or an incompatibility between my hardware and this card. Any thoughts?

Hauppauge sure doesn't know how to develop a driver.

Thanks,
Jeff

 

[Ace]

You can check the software vendor to determine compatibility/support for your system here: http://www.hauppauge.com/site/products/data_colossus.html

It could be faulty, but from my reviews lots of other people are having issues with this driver, so it's a known problem.

I would try downloading and installing any updates and device drivers for your computer from Windows Update... Make sure everything is up to date. Also scan your computer for computer viruses, and check your hard disk for errors. Unless you run Windows 2000, 0x3 just means that a device object has been blocking an IRP for too long a time, which is also indicated in the bug check for the minidump

 

[affeking]

Well, it definitely fits the system specs. They didn't exactly test this with every hardware combination, though. I suspect right now it's not playing nice with either my video card or motherboard. I have it running in another machine right now as a test. It's not a perfect test, as I don't have everything set up identically, but it's close. So far it's been running a couple of hours without incident.

Silly question for you. The minidump mentions a power state failure. Can this have something to do with the sleep settings in windows or the BIOS? Is this a problem that occurs when the system tries to sleep? It seems unlikely, as I've had it happen when I was actively using it. I only ask as a bit of what I've read on this error pointed towards power management issues.

I'm still encouraged that it's working at the moment in another PC. If it makes it the night, I'll hook the card up to some live recording material (right now it's recording screensavers from the dish box) and see if that makes any difference. Then I'll try a video card transplant. I'm not really sure where else to go with it.

Thanks

 

[Ace]

No, I don't see that being possible. The bugcheck shows parameter (0x3) which means an IRP was being blocked for too long of a time, the usual is around 10 mins.

This is most likely with the hauppage driver on that system. The blocked IRP address in the arg on the other dump shows: 0x87dbe9d8

0: kd> !thread 82936380
GetPointerFromAddress: unable to read from 8296b84c
THREAD 82936380 Cid 0000.0000 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from 8292b4dc
Owning Process 82936640 Image: <Unknown>
Attached Process 85103a40 Image: System
ffdf0000: Unable to get shared data
Wait Start TickCount 224563
Context Switch Count 2702745
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address nt!KiIdleLoop (0x82879e00)
Stack Init 82929fd0 Current 82929d1c Base 8292a000 Limit 82927000 Call 0
Priority 0 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
ChildEBP RetAddr Args to Child
82929a94 828c8eef 0000009f 00000003 851b6d70 nt!KeBugCheckEx+0x1e
82929b00 828c8f68 82929ba0 00000000 82936380 nt!PopCheckIrpWatchdog+0x1f5
82929b38 8287c019 829446e0 00000000 9147da28 nt!PopCheckForIdleness+0x73
82929b7c 8287bfbd 8292cd20 82929ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82929c68 8287be7a 8292cd20 82929ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82929cdc 8287a00e 00036d34 85b83a90 82936380 nt!KiTimerExpiration+0x25c
82929d20 82879e38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82929d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38 (FPO: [0,0,0])

*** Error in reading nt!_ETHREAD @ 85103768

The thread it's having trouble reading from: 0x85103768

Irp is active with 3 stacks 2 is current (= 0x87dbea6c)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [ 16, 0]   0  0 851b6d70 00000000 9312c1e8-86452520    
	       \Driver\PnpManager	ks!CKsDevice::CompleteDevicePowerIrp
			Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 8518bdb8 00000000 828859d9-87c696e8 Success Error Cancel pending
	       \Driver\hcwD1capture	nt!IopUnloadSafeCompletion
			Args: 00021100 00000001 00000001 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-879b59b0

Still debuggning to see what I can find with the thread and blocked IRP though.

Edit: You are testing this on another Windows 7 machine or is it a different OS entirely?

 

[michelsmith]

Hi,

Do you remember making any recent changes to the computer prior to this issue?

I would suggest you to follow the steps in the link and check if the issue persists:

http://windows.microsoft.com/en-us/windows7/Resolving-stop-blue-screen-errors-in-Windows-7

Also check event viewer for error follow the steps in the link:

http://windows.microsoft.com/en-US/windows7/What-information-appears-in-event-logs-Event-Viewer

 

[Ace]

If you were to use Event viewer, the things to pay attention to would be the warnings and errors for the Program and System Events, being that when you start up Windows Media Center it might give you some additional information on any errors with your Hauppage, and as well as the System Event logs.

Sidenote: If you would be willing to provide some extra information as well, I could provide you with a tool I developed specifically for Windows 7 systems that will provide information about system packages, services, processes, BIOS information, boot info, CPU, and even networking information, however you'll need to install or make sure that you have .NET framework 4 installed onto your system to run it. You can use it for personal use if you like as well, but I developed it specifically dedicated to my own forum.

I had notified another Microsoft MVP to take a look at this thread, so he could possibly respond as well here, and may have an answer for you if I can't help you.

 

[affeking]

Basically, the last event I see in the System log when it freezes without me actively using it is:
"The Windows Media Center Scheduler Service service entered the stopped state."

Preceding that are messages showing it entering and existing that state without issue. So, it could just be a coincidence that this is the last message I see, as nothing else was really going on during this timeframe.

At another point, I see "The Hauppauge Media Center Service service terminated with the following error: %%-1", but this wasn't a time I saw a BSOD. This may be a time when it seemed to have frozen tuning and I had to restart...I don't recall for certain.

I have trouble recreating it on the machine I'm currently running in. It just seems to fail between 12-24 hours.

I can do some more testing on the original machine, and provide some more logging from there. It seems to happen a lot more 'on demand' on that box. Basically just using the tuner triggers it. Let me know if there is a specific log I should be looking at aside from System. This is where I see the errors related to the BSOD, but I am not sure where else to look. The 'Media Center' logs are completely clean.

I'd consider running the tool you mentioned. I already have .NET on the other machine in any case.

Thanks!