Results 1 to 7 of 7
  1. #1
    Star Lounger
    Join Date
    Mar 2011
    Posts
    64
    Thanks
    14
    Thanked 1 Time in 1 Post

    0000009f Crash Redux

    The same 0000009f crash occurred again last night, 5 1/2 months since the last crash in January 2015.

    Here is a link to my thread last January: http://windowssecrets.com/forums/sho...update-program

    Once more, it was while the computer was unattended, at a few minutes past 3 AM.
    All hardware is identical to that in January.
    I checked the current MS Hotfix and it seems to be the same one I ran back in January . . .
    As mentioned back in January, I installed a program called WhoCrashed.
    I have captured the MSInfo32.NFO file, the *.dmp file, the file generated by "Who Crashed" as well as the screen shot of the 'problem details' generated by the MS Action Center.
    I don't see anything that 'jumps out' at me . . .
    Is it possible that 5 1/2 months of MS patches may have tweaked the changes made by the Hotfix and (perhaps) I should run it a second time?

    All thoughts are respected!
    Thanks ahead of time,
    Regards,
    Bob Miller

  2. #2
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,490
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Probably better to collect some fresh data, Bob. Read and carefully follow this: http://www.sysnative.com/forums/bsod...8-7-vista.html

    Attach the required zipped folders back here and we can check them over for you - if the files are huge, upload them to somewhere publicly accessible like SkyDrive and paste the link.

  3. The Following User Says Thank You to satrow For This Useful Post:

    robtlmiller (2015-06-28)

  4. #3
    Star Lounger
    Join Date
    Mar 2011
    Posts
    64
    Thanks
    14
    Thanked 1 Time in 1 Post
    Satrow, again: Thank you!
    ASAP, I will follow the instructions on the sysnative web site.

    I did find it curious that Google Chrome "flagged" the web site as being "harmful":

    The site ahead contains harmful programs
    Attackers on www.sysnative.com might attempt to trick you into installing programs that harm your browsing experience (for example, by changing your homepage or showing extra ads on sites you visit).

    I used Firefox to access it . . .
    Regards,
    Bob Miller

  5. The Following User Says Thank You to robtlmiller For This Useful Post:

    satrow (2015-06-28)

  6. #4
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,490
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Harmful?! Someone at Google has a bizarre sense of humour then, I'll flag that up with the admin team at Sysnative, thanks for reporting it.

    EDIT: the Admin team are looking into it, at least one of them uses Chrome as default browser and doesn't see any such warning.
    Last edited by satrow; 2015-06-28 at 16:23.

  7. #5
    Star Lounger
    Join Date
    Mar 2011
    Posts
    64
    Thanks
    14
    Thanked 1 Time in 1 Post
    Satrow,
    Again thank you for your help!
    I posted the two files requested attached to an email in the sysnative's forum.
    Per your request, they are also attached to this email.

    P.S.: I have NO IDEA why I got that WARNING when using Google Chrome . . .
    I even "cleared browsing data" and tried a second time and got the same admonition.
    Again, thank you for your insight,
    Regards,
    Bob
    Attached Files Attached Files

  8. #6
    Star Lounger
    Join Date
    Mar 2011
    Posts
    64
    Thanks
    14
    Thanked 1 Time in 1 Post
    Hello again, Satrow:

    Sysnative just sent me a reply, telling me the cause is the driver for my Hauppaugue TV card driver (if I understood them correctly):

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

    Code:
    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
    Code:
    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 remove 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.

    I have forwarded their findings to the people at Hauppaugue and will keep everyone in the loop.
    Regards,
    Bob

  9. #7
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,490
    Thanks
    284
    Thanked 577 Times in 480 Posts
    That analysis and advice looks spot on, Bob.

    I'd remove it and then uninstall the drivers for it (it looks like it's USB). Wait until you get a fix/workaround from Hauppage before reconnecting/reinstalling it, no point in risking further blue screens until the.

  10. The Following User Says Thank You to satrow For This Useful Post:

    robtlmiller (2015-06-29)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •