Prime95 (Vista 64)

[Robster]

So I left Prime running when i went to sleep. When i woke up windows had rebooted, and Vista said that the reason was "blue screen".

I'm just curious, is blue screen a common failure result (if using wrong fsb/voltage etc).

 

[graysky]

Yes, you need more vcore or whatever core to sustain your overclock. Common MB vcores to increase as well as CPU vcore are: NB and VTT. Also consider ICH. What are your overclock levels?

 

[Robster]

I tried 9x345 = 3105. I left the vcore at 1.3000v. Did a 9½ h Small FFts, everything went fine. But that time, I had the other voltage values on "automatic", except for the CPU of course...

Later i tried 9x355. After I woke up, windows informed me about the blue screen. But if i remember correctly, I didn't use automatic voltages at that time.

Here's my current

BTW, i accidentally used 2.2v on my RAMS for maybe 10 min, (Its' default volts are 2.0-2.1). Have i harmed them in any way, and is the warranty now gone?

 

[graysky]

RAM is fine and your warranty is probably still 100 %.

 

[bryanW1995]

you can adjust most of your setting sin uGuru, but make sure that you don't have cpu-z on when you do it. As long as you're close when priming, you will just get an error message instead of a blue screen. If you're only at 3.1 then you SHOULD just need to add vcore for now. Of course, with 2x2 gb ram you might need a little bit more mch.

If you're going for max OC then you can just jump straight to these settings then tweak them as needed:

1.52 mch
1.32 vtt
1.60 ichio
1.09 ich
69% gtlref (for both 0/2 and 1/3)

I ran my e6750 at these settings for 9 mos before dropping in a Q9450 and oc'ing it to 3.6 last month. I only have 2x1 gb ram, however, but I also need much more fsb than you so those should be sufficient. How's your airflow in the p182? my antec 900 is great, I have the 120mm's on medium and the top exhaust on high.

I have my system in a hot (26c) room and run seti 24/7. I never get closer than 30c to tjunction on my hottest core and 53c is the highest I've seen my pwm. lmk if you have any questions.

 

[Robster]

First of all, thanks guys for your help!

So here's the latest;

As I said earlier, I can run 3.1Ghz with 3.1000V for 9h+ Prime95 fluently. And the only volts I've touched, are the CPU vcore and my DDR2.

Now. I want to achieve 3.2Ghz but neither of these volts worked: 1.3000V, 1.3100V, 1.3200V and 1.3300V (Prime crashes or BSOD). But 1.3400V gave me these results. Notice thread 2, is that what you meant bryanW1995 by

you will just get an error message instead of a blue screen

Here are my configs that I've now used for the latest above mentioned and the successful testing of 3.1Ghz @ 1.3000V. As I said, only touched the Vcore and DDR2, rest is default...

It seems strange that I can OC to 3.1Ghz without even touching the VCore, but when I wanna get the extra 100mhz, I have to bump it up to 1.3400V. Does that mean that it is time to change those other settings as you mentioned, and then possibly lower the VCore??
I saw your recommendation, but It's a bit high don't you think, considering what I've achieved so far with my current settings?

What would you recommend for me @ 3.2Ghz (mch, vtt, ichio, ich, gtlref). (hopefully if i touch those settings, I can lower the vcore?).


Oh and I almost forgot, here are my temps at idle. I think my temps are quite normal, or what do you think? Running my rear TriCools 120mm exhaust and top fan on medium. Extra 2x120mm in the middle hdd chamber normal/high speed. And the last TriCool 120mm next to the PSU at high speed.

 

[Tweakin]

Originally posted by: Robster
First of all, thanks guys for your help!

...But 1.3400V gave me these results. Notice thread 2, is that what you meant bryanW1995 by

you will just get an error message instead of a blue screen...

Thread 1 died, and that means you probably need to feed the beast a little more vcore. As you stated, some feel that all this extra voltage is not worth the extra 100 MHz and heat...I for one am one of those folks.

I think your tems are fine for now...especially since you are still trying to find your sweet spot. Just keep pluggin...you'll get there.

 

[bryanW1995]

I gave you my voltages so that you would know what some safe 24/7 voltages are. If you want your max oc then I highly recommend bumping up your other voltages before using any more vcore. you're fine at 1.52 on mch, esp with all that good airflow, but you can dial it to a lower level like, say, 1.37 or so for starters if you like. mch and vtt are your most important settings right now, probably more important than vcore. 1.30-1.32 isn't that much on vtt, either. You have one of two potential problems right now: 1. your q6600 is a crappy overclocker. if that's the case then I'd leave it at all stock at 3.1. 2. you need to adjust your other voltages. try this first, the worst that can happen with these minimal adjustments is that you'll find that your problem really is just that the chip doesn't want to go over 3.1.

 

[Robster]

Thanks Bryan.

I will try your settings, i will try a prime 95 test now, but is the 1.3400V necessary? (Was hoping i could get a lower one, by bumping up those other volts).


EDIT

Oh btw, here are my real idle temps after watching a 2h long dvd film. 3105Ghz @ 1.3000V, just to tell whereabout my cooling/temps are...

 

[demiurge3141]

Originally posted by: Robster
So I left Prime running when i went to sleep. When i woke up windows had rebooted, and Vista said that the reason was "blue screen".

I'm just curious, is blue screen a common failure result (if using wrong fsb/voltage etc).

up vcore. the ip35-pro has a large vdrop/vdroop.

 

[SickBeast]

Prime95 will give you a BSOD in Vista 64 unless you use the 64-bit version of Prime95.

I had this same problem with my Opteron 165.

Your hardware is fine. :beer:

 

[Robster]

Yeah I use the 64-bit version of Prime95.

Now in my most recent test, where i bumped up the other volts, i got this. What's the deal. I assume i'm closing up on 3.2Ghz.. at least it didnt't crash immediately.

 

[graysky]

@robster - to me that's worse than a rounding error. The app crashed. Did you have a look at my stress testing guide?

 

[Robster]

graysky, no I haven't read your stress guide (didn't even know about it, but looks very good!).

I got that app crash with these settings:

356x9 = 3.2Ghz

Vcore: 1.3200v
CPU VTT: 1.31v
Mch: 1.44v
Ich: 1.09v
ichio: 1.60v
gtlref: 68% (both)

But when changing the vcore to 1.3300 (using the same other volts), i got this.

I will try later with 1.3400 vcore and same volts, hopefully it will be successful.

 

[ir faceless]

Robster, quit OCing and get a life

btw gl with all the tests u r going trough (att du orkar).

cya on vent

 

[bryanW1995]

don't listen to ir faceless, oc'ing IS your life now! :evil:

1.34 vcore should get you there. the other settings should get you to 3.6+ on a Q6600. Make sure when you're done with your oc that you try to minimize all voltages per graysky's guide. Remember to keep track of all of your data, too, as that will help immensely at the end.

 

[ir faceless]

bryanW1995, i'm just messing around with my friend

 

[Robster]

Originally posted by: ir faceless
Robster, quit OCing and get a life

btw gl with all the tests u r going trough (att du orkar).

cya on vent

Haha, yeah face.. I admit, I'm an OC addict now

1.34 vcore should get you there. the other settings should get you to 3.6+ on a Q6600. Make sure when you're done with your oc that you try to minimize all voltages per graysky's guide. Remember to keep track of all of your data, too, as that will help immensely at the end.

I'll try 1.34 when i get back home again with all the other voltages included, and just run dram, say 1:1. Hopefully, hopefully.. i'll get some results.. otherwise it just won't go above my current fsb . And so i'll stick with that (hell, it's even factory/untouched volts and runs 3.1ghz, idle temps 34c per core, it's a pretty good deal anyway ).

Thanks again bryan

 

[flexy]

Originally posted by: Robster
So I left Prime running when i went to sleep. When i woke up windows had rebooted, and Vista said that the reason was "blue screen".

I'm just curious, is blue screen a common failure result (if using wrong fsb/voltage etc).

if i would post every time i get a BSOD priming or using OCCT we would need a new forum, seriously

I rather get BSODs than "errors" when i do stability testing.

 

[Robster]

Originally posted by: flexy

Originally posted by: Robster
So I left Prime running when i went to sleep. When i woke up windows had rebooted, and Vista said that the reason was "blue screen".

I'm just curious, is blue screen a common failure result (if using wrong fsb/voltage etc).

if i would post every time i get a BSOD priming or using OCCT we would need a new forum, seriously

I rather get BSODs than "errors" when i do stability testing.

Hehe, well don't expect too much from a beginner like me

 

[bryanW1995]

Originally posted by: flexy

Originally posted by: Robster
So I left Prime running when i went to sleep. When i woke up windows had rebooted, and Vista said that the reason was "blue screen".

I'm just curious, is blue screen a common failure result (if using wrong fsb/voltage etc).

if i would post every time i get a BSOD priming or using OCCT we would need a new forum, seriously

I rather get BSODs than "errors" when i do stability testing.

why is that? I've found that I'm more likely to get a bsod when I'm very far away from stability, then I can prime longer and longer as stability is approached. Usually if I can prime for more than a couple minutes then I won't get a bsod.

 

[VirtualLarry]

Originally posted by: SickBeast
Prime95 will give you a BSOD in Vista 64 unless you use the 64-bit version of Prime95.

I had this same problem with my Opteron 165.

Your hardware is fine. :beer:

That's concerning. No stable Win32 app should cause Vista64 to BSOD, unless it has severe kernel bugs. I've heard tell that SuperPI causes Vista64 to bug out too. I still don't know if that's just bugged/overclocked/unstable hardware, or if there really are kernel bugs in Vista64, when dealing with heavily computational-oriented programs.