Installed a new cpu and my pc went boom
Tags:
Last response: in CPUs
Upgraded my 1800 xp to 2500 barton today, found out my a7v266-e mobo doesn't suppport it very well. ANyway i goto work with pc on as always and when i came back windows was frozen. Rebooted and after windows xp sp2 loads i get a blue screen saying theres a problem with hardware and windows stop to prevent damage. I played with bios a bit..downclocked the cpu..nope. I revert to my old cpu, Still can't boot. The POST is ok. I tried to boot from cd to repair windows..it reboots. I tried to format but it reboots. HELP!
More about : installed cpu boom
Power supply still fully functional?
<A HREF="http://www.nuklearpower.com/daily.php?date=050421" target="_new">You ever get the feeling that the universe is a vast, impersonal emptiness that exists only to hurt you?</A>
@ 186K -> 200,000 miles or bust!
<A HREF="http://www.nuklearpower.com/daily.php?date=050421" target="_new">You ever get the feeling that the universe is a vast, impersonal emptiness that exists only to hurt you?</A>
@ 186K -> 200,000 miles or bust!
Related ressources
- New PSU went boom ! - Forum
- KG7-RAID + W2K install = Boom - Forum
- Boom goes the PSU, please help - Forum
- GeForce 8800: Here Comes the DX10 Boom - Forum
- Installed new fan..turned on PC ...ALL MY LIGHTS WENT OUT! - Forum
First, the 2500+ has a fsb at 166(333) and your motherboard has the VIA kt266 chipset, which support CPU with fsb at 133(266). That means that your CPU wont run at what it was supposed to run, unless you cranck up the multiplier. Second, Since it is not in the list of supported CPU by your motherboard, then the BIOS would not recognize it too, and may have problems to put the right voltage/timing setup. That could lead to OS screwup, as it seem to be the case there..
better get a nforce2 board that support your CPU right on and reinstall Windows... You got a lesson here..
<font color=red>Sig space for rent. make your offer.</font color=red>
better get a nforce2 board that support your CPU right on and reinstall Windows... You got a lesson here..
<font color=red>Sig space for rent. make your offer.</font color=red>
The 2600+ must be the TB version, with the 133 FSB. You should clear the CMOS and try again.. Unplug the computer, press the power switch to discharge what migh remain of electricity in your system and remove the batterie for 4-5 minutes. Then set the fsb to 133 in BIOS and try again.
<font color=red>Sig space for rent. make your offer.</font color=red>
<font color=red>Sig space for rent. make your offer.</font color=red>
My wife's MoB is an nForce2 she originally had an XP 2500+ at a FSB setting of 333 MHz the BUS jumper on her MoB is 3 pins, pin 2&3 support 333 and 400 MHz fsb it is currently running an XP 3200+ CPU and working fantastic but only at 2.1 GHz. The old Barton XP 2500+ we could run at 2.2 GHz but the 3200+ wont.
All this is I believe is a RAM issue because I do not think her RAM is totally supporting 200 MHz and the system locks on the post screen. Faster RAM will proly get the XP 3200+ up to 2.2 GHz without trouble. The 3200+ also will not support any Aggressive BIOS settings with the current RAM it crashes on post and you must clear the CMOS to get control back.
I am still very impressed with the ability's of the XP 2500+ CPU and if I had known the 3200+ issues prior on the nForce2 MoB I would not have bother purchasing the 3200+ cpu for her at all. Overall performance of the 3200+ can still be felt in an online game even if it is running at stock speed it does have a slight edge over the overclocked 2500+ but I believe this is a heat issue caused by the 2500+ getting to hot over long run times.
Overall I was not greatly impressed with the nForce2 ASUS MoB it's something you have to get used to tweaking before you get it rocking correctly. Tweaking will involve cost for cooling components and upgrading RAM to meet the 3200+ cpu requirements.
My FX makes her drool and we are in the process of building her an SLI system but we are waiting for the next build in supporting MoB and I want to see what Nvidia is going to shoot out next in the development of SLI cards.
Wating means I have not even botherd to look in months!!
<font color=red>GOD</font color=red> <font color=orange>LOVES</font color=orange> <font color=red>CANADA</font color=red>
All this is I believe is a RAM issue because I do not think her RAM is totally supporting 200 MHz and the system locks on the post screen. Faster RAM will proly get the XP 3200+ up to 2.2 GHz without trouble. The 3200+ also will not support any Aggressive BIOS settings with the current RAM it crashes on post and you must clear the CMOS to get control back.
I am still very impressed with the ability's of the XP 2500+ CPU and if I had known the 3200+ issues prior on the nForce2 MoB I would not have bother purchasing the 3200+ cpu for her at all. Overall performance of the 3200+ can still be felt in an online game even if it is running at stock speed it does have a slight edge over the overclocked 2500+ but I believe this is a heat issue caused by the 2500+ getting to hot over long run times.
Overall I was not greatly impressed with the nForce2 ASUS MoB it's something you have to get used to tweaking before you get it rocking correctly. Tweaking will involve cost for cooling components and upgrading RAM to meet the 3200+ cpu requirements.
My FX makes her drool and we are in the process of building her an SLI system but we are waiting for the next build in supporting MoB and I want to see what Nvidia is going to shoot out next in the development of SLI cards.
Wating means I have not even botherd to look in months!!
<font color=red>GOD</font color=red> <font color=orange>LOVES</font color=orange> <font color=red>CANADA</font color=red>
I explained to Spacelord on another thread why his +2500 was only running at 1.4 GHz on his KT266 chipset yesterday, so I wasn't surprised to hear that his system has locked.
Your only hope is to clear the CMOS and try to reset the board to factory defaults. Follow the instructions the previous poster gave...find the little watch battery stuck on the board, pop it out, and then leave it for 10-15 minutes. Put it back in and with any luck your system will boot. Oh, and don't do this with the +2500 in. Go back to your +1800 and cross your fingers.
Do your homework with upgrades. AMD has a number of different AthlonXP's, all with different FSB speeds and cores. You ideally want to match the processor bus speed with the board FSB and Memory speeds so things run synchronously. ie. a +2500 chip with a KT333 motherboard and PC2700 RAM. Running things asynchronously is not efficient in an XP system.
Give me Convenience or Give me Death!
Your only hope is to clear the CMOS and try to reset the board to factory defaults. Follow the instructions the previous poster gave...find the little watch battery stuck on the board, pop it out, and then leave it for 10-15 minutes. Put it back in and with any luck your system will boot. Oh, and don't do this with the +2500 in. Go back to your +1800 and cross your fingers.
Do your homework with upgrades. AMD has a number of different AthlonXP's, all with different FSB speeds and cores. You ideally want to match the processor bus speed with the board FSB and Memory speeds so things run synchronously. ie. a +2500 chip with a KT333 motherboard and PC2700 RAM. Running things asynchronously is not efficient in an XP system.
Give me Convenience or Give me Death!
Thanks guys, i'll try to clear the CMOS now. My old 1800 isn't even T-bed it's palomino rofl. Question: is either of the cpu would be fried..it wouldn't even boot at all right? i fear i have damaged my 2500 ..i don't think i did tho.
If that doesn't work..im going to give my pc to a technician for him to replace the mobo tomorrow, i'll get an av7n8x asus mobo and 1gig of 2700 ram. If clearing the cmos brings it back..i'll wait a bit and do that myself..cuz tech dude is faster than ordering on ebay tho it's much more expensive.
<P ID="edit"><FONT SIZE=-1><EM>Edited by Spacelord on 04/28/05 00:21 AM.</EM></FONT></P>
If that doesn't work..im going to give my pc to a technician for him to replace the mobo tomorrow, i'll get an av7n8x asus mobo and 1gig of 2700 ram. If clearing the cmos brings it back..i'll wait a bit and do that myself..cuz tech dude is faster than ordering on ebay tho it's much more expensive.
<P ID="edit"><FONT SIZE=-1><EM>Edited by Spacelord on 04/28/05 00:21 AM.</EM></FONT></P>
Update! I changed my mobo for an Asus A7n8x-x, 1go of 3200 ddram and brand new 160go hdd. I got it today, quickly plugged it in and booted from my old 40go hd as master and 160 one as slave...boom! same blue screen as before. Fine, windows is fuber cuz of new hardware i think so i set my previous as slave and new as master and try to install windows on it, nope blue screen of death again! So whatever! my old hdd is broke then so i set my new one as master, unplug the 40go hdd and proceed to install windows. Format and then it start copying files...i go downstairs to get a drink and when i came back up the pc was shut down. Wtf? start it..goes down 2 sec later. Ok i reboot again and check bios..cpu was at 96c!!! grr...i change my fan/heatsink to stock one..i was using a thermaltake one and it's fine. Re-try to install windows...blue screen of death again.
Crazy! i have NO idea what's wrong! the dude at puter store couldn't help me but his technician will look into it. First time in years i have to turn to professional help heh
Anyone has nay ideas here? as i stated before in the thread, it was doing that with both my 1800 and 2500 on my asus a7v266-e before. The 2500 barton i bought on ebay could be dead but then when i went back to my 1800 it should have worked fine but didn't. How come the same problem can happen TWICE on DIFFERENT hardware?
Crazy! i have NO idea what's wrong! the dude at puter store couldn't help me but his technician will look into it. First time in years i have to turn to professional help heh
Anyone has nay ideas here? as i stated before in the thread, it was doing that with both my 1800 and 2500 on my asus a7v266-e before. The 2500 barton i bought on ebay could be dead but then when i went back to my 1800 it should have worked fine but didn't. How come the same problem can happen TWICE on DIFFERENT hardware?
96C? You might already fried your processor..
I had a friend who didn't install his new 2400+ and never got his windows installed properly (keeps getting BSOD, and found out temp too high), after trying a while, his pc refused to boot anymore. He brought his pc to me, I tested his processor on my pc, no boot, but his pc works fine with mine. so conclusion: Processor was fried due to heat
I had a friend who didn't install his new 2400+ and never got his windows installed properly (keeps getting BSOD, and found out temp too high), after trying a while, his pc refused to boot anymore. He brought his pc to me, I tested his processor on my pc, no boot, but his pc works fine with mine. so conclusion: Processor was fried due to heat
Related ressources:
- ForumGPU Capacitor went KaBOOM!
- ForumWhere AMD went wrong by enthusiasts....
- ForumPrices went down.
- ForumScreen went blank .. on every game
- ForumWent from Radeon to Nvidia Graphics card.
- ForumBig problems... what went wrong here.
- ForumSped up fans and CPU temp went UP?
- ForumInstalled new gpu and its overheating the cpu
- ForumInstalled a new CPU /heat sink - PC not starting up
- Forum[ CPU Problems]
- ForumNew motherboard needed with new setup?
- Forum212 evo fan replacement
- ForumI have no CPU driver installed!!!
- ForumComputer fall down go boom? :(
- ForumDetermine Installed CPU
- More resources
!
I'm the good time that was had by all