Hi Belthasar.
Do some basic things before starting overclocking.
Update your BIOS to the latest possible.
Code:
BiosVersion = P1.10
BiosReleaseDate = 08/30/2011
Get the BIOS version 2.20 dated 6/6/2012 from
ASRock > P67 Extreme4 Gen3.
Make it sure that the PSU is supplying adequate power.
Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.
Dont let the computer overheat. Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of
Speccy.
Have you overclocked the Processor?
Code:
Socket Designation CPUSocket
Processor Type Central Processor
Processor Family bfh - Specification Reserved
Processor Manufacturer Intel
Processor ID a7060200fffbebbf
Processor Version Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
Processor Voltage 80h - 0.0V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 3600MHz
Status Enabled Populated
Processor Upgrade Other
L1 Cache Handle 0005h
L2 Cache Handle 0006h
L3 Cache Handle 0007h
Stress test the CPU.
Hardware - Stress Test With Prime95
RAM ... 2x4 GB @1600 MHz.
Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.
Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark
Those tests are needed, to ensure that the hardware are in good condition to be overclocked.
Also, you should know that improper overclocking causes BSODs. As you are new in overclocking, I will request our overclocking team to guide you the proper way.
In the mean time you supply the information and the test results those are asked .... those will be helpful in the process.
_________________________________________________________________________________________________
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff88002f65180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f65180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff880`0331d648 fffff800`032daa3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f65180 : nt!KeBugCheckEx
fffff880`0331d650 fffff800`0328d6f7 : 00000000`00000000 fffff800`00000002 00000000`000030d4 fffff880`061e4000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`0331d6e0 fffff800`037fe895 : fffff800`03824460 fffff880`0331d890 fffff800`03824460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0331d7e0 fffff800`032800d3 : 00000000`63f73e9a fffff800`033fee80 00000000`00000000 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`0331d810 fffff800`032889e8 : fffff800`033fee80 fffff800`00000001 00000000`00000000 fffff880`0331da98 : nt!KiInterruptDispatchNoLock+0x163
fffff880`0331d9a0 fffff800`0323ccba : 00000000`00000004 00000000`00000000 00000000`00000000 fffffa80`09d18060 : nt!KeFlushMultipleRangeTb+0x258
fffff880`0331da70 fffff800`0323cc3c : 00000000`00000000 fffff880`00000068 00000000`00000000 fffffa80`06d11040 : nt!MmOutPageKernelStack+0x56
fffff880`0331db50 fffff800`032b7588 : 00000000`00000000 00000000`00000080 fffffa80`06d11040 00000000`00000000 : nt!KiOutSwapKernelStacks+0x11c
fffff880`0331dbc0 fffff800`03521bae : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0x48
fffff880`0331dc00 fffff800`032748c6 : fffff880`02f65180 fffffa80`06d22b50 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0331dc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------