• 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.

Really strange problem

Timmah

Weaksauce
Joined
Oct 15, 2003
Messages
70
I just built a pc for my cousins girlfriend. It's a Biostar KM400 board with a duron 1.6 and 256mb crucial ddr 266. well the install of win xp goes great. accidentally didnt jump it to 266 fsb so it was running at 1.2. i fix the jumper and its now running at 1.6 but now when you goto system properties in xp it says the following

AMD Duron(tm) procu{s[]}

WTH!!! never seen that before. when the mobo is clocked at 100 fsb and the duron at 1.2 it shows up normally, "AMD Duron processor.

i have no idea. i'm testing it with prime95 for stability now. any ideas guys??
 
ok, I assume you get the weird cpu ID when you are booting. It should not be a problem, as long as the system works fine. Now if the system hangs, locks up, doesn't boot properly, etc., you might want to clear the bios.
Also, a bios update may fix the incorrect id. Does it mean you system has a real problem, no, as long as that is the only symptom showing...
 
Originally posted by HvyMtl
ok, I assume you get the weird cpu ID when you are booting. It should not be a problem, as long as the system works fine. Now if the system hangs, locks up, doesn't boot properly, etc., you might want to clear the bios.
Also, a bios update may fix the incorrect id. Does it mean you system has a real problem, no, as long as that is the only symptom showing...


It shows up in windows. It's been running Prime95 now for 6 hours @ 100% cpu load and no errors yet. I feel it's a "cosmetic" error. I'm going to update the bios. Thanks!!
 
Back
Top