can't overclock i5-2500k

Toggle sidebar Toggle sidebar
O

OrbitalshocK

Reputable
Apr 1, 2014
33
0
4,530
SPECS:
z68xp-ud3 Bios ver. f10
16gb ddr 1600 ripjaw series cl9 9-9-9-24 (exact model listed on supported memory list on mobo website)
i5-2500k
water cooled...corsair h..60?
main OS drive: Crucial m500 (old firmware. MU03)
EVGA GTX 780 Classified
850w thermaltake power supply (switched out my OCZ ModXstream Pro 600w to see if that was the problem)

hey guys...i'm having issues overclocking my system ever since i added some new components. I could've been having these issues since reinstalling windows OR since going from windows 7 to windows 8.

so key points:

not just new hardware, but new software all over the place.
last time overclocked: windows 7 ultimate
New GPU (gtx 460 to a gtx 780 classified)
new memeory (8gb 1600 kingston hyperX to 16gb ripjaw series 1600)
gpu usage in games like crysis 3 shows 92-100% while CPU shows 40-70% for each core but gpu POWER % never goes above 85? not sure if this is related.


what i've done to try and fix the problem:
driver fusion found like 10 drivers for various things that i hadn't updated...chipset and usb stuff mostly. integrated sound and video etc.
updated motherboard from f4 bios to f10

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

errors caused by overclocking:
i have tried to just use the multiplier to get to a simple 4.0ghz...didnt work.


i've received numerous errors, heres my whocrashed.


Welcome to WhoCrashed (HOME EDITION) v 5.01

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


Home Edition Notice

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

System Information (local)

computer name: TAYLOR-PC
windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: Z68XP-UD3, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17025798144 total
VM: 2147352576, free: 1919991808



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 5/18/2014 7:27:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-6937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x1A (0x3453, 0xFFFFE00076C2A6C0, 0x21CAD0, 0x4)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/18/2014 6:12:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-6593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xFC (0xFFFFC0014D6053CA, 0x80400000029A9963, 0xFFFFD00096345DC0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/18/2014 5:39:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-6750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x657CF)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800104727CF, 0xFFFFD0005DFE82C8, 0xFFFFD0005DFE7AD0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 5/18/2014 6:52:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051814-10734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0xFC (0xFFFFC001094055E5, 0x80400000029A1963, 0xFFFFD000C145A380, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Conclusion

4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
 
Sort by date Sort by votes
4Ryan6

4Ryan6

Champion
Apr 14, 2002
20,610
6
52,915
Best advice to you is to study an overclocking guide and learn what you are doing.

Failed overclocks corrupt the GPU drivers and they always need to be reinstalled.

Always roll back to stock settings when installing an operating system if the previous overclock was unstable you have a corrupted operating system as well.
 
Upvote 0 Downvote
O

OrbitalshocK

Reputable
Apr 1, 2014
33
0
4,530
well, i didnt actually try and do anything fancy....i upped the multiplier to 40 from 33. i didnt think i would need to up my vcore in order to do that as the last time i overclocked was years ago and i did exactly the same thing....pushed it from 33 to 45....and that was constant i never changed it even when working instead of playing games....but i only kept it that way for maybe a month and realized it wasnt really making anything run faster....i had a gpu bottleneck not a cpu one...so i just set it to normal and left it alone.

that being said....i got some more weird startups last night/today. it was giving me bsod and saying 'boot drive inaccessible' and i got a bsod sometime last night apparently with

crash dump file: C:\Windows\Minidump\052014-9375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.




i'm debating updating my SSD firmware...i'm doing RECIMG right now to save my OS and important files since its my OS drive though.....kinda nervous especially with the amount of oddities happening since i reinstalled all this software AND added a gpu and memory and the ssd in question. i also thought it might be my cpu.....maybe it needs to be reseated or something?? or a busted motherboard but i have NO idea how to tell if its busted other than being able to recognize a faulty cap from leakage and/or the top being pushed up.

i posted a thread in the storage category about suggestiosn for updating games because my home internet is metered now (live inthe boonies for now) which means i've been lugging my computer back and forth from the office once a week for a couple months. nothing is loose, and i checked the screws on the cpu cooler to make sure they were tight.
 
Upvote 0 Downvote
O

OrbitalshocK

Reputable
Apr 1, 2014
33
0
4,530
i think my system reserved folder might actually be the culprit? isnt system reserved supposed to be marked as active (it is) but boot, system, etc. is on the C: drive?? or is system reserved supposed to say system, and active?


 
Upvote 0 Downvote
4Ryan6

4Ryan6

Champion
Apr 14, 2002
20,610
6
52,915


I don't see anything wrong there.

Overclocking a 2500K is a simple matter of increasing the CPU multiplier and the CPU supplied voltage to be sufficient to sustain the increased overclock, not enough voltage equals instability, Period!

This may help you, I Don't Know? It was originally written for an ASRock M/B.

As with any advice given at THGF regarding overclocking, neither I 4ryan6, Toms Hardware Guide, or the owners Best of Media are taking any responsibility for your overclocking your own hardware, you take sole responsibility for your own actions!

This guide is like a Cliffnotes version for advanced overclockers, this is not a novice guide even though very simple!

It is written assuming you are familiar with your BIOS and how to maneuver, change settings, and Clear CMOS when needed, and also that you will be able to translate each BIOS terminology, to the same feature as your M/Bs listed BIOS functions, to gain the same results.

Danger: Going past 1.500v is not recommended unless you have an extremely good cooling solution, meaning high end water cooling, air cooling is not a sufficient cooling solution for the heat this overclock generates, or you will be thermal throttling and not realize it. If you choose to disable thermal throttling you could very well loose your CPU from the voltage/heat required to reach the higher multipliers, remember 1.520v is Intel's tested maximum limit at the time this was written! See: Page 75 Table 7:1

The method I'm going to share here disables all Intels energy saving features, it also disables Turbo Boost, so if you want to run those features, stop reading right now, this is not the guide you need.

This guide will allow you to overclock all 4 cores, with no voltage or multiplier throttling, once again, make sure you have more than just adequate cooling, when overclocking all the cores.

Memory Note: The Sandy Bridge CPU memory controller is designed to run at either 1066mhz or 1333mhz any memory speed past 1333mhz is overclocking the CPU memory controller so you don’t want to overclock the memory from the beginning you need a solid memory foundation to overclock from, or you may be starting out already unstable and never be able to resolve it, no matter what CPU voltage you use.

It is important to manually BIOS set your Memory Timings and Memory Voltage requirements to 1333mhz (Very Important) This will be your best initial route to take, you want your memory literally bulletproof and stable when raising the CPU multipliers to higher levels.

Forget XMP preset profile at this point and research your memory at the website to discover what timings and voltage your memory can run at 1333mhz speed and manually set those timings and voltage!

AFTER! You arrive at a rock solid increased multiplier overclock, you can experiment increasing your memory speed to a higher setting, then if it won’t stabilize you can always drop back to your rock solid stable memory foundation speed.

Memory Note: 1T and 2T settings need to be tested for stability, I recommend you start with the 2T setting and when you reach your highest stable overclock, then see if it will remain stable if you use the 1T setting.

Every motherboard BIOS is different as to labeling each feature so it's your responsibility to discover your motherboards relation to these named settings, an ASRock P67 Extreme 4 is the motherboard BIOS these setting were taken from, I'm not making this long and drawn out so lets get down to business guys!

Disable these Intel CPU features, Enhanced Halt State (C1E), CPU C3 State Support, Package C State Support, C6 State usually on a Z68 M/B, Hardware Prefetcher, Adjacent Cache Line Prefetch, No-Execute Memory Protection, Spread Spectrum, Intel Virtualization (Unless you're running WinXP virtual within Win7, in that case leave it enabled)

Intel Speed Step Special Instructions:
Before you disable Speed Step, which disables Turbo Boost, set Turbo Boost Power Limit to [Manual]
Set Short Duration Power Limit to 140
Set Long Duration Power Limit to 180
Set Long Duration Maintain to the max allowed sec. (Mine is 56)
Additional Turbo Voltage (Mine is set to +0.527 and is working fine, Too little is not good and too much is not good, you'll have to figure this one out for yourself, if the voltage I'm using will not work for you)

BIOS save these special instructions exit and re-enter the BIOS and then disable Intel Speed Step

Some motherboards may allow the BIOS saving of the Intel Speed Step special instructions all in one step, my ASRock P67 Extreme 4 motherboard would not.


Leave CPU Thermal Throttling and Internal PLL over voltage, [Enabled]

Active Processor Cores = All

Core Current Limit = 200 (This is a wattage setting.)

CPU Ratio = Manual (This is the control to manually set your multiplier)

Host Clock Overide or Base Clock = 100mhz ( Do not increase this BCLK, you will be increasing the multiplier, not the base clock)

Voltage Settings;
Power Saving Mode = Disabled
CPU Core Voltage = Fixed or Manual (However your M/B lists this setting to give you manual control over it)
Fixed voltage = ?.??? ( Whatever solid voltage it takes to run a certain multiplier, do not use Offset Voltage)
CPU Load Line Calibration = Level 1 (For an ASRock M/B is 1 to 1, you want as close to straight across voltage from BIOS to OP/SYS, since you will not be speed throttling down with these settings)

DRAM voltage = (You've already manually set that)

Leave all the rest of the voltage setting on AUTO, PLL, VTT, etc.

***********************************************************************************************

Now you're to a point where you simply trial and error boot to discover what manually set CPU voltage will stably run the multiplier you choose.

Testing to Stability:

When getting in the stability ballpark Intel Burn Test saves a remarkable amount of time vs hours of Prime95, use stress testing of your choice to arrive at the first step of stability!

Stress testing programs only test CPU and System Memory, they are not the total stability final say so, as some believe as they do not test Graphics, Sound, or Application or Operating System load, you need to continue testing for stability, to discover if you are using enough CPU voltage to support the multiplier you’ve increased to.

Continuing testing for stability, I suggest using a combination of benchmark programs such as Futuremark’s, 3DM06, 3DMVantage, or 3DM11, or 3Dmark, if you have the advanced versions of any of them you can max the testing settings, (Increase screen resolution, and add all the eye candy testing features, like Anti Aliasing, Antistrophic Filtering, etc. Max all you can) and run 2 or 3 loops.

If you encounter crashes increase your Vcore another notch and continue testing until you can run multiple loops without crashing, and you are pretty much there as far as stability is concerned, but continue and add some gaming with high graphic and sound, and if you have no crashes at all when sound is brought into the picture you’re good to go, if you do experience an in game crash bump up your Vcore another notch.

Always keep in mind, it’s desirable to run as low a Vcore voltage as you can, however it will take a certain voltage level to be 100% stable at the increased multiplier levels and there’s really no getting around that.

Additionally SLI or Crossfire setups usually require additional Vcore increase from the stability level of testing out a single GPU to stability.

It is just not necessary to run 24 hours of Prime95 as some suggest, you can do that and still crash a few minutes into a game, you’re only increasing the multiplier and Vcore voltage, all your other setting are default, so weeding out FSB instability is not necessary with this type of overclock.

Anyone reading this should know how important your cooling is, a good aftermarket cooling solution is an absolute must for reaching the higher multipliers stably, and you should monitor your temps with a program like Real Temp vs 3.70.


Good Overclocking to you and have fun! Ryan





 
Upvote 0 Downvote
O

OrbitalshocK

Reputable
Apr 1, 2014
33
0
4,530
well one thing i thought was weird was that i did my very first 'true' overclock and it worked. before...i had kept turbo and everything on and just raised the multiplier to 45 and left the vcore setting on auto. it had worked fine when i previously tried it oh...three years ago or something. but when i set the multiplier to 41 and raised the vcore from its auto setting it worked just fine. i ran prime95 through the night using the 'blend' setting and hwinfo recorded max temp at 54 on one of the cores and 53 on the other 3.


does the mobo's inability to automatically set a good vcore mean that something is wrong with the cpu and/or mobo? also, what is the lowest hwinfo should record as my vcore??
my readings since i rebooted this morning:
core vid(same for all 4): avg 1.227, max 1.351, min .966
vtt: 1.044-1.056
+3.3VL3.324-3.344
+12v: 12.221 no variation
+5v: 5.042 no varation
vcore: 1.284-1.332, average: 1.322
dimm: 1.512
3vsb: 3.40b no varation
vbat: 3.168 no varation


all 4 thermal throttling state 'no'...i have all the options set on auto in bios not sure why its not enabling it.

and i have a water cooling system for my cpu (h60 i believe) and the pump reads as only going around 440rpm is that okay?
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom