Solved Graphics WEI changed from 6 to 7.3 up after Re-assesment

[dorian hawkmoon]

After I installed the extra 2GB to my 4GB RAM, I clean installed (from x86) to Win 7 x64. My first WEI score was 6.0 , after a reassessment Desktop and also Gaming WEI score went up to 7.3! Graphics driver was latest at the time of both assessments, the only changes were :-

1) I updated DirectX after a game wasn't running because of an old/non-existent dll file
2) Turned off unnecessary desktop animations (menu, boxes etc.)
3) Installed Service Pack 1 and clean installed (after using AMD Display cleaner of Driver Fusion) the same driver.

What gives? I mean, I am glad...but I won't be if it's a fluke or some other potential problem, sitting... waiting !

 

[Wordsworth]

I expect installing Service Pack 1 made the change. I've never read anything about 7 SP 1 and WEI corrections, but Vista's Service Pack 1 improved graphics WEI scores for some cards because it fixed an algorithm used to determine the WEI graphics score. Windows 7 SP 1 was released about the time AMD brought the 6000 series to market which may play a role here as well if AMD was looking after things playing well together.

 

[dorian hawkmoon]

Ok, I see, thanks-that's a good thing then, I guess!. Btw. I sometimes face an occasional BSOD once in every 20/30 restart or startup cycles- 'HyperTransport Watchdog Timeout Error', can this be because of AMD driver? If so should I use drivers (always a little old) from MSI (http://www.msi.com/product/vga/R6770-MD1GD5.html#/?div=Driver&os=Win7%2064) rather than latest AMD video drivers from AMD site?

 

[Wordsworth]

I'd make certain you have the latest AMD drivers for the video card installed rather than those from MSI. I'd also take the card out and re-install just to make certain it is seated properly. From looking at your System Specs, I'm sure you know I'd also question the mix of RAM you have in the system. If drivers and re-seating the card don't resolve the problem, you might try going with just the Corsair memory only and see if that resolves it.

The HyperTransport error does have to do with CPU bus technology in AMD systems. You can do a search here for info on it or start a new thread in the BSOD Help and Support Forum here if necessary.

 

[stormy13]

Not driver related,

"HyperTransport Watchdog Timeout Error" (0x00000124 code BSOD) - TechSpot Forums

"HyperTransport Watchdog Timeout Error" (0x00000124 code BSOD) - CPUs - CPU-Components

On AMD based motherboards stop 124 errors are usually due to something either not getting enough voltage or defective on the motherboard. Start with setting the CPU voltage manually,



Start around 1.35V and see how if it still happens. If it does then go back and increase it one notch a see if it still happens. Don't go any higher than 1.4V.

If that doesn't fix it back it off back to 1.35 and try increasing the HT voltage,



starting at 1.25V, and working up to 1.3V if necessary.

If all that fails then it is likely something else on the motherboard, and the board should probably be replaced, or at least RMA'ed if still under warranty.

 

[dorian hawkmoon]

@Wordsworth: This BSOD started to occur long before I installed the extra RAM,it just happened to resurface after I installed x64 and RAM, and started rebooting a lot to install software & drivers. I checked, the gpu is seated firmly as far as I can see.

@stormy13: Okay, I see your point also. To tell you the truth, this BSOD started after I changed my cpu (& mobo twice:first new one from Gigabyte was faulty and restarted a lot from BOSDs) from older athlon II x2 240 to the present config. I was a wee bit suspicious/dissatisfied with both! I didn't get the Athlon II X3 445 I was angling for then. I will try to tinker with the voltages as you have suggested...

 

[Wordsworth]

Yea, I was just covering the quick and easy stuff because one can always hope there's a quick fix. I mentioned looking into the HyperTransport at the end because from what I've read it looks to be where you'd end, unfortunately. I've never built an AMD system but from what I've seen concerning this stormy13 is likely right about the mobo eventually needing replacing.

 

[dorian hawkmoon]

Thanks guys, fought with the issue and as some of you already know- had to change the darned mobo, and the cpu along with it! Talk about luck...the Asus was a replacement for another DOA mobo :shock:, or maybe it's just that the PC parts are not what they used to be.