Blue Screen every day

I have just buyed a new pc and continuously receiving "A clock interrupt was not received on a secondary processor within the allocated time " error and different blue screens on original up to date Windows 7 64bit home premium. It happens once a usage, when I have 1 error a time and after restart I can play any games or do anything for days if not restart nothing happens, but blue screen always comes once a usage...

Asus Rampage III gene x58
Corsair 6gb triple
WD 1 TB sata III caviar black
XFX HD6950 2048 mb
Recom Power engine 580
cooler master haf 922

attached is the error files and health report, what should I do?

mcagris said:

I have just buyed a new pc and continuously receiving "A clock interrupt was not received on a secondary processor within the allocated time " error and different blue screens on original up to date Windows 7 64bit home premium. It happens once a usage, when I have 1 error a time and after restart I can play any games or do anything for days if not restart nothing happens, but blue screen always comes once a usage...

Asus Rampage III gene x58
Corsair 6gb triple
WD 1 TB sata III caviar black
XFX HD6950 2048 mb
Recom Power engine 580
cooler master haf 922

attached is the error files and health report, what should I do?

these are all BC 101

The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.

Usually it means you need to update your intelppm.sys file which is either in BIOS or the cd that came with the computer

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Code:

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


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\020911-11715-01.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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a57000 PsLoadedModuleList = 0xfffff800`02c94e50
Debug session time: Wed Feb  9 15:06:14.996 2011 (GMT-5)
System Uptime: 0 days 2:07:11.041
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9C, {0, fffff88002f6cc70, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff88002f6cc70
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff80002a206e0 to fffff80002ac7740

STACK_TEXT:  
fffff880`02f6cc38 fffff800`02a206e0 : 00000000`0000009c 00000000`00000000 fffff880`02f6cc70 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f6cc40 fffff800`02a1fe1f : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`02f6cd90 fffff800`02a13e88 : 00000000`00000000 fffff880`02f64180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`02f6cdc0 fffff800`02ac5fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f6cdf0 fffff800`02ac5e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6cf30 fffff880`040469c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f8cc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
intelppm+39c2
fffff880`040469c2 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  intelppm+39c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc0fd

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+39c2

BUCKET_ID:  X64_0x9C_GenuineIntel_intelppm+39c2

Followup: MachineOwner
---------

I had a cpu voltage warning today but could not catch what it was because it restarted the pc immediately.

May be my motherboard can not do the right feed for cpu?

I check the frequencies with AI suite II and below is the figures:

CPU=0,946 V (sometimes I see it goes up to 1,27 ??)
CPU PLL= 1,819 V

the file intelppm.sys is up to date

mcagris said:

I had a cpu voltage warning today but could not catch what it was because it restarted the pc immediately.

May be my motherboard can not do the right feed for cpu?

I check the frequencies with AI suite II and below is the figures:

CPU=0,946 V (sometimes I see it goes up to 1,27 ??)
CPU PLL= 1,819 V

the file intelppm.sys is up to date

Your intelppm is date 7/13/2009 (there may be newer) but even if there inst, driver do get corrupted. While unsure of the intellppm's function it may control the very voltage you are toying with now. It cant hurt to re-install it and is both easy and free.