BSOD 101 when start using my pc!

[dangerous35]

hello guyz.i buy new gaming pc 2 months ago but not branded I custom maded.after using 2 months its giving me some BSOD errors like these 1.(A Clock Interrupt Was Not Received On A Secondry Processor With In The Allocated Time Interval) 2.(IRQL Not Less Or Equal) 3.(Uncorrectable Hardware Error BLUE SCREEN).ok now i will tell u my story thats what happens.when i connected my all hardware of my new rig i quickly goto BIOS and overclocks the cpu to 4.2 ghz with voltage of 1.36V which is safe range thats i know.installed windows 7 64BIT and windows vista 64BIT ultimate versions.both working fine from 2 months but i used windows vista much more then 7.i keep 7 for emergency use.its works fine with 4.2 ghz from 2 months.then i goto bios and overclocks more set to 4.7 ghz with voltage of 1.46 and all cpu features enabled (CPU Pll Overvoltage Enabled) turbo 4.7 ghz and multiplier to 47 then save and restart after rebooting windows run fine when windows loading some programs at startup its gives me BSOD of (A Clock Interrupt Was Not Received On A Secondry Processor With In The Allocated Time Interval) i quickly changed the settings to default and restart after rebooting windows loaded successfully.I used my pc 4-5 hours after that get cpu one BSOD or random BSOD which i describe on top.i checked everything all parts,cables,vga,heatsink,thermal grease,rams,power,bios updated to latest and flashed serval times,installed new windows,all latest driver,temps,checked HDD after checking thats all i still cant find solution same BSOD,S.then i think its may be power supply problem i goto BIOS and downclocked the cpu tO 3.2 GHZ turbo also 3.2 ghz and everythings defaults save and reboot after rebooting windows loaded fine and voila everything work fine i used my pc daily with 3.2 ghz its works fine and when i increased the cpu to 3.3 ghz its getting crashed with BSOD.i figured out one new thing that when i increase vcore to 1.35 v Its works on 3.4.ghz but before its was working on 3.4 ghz default with every setting on default.and yes heres my pc specification!
PC SPECIFICATION
CPU = INTEL CORE I7 2600K 3.4GHZ 8MB CACHE
RAM = KINGSTON 8GB DDR3 1333 MHZ
MB = GIGABYTE Z68A-D3-B3
VGA = GIGABYTE GTX 470 1280 MB GDDR5 SOC
PSU = GIGABYTE SUPERB 550 WATTS
COOLING = 3 EXTRA STOCK FANS 3200 RPM
CD/DVD = 2 LG SUPER MULTI DRIVES
HDD = WD BLUE 320 GB 7200 RPM,WD GREEN 1TB
DISPLAY = SAMSUNG SYNCMASTER P2370HD
OS = MICROSOFT WINDOWS VISTA ULTIMATE SP2 64BIT
CONTROLLER = XBOX360 CONTROLLER FOR WINDOWS
PLZ GUYZ HELP ME FOR GOD SAKE I SPEND TO MUCH MONEY ON MY PC.Sorry For My Poor English Thank U!!!

 

[richc46]

Welcome
You have given us 3 dump reports, 2 say inconclusive, the third says hardware.
Do you get any beeps when you boot the computer, boot with speakers on.

 

[dangerous35]

no i dont get any beeps!

 

[richc46]

Im sorry, but with the information given, the best that I could do is give you this thread. I think that if followed, you will find the cause of your problem
Stop 0x124 - what it means and what to try - Windows 7 Forums

 

[dangerous35]

Welcome
You have given us 3 dump reports, 2 say inconclusive, the third says hardware.
Do you get any beeps when you boot the computer, boot with speakers on.

ok there is my new dump plz plz check!thanks

 

[richc46]

They all come up inconclusive. I still believe its hardware and that you should follow the information that I gave you

  Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_Latest Dump (PLZ CHECK).zip\Mini102011-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18484.amd64fre.vistasp2_gdr.110617-0336
Machine Name:
Kernel base = 0xfffff800`0245c000 PsLoadedModuleList = 0xfffff800`02620dd0
Debug session time: Thu Oct 20 13:23:29.072 2011 (GMT-4)
System Uptime: 0 days 0:03:20.460
Loading Kernel Symbols
...............................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffffa6001b24180, 6}
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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffffa6001b24180, The PRCB address of the hung processor.
Arg4: 0000000000000006, 0.
Debugging Details:
------------------

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  linpack_xeon64.
CURRENT_IRQL:  d
STACK_TEXT:  
fffffa60`0638bb78 fffff800`024723b0 : 00000000`00000101 00000000`00000019 00000000`00000000 fffffa60`01b24180 : nt!KeBugCheckEx
fffffa60`0638bb80 fffff800`024afd7a : fffff800`024433c0 fffffa60`0638bca0 00000000`0000004c fffff800`024433c0 : nt! ?? ::FNODOBFM::`string'+0x2de4
fffffa60`0638bbc0 fffff800`02420f04 : fffffa60`0638bca0 fffff800`024433c0 00000000`07cb0a80 fffff800`024ffce3 : nt!KeUpdateSystemTime+0xea
fffffa60`0638bbf0 fffff800`024af53d : 00000000`07ca3d80 fffffa60`0638bca0 fffffa80`07923e40 00000000`000000a4 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`0638bc20 00000000`005777c5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x14d
00000000`0371f4a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5777c5

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_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------

 

[niemiro]

They all come up inconclusive. I still believe its hardware and that you should follow the information that I gave you.

Once we get the tests back from that, if negative, Driver Verifier is the way to go, as often 0x101 is caused by incorrect usage of a spinlock by a driver, hence DV sometimes works miracles. In terms of settings, everything except for Low Resource Stimulation

 

[dangerous35]

i tested with 3 core its working fine but when i enable all 4 cores its getting crashed with bsod so what its mean my cpu core is dead and i followed your link but still cant find solution!is there any thing else remaining on my side that i can do!

 

[dangerous35]

4 cores works fine if i increased vcore dynamic voltage but temps go high i tested with linx!

 

[richc46]

My expertise has helped you find the problem. I do not know how to solve it. I and the other members will offer all the help that we can, however.

 

[dangerous35]

temps go high as 98c with prime 95 testing what the hell!

 

[richc46]

Thats the point of prime testing. It puts stress on the computer, to see what gives. Appears that undersress you overheat. The cause of your problem?