• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

7970 Issue - RMA Time?

Eluder79

Limp Gawd
Joined
Feb 4, 2008
Messages
383
So, on Friday, I decided to try out the developer release of the 12.4's which many have been raving about. Prior to that, I updated to the latest version of Aida64 beta and updated my NIS 2012 just for the heck of it. Upon a reboot, I noticed that my system hung at the Windows 7 boot logo. I thought nothing of it and reset the machine and it booted into Windows ok. From there I upgraded the drivers to the 12.4's and tried running a game to see what kind of improvements that may be had with this driver set.

So first thing I tried is BF3 and when I went to resume my campaign, during the load process it hard locked. I found this odd since I am not OC'ing my cards at this point, just left them stock to see how it runs. Figured it was just a fluke, so I loaded BF3 again and once again, it hard locks. At this point I figured it's a crappy driver set, but I tried Dirt 3 since this is another DX11 title. Same thing here, the game hard locked before I could even get past the menus.

At this point, I attributed this issue to the drivers, so I uninstalled the set, ran driver cleaner to be safe and reinstalled the 12.2 WHQL set. Upon boot up into Windows, it hung on me at the Windows boot logo again and I started to wonder wtf is going on. Tried loading up BF3 and Dirt 3 again and it hard locks again, even with the 12.2's which I never experienced before. At this point, I got a little fed up and decided it's time for a format since I haven't done it in roughly a year. So I proceeded the format and reinstall of Win7 Ultimate x64.

Things were running ok, but I had yet to install the 12.2 CATs as I was more concerned with getting as many core drivers and apps reinstalled. Installed the 12.2's and had the lockup at the Windows boot logo again. So at this point, I decided to remove one of the GPUs (the Asus) and try again. Things boot ok at this point and I started to test the Windforce 7970 on its own. It seemed to run ok through the Dirt 3 bench, but I ran it again for good measure. This time I noticed an odd hitch, the game froze/stuttered for a split second, but the oddity with this freeze was that the card's fan completely shut off at this point, so it's as if it the card was dying or something. I tried a 10 run bench of Metro 2033, and it did it somewhere around bench run 6 or 7.

So, now I decide to reset my bios by yanking the CMOS battery, and also decided to remove the Windforce and try the DCUII as a standalone instead. So far the Asus hasn't had this odd stutter/freeze issue that the Windforce experienced, so I'm starting to wonder if the Windforce is somehow going bad on me.

Anyone have any ideas what this stutter and hang at bootup with CFx could be? I thought originally it was bad drivers, but a format should obviously have resolved that. Thanks.
 
Are you loading the AMD HDMI sound drivers and the Realtek drivers? Whenever I do both I have problems so I don't install the AMD HDMI sound drivers.
 
I have never had issues with installing Realtec sound + ATI HDMI sound + My headphone Amp DAC
 
Yes, I have installed the latest realteak drivers as well as the ATI HDMI drivers.
Note that my system doesn't appear to exhibit any issues with the Asus card as a standalone.
I'm going to try the Gigabyte again since I've yanked the CMOS batter and reset my BIOS. It could be motherboard related, but that I'm not sure of. Trying to isolate the issue still you could say.
 
Not from what I've experienced.
This problem is new, as my CF setup was running quite well for a month at least.
 
So this problem went away for a few weeks after I yanked the CMOS battery, but Sunday night, the problem reared its ugly head again and I'm baffled as to what is causing it.
I've tried running a single card in both PCIE slots and things seem ok right now, but once I pop 2 cards in, it starts to act up again...

Anyone have any ideas?
 
The hitching is pretty much gone, it's the hard locking that is now the issue...
 
Back
Top