Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
1. All dumps are listed above.Ranma_Sao said:Help me to help you:
http://www.hardforum.com/showthread.php?t=828696
Glow said:1. All dumps are listed above.
Glow said:I wrote it funny
I emailed their tech support. waiting for anything. I have unistalled the drivers so my HP is just sitting there nothings bluescreened yet so I dunno if it's the root of all the prblems then I'll just leave it out for now. I have no idea why it would cause this thoughmikeblas said:Let me try to be clearer. The code that's faulting is in the driver for your Hauppague card. Without any more information from you, we can't make a more specific diagnosis.
Even with more information from you, I don't think the diagnosis would be any different: we don't have the source for the Hauppague drviers, and therefore can't figure out what specificly is causing the driver to fault.
What did Hauppague say when you contacted them?
Glow said:I have no idea why it would cause this though
Philip said:Here is what MS has to say about that stop error.
http://support.microsoft.com/?kbid=330182&sd=RMVP
mikeblas said:The 150MCE card that Glow is using is designed for Windows XP Media Center, not Windows XP. The driver will interact deeply with an MPEG decoder provided by Media Center Edition, and that decoder isn't present on plain Windows XP installations.
da sponge said:IIRC media center provides NO mpeg decoder by default. The card manufacturer does. As long as Glow has installed the hauppage mpeg decoder or any MCE compatible decoder, the interaction between the driver and decoder should not be an issue (unless there's a bug, but I'd think that would be independent of MCE bs regular XP).
mikeblas said:Your recollection doesn't match what Hauppague says on their website about the card and the decoders.
In the majority of cases, a bug is exactly what causes a blue screen.