Sign in with
Sign up | Sign in
Your question
Solved

New machine unstable

Tags:
  • Homebuilt
  • Systems
Last response: in Systems
Share
September 5, 2010 11:53:46 PM

Hello, I just built a new machine for gaming and work. I've built several machines in the past. I'm ok with the mechanics of building a machine, but I'm lousy on the troubleshooting and software side of things.

It's an i7 930 using stock heatsink, with an ASUS NVIDIA 480, ASUS P6X58D mobo, 12GB Corsair dominator DDR3 1600 RAM, Corsair 850W PSU.

The problem I'm running into is the OS (Win7) is unstable. In one day, the finder has crashed on me, I've had one blue screen, Flash crashes all the time, Firefox crashes often, Vuze crashes often, and the three games I've tried all CTD upon a few minutes of playing.

I've never had problems like this before, all three of the PC's I've built in the past just magically worked. Any help or suggestions on things to check would be greatly appreciated. Thanks!

-John

More about : machine unstable

September 5, 2010 11:59:56 PM

How many ram sticks do you have?

What type of case do you have.
m
0
l

Best solution

a b B Homebuilt system
September 6, 2010 12:03:26 AM

Did you set the timings and voltages manually for the RAM? I highly doubt there is a 12GB kit of dominators that will run probably at 1.5V. Once you set the timings and voltages if its still unstable run memtest for a few passes and see if it gets any errors.
Share
Related resources
September 6, 2010 12:06:54 AM

I'm running 6 sticks of TR3X6G1600C8D Corsair Dominator RAM. I was just reading up on them and it says they should be running at 1.65V. I'm going to check the voltage in the BIOS right now.

I'm running a Coolermaster Cosmos case.
m
0
l
September 6, 2010 12:15:21 AM

That motherboard only officially supports 12 gb of ram at maximum 1333mhz.

Try clocking it down to 1333.
m
0
l
September 6, 2010 12:46:44 AM

Oh, that's dissapointing. Oh well.

So I clocked it down to 1333 and set the timing to 8,8,8,24, but I'm confused as to the voltage. It should be set to 1.65V as I understand it, but I'm not sure where to set that? There is a QPI/DRAM Core Voltage setting, and a DRAM Bus Voltage setting. Which one do I change?
m
0
l
September 6, 2010 1:14:59 AM

I set the QPI to 1.35v and the bus to 1.64v judging from what I've read around, and everything seems to be running fine. My games are running, anyway. Thanks guys! I didn't even know where to begin to look... at least now if I have any further problems I have a basis to start a search from.
m
0
l
September 6, 2010 1:15:40 AM

Try testing the stability of your pc before you up the voltage because 1.65v is the max voltage that you can use before you can burn out the memory controller on your i7.
If your system is still not stable then ram voltage is under AI Tweaker, scroll down to where it says *****please key in numbers directly!***** .
m
0
l
September 6, 2010 2:15:48 AM

Well I was able to play Mafia2 for about 30 minutes, but it still crashed. Much better than the 30 seconds it lasted every time I tried it before.

Is it ok to lower the RAM voltage randomly? Should I set it to 1.5 or something? I really don't know jack all about tweaking numbers in the BIOS and I don't want to blow something up by accident.
m
0
l
September 6, 2010 1:58:26 PM

So the crashing was still happening, just not as badly as before for some reason. So I ran Memtest and got some errors, ran each stick individually, and it turns out one of the sticks was bad :( 

So I'm running on 6GB for now until I RMA the bad stick, but everything is running completely stable now! Thanks, the both of you, for your assistance. I never did a memory check before, I've never had bad memory before, so this was all new to me, and your questions and theories really helped a ton.
m
0
l
September 6, 2010 1:59:10 PM

Best answer selected by z0mbi.
m
0
l
a b B Homebuilt system
September 6, 2010 8:58:01 PM

I had the same thing happen to me in the spring, but Gskill was nice and quick about it and even with shipping between new york and california i had my system back up and running in under a week, so while it sucks to wait its good to know what the problem was.
m
0
l
!