Seeking Advice: Re-assembly of an Over-Clocked System

[BonzaiDuck]

I am retiring a Q6600 C2Q system with a 680i motherboard.

It is over-clocked to a stable 3.0 Ghz.

I wanted to give the system to my brother before Xmas or end of the year.

I was planning to simply move it to a new and smaller case for Bro. Then, all I need to do is replace the hard-disk storage (leaving power-consumption somewhat reduced in the reconfiguration) and install a Windows 7 64-bit OS.

Should I reset the over-clock to default settings- restoring them after the hardware is reconnected? Has anyone here at the forums had experiences otherwise that would make it wise to do so?

 

[Idontcare]

I reduced the OC on my 3.3GHz Q6600, setting it back to stock clocks in fact, when I upgraded to an SSD.

Depending on what your brother is going to use the system for, he might appreciate the quiet and lowered electric bill of just having it at stock, SSD or not.

 

[tweakboy]

I reduced the OC on my 3.3GHz Q6600, setting it back to stock clocks in fact, when I upgraded to an SSD.

Depending on what your brother is going to use the system for, he might appreciate the quiet and lowered electric bill of just having it at stock, SSD or not.

What stepping you got B3 or GO revision ? yes SSD closes down the bottleneck,,,, wheter your @ 2.4 or 3.4Ghz ,,,

iive seen first hand on my old mans machine how SSD is amazing. I mean not boot up but,, starting of apps and loading stuff soo fast,, hes @ 375mbps SATA 3. But only gets a 7.5 in Winblows 7 WEI .. its set to RAID in the bios I think......

Soon I will need to get on the SSD bandwagon,, and buy a small 80GB for 80 bucks or something,, and use it as my DAW storage,,,,, 🙂 :whiste:

 

[RavenSEAL]

What stepping you got B3 or GO revision ? yes SSD closes down the bottleneck,,,, wheter your @ 2.4 or 3.4Ghz ,,,

iive seen first hand on my old mans machine how SSD is amazing. I mean not boot up but,, starting of apps and loading stuff soo fast,, hes @ 375mbps SATA 3. But only gets a 7.5 in Winblows 7 WEI .. its set to RAID in the bios I think......

Soon I will need to get on the SSD bandwagon,, and buy a small 80GB for 80 bucks or something,, and use it as my DAW storage,,,,, 🙂 :whiste:

Only 375 on SATA3?

D:

 

[Idontcare]

What stepping you got B3 or GO revision ? yes SSD closes down the bottleneck,,,, wheter your @ 2.4 or 3.4Ghz ,,,

iive seen first hand on my old mans machine how SSD is amazing. I mean not boot up but,, starting of apps and loading stuff soo fast,, hes @ 375mbps SATA 3. But only gets a 7.5 in Winblows 7 WEI .. its set to RAID in the bios I think......

Soon I will need to get on the SSD bandwagon,, and buy a small 80GB for 80 bucks or something,, and use it as my DAW storage,,,,, 🙂 :whiste:

I've got 5 G0's here. The one B3 I had was actually a QX6700, but it died after a couple years at 4GHz on vaporphase.

 

[Shmee]

mb back it off a little, to whatever you are comfortable and know wont cause him issues. 3.0 is a good start, but since the board is a 680i and not a 780i like in my old comp, 2.8 might be better. still a 400 MHz OC.

 

[BonzaiDuck]

mb back it off a little, to whatever you are comfortable and know wont cause him issues. 3.0 is a good start, but since the board is a 680i and not a 780i like in my old comp, 2.8 might be better. still a 400 MHz OC.

Well, folks -- thanks for responding so quickly.

There's an insinuation in some posts about an SSD. No SSD. I'm going to take him down from a RAID5 to a single disk. He hates RAID. He had a RAID0 go south on him.

He currently has a Northwood P4 3.2Ghz with 3GB RAM. He'll get the Q6600 with 4GB RAM.

He mostly uses his laptop, but works with music on the desktop.

But to my question: That system has been running rock-stable at those settings for 42 months. I suppose I could "tune it down" to stock settings, but it runs fine as is. I just wondered if there were mishaps or troubles for taking it apart and reinstalling it in a new case when the net result will be only a decrease in power consumption.

I'll probably make a note of the settings and set it to default. Then put the settings back in BIOS and run some stress tests.

I just wanted to avoid going to that trouble . . .