Since recivining my replacement 1600+ I have now been able to over-clock :D
A problem arised this morning though when i was setting it up to run at 1.73Ghz (163FSB) and do a stabilaty test whilst i was at work.
I know it's stable at 1.7Ghz (160FSB) but as i was taking it up 1 FSB at a time when I got to 162FSB it stoped detecting as an Athlon XP, and only came up as and athlon.
I know it'll detect a Athlon XP 2100+ (1.73Ghz) because i had it up to that the other night, but i can't understand why it won't detect now???
I also checked in XP sys propertys and wcpuid and niter of them come up as a XP either.
A problem arised this morning though when i was setting it up to run at 1.73Ghz (163FSB) and do a stabilaty test whilst i was at work.
I know it's stable at 1.7Ghz (160FSB) but as i was taking it up 1 FSB at a time when I got to 162FSB it stoped detecting as an Athlon XP, and only came up as and athlon.
I know it'll detect a Athlon XP 2100+ (1.73Ghz) because i had it up to that the other night, but i can't understand why it won't detect now???
I also checked in XP sys propertys and wcpuid and niter of them come up as a XP either.
Comment