Question 6700k OC questions

[Gt403cyl]

So it's been about a year and a half since I've played with my 6700k OC, back when I got it I was able to run 3DMark with valid results at 5.0GHz but wasn't super stable and I decided on a safe OC for 24/7 at 4.7GHz, 1.38v.

Today I decided to play with it again and I think I found a stable 4.9GHz profile. I used Aida64 and HWMonitor with CPU-z to see what was going on with temps/voltages.

CPU - 6700k
Motherboard - MSIZ170 Xpower Gaming Titanium
Latest BIOS
Custom loop 280mm x 60mm + 360mm x 30mm rads

I know max temps are a little on the high side and the vcore is a little high as well, just wondering if I should tone it back a bit or if I am ok...

Spoiler: screenshot

Things are fine at 4.7GHz just checking if it's worth squeezing the last bit out.

 

[Indus]

Aida is a super stress test to see if its stable.

Even during gaming all day, you won't stress it that much so go for it.

 

[Gt403cyl]

I tried it for a few rounds of PUBG and my PC crashed with a black screen and the broken audio, so loaded up my 4.7 profile and will have to play with it more, it was solid for 4 games and the 5th one crashed... black screen so I have to check the cause later...

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000018, 0x0000000000000000, 0xffff888195566180, 0x0000000000000004)


Problem Event Name: LiveKernelEvent
Code: 117
Parameter 1: ffffbb8b1a5a1460
Parameter 2: fffff8030b9ece38
Parameter 3: 0
Parameter 4: 4d8
OS version: 10_0_17763
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17763.2.0.0.768.101
Locale ID: 1033

Those are the reports I got.

 

[Indus]

I tried it for a few rounds of PUBG and my PC crashed with a black screen and the broken audio, so loaded up my 4.7 profile and will have to play with it more, it was solid for 4 games and the 5th one crashed... black screen so I have to check the cause later...

I think that's PUBG not the comp.. I've had problems with that game on a couple of computers till I stopped playing last October.

And I thought it was my overclock but nope.. PUBG has -Redacted- code.

Try other games.

You already know that profanity is not allowed in the Tech forums.

Daveybrat
AT Moderator

 

[Gt403cyl]

ok thanks will try it again tomorrow

 

[Shmee]

Try running memtest as well, just to be safe. Use the latest UEFI memtest from passmark, v7.5

 

[Gt403cyl]

Try running memtest as well, just to be safe. Use the latest UEFI memtest from passmark, v7.5

Did you mean v8.1? That's the latest?

 

[Gt403cyl]

It passed Memtest with 0 errors.

Haven't had time to work on it aside from running memtest.

 

[Shmee]

You are right, good catch! I had not seen that they had a newer one out.

 

[Gt403cyl]

Well I played around with it some more today.

Bios settings that didn't crash during 20 minute Aida64 run:
49 multiplier
CPU core: 1.450v
LLC Line 3
Everything else CPU related on Auto

Aida64 showed:
CPU vore voltage at 1.478v
111.24w Package power
Max Package temp was 88c avg was 82c
Max core temp was 92-95c avg was 73c

I tried running XTU benchmark and it BSOD half way through (sys service exception)

LLC Line 3 in BIOS is basically flat, Line 2 raises a bit and Line 1 raises a lot, given the voltages I don't think trying lines 1/2 would be good (could be wrong though)

Going to try some other benchmarks and see how it goes with these settings, any advice on tweaks is appreciated.

EDIT:

Tried some Cinebench R15 and got a 1027cb so checked that on HWBot, placed #141 for x4 on H20 so I'll take it.

I don't think I'll get 5.0GHz stable, I'm still not convinced 4.9GHz is 100% stable right now.
A delid might help temps, not sure if that's my wall, not going to delid though as really I don't want to at this point.

 

[Shmee]

IMO, 1.4 and up is too high for Vcore. I would settle for lower with fewer volts.

 

[Gt403cyl]

IMO, 1.4 and up is too high for Vcore. I would settle for lower with fewer volts.

100% agree, I run 4.7GHz @1.380v for 24/7.

I was just trying to see if I could get back to 5.0GHz for a couple runs to see if there has been any degradation or performance changes since Q3 2015.