Overclock.net › Forums › Intel › Intel CPUs › Complete Overclocking Guide: Sandy Bridge & Ivy Bridge | *ASRock Edition*
New Posts  All Forums:Forum Nav:

Complete Overclocking Guide: Sandy Bridge & Ivy Bridge | *ASRock Edition* - Page 918

Poll Results: Was this guide helpful?

Poll expired: Oct 17, 2012  
  • 80% (237)
    Yes (and I DO have an ASRock motherboard).
  • 15% (45)
    Yes (but I DO NOT have an ASRock motherboard).
  • 2% (7)
    No (and I DO have an ASRock motherboard).
  • 2% (7)
    No (but I DO NOT have an ASRock motherboard).
296 Total Votes  
post #9171 of 9543
Quote:
Originally Posted by SEJB View Post

I am currently out of ideas on why my build is freezing up.

Relevant specs
2700k(2012-04-24)
Gainward GTX1070 GS
Z77 Extreme4
A-Data XPG 1600 Mhz 9-9-9-24 16 GB (8x2) AX3U1600W8G9-DB
XFX Pro series 850W( Purchased at 2013-01-28) Could it be going old?
Creative X-fi Xtremegamer using the drivers from creatives webpage.
Primary harddrive is an 850 Evo SSD which was installed in January.
Currently on Windows 10 version 1607 but the issues arise in windows 7 as well.

Running a XL2730Z as primary monitor via DP and a secondary XL2410T as secondary monitor via DVI-D.

For the past few months I have been experiencing freezes that I have been unable to solve. The freezes can come at completely random times although they mostly seem to occur around CSGO lately which is a shame since it is the game I prefer playing.
It never freezes while in an actual game but only in menues which previously led me to believe the issue was idle voltage, I have tried every possible value up to an offest of +0.100 which gave the same results.
The issues have persisted even though I have changed my GPU and from AMD to Nvidia so the GPU shouldn't be at fault.

Sometimes I get crashes where everything goes black on my primary monitor and nothing updates on the secondary monitor although I can still talk just fine on teamspeak, when this happens I can force off the fullscreen application using unified remote after a while since it takes an unusually long time for the task manager list to show up in unified remote.

The issues also occur at complete stock which is why I am completely lost since if it was just at OC settings I could figure out that my OC was unstable even though I get no bluescreens but just freezes.
Currently my CPU runs at 4,5 Ghz at a full load voltage of 1.32 with it mostly hovering between 1.304 and 1.32 when gaming. I have had it up to 1.394 without any change in behaviour. Temperatures never pass 65C with my NH-D15
LLC levels have been tested at 1 to 5 without any changes.

  • Upping corevoltage and PLL voltage to no results.
  • Clean reinstall of windows and all drivers
  • Reseated my GPU
  • Turned dynamictick off in Windows as suggested by another thread on this forum when googling.
  • Turned off Speedstep to force it to run at a constant speed and voltage.
  • Tried a completely different pair of ram sticks in all slots.
  • Checked all cables in my computer
  • Run prime95 without issues
  • Run a full memtest for 24 hours without any errors.
  • Reflashed the newest bios to see if it could have been slightly corrupted somehow.
  • Tried setting the ram to 1333 Mhz due to Sandys theoretical limit being there.

and what does your error log say? you can work out most of your problems by cut n copying the error message in google and find ur answer.

this is what im referring too, -




the WHEA errors help minimise ur overclocking waste of time so much. prime can run apparently stable but the cpu is failing then jump starts itself to no apparent issue then its unstable but onlj just
if you see Whea erros while running primeor anything ardous u need to up ur cpu volts ussual
Edited by MattBaneLM - 8/31/16 at 12:10pm
post #9172 of 9543
Error log says absolutely nothing. Just tells me I had forced shutdowns after I have to hard reset which is eventID 41.

As said I have upped my voltage to 1.394 with no difference at all.

Not a single WHEA error in my log

PSU voltages are as follows which should be fine right?

12v: 12,091v
5v: 5,064
3,3v: 3,376

Might as well try the 2.90M bios I guess
Edited by SEJB - 8/31/16 at 1:08pm
post #9173 of 9543
Does the PC freeze often enough that it should always appear within 24 hours? When you ran your 24 hour memtest, there was no freeze, so if the freeze happens often enough it has to be something that is only involved when you are in Windows. This could then be Windows or some software or some hardware other than CPU and RAM (and the parts of the board involved with CPU and RAM).

I think in theory a freeze should be caused by certain spots in memory getting corrupted and the Windows kernel then crashing so bad that it can't do anything anymore (like can't record a BSOD to disk anymore). As the memory and CPU appear to work correctly, the corruption hopefully comes from something else and could be a software problem.

The only software that has low-level access to do this are drivers and an antivirus or perhaps also a backup tool. You could experiment with removing and disabling different devices and the antivirus etc.

A thing you could do is think back about when the problem first showed up. If you still have the same Windows installation, there's like two or three different screens you can find somewhere in the Control Panel that show a list of programs or a list of Windows updates. Those have a date column you can use for ordering the list by date. You could see what changes happened there somewhere before the first date with problem you remember.

I think some hardware could also misbehave as the things on the board and in PCI slots can access RAM (I don't know if they really can write anywhere or not), but I guess you could also blame that on the hardware's driver and treat it as a software problem.

Right now some Windows files might have gotten corrupted in past crashes. You might want to occasionally run the "sfc /scannow" command on an Administrator command prompt while experimenting. This "sfc" command is the "System File Checker" tool that ships with Windows.

I'd hope the PSU is fine if the 24 hour memtest passed, but perhaps something happens while gaming as the GPU starts using power? You might want to test with another PSU.
post #9174 of 9543
As said I have clean installed windows several times and tried different ram and I am now running another GPU. The windows files would most likely not be corrupted after a completely clean install.

All the voltages given by the PSU should indicate that it is fine but I'll try to test another one. I have been considering the soundcard to be the issue but I have found nobody with freezing problems with it so it seems far fetched.

Removed and wiped all soundcard drivers but just encountered another soft lockup where I can still communicate on teamspeak and it takes ages for the fullscreen application to turn off
Edited by SEJB - 9/1/16 at 12:46am
post #9175 of 9543
Help 3570K @4.5GHZ, 1.200-1.212V

I still got a single error WHEA Logger (Event ID 19) randomly in a day. Does anyone also have the same problems?

If you still got this error, that's mean our OC is not stable?

I will try to bump voltage again a notch if this error still appears.
Edited by zipper17 - 9/1/16 at 10:55pm
PC Gaming 4 Life
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 3570k @4.7GHZ Biostar TZ77XE4 Galax GTX 1070 EXOC 2x8 Team Vulcan 19200 @2400 CL11 DDR3 
Hard DriveHard DriveOptical DriveCooling
Seagate 500GB, Seagate 2TB Crucial MX100 256GB Lite On 24x sata CM Hyper 212 EVO  
OSMonitorPower
Win 10 Pro 64 bit  Dell U2515H Seasonic ss 650 At 
  hide details  
Reply
PC Gaming 4 Life
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 3570k @4.7GHZ Biostar TZ77XE4 Galax GTX 1070 EXOC 2x8 Team Vulcan 19200 @2400 CL11 DDR3 
Hard DriveHard DriveOptical DriveCooling
Seagate 500GB, Seagate 2TB Crucial MX100 256GB Lite On 24x sata CM Hyper 212 EVO  
OSMonitorPower
Win 10 Pro 64 bit  Dell U2515H Seasonic ss 650 At 
  hide details  
Reply
post #9176 of 9543
Quote:
Originally Posted by zipper17 View Post

Help 3570K @4.5GHZ, 1.200-1.212V

I still got a single error WHEA Logger (Event ID 19) randomly in a day. Does anyone also have the same problems?

If you still got this error, that's mean our OC is not stable?

I will try to bump voltage again a notch if this error still appears.

WHEA is a hardware error that is caught and corrected. So it is close. Usually a bump or two to VCore clears these up, if not addressed they will eventually not get corrected and turn into a BSOD.

You are on the right path.
Blue540
(14 items)
 
x99
(18 items)
 
B.M.O.
(10 items)
 
CPUMotherboardGraphicsGraphics
6800k ASUS X99-A EVGA 980 FTW ACX 2.0 EVGA 980 FTW ACX2.0 
RAMHard DriveHard DriveCooling
Corsair Vengeance CMK32GX4M4B3200C16W Crucial MX100 WD Blue 1TB EK Supremacy EVO 
CoolingCoolingCoolingOS
EK 480 PE EK 240 PE EK D5 Vario Windows 10 
MonitorKeyboardPowerCase
Samsung 49KU7500 (curved 4k) Corsair K65 NZXT Hale 90 V2 1000W Thermaltake X9 
MouseMouse Pad
Logitch G100S X-Trac Ripper 
CPUMotherboardGraphicsRAM
6400k msi A75MA-P33 Sapphire 6670 passive hynix 2 GB dual channel 
Hard DriveOSMonitorKeyboard
WD  windows 8.1 e-machine wireless 
PowerCase
king win 600w custom built 
  hide details  
Reply
Blue540
(14 items)
 
x99
(18 items)
 
B.M.O.
(10 items)
 
CPUMotherboardGraphicsGraphics
6800k ASUS X99-A EVGA 980 FTW ACX 2.0 EVGA 980 FTW ACX2.0 
RAMHard DriveHard DriveCooling
Corsair Vengeance CMK32GX4M4B3200C16W Crucial MX100 WD Blue 1TB EK Supremacy EVO 
CoolingCoolingCoolingOS
EK 480 PE EK 240 PE EK D5 Vario Windows 10 
MonitorKeyboardPowerCase
Samsung 49KU7500 (curved 4k) Corsair K65 NZXT Hale 90 V2 1000W Thermaltake X9 
MouseMouse Pad
Logitch G100S X-Trac Ripper 
CPUMotherboardGraphicsRAM
6400k msi A75MA-P33 Sapphire 6670 passive hynix 2 GB dual channel 
Hard DriveOSMonitorKeyboard
WD  windows 8.1 e-machine wireless 
PowerCase
king win 600w custom built 
  hide details  
Reply
post #9177 of 9543
Wot he said^
Keeping an eye on error log can save so much wasted time on prime runs! I think of when I used to do that. What a numpty I feel
post #9178 of 9543
Quote:
Originally Posted by inedenimadam View Post

WHEA is a hardware error that is caught and corrected. So it is close. Usually a bump or two to VCore clears these up, if not addressed they will eventually not get corrected and turn into a BSOD.

You are on the right path.



Yeah my 3570k @4.5ghz with adjustable 1.200-1.212Vcore, it's been running ~24hours since first attempt. by far only got a single WHEA Logger error. But before that got 23 WHEA errors if under 1.200 v.

Not sure if I should raise voltage or not , getting nerves if the cpu will get overheats.
let's see if the problem still appears.

how many core voltages does it needs 3570K at@ 4.5ghz or 4.6ghz in general?

I was at 4.2GHZ before without touching any Vcore. None whea logger error.
Edited by zipper17 - 9/2/16 at 4:54am
PC Gaming 4 Life
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 3570k @4.7GHZ Biostar TZ77XE4 Galax GTX 1070 EXOC 2x8 Team Vulcan 19200 @2400 CL11 DDR3 
Hard DriveHard DriveOptical DriveCooling
Seagate 500GB, Seagate 2TB Crucial MX100 256GB Lite On 24x sata CM Hyper 212 EVO  
OSMonitorPower
Win 10 Pro 64 bit  Dell U2515H Seasonic ss 650 At 
  hide details  
Reply
PC Gaming 4 Life
(11 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i5 3570k @4.7GHZ Biostar TZ77XE4 Galax GTX 1070 EXOC 2x8 Team Vulcan 19200 @2400 CL11 DDR3 
Hard DriveHard DriveOptical DriveCooling
Seagate 500GB, Seagate 2TB Crucial MX100 256GB Lite On 24x sata CM Hyper 212 EVO  
OSMonitorPower
Win 10 Pro 64 bit  Dell U2515H Seasonic ss 650 At 
  hide details  
Reply
post #9179 of 9543
I got around overclocking my chip again, due to BF1 beta, trying to see if there's any difference. I just noticed that in HWiNFO, the Power (Input) of this chip reaches 166.500W. Is this normal? I just saw it today. +reps to anyone who can clear up this power input level thing. Thanks! thumb.gif

Vcore at 1.232V max for 4.3GHz, and I can't go any lower than that. It also seems that my chip has reached its thermal wall, so 4.3GHz might be my best OC with this chip.
post #9180 of 9543
Quote:
Originally Posted by zipper17 View Post

Yeah my 3570k @4.5ghz with adjustable 1.200-1.212Vcore, it's been running ~24hours since first attempt. by far only got a single WHEA Logger error. But before that got 23 WHEA errors if under 1.200 v.

Not sure if I should raise voltage or not , getting nerves if the cpu will get overheats.
let's see if the problem still appears.

how many core voltages does it needs 3570K at@ 4.5ghz or 4.6ghz in general?

I was at 4.2GHZ before without touching any Vcore. None whea logger error.

all will be a bit diff as we know but I had 4600@ 1.20 ans a td
4700 - 1.30
4800 - 1.40

hmmm... seeing a pattern lol
im talking bottom voltage at MAX load as read by aida

cpu volts isn't the only voltage that countsif you have a heap of / or very tight ram vtt might need a hand? I would be auto with most at 4500 but try 1.69-1.87 on vtt and despite what others say pch needs a crank up a notch or so somethime (not much)

vscca I haven't needed to touch at what my sig says 24/7 stable
also try ppl volts auto with pll overvoltage enabled


all just thoughts. don't have your mobo...
if you can post all your bios settings in a thread we can see if theres any glaring problems

also ram... manual set timings or xmp? running a touch over specified ram volts?

everything says to me just keep cranking up cpu volts till error goes away. 9 times out of 10 that's what I needed. and for a messive volt range I was only getting WHEA errors but NO CRASH. I think I went from about 1.350 volts to over 1.40 only getting WHEA's which had me doubting just cpu volts were to blame. anyway you can see it all in my thread.

oh and kumusta smile.gif
Edited by MattBaneLM - 9/2/16 at 7:17am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Complete Overclocking Guide: Sandy Bridge & Ivy Bridge | *ASRock Edition*