TV-card problem

  • Thread starter Thread starter Matti Paalanen
  • Start date Start date
M

Matti Paalanen

Hi!

I have had hard time trying to get tv-card working on W2K. I have Asus
mobo with latest Via drivers, Radeon 9100 with latest catalyst drivers
an hardware configuration where I took off Audigy because I first
thought that it would be the source of my problems. TV-card is
Hercules SmartTV Stereo.

I can install the card and drivers ok, without any problems and I can
get the video working on VirtualDub in default mode, although the
picture is greyscale for some reason, but when I try to open for
example InterVideo WinCoder or CyberLink PowerVCR, I get BSOD when
they are loading. Basically the main information is:

Stop: 0X0000001E

KMODE_EXCEPTION_NOT_HANDLED

8045647C base at 80400000 ntoskrnl
BFD58136 base at BFD52000 stream.sys


I haven't found any good information on what is the problem here, but
on one thread one guy had similar problem and somebody said to him
that it's probably bug in Ati code?

So I was just wondering if somebody has had same problem and figured
out the reason/solution? Or does anybody have any good advice, what to
try next?

Thanks!

-Matti Paalanen
 
Matti Paalanen said:
Hi!

I have had hard time trying to get tv-card working on W2K. I have Asus
mobo with latest Via drivers, Radeon 9100 with latest catalyst drivers
an hardware configuration where I took off Audigy because I first
thought that it would be the source of my problems. TV-card is
Hercules SmartTV Stereo.

I can install the card and drivers ok, without any problems and I can
get the video working on VirtualDub in default mode, although the
picture is greyscale for some reason, but when I try to open for
example InterVideo WinCoder or CyberLink PowerVCR, I get BSOD when
they are loading. Basically the main information is:

Stop: 0X0000001E

KMODE_EXCEPTION_NOT_HANDLED

8045647C base at 80400000 ntoskrnl
BFD58136 base at BFD52000 stream.sys


I haven't found any good information on what is the problem here, but
on one thread one guy had similar problem and somebody said to him
that it's probably bug in Ati code?

So I was just wondering if somebody has had same problem and figured
out the reason/solution? Or does anybody have any good advice, what to
try next?
Click to expand...

It's a driver problem, definitely not the first for ATI.
Contact them.

Rick
 
Back
Top