• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Think I nearly killed my Q6600

cje

cje

cje

Associate
Joined
3 Jan 2009
Posts
786
Right, I had a stable overclock at 1500 FSB, with 1.5 volts in BIOS.

I had completed 25 passes of Intel Burn Test at maximum stress. Temperatures according to nvidia monitor, realtemp, coretemp were not hitting above 70 degrees.

All was fine, the test over, I downloaded OCCT from the internet, installed and ran it. 5 minutes later, I saw my Vcore was reported as 1.56, even though I set it to 1.5 in BIOS. Then, my pc just switched itself off, just like a pwoer cut. Damn I thought, I must have killed the cpu. I switched the pc on again, it lit up for a second, then died again. I switched it off in the wall, waited 2 minutes, and turned it on again. This time it came on as if nothing was wrong. I loaded setup defaults in BIOS, just incase.

Anyone know if my cpu was dying? Or was it something else?
 
Can you get to windows with default setting?
If you can i don't think you killed your CPU.

For me to get 1500 FSB, i only need 1.443v in BIOS and my Q6600 vid is 1.3250.

If you could post your setting maybe we can compare it :)
 
Nah, I didn't kill it, hence the "nearly" its fine back in windows now.

As for settings, to get 1500 FSB with my Q6600 VID 1.3v:
Vcore: 1.4875
NB : 1.46
Ram : 1.60
Vtt 1.36

using Striker II Extreme, I've got 4 ddr3 modules, and I've been told that a NB of 1.45 should stabilise them.

As for Vcore, I set Vcore of 1.4875 in BIOS, and some programs report it as 1.56! The previous version of cpu-z and speedfan report 1.49. Which ones are correct?

EDIT - I also though over heating, as I has previously completed 25 passes of the intel burn test.
 
What motherboard are you using?
And surely, with vdroop, the Vcore would drop in windows/during cpu usage, and certainly not be elevated.

I'm running a P5Q Pro with an FSB of 431 (1724) but CPU ratio x8 with NB voltage on Auto (8GB DDR2 800 @ 863, it works so I couldn't be bothered with doing it manually). My Q6600 vCore is 1.4625 - what multiplier are you using? I have about 0.06v vdrop under load (VID 1.3125)
 
Asus Striker II extreme 790i Ultra. When I've got Loadline Calibration Enabled in Bios, it does eliminate Vdroop, so when I specify 1.4875 in bios, then with older cpu-z it reports 1.49. But with the newer cpu-z it reports 1.58. Even when loadline calibration is disabled.

I'm afraid to clock it again incase I actually kill it. I think it was temperature related though.
 
I've had my temps into the mid-70s before. Not for too long tho, and at lower voltage, and all chips are different.. but given that yours recovered after a couple of minutes, yes chances are it is indeed a temperature thing.
 
I wouldn't worry about those volts too much - tho I don't reccomend those kinda voltages if its your only CPU and you want it to last. I've had an E6600 on 1.65vcore (water) for ages without the CPU showing any kind of problem whatsoever.
 
I have this problem with my Q6600, strangly enough temps are normal, but after a powersupply shorting out it won't go past 333FSB it works at anything below.

I used to have it sitting happy at 3.62Ghz for 1.4 volts, now it wouldn't even go there :|
 
Yeah, I've had problems were I can't run it stable with anything between 1400-1600 fsb, it seems like and fsb hole, but nobody else has reported this problem. I'll have to try raising the fsb and lowering the multiplier to see if it might be a mobo stability issue. I've got 4 ddr3 modules, so I might not be pumping enough volts to it. But since I havent watercooled it, it might be that overheating.
 
1.56v is very high, Q6600s in the same board will reach different FSBs so your right it could be the chip as well as the board.
 
Well, I think it must have been RAM or Mobo problem. I'm running 1600 with 8x multi on 1.425 volts. And its just fine, however, I cant run it stable at all with 1420 fsb and 1.45 volts even.

So yeah, I was pumping more Vcore, whilst vcore wasn't the problem. I've got all other voltages except vcore on auto at the moment, and its happy as pie. However, if I set them manually to what it sets them on auto, it'll freeze and crash randomly.

This motherboard is a right pain to get it stable I suppose.

EDIT - But I still don't get it why I set 1.425 in BIOS, and CPU-z reprots in windows voltage of 1.5 ?
 
Nope, but I've found that my stability issues did not derive from the CPU.

I'm currently unstable at 1600 fsb, but with 6x multiplier. So I don't know what voltages to raise now. Nb 1.44, Vcore 1.45, rest on auto. PCIE 101 and SPP<>MCP 200.
 
got my q6600 running at 3.2ghz with 400x8 setting. with 2gigs of ddr3 ram i can run 1:1 ratio of 1600fsb and 1600mhz ram speed.

but with 4 sticks of ram 1600mhz operation no longer possible i have to use divider to lower ram speed to 1280mhz and im 100% stable. ram wont do more than around 1450mhz when using 4 sticks.

mobo is gigabyte p35t-dq6.

ram is 4 sticks corsair 1600mhz xms3 7-7-7-20 stuff.
 
it could be a FSB hole, but it does the same with two mobos, and two sets of RAM :| and it boots but it just don't go into windows :| on one of the mobo I had it happy at 400FSB 1.4volts on a maxumise 2 formular with no multiplayer set
 
I'll try lowering ram speed. Its supposed to run 1333 mhz, I've left it unlinked, but no go. I'll try 1280 later tonight.
 
Also remember that when it runs it's tests OCCT overclocks by a little so if your on the edge of stable settings normally OCCT may just push it that bit over the edge.
 
RizlaKing said:
Also remember that when it runs it's tests OCCT overclocks by a little so if your on the edge of stable settings normally OCCT may just push it that bit over the edge.
Click to expand...

what are you on about??? :rolleyes:

occt is basically a prime95 wrapper, and prime is best used as a memory/memory controller stress test.
 
IBT is a good benchmark but it stress the processor in a different way to OCCT and Prime95 and therefore stable settings in one doesnt always mean stable in the other...

In regards to what happened at reboot this is a standard feature on most motherboards, where it has detected the settings were unstable and therefore loads at defaults, so the PC will power... unpower and then boot on stable settings
 
You must log in or register to reply here.
Back
Top Bottom