When I get the crashes it doesn't give the BSOD, but it'll freeze the screen, then I lose the display entirely -- it's usually necessary to power off at that point, since even a hard reset has no effect. Other than that it sounds just like the problem I was/am having -- I didn't mention that I *thought* it might be on channels with poor signal, or where the tuner had trouble locking on, because I wondered if it was either my imagination or symptoms of a pending crash.
I could never backtrack successfully to 8.2 though -- I came very close in XP, but then had the problem/crashes occur on the avivo-related pages in CCC. OTOH I had no problems with tuning crashing the system after going back to 8.2. In my case running the channel scan in CMC for the analog tuner was guaranteed to crash 8.3. Disabling my Audigy 2 sound card helped -- updating CPU drivers hurt dramatically -- but nothing I did, including turning off anything that started with XP & fooling with running processes cured the problem. Adding .NET 3.5 did seem to help a bit.
Since I never had that sort of problem from anything ATI over the course of almost a decade I didn't have a good backup with 8.2, so I moved back to 8.3, stuck now waiting for 8.4 with fingers crossed. I was thinking that if 8.4 didn't do it there's always that new Hauppage device coming out with HD component capture, but now I'm thinking I may have to deal with it anyway if you're getting crashes from the HomeRun.
I'd been playing with digital tuner issues in Vista -- I haven't found an easier cure or a lot of documentation on BDA in Vista, so it looks like using XP drivers *may* be the best solution for me for now. FWIW I *think* that Vista &/or DX 10 introduces different, separate methods of handling BDA stuff, & the Vista 650 drivers work with whatever new methods, but not the older stuff like XP & most non-MS apps use. *Maybe* with these crashes we're seeing the results of driver code that's starting to include more DX 10?
One thing I did find was installing .NET 3 or 3.5 adds the option to use the new evr video screen rendering, as opposed to the old vmr9... For me using evr helps stability a whole lot, so maybe it's something you'd want to check out?
I could never backtrack successfully to 8.2 though -- I came very close in XP, but then had the problem/crashes occur on the avivo-related pages in CCC. OTOH I had no problems with tuning crashing the system after going back to 8.2. In my case running the channel scan in CMC for the analog tuner was guaranteed to crash 8.3. Disabling my Audigy 2 sound card helped -- updating CPU drivers hurt dramatically -- but nothing I did, including turning off anything that started with XP & fooling with running processes cured the problem. Adding .NET 3.5 did seem to help a bit.
Since I never had that sort of problem from anything ATI over the course of almost a decade I didn't have a good backup with 8.2, so I moved back to 8.3, stuck now waiting for 8.4 with fingers crossed. I was thinking that if 8.4 didn't do it there's always that new Hauppage device coming out with HD component capture, but now I'm thinking I may have to deal with it anyway if you're getting crashes from the HomeRun.
I'd been playing with digital tuner issues in Vista -- I haven't found an easier cure or a lot of documentation on BDA in Vista, so it looks like using XP drivers *may* be the best solution for me for now. FWIW I *think* that Vista &/or DX 10 introduces different, separate methods of handling BDA stuff, & the Vista 650 drivers work with whatever new methods, but not the older stuff like XP & most non-MS apps use. *Maybe* with these crashes we're seeing the results of driver code that's starting to include more DX 10?
One thing I did find was installing .NET 3 or 3.5 adds the option to use the new evr video screen rendering, as opposed to the old vmr9... For me using evr helps stability a whole lot, so maybe it's something you'd want to check out?