HD 3870 Crash??

[Paul343]

Good day,

I have installed the C++ patch and MS run-time is installed (many times). All of the current drivers and BIOSes are installed for all hardware. All software is fully up to date.

Using the lastest release of GB-PVR, the system just reboots when PVRX2 is executed. (The system runs fine with in the original style in this new release...)

Does anybody else have problems with the HD 3870 card? I am not sure, but I think there maybe a driver issue with the ATI drivers. (Windows reports a driver conflict after the reboot).

I am hoping that there is someone out there who has no problems with this card, so I can eliminate it as a cause.

Thanks, I would hate to have to exchange the card, as GB PVR is used all the time....



Basic System:
Maximus Formula
Sapphire HD 3870
Win XP
ATI 550

[gEd]

the driver conflict may be the cause of the crashes. Either that, or you have a faulty card.

see if you can download driver cleaner to remove all the ATI and any other old drivers and start again. Maybe you still have drivers from your previous card lying around.

[Paul343]

Thanks for the reply,

Well, I started from a reformat..... FUN

It seems that I can open PVRX2 with the ATI drivers now, and also with the Omega drivers. This is good. The catch...

As soon as I try to configure a capture device, the program shuts down. Windows does not reboot as before, so I am better off, but still some road to go down.

I am trying different drivers (older that is) to see if one will work.

GBPVR Config "sees" the card - but only for a second (literally) before it closes.

I'm a bit lost on this one. Does anyone have any other ideas?

Thanks,

Paul

[donschjr]

Search the boards, there is a fix for this problem in a couple of similar threads about config crashes.

[Paul343]

Thanks, I will. Still going through motions... The TV card works, (get all of the channels on the tuning assistant) so I count that as progress.

Hopefully its just something simple that I overlooked.

[Paul343]

The patch "NativeUtilities.dll" fixed the issue!

All is excellent,

Thanks to all that responded and to Sub for making the fix.

Cheers,

Paul