3570k & z77 dh - game crashes

smurf300 · 16 Jul 2013 at 21:20

Hey guys, I have today set my oc on the z77, I used this tutorial http://www.youtube.com/watch?v=NxCPyF-1tTc

the only thing I did differently was set the turbo ratios at 42 instead of 45 because I wanted to be modest, other than that I only changed what this guy does in the tutorial

Thermal monitor - Disabled
Turbo power limit - 250
Core Current limit - 250
cpu pll - 1.650v

Now I turn on the game I currently am playing, for good 10 mins, I always keep msi ab and real temp on my second monitor to check the temps, gpu is at like 60 and cpu max hits 70 though usually early 60s whilst playing. So I'm curious if anyone might have an idea as to how or why it crashes the game, it doesn't crash the PC just the game, also note that I have a gtx 670 FTW which was ever so slightly oc but now I've set that as default to test it.

I should also add that I also select the memory xmp profile 1, which I haven't done before so there's the possibility of that as well?

setter · 16 Jul 2013 at 21:26

xmp on the ram should be ok and both gpu/cpu temps seem ok, what vcore are you using for the overclock. Sometimes with not enough you can pass stress tests ok but games will fail. Check the windows event viewer for whea errors, event id 19 cpu parity iirc. Theese are a sign of not enough vcore, increasing it a few clicks can help.

smurf300 · 16 Jul 2013 at 21:36

setter said:
xmp on the ram should be ok and both gpu/cpu temps seem ok, what vcore are you using for the overclock. Sometimes with not enough you can pass stress tests ok but games will fail. Check the windows event viewer for whea errors, event id 19 cpu parity iirc. Theese are a sign of not enough vcore, increasing it a few clicks can help.

The vcore is on auto, I just checked event viewer and here is what it says

'A corrected hardware error has occurred. Reported by component: Processor Core'

Source : WHEA
EVENT ID : 19

Would this mean that maybe the auto vcore is not a good way to go?

setter · 16 Jul 2013 at 21:48

Id personally avoid auto. What sort of vcore was the chip using when stressed/gaming? Check with cpuz, adding a few notches higher than this set manually may help. But off course keep an eye on temps.

BluD · 16 Jul 2013 at 22:03

Yeah like setter said find out what vcore your using at load in cpuz and add a bit more untill its stable in the games your playing.

smurf300 · 16 Jul 2013 at 22:09

Yeah thanks for the advise guys, reading through forums people seem to be against auto vcore, looks like it was running at 1.18v , going to go manual and increase in increments and do half hour on prime each time.

smurf300 · 16 Jul 2013 at 22:59

So just a double check, when I get this same error, just to inc the vcore each time until it's 100% stable?

wazza300 · 16 Jul 2013 at 23:07

Try llc high

CPU v normal
+0.020v CPU offset,then see if it makes it into windows and stress CPU while looking in CPU-z and make a note if load CPU v

Adjust offset if need be to be stable,only one/two clicks a time,stay below 1.4v load CPU v and below 80c core temps if you can or 80-85c

smurf300 · 18 Jul 2013 at 01:33

Ok finding this a little strange anyway been testing more today, I had the vcore set to 1.280 it crashed on prime within 5 mins(first test) I put it up to 1.290v anyway here's a photo and I found it interesting that the voltage is only at 1.236 on cpu z? here's a picture I took as I started, currently on test 15 and passed all thus far so a bit more promising now. Does this mean that the vcore you set in the bios isn't actually used? Or is it like saying, 'you can use upto this' ;/

http://i.imgur.com/T2eKa1Q.jpg

It crashed on test 20, anyway I restarted and put the vcore up a not(1.295v) when i get into windows I start cpu z and it indeed is 1.295v, then when I start prime, the vcore goes down to 1.236-48 again ;/ . I have a feeling this may have something to do with c3/6 state, but will await a reply to see if it's ok to turn this off.

smurf300 · 18 Jul 2013 at 02:58

OK reason why I'm making another post is because my last was so messy, expect more of the same, anyway I went back to that video, and decided to turn all the c3 etc turbo and all that off and do it the original way, with no turbo and no throttling stuff enabled, 1.275v and running prime for close to 45 minutes with no errors. I think maybe the idea behind all that turbo and such is good, but not quite working perfectly yet?

BluD · 18 Jul 2013 at 06:30

It all works fine, but i find needs a little more vcore to get it stable rather than setting ya speed manually, problerbly cause the speeds are jumping all over the place, i get the same thing on my graphics card when i enable Powerplay it gets a bit twitchy at high speeds and requires a little more voltage.

I guess i ya use ya PC a lot without stressing your CPU/GPU much then powersaving features are a must, even if ya need to run at a slightly lower speed, if ya just turn it on for gaming then youll not be making much use of the powersaving and might as well set everything manually to get your optimum speed. This is just what i found with my experience overcocking this system anyway, maybe others found their systems worked better using powersaving features.