- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
re: PC Discussion - Gaming, Performance and Enthusiasts
Posted on 6/12/14 at 8:24 pm to ILikeLSUToo
Posted on 6/12/14 at 8:24 pm to ILikeLSUToo
BCLK/PCI Frequency: 100.0
Turbo Ratio: By all cores @ 45
Internal Pll Overvoltage: Auto
CPU Voltage: Offset Mode
Offset Voltage: Auto
DRAM Voltage: 1.5
VCCSA Voltage: Auto
VCCIO Voltage: Auto
Let me know if there is anything else I am missing.
Edit: Forgot the test program: OCCT
It ran for about a minute then stopped because it got to 80
Turbo Ratio: By all cores @ 45
Internal Pll Overvoltage: Auto
CPU Voltage: Offset Mode
Offset Voltage: Auto
DRAM Voltage: 1.5
VCCSA Voltage: Auto
VCCIO Voltage: Auto
Let me know if there is anything else I am missing.
Edit: Forgot the test program: OCCT
It ran for about a minute then stopped because it got to 80
This post was edited on 6/12/14 at 8:30 pm
1
Posted on 6/12/14 at 8:53 pm to Phil
Oh, that's because you have the CPU voltage in offset mode, plus auto. It's going to give you way more voltage than you need for that clock. If you look at CPU-Z while doing the stress test I bet you'd see your vcore at 1.4 or higher.
Switch it to manual mode and set a static voltage of 1.30v with the turbo ratio of 45. Use CPU-Z to see your voltage while stress testing.
1.3v might not be stable, so just start with that and work your way up if you blue screen.
Also, 80 degrees is no reason to panic and shut it off. 90-95 will be the throttle point. I thought at first you were saying that it was automatically throttling and eventually shutting off due to super-high temps. Still, 80 is a bit high for that overclock, and I bet it's because of your auto voltage setting. That board (and Z68/Z77 in general) is overly liberal with the voltage in auto/offset mode.
Switch it to manual mode and set a static voltage of 1.30v with the turbo ratio of 45. Use CPU-Z to see your voltage while stress testing.
1.3v might not be stable, so just start with that and work your way up if you blue screen.
Also, 80 degrees is no reason to panic and shut it off. 90-95 will be the throttle point. I thought at first you were saying that it was automatically throttling and eventually shutting off due to super-high temps. Still, 80 is a bit high for that overclock, and I bet it's because of your auto voltage setting. That board (and Z68/Z77 in general) is overly liberal with the voltage in auto/offset mode.
This post was edited on 6/12/14 at 8:54 pm
Posted on 6/12/14 at 9:02 pm to ILikeLSUToo
Thanks for the help. I will make those changes and get back to you. If I get the blue screen I can just reboot and change the voltage right?
Posted on 6/12/14 at 11:14 pm to Phil
yep
Posted on 6/13/14 at 12:14 pm to ILikeLSUToo
Anyone interested in LFD2 co-ops tonight?
Posted on 6/13/14 at 12:22 pm to LSU Coyote
quote:
You have IB or HW?
SB. 2600k
Posted on 6/13/14 at 12:32 pm to brucevilanch
Hey, dick...I need to talk to you. I called yesterday and your wife answered.
Posted on 6/13/14 at 12:35 pm to stout
So sorry. I got tied up with a friend and didn't get home late. Your phone is about to ring.
Posted on 6/13/14 at 12:44 pm to brucevilanch
Just hop on skype
Posted on 6/13/14 at 12:55 pm to stout
I'm on. 
Posted on 6/13/14 at 1:01 pm to stout
And I tried to talk to you last night. Came up dry. Thanks...
Posted on 6/13/14 at 1:09 pm to Devious
Huh? I must have had Skype open on my phone because I wasn't on Skype last night on my PC. Sorry
Posted on 6/13/14 at 1:13 pm to stout
Just forward me those bruce and lew pics. We'll call it even.
Posted on 6/13/14 at 1:20 pm to Devious
Posted on 6/13/14 at 7:33 pm to brucevilanch
Replaying Crysis 3 ATM to monitor VRAM usuage, since Watch_Dogs is eaten it up.
Well, I understand open world vs a box but still, Watch_Dogs honestly looks like shtt even compared to AC4, much less Crysis 3. Now Crysis actually looks and feels real at times with only using 2.75-2.8 inside the semi-open world dome. Now compare this to Watch_Dogs near limitless demand for resource and it only produces something which looks 3-4yrs old.
Ubisoft is a terrible developer and the only thing I trust from them is the team working on FarCry series. Then again, they use a different engine which lifts it from the other junk produced by Ubisoft.
Well, I understand open world vs a box but still, Watch_Dogs honestly looks like shtt even compared to AC4, much less Crysis 3. Now Crysis actually looks and feels real at times with only using 2.75-2.8 inside the semi-open world dome. Now compare this to Watch_Dogs near limitless demand for resource and it only produces something which looks 3-4yrs old.
Ubisoft is a terrible developer and the only thing I trust from them is the team working on FarCry series. Then again, they use a different engine which lifts it from the other junk produced by Ubisoft.
Posted on 6/13/14 at 8:11 pm to brucevilanch
We bf4ing it up tonight?
Posted on 6/13/14 at 8:47 pm to ILikeLSUToo
LINK
This is what I ran at with 1.3V.
The spike in CPUTIN is making me nervous. Is that normal? I know I didn't run it for long.
This is what I ran at with 1.3V.
The spike in CPUTIN is making me nervous. Is that normal? I know I didn't run it for long.
Posted on 6/13/14 at 9:20 pm to Phil
That's definitely a software glitch and not a real temperature. I've seen it happen on a variety of components in HWMonitor, afterburner, and the like. You can google CPUTIN 127 and see a ton of people who've had the same glitch in other software. Just look at the individual core temps.
You're gonna need to run it more than 5 minutes to test stability. One of the cores is hitting 80-ish. Safety-wise, that's fine. We aren't talking about running this test for weeks or anything. Just an hour or two. If you're a die-hard OC purist, 24 hours, but I haven't done that in a long time. I'd rather run 30 minutes of a hardcore stress test and spend a few days gaming or encoding to test real-world stability.
The disparity in two of those core temps could be a concern. 12.5 degree difference in the hottest and coolest core under load. That's not uncommon but might indicate some unevenness in heatsink pressure or TIM distribution. Not sure how your fan curve is set up to say whether the other core temps are reasonable for the voltage/clock. Hyper 212's can be tricky.
You're gonna need to run it more than 5 minutes to test stability. One of the cores is hitting 80-ish. Safety-wise, that's fine. We aren't talking about running this test for weeks or anything. Just an hour or two. If you're a die-hard OC purist, 24 hours, but I haven't done that in a long time. I'd rather run 30 minutes of a hardcore stress test and spend a few days gaming or encoding to test real-world stability.
The disparity in two of those core temps could be a concern. 12.5 degree difference in the hottest and coolest core under load. That's not uncommon but might indicate some unevenness in heatsink pressure or TIM distribution. Not sure how your fan curve is set up to say whether the other core temps are reasonable for the voltage/clock. Hyper 212's can be tricky.
Posted on 6/13/14 at 9:23 pm to ILikeLSUToo
Yea I ran another for 10 minutes and got the blue screen I am trying to go back and up my voltage now. Everything I read says go up by .05 so I would be at 1.35 now
Posted on 6/13/14 at 9:31 pm to Phil
0.05 at a time is a bit much (but it's a quicker way to find stability if you have good cooling) With your cooling, 1.35 is probably the top end anyway. If you're stable at 1.35v, your next step is to go down by 0.005, running the stress test at each increment, until you blue screen again. Then go back up by 0.005.
Page 855 of 1912
Popular
Back to top
Follow TigerDroppings for LSU Football News