[SOLVED] 0000009f crash

[Robtl]

Hello,
Thank you for your help!
My problem is with a BSOD and a 0000009f crash.
I ran the appropriate MS hotfix in January 2015 after three crashes and no further repeats until 06-27-15.
I have attached the two requested files . . .
All help is appreciated - Thank you!
Regards,
Bob

 

[Patrick]

Under normal circumstances, a kernel-dump is need to debug 0x4 1st argument, but it's showing the driver causing the lock.

0: kd> kC
Call Site
nt!KiSwapContext
nt!KiCommitThreadWait
nt!KeWaitForSingleObject
hcw72DTV
hcw72DTV
hcw72DTV
ks!WPP_ThisDir_CTLGUID_AvStream
ks!WPP_ThisDir_CTLGUID_AvStream
hcw72DTV
ks!KsWorkSinkItemWorker
usbccgp!UsbcAcquireRemoveLock

0: kd> lmvm hcw72DTV
start             end                 module name
fffff880`09430000 fffff880`095c7e80   hcw72DTV T (no symbols)           
    Loaded symbol image file: hcw72DTV.sys
    Image path: \SystemRoot\system32\DRIVERS\hcw72DTV.sys
    Image name: hcw72DTV.sys
    Timestamp:        Fri Aug 15 13:54:54 2014

WinTV HVR-950 ATSC/QAM driver is supposed to release a lock, but it doesn't, therefore it's put into a wait state by KeWaitForSingleObject. Since we inevitably never release the lock, the system bug checks with 0x9F 0x4 1st argument.

Update or uninstall your WinTV HVR-950 ATSC/QAM drivers/device.

 

[Robtl]

Patrick,
Thank you!
I have emailed the findings to Hauppauge, as I believe I have the most recent drivers installed, and would prefer not to uninstall the device . . .
Best Regards,
Bob Miller

 

[Patrick]

You're welcome.