Overclock.....BSOD

[Shane]

Hello people,

okay so because for some reason i cant remember my overclock went back to stock,i think i had to reset the bios for something some time back and ive been running at stock since then...

Anyway today i overclocked to 3.2Ghz and ran prime95 until it reached the following

[Sun Apr 19 12:14:11 2009]
Self-test 1024K passed!
Self-test 1024K passed!
Self-test 1024K passed!
Self-test 1024K passed!
[Sun Apr 19 12:29:59 2009]
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
Self-test 8K passed!
[Sun Apr 19 12:45:01 2009]
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!
Self-test 10K passed!

I was not in the room at the time,But from downstairs i heard my pc had restarted because of the windows login screen sound and i though WTH lol

I got the "Windows has recovred from an unexpected shutdown" error when i logged in and this was what it said why.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8006902C6E
BCP3: 00000000B2000000
BCP4: 0000000000000115
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\Mini041909-01.dmp
C:\Windows\Temp\WER-53586-0.sysdata.xml
C:\Windows\Temp\WER34D5.tmp.version.txt

Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Anyone know what happened?

Im sure ive applied enough voltage,il get the correct readings from the bios and report back.

 

[Candy]

Have you tried overclocking, or even under-clocking, your memory a bit? With mine, when I overclock to 3.6 I have to raise the voltages a fair bit and change my memory overclock from auto to x2 which is actually less then what the auto sets it at, but its the only way to get it to boot. I havnt spent enough time working out how to make it properly stable (and even if its possible) cos it doesnt last long in Prime95 at that (a better cooler would help), but it boots so its an indication I'm on the right track. If I just leave the memory at auto I get BSOD.

 

[Candy]

Also, Danny has his Q6600 at 3.2 so you could ask him what he's done if he doesnt see this thread.

 

[Shane]

Ive had mine overclocked stable at 3.3Ghz for ages,Like i said i had to reset for some reason and thought i would only go to 3.2 this time just to help with those temps a little bit but seems it doesnt want to play this time

 

[Kornowski]

You remember all those problems I was having with my computer and OC'ing, all the BSOD's I got?

I've managed to get stable now and I put it down to two things;

1) Turn everything you don't need off! Speed Spectrum, EIST, C1Em TM1 & TM2. What I found was, when it was enabling the speedstep, it lowered my vCore so that it was a little under what it actually needed and it would BSOD. All these little things mess with your OC, too.

2) Run your Memory un-linked from your CPU. (Don't know if your board will let you?) I used to be running a 1:1 ratio on my RAM and then I started to run into problems. I then lowered my CPU OC so my RAM was only 20Mhz over stock, yet I still got problems. This could be my Ballistix being the crappy single sided ones, but I don't know. I'm now running them un-linked from my CPU and I've set them to 800Mhz (stock speed) and they're chuggin' along fine, with my CPU at 3.2Ghz.

Check your NB voltage and make sure your RAM is set to it's specified voltage, too.
Hope this helps.

 

[Kesava]

I have mine on 3.4, can't remember the settings, will tell you once I restart. I have never messed around to find my max OC. I just set it to 3.4, put the ram on the setting that made it clock at 1066 instead of 800. If I put it on auto then it would go further and I don't know what my ram can clock to so I don't wanna go there. Then I upped the vcore until it was stable.