author=NickN link=1232059827/0#1 date=1232065264]
2. Do I keep notching down the VCORE till it is unstable?
Yes however be aware you may be stable in OCCT tests and in hard 3D you may see a glitch.. try tapping Vcore up a touch if this happens
Man...that sucked....
So at 4.18 Ghz I ran OCCT and let it finish. I hit 80 a few times very briefly, but the test finished. Fired up fsx took off from LA just after installing Nicks Sun Fix....I wanted to see how it looked with bloom on. I load up in the Extra and head West, with cloud tops at about 12,000. So at about 11500 I am finally getting on top but I am right in the middle of a large cloud. For some reason I am in spot view with smoke on from the Extra. I had real Twemp active was was about 65 across the cores. Next thing I know both my displays go white and I lose it all. 5 seconds on the power button to shut it down...wait a little bit and I want to see what happends on a normal boot. Boot up past the Bios and the damn SAS controller (raid) piops up...I had that disabled cuz I don't use raid. Well, low and behold all the bios settings went back to default. I get back to the bios, and reset all my settings...I boot but after f-10 > Enter....screen goes blank and just sits there. Hard reset and than restart.....Option for safe mose, but I go right to Windows.....Now...clocked I am at 2.2 Ghz...WTF?
Reboot....lower the clock...22 @ 170 reboot...same damn thing. Back to the bios reset everything back to default...restart and all is normal from out of the box...Run OCCT for 20 minutes and I was at like 40c on that test. Go back to bios and clock it back to 4.1 ish and it seems to be holding....so before I start OCCT and get another BSOD Shall I be raising Vcore and leaving the clock alone? As it stands now...I am at: 22 by 188 = 4136
Vcore is at 1.392 and am idle at 40c........do I inch up vcore a little than occt test, followed by some WX in FSX?