New hardware, constant restarts

I just replaced my mobo, ram, processor, and gpu. After I did that I couldn't get the computer to get passed what mode to start in (safe, norm, etc).

At first I thought it was the new gpu taking up to much power (have 650w psu) but after I tried my old card it still would restart. I then tried to run it up with individual sticks of ram to see if one of them had a memory leak but with both sticks it still restarted.

The hard drive was formatted before I swapped the parts and the computer will still run with the old set up. I'm at a loss of what to do now and majorgeeks has always been a good place for me to stop when I have no clue what is going on.

These are the new parts I put in

GeForce 9800 GTX(G92) 512MB 256-bit GDDR3
Core 2 Duo E7400 Wolfdale 2.8GHz 3MB
CORSAIR 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800
XFX MG63Mi7159 LGA 775 NVIDIA GeForce 7150 / nForce 630i

Thanks in advance for any help

 

Did you format and reinstall the OS with the old parts still in place?

 

Yah I formatted it and installed it with the old parts because I can't get to formatting it with the new parts. It doesn't let me get that far. I didn't think it would be to much of a problems if i didn't install and drivers.

 

If you installed the OS with the old parts in place, I would think that is part of your problem as Windows searches the computer for installed devices during the set up phase and will try to install the drivers for the devices that it originally found when it tries its first boot. I may be wrong in this, in which case others will definitely tell you/me and offer better advice!

To me, it would be better to blank/zero the hard drive, install your new parts, and then post with whatever problems that it presents. Hope this helps!

 

Should I just nuke it with of the programs from this site to get it clear?

 

I generally use this one myself, http://www.majorgeeks.com/Dariks_Boot_and_Nuke_d4596.html.

 

Ok so I bought a new hdd because I was going to get a new one anyways for the old parts. Problem is now I keep getting this error message, I've searched the forums for the answer of this message but haven't been able to find one. I keep getting the message:

"Windows could not start because of a computer disk hardware configuration problem. Could no read from the selected boot dis. Check boot path and disk hardware"

I really can't do anything besides that, I can't get into the bios or anything. It's a clean hdd and it wont even run the windows boot disc. I tried plugging it into all of the sata ports but no luck. Only way the windows disk will initiate is if i unplug the hdd.

 

I'm assuming that we are talking about XP, as you didn't mention an OS. Have you checked to make sure that you have your CD/DVD drive jumpered correctly as for master/slave configuration? Have you checked your motherboard manual, and do you have the drivers disk that it should have shipped with?

Assumed XP because Vista has native support for SATA drives!

 

You are correct the os is xp and I do have the driver discs for the parts that I bought. The thing is I can't even load xp onto the hdd and don't I need that on the hdd before i even start using the driver cd's. As for the cd/dvd drive being jumpered the wrong that could be a possibility since I did previously have 2 in this system and now only 1.

 

Yes, you do need XP on the system before using the driver CD! I questioned the CD/DVD jumper arrangement, as I've ran into the same issue with the error that you mentioned before. But while you have the hard drive unplugged, it might be a good idea to go into BIOS and check that you have the CD/DVD listed as the first boot device.

Should you have any problems with the SATA drivers, I'm including this link for reference as it does mention nforce boards, http://www.techspot.com/vb/all/windows/t-20564-Problems-installing-xp-on-SATA-drive.html. Hope this helps!

 

I think I read the same problem on here the other day, the answer was he had not plugged his DVD drive in properly.

 

It was in slave and I switched it to master but was still getting that message. I disconnected my hdd and took out the windows cd to see if I could get into the bios but no luck. Just kept getting a message to boot in a boot device. So I plugged in my hdd and put in the cd while it said that and it loaded up the windows set up. I was pretty excited since it finally was going somewhere. After I did the format and did the set up it restarted like normal to continue the process but now that it loaded up I'm getting the same message about not being able to read the boot disk.

 

Start from scratch. pull m-b battery or use jumper to clear cmos. Possibly a bad disc of xp. ed

 

Ok after clearing the cmos and resetting the m/b battery I was finally able to get into the bios. It had the boot order listed as hdd then cd and I swapped them around. Now it will ask me if I want to boot from cd and I do so I can get the set up going. Except now when the set up is going it restarts shortly into it. If I do not choose to go with the cd it will give me the same message it has been giving me.

This problem is starting to seem hopeless :confused

 

Have you tried another cd/dvd drive? I had an issue where one cd/dvd would give me problems but another worked right off.

 

I think a bad drive would give you a message of cannot copy file, possible over heat of cpu, check heatsink is making good contact with cpu. ed

 

I believe that you will have to load the SATA drivers during the XP installation for this to work!

 

Ok I checked the heat sink and contact was good. I also tried the stock heat sink (have after market one on it now) and it still restarts during windows install.

How would I go about install sata drivers during the xp install? I don't know why the sata would cause the restarts it never caused a problem with my old hardware and that was like 2 1/2 years older.

I'm running out of ideas but don't want to give up because then these parts would just be a waste of money :confused

 

Check the link that I provided in post 10. XP doesn't have native support for SATA and this could be why you are now getting the message. It can't copy files to a drive that it can't find, nor would/will it be a boot drive until the drivers are installed. As for how to install the SATA drivers, there is an option early in the Windows setup routine where it says to press F6 if you need to install SATA/RAID drivers. This is where you need the floppy with the drivers.

As for why your hardware gave no problems with the old setup and does with the new, you have a new motherboard and hard drive and best that I can tell it is a different configuration than what you previously had.

 

I don't have a floppy drive so I couldn't load the sata drives, so I just tried my wife's cd of vista since you said it automatically supports it. After I select boot from cd it starts to load windows but shortly after it restarts. Then I get a blue screen of death (for the first time a good thing) that reads this.

MACHINE_CHECK_ERROR
stop: 0x0000009c (0x00000000, 0x8d0a1120, 0xb2000040, 0x00000800)

I looked this problem up and said could be because the computer doesn't recognize parts or something to do with pentium processors. I'm pretty sure all the parts are being recognized though because when I look at the parts in bios it shows correct readings for all the parts (storage space, speed, etc.) besides the gpu but I don't think it shows that information anyways. It just asks where I want to load my graphics from.

Also I can only get into the bios after I clear the cmos.

 

The only other thing i can think of is the fsb is too fast for the cpu, check mb specs and see if they match in default mode. I believe this is why you have to clear the cmos every time. ed

 

I think I found the problem. That board doesn't support that processor. The mb series does but the mg series doesn't support e7***.
http://www.xfxforce.com/en-us/produ...~/ecms.aspx/XFXCPUCompatibilityList-Intel.pdf

 

Wow I didn't even notice that, well thanks for the help. I'll have to send the old one back and replace with a new one. I'll let you know how that goes.