Newly Built Cpu Freezes, any help welcome

[dsun0814]

Hey guys, I recently built my computer, but it often freezes unexpectedly. I am not even running any new programs or anything.

I have been using everest to check my computer parts' temperature and voltage settings. Everything seems to be fine.

Perhaps it's a problem with the voltage settings for my RAM. I currently have it set at 2.0 V for my DDR2 6400 G-skill.

Here are my parts. Perhaps you guys can tell me if my parts are not compatible with each other.

1. Antec Nine Hundred Black Steel ATX Mid Tower Computer Case

2. LITE-ON 20X DVD±R DVD Burner Black IDE Model DH-20A4P-04 - OEM

3. ASUS M2N32-SLI Deluxe Wireless Edition AM2 NVIDIA nForce 590 SLI MCP ATX AMD Motherboard - Retail

4. G.SKILL 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model F2-6400CL5D-2GBNQ - Retail

5. EVGA 256-P2-N758-TR GeForce 8600GT SCC 256MB 128-bit GDDR3 PCI Express x16 SLI Supported Video Card - Retail

6. Rosewill RX750-D-B ATX12V v2.2 & EPS12V v2.91 750W Power Supply

7. AMD Athlon 64 X2 6400+ Windsor 3.2GHz Socket AM2 125W Dual-Core Processor Model ADX6400CZBOX - Retail

8. Seagate Barracuda 7200.10 ST3500630AS 500GB 7200 RPM SATA 3.0Gb/s Hard Drive - OEM

Thanks a lot!!

 

[wahnula]

Set all the BIOS settings at optimized defaults, see if it still freezes. Unless, of course, you need to enable SATA or the like in the BIOS for the system to boot. Use all stock settings, timings, and voltages. Set the Asus AI application to 0 if you're using it.

Start removing things like a stick of RAM and the DVD drive, then swap the RAM sticks.

Check if there's a newer BIOS available; likewise graphics driver & sound driver.

Run a benchmark like SiSoft Sandra Lite and see if it locks up at the same point, that could help pin it down. Try another GFX card if you have one.

If no luck, take the mainboard out of the case and do a "breadboard" build with all parts laid out on a non-conductive surface, like a piece of cardboard or a towel.


Tony

Users helping Users...

 

[firewolfrl]

kick the G Skill ram to 2.2 that may work to bring stability. I used G Skill with the M2N32 deluxe board and that is what I had to do.
also you should call G skill for the right timing settings.


good luck

 

[kmcferrin]

The memory should have a sticker on the module that lists the appropriate timings and voltages. Make sure that's what you're set to and you'd be good to go. I do know that G.Skill does sell DDR2-800 modules that require higher than stock voltages to be stable at 800 MHz, but they also put the required voltage on the modules.

Other than that, the biggest cause of freezes/lockups is usually cooling, or the lack thereof.

________________________________________
CompTIA A+, Network+, Server+, Security+
MCSE:Security 2003
MCITP:Enterprise Administrator

 

[firewolfrl]

I just looked at my gskill memory and it does not state voltage or timings just the model number...but then it is DDR2 800 memory that I purchased at newegg with the timing and voltage I specked out for the computer that my son uses now for games....lol. I needed the timing and voltage to match other ram that I had already in the machine

Gskill does not have the greatest support but their forum page should help:

http://newgskill.web-bi.net/gstechforum/

just to note I do make it a habit of writing the timing and voltage on the ram so I don't forget...

 

[alex304]

Have you tried to disable the "fast post" option in the BIOS. I had a similiar problem that was caused by bad ram. The OS would lock up and switching RAM didn't make any difference because the OS was installed with the bad ram. After fighting with this computer for a weekend, I decided to disable fast post and bad RAM was picked up during the POST. I removed the bad RAM and reinstalled the OS and every ran fast and smooth!!!

 

[vanka25]

The OS would lock up and switching RAM didn't make any difference because the OS was installed with the bad ram.

I fail to see how this would be true. I have also had issues with bad RAM, doing a simple swap always fixed it without the need to completely re-install the OS.