danmitch1
Well-known member
- Joined
- Dec 15, 2007
- Messages
- 2,318
So I couldnt help my self and got my 9900k oc'ed to 5ghz on all cores (4.3 ghz uncore) with automatic avx offset, 1.345 v core and XMP 3200 ram profile on my Gigabyte z390 Aorus Ultra.
I can do 5.1 at 1.36 vcore but it gets toasty, maybe down the line ill get a custom loop and push it but for now the 5ghz is great.
That being said, Im not prime 95 stable, and some might say its not a true oc but I just couldnt get it stable and cool with prime 95 with or without avx.
Im aida64 30min, cinebench 15 and 20 (4 consecutive runs each) stable with temps staying below 91c.
Roughly 1.5 hours of Assassins creed Odyssey 2k maxed out settings generated 77c max.
1 hour of Battlefield V 2k maxed settings generated 74c max.
Adobe software and 3ds max work great. No buggy activity at all.
So this is stable enough for me.
Anyway, now I re-instated all the power features and set windows to a balanced power profile.
Everything is staying stable but whats bugging me is that my Vcore is locked at 1.345.
To enable the dynamic vcore I have to set my vcore to "normal" but then the vcore shoots up to 1.5 ! (with immediate skyrocketing temps evidently)
Is this just something I have to deal with? I guess 1.345v constant isnt the end of the world but still.
Another thing I cant figure out is what hw info is monitoring with
VR LOOP 1 - There are two instances, one that hovers with and without load between 48c - 58c
the other 57c - 68c
and
VR VCC Temperature (SVID) - This seems to have the same as the second instance of VR LOOP 1 hovering between 58c - 68c
I thought it was the VRM temps but then I have VRM MOS which hovers between 35c - 45c.
Either way I guess those temps are not too crazy but I cant find any solid detailed info about what they are acually reading.
All other temps seems great.
This screenshot is taken after a 15 minute aida64 test
I can do 5.1 at 1.36 vcore but it gets toasty, maybe down the line ill get a custom loop and push it but for now the 5ghz is great.
That being said, Im not prime 95 stable, and some might say its not a true oc but I just couldnt get it stable and cool with prime 95 with or without avx.
Im aida64 30min, cinebench 15 and 20 (4 consecutive runs each) stable with temps staying below 91c.
Roughly 1.5 hours of Assassins creed Odyssey 2k maxed out settings generated 77c max.
1 hour of Battlefield V 2k maxed settings generated 74c max.
Adobe software and 3ds max work great. No buggy activity at all.
So this is stable enough for me.
Anyway, now I re-instated all the power features and set windows to a balanced power profile.
Everything is staying stable but whats bugging me is that my Vcore is locked at 1.345.
To enable the dynamic vcore I have to set my vcore to "normal" but then the vcore shoots up to 1.5 ! (with immediate skyrocketing temps evidently)
Is this just something I have to deal with? I guess 1.345v constant isnt the end of the world but still.
Another thing I cant figure out is what hw info is monitoring with
VR LOOP 1 - There are two instances, one that hovers with and without load between 48c - 58c
the other 57c - 68c
and
VR VCC Temperature (SVID) - This seems to have the same as the second instance of VR LOOP 1 hovering between 58c - 68c
I thought it was the VRM temps but then I have VRM MOS which hovers between 35c - 45c.
Either way I guess those temps are not too crazy but I cant find any solid detailed info about what they are acually reading.
All other temps seems great.
This screenshot is taken after a 15 minute aida64 test
Last edited: