MTDEW
Diamond Member
Wife has been running a Epox 8RDA+ mobo with a mobile barton 2500.
Been running solid now for months.
I had it set at 2200mhz with 1.8v (11 x 200fsb)
Anyway, system always ran great no lockups or issues.
Now one day she said she was cleaning and pc was left running at desktop as usual.
She came back and it was apparently locked up, she tried rebooting...it never did.
So heres where i come in, cleared cmos, no post, no beeps NOTHING!
Tried all the normal stuff to get it to post, no go.
So ok, i fugure darn cpu must of took a dump.
Had a desktop barton sitting here, so i threw that in and her pc and all was good.
NOW THE WIERD PART!
I have an old abit NF7-S v1.0 mobo sitting here and some Kingston "value ram" DDR 400 sticks.
So i though what the heck, i threw her "dead" mobile barton and the rest of the hardware into and extra case.
And what do ya know, it posted/booted right up.
So after playing with it for awhile i decided to set it to where i had been running ot b4.
11 x 200 fsb / 1.8v, sure enough it did it easily just as it did b4.
Installed HL2 to see how it ran with the setup and and old 9700 pro i had thrown in there.
(btw: HL2 ran surprisingly well on a 9700 pro)
So for the next 2 days it ran just fine.
3rd day i started the pc, it came "cpu is unworkable or has been changed"
Ok, reset bios to defaults, darn thing boots up as a Duron 2000 (20 x 100fsb)
And thats ALL it will boot as!
No matter what changes i make in the bios, it WILL NOT boot at any other settings other than the "system defaults".
Tried 3 different bios on the NF7 -S - nope same duron crap
So i stuck in back into the epox 8RDA+ board, SAME THING! its recognized as a Duron 2000 (20x100fsb).
And all results are same as in the abit board, darn thing wont even post with ANY other settings.
Tried upping/lowering voltage, and just about every combo multiplier/fsb you can think of, always same thing.
"cpu is unworkable or has been changed" "defaults loaded" - Duron 2000 cpu.
So ive got a mobile barton 2500 with an indentity crisis in two different mobos.
I didnt even know anything like this was possible, it woulda been more believable if the thing would have just died...LOL
Any ideas?
Anyone ever here of this happening to an OCed cpu? (it being detected as an entirely differen cpu)
Been running solid now for months.
I had it set at 2200mhz with 1.8v (11 x 200fsb)
Anyway, system always ran great no lockups or issues.
Now one day she said she was cleaning and pc was left running at desktop as usual.
She came back and it was apparently locked up, she tried rebooting...it never did.
So heres where i come in, cleared cmos, no post, no beeps NOTHING!
Tried all the normal stuff to get it to post, no go.
So ok, i fugure darn cpu must of took a dump.
Had a desktop barton sitting here, so i threw that in and her pc and all was good.
NOW THE WIERD PART!
I have an old abit NF7-S v1.0 mobo sitting here and some Kingston "value ram" DDR 400 sticks.
So i though what the heck, i threw her "dead" mobile barton and the rest of the hardware into and extra case.
And what do ya know, it posted/booted right up.
So after playing with it for awhile i decided to set it to where i had been running ot b4.
11 x 200 fsb / 1.8v, sure enough it did it easily just as it did b4.
Installed HL2 to see how it ran with the setup and and old 9700 pro i had thrown in there.
(btw: HL2 ran surprisingly well on a 9700 pro)
So for the next 2 days it ran just fine.
3rd day i started the pc, it came "cpu is unworkable or has been changed"
Ok, reset bios to defaults, darn thing boots up as a Duron 2000 (20 x 100fsb)
And thats ALL it will boot as!
No matter what changes i make in the bios, it WILL NOT boot at any other settings other than the "system defaults".
Tried 3 different bios on the NF7 -S - nope same duron crap
So i stuck in back into the epox 8RDA+ board, SAME THING! its recognized as a Duron 2000 (20x100fsb).
And all results are same as in the abit board, darn thing wont even post with ANY other settings.
Tried upping/lowering voltage, and just about every combo multiplier/fsb you can think of, always same thing.
"cpu is unworkable or has been changed" "defaults loaded" - Duron 2000 cpu.
So ive got a mobile barton 2500 with an indentity crisis in two different mobos.
I didnt even know anything like this was possible, it woulda been more believable if the thing would have just died...LOL
Any ideas?
Anyone ever here of this happening to an OCed cpu? (it being detected as an entirely differen cpu)