Flashing banner causes 100% cpu???

[CPSLOJester]

Check out this banner that is located at the top of www.wcfords.com ...it will be the banner that says "Get your free WCFord sticker today!", if you don't see that hit reload until you do.

Ok, my system does the weirdest thing. When viewing this banner, my cpu usage will spike up to 100% when the banner flashes when "today" appears. Any ideas why? I've tried a whole bunch of ATI drivers and Omega drivers, I reinstalled Win2k yesterday and tried with the default IE 5.0, then tried IE 5.5, and now 6.0 and still no dice. None of my friends have this problem and they all have non-ATI cards so this leads me to believe that it's a ATI driver problem. Anyone else having this problem and know a fix? If you have a Radeon and Win2k or XP watch your CPU usage as the banner flashes, does it go up at all?

 

[NateSLC]

I have a Radeon 64 DDR VIVO and Windows XP w/ Athlon 1.33Ghz..

And, yes, it happens to me too.

 

[ShadowFox]

i have an athlon 1.2@1.4 and a Radeon 32mb DDR and it boosts it to 46%

 

[ShadowFox]

you know reinstalling Win2k for a problem with a gif image is.... ummmmm..... right

 

[Splork]

No problem here. Course I have Seti running.

-sp

 

[CPSLOJester]

Well it's nice to know that I'm not alone on this problem at least...stupid ATI and their crappy drivers.



<< you know reinstalling Win2k for a problem with a gif image is.... ummmmm..... right >>



I've been in need of a reinstall for quite some time so I figured why not see if the problem would go away after reinstalling....

 

[RedShirt]

Same prob here.

Athlon 1.33, Radeon 64 Vivo, 512 MB RAM.

 

[BatmanNate]

It boosts my CPU usage up to all of 2% average between the both of them, running a pair of XP 1500's on a GeForce2 GTS 64mb, WinXP.

 

[passign]

hehe, whens there's a bug..there's a reinstall::)))))))))))))))))))))))

 

[Nefrodite]

using a ghost image saves reinstallation time

 

[CPSLOJester]

Does anyone running a Intel/Radeon system have this problem? So far I've only people with Athlons have reported back so it might be an AMD/Radeon bug.