Athlon XP Mobile 2600+ fried? and anyway to fix the blue screen?

[Liguid]

Edited: ** Thanks Guys **
And yah it looks like i have to get a new processor

-

ok heres the story... i recently bought a Athlon XP Mobile 2600+ from someone on this forums. i got it and put it in my brothers old motherboard. he has a abit kx7-333. it booted up as 500 or 600 mhz so i clocked it to 195x10 to run at 1.95ghz to test it. after that it stopped working even after i rested the cmos. so i thought it was a motherboard issue and i just got a a7n8x-e deluxe. and it still does not work. i tried sticking in a athlon xp 1600+ and that booted up fine except for the blue screen i get from xp cause of different mobo chipset. but is there any other way to check if the processor is really dead?

Also im getting a blue screen after in installed the a7n8x-e deluxe. so im wondering if there is a way to fix the blue screen. i heard rumors about changing the windows folder name?

please let me know asap. i need to get my brothers computer up and running before his spring break is over. he needs it for school.

 

[imported_Phil]

CPU dead.

 

[Fern]

Regarding Blue screen resulting from different chipset drivers, see HERE. This is an AT article on changing mobo/drivers. Look at the bottom of the article under "Misc". It discusses a short cut method to get chipset drivers changed.

Fern

EDIT: I se nothing in what you wrote that should cause a mobile 2600 to burn up/fry. 10 x 195 is only 1.95ghz. Did you up the vcore substantially?

 

[Slikkster]

"Blue Screen" doesn't tell us anything. There's thousands of them. How about quoting exactly what the screen says.

 

[FlyingPenguin]

You need to do a Repair install of WinXP after swapping mobos (unless the two mobos use the same chipset). Boot from the XP CD and choose "Repair" from the 2nd menu after the EULA (NOT "Repair from Recovery console" in the first menu).

This wipes the device manager and re-installs WinXP generic drivers. You then have to install all the latest drivers yourself afterwards. You must also install all the Windows updates again afterwards. NOTE: Make sure you enable the firewall or you're behind a router BEFORE going online until you install all the updates or you'll immediately get infected by the Sasser or MSBlaster virus (unless your XP CD is slipstreamed to SP2).