windows thinks it's a duron (but it's not!)

[eklass]

not sure here, but i swapped out my odl athlon 850 for a brand new spiffy athlon xp 2000+. my mobo (asus a7v133) doesn't natively support it, so i had to flash to the latest bios (1009). not sure what's going on here, as i've got the mobo set to jumperfree, but the biod want sto auto-set it to 850/1133 (depending on bus speed). knowing it is a 1.67GHz, i manually set it to 133 x 12.5, and despite not all my ram being pc133, it seems to run... except windows thinks it's a duron! it reports an athlon xp 1.67 on bootup, but windows still insists it's a duron... and someone how my comptuer seems a bit slow... i get this jerky-skippy motion. i tried to confirm by finding a cpu detection program, and it reports the info below... any ideas?

p.s. note the cpue vendor and model vs. the cpu-id name string... what do i do!?!?


CPU Identification utility v1.9 (c) 1997-2002 Jan Steunebrink
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
CPU Vendor and Model: AMD Athlon XP P1700-P2700
Internal CPU speed : 1677.0 MHz (using internal Time Stamp Counter)
Clock Multiplier : Available only in Real Mode!
CPU-ID Vendor string: AuthenticAMD
CPU-ID Name string : AMD Duron(tm) Processor
CPU-ID Signature : 0681
³³³ÀÄ Stepping or sub-model no.
³³ÀÄ Model: Indicates CPU Model and 486 L1 cache mode
³ÀÄ Family: 4=486, Am5x86, Cx5x86
³ 5=Pentium, Nx586, Cx6x86, K5/K6, C6, mP6
³ 6=PentiumPro/II/III, CxMII/III, Athlon, C3
³ F=Pentium4
ÀÄ Type: 0=Standard, 1=Overdrive, 2=2nd Dual Pentium
Current CPU mode : Protected
Internal (L1) cache : Enabled in Write-Back mode

 

[ChampionAtTufshop]

i get same thing on a7v
cpuid=681....do you have a tbred b?

 

[lobadobadingdong]

pull the pc-100 and see what it does, it may be scaling down the fsb automatically and still thinks you have a 100mhz fsb instead of the 133 you inputed. at the current prices of pc133, why not go buy a stick of 256mb, after mir's you can usually get them for under or about $20. If your bios(latest flash) says it supports the XP's, then it shouldn't have a problem reporting it to windows, pc 133 is a hinderance to the XP's so I imagine with pc100 it would act like about a 1.2Ghz Athlon with all pc133 probably closer to the 1.4Ghz Athlon(non XP). A newer mobo and ddr would do that proc well.

800th post!

 

[eklass]

got a bit more info... from cpuid:

Cpu Name AMD Athlon XP (Thoroughbred)
Specification AMD Duron(tm) Processor
Family / Model / Stepping 6 8 1
Extended Family / Model 7 8
Package Socket A
Core Stepping B0
Technology 0.13µ


i'm planning on going full-on new mobo and ddr, but there's a lan party i'm going to on saturday... won't exactly have time to get it in 🙁

also, i think that 256MB of my RAM is pc100 and 256 is pc133, so pulling half would not be goof for 15 hours of battlefield this weekend...

i will pull it and see what happens as far as reporting it as a duron...

 

[ChampionAtTufshop]

if wcpuid shows it at 133mhz freq, then its at 133

its probably just the board mis detecting it
mine, on startup, sez its an amd athlon xp 1400mhz....which is correct....cept for the fact that its oced via mult lol to 1700mhz (100*17)
mymobo dont like high fsbs...

 

[Soulkeeper]

Originally posted by: ChampionAtTufshop
i get same thing on a7v
cpuid=681....do you have a tbred b?

really ? hehe i get the same thing on my A7V also only i'm in linux


it reall doesn't matter as long as the cache is seen and everything works
it's only a bug in some code somewhere responsible for displaying what yur running won't affect performance or anything

 

[ChampionAtTufshop]

Originally posted by: Soulkeeper

Originally posted by: ChampionAtTufshop
i get same thing on a7v
cpuid=681....do you have a tbred b?

really ? hehe i get the same thing on my A7V also only i'm in linux


it reall doesn't matter as long as the cache is seen and everything works
it's only a bug in some code somewhere responsible for displaying what yur running won't affect performance or anything

yea
im in xp lol

also, im at 1700mhz (default vcore heh....1800mhz needs like 1.85+ lol..) and in bios whenit starts up it sez 1400MHz (even though its at 1700MHz)
...but if i change freq to 101 (from 100....more like 100.9 cuz of good old asus ) it reports correctly (1700something MHz)

just a few bugs....whatever..it all works good so im happy haha

 

[eklass]

a7v133 here... i temporarily fixe dht eproblem by setting it to 100x12.5. at least windows isn't jerky now... i know it's not the full 1.67 i paid for (which i will get when i swap the mobo and ram)... but any way you slice the pie, it's 400MHz more than my old 850B

 

[eklass]

just as an update... i got my Giga-byte GA-7AXP Ulta motherboard in on Friday. That (wth native Athlon XP support) coupled with nifty Crucial DDR 2700 RAM, the system is smoothly sailing... now onto the vid card...

oh yes, and windows now correctly reports the correct processor