Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: HP m9600t Win7 clock interrupt not received on secondary processor

05 Dec 2012   #1
WillPC

Windows 7 Home Premium 64bit
 
 
HP m9600t Win7 clock interrupt not received on secondary processor

HP m9600t Win7 clock interrupt not received on secondary processor crash.

Pc will crash and display BSOD with the following error:
"A clock interrupt was not received in a secondary processor within the allocated time interval"
My PC will fine for an hour or so and then crash. I tried the Win 7 system repair without success. It just stuck in a loop.

Where do I begin to troubleshoot this issue? I've uploaded the SF Diagnostic Tool results.

I've not installed any new hardware recently. The last software update was Quicktime/itunes. Unfortunately, my system restore only shows restore points well in the past.

Many thanks in advance for any help,
Will


My System SpecsSystem Spec
.
05 Dec 2012   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

These threads should help you start.
Quote:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80097c08f8, 0, 0}

Probably caused by : GenuineIntel

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80097c08f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0357e6f0 fffff800`0351fcb9 : fffffa80`097c08d0 fffffa80`06a2fb60 fffff8a0`0000000e 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`0357ec10 fffff800`03400687 : fffffa80`097c08d0 fffff800`0347a2b8 fffffa80`06a2fb60 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`0357ec40 fffff800`03367a35 : fffff800`034dbac0 00000000`00000001 fffffa80`087f7de0 fffffa80`06a2fb60 : nt!WheapProcessWorkQueueItem+0x57
fffff880`0357ec80 fffff800`032e4471 : fffff880`01288e00 fffff800`03367a10 fffffa80`06a2fb00 00000000`0000055a : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`0357ecb0 fffff800`03574f7a : 00000000`00000000 fffffa80`06a2fb60 00000000`00000080 fffffa80`06a16040 : nt!ExpWorkerThread+0x111
fffff880`0357ed40 fffff800`032cb9c6 : fffff880`03371180 fffffa80`06a2fb60 fffff880`0337c0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0357ed80 00000000`00000000 : fffff880`0357f000 fffff880`03579000 fffff880`030b8540 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

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

5: kd> !errrec fffffa80097c08f8
===============================================================================
Common Platform Error Record @ fffffa80097c08f8
-------------------------------------------------------------------------------
Record Id     : 01cdd1c604228f64
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/4/2012 2:21:18 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80097c0978
Section       @ fffffa80097c0a50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Micro-Architectural Error
Flags         : 0x00
CPU Version   : 0x00000000000106a4
Processor ID  : 0x0000000000000004

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80097c09c0
Section       @ fffffa80097c0b10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000004
CPU Id        : a4 06 01 00 00 08 10 04 - bd e3 98 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80097c0b10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80097c0a08
Section       @ fffffa80097c0b90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : Internal timer (Proc 4 Bank 5)
  Status      : 0xfe00000000800400
  Address     : 0x0000388000c0196a
  Misc.       : 0x0000000000007fff
My System SpecsSystem Spec
05 Dec 2012   #3
WillPC

Windows 7 Home Premium 64bit
 
 

Hi Koolkat77,
Many thanks for your reply and suggestions. Since my first post, I've the following additional insight:
1. In performing a diagnostic test "F9", the PC passes everything except Boot Path. It fails test with BIOHD-5 error
2. In exiting the test, Windows will not load instead I get "read disk error" ctrl-alt-del

Is this the hardware that's stressed - my hard disk drive?

It's odd since the HDD passes the diagnostic test above aswell as an earlier CHKDSK scan.

Thoughts?

Thanks,
A
My System SpecsSystem Spec
.

06 Dec 2012   #4
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Your crash report zip file was incomplete.
When you can, upload the complete report, so we can help you.
Blue Screen of Death (BSOD) Posting Instructions
When posting any crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes.

Are you overclocking anything?

Is this your computer?
HP Pavilion Elite m9600t Desktop PC Product Specifications and Configurable Options
If it is, can you verify the components?
We need more details on your system.
Do you still have the original PSU?
OEM PSUs are not the best quality and do go out frequently.

HP diagnostics may be ok for some things but, you need to run other tests. These tests are more thorough and will give us a better idea of where to start.

This test will be ran from a CD/USB stick and doesn't need W7 to be running.
Run Data Lifeguard Tools 11 for DOS on your hard drive.
How to create a Data Lifeguard diagnostics bootable CD.
Run the QUICK TEST and the EXTENDED TEST.

Do you have the W7 installation disks?
If you don't follow this tutorial to make a System Repair Disc.
How to Create a Windows 7 System Repair Disc
Quote:
If you are unable to boot your Windows 7 to create a Windows 7 System Repair Disc, then you could create it on another computer to use on your computer.
From 19, Jan 2011
Code:
STOP 0x0000007A: KERNEL_DATA_INPAGE_ERROR
Usual causes:  Memory, Paging file corruption, File system, Hard drive, Cabling, Virus infection, Improperly seated cards, BIOS, Bad motherboard, Missing Service Pack
ERROR_CODE: (NTSTATUS) 0xc0000056 - A non close operation has been requested of a file object with a delete pending.
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
MODULE_NAME: memory_corruption
FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096
This was after you got the new WD hard drive.
Have you ran memtest86+ again since 24 Jan 2011?

Run memtest86+ for 7 full passes, with all RAM cards installed.
Best to run overnight as depending on the amount of RAM you have may take several hours.
If you get any errors you can stop the test.
RAM - Test with Memtest86+

From 22, April 2011 and 3, May 2011
Code:
STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT
Usual causes:  Device driver, BIOS bug, hardware defect
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.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
CPU issue.

From 25, June 2011
Code:
STOP 0x0000009C: MACHINE_CHECK_EXCEPTION
Usual causes:  Hardware error (similar to STOP 0x124)
BUGCHECK_STR:  0x9C_GenuineIntel
FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c
Another CPU issue

From 3, Dec 2012
Code:
STOP 0x00000124: WHEA_UNCORRECTABLE_ERROR
Usual causes:  Hardware, Incompatibility, May be driver corruption
Probably caused by : GenuineIntel
BUGCHECK_STR:  0x124_GenuineIntel
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV
CPU again.

This indicating a CPU problem for a long time.
These will have to wait until you can boot W7.
Have you checked the CPU core temps?
Use Real Temp , to check the CPU temps when at idle, under load and/or testing.
Let us know the minimum and maximum temps you get.

Have you remove the CPU, or the CPU cooler?

These kind of errors can be caused by bent CPU pins, bad motherboard or bad PSU, and of coarse a bad CPU, which is rare.


From your System Event Logs:
Code:
Event[32654]:
  Log Name: System
  Source: Disk
  Date: 2012-09-20T15:17:07.116
  Event ID: 11
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: HomeOffice-PC
  Description: 
The driver detected a controller error on \Device\Harddisk8\DR9.
This is indicating a hard drive error.

Your System Event Logs stop on 1, Oct '12
To check the System Event Log settings.
1. Start Event Viewer.
2. In the console tree, expand Windows Logs and select System.
3. On the Action menu, click Properties.
4. In the General Tab, ensure 'Enable logging' is checked.
Maximum log size should be 20480
Under 'When maximum event log size is reached': select 'Overwrite events as needed (oldest events first)'
Click OK.

If you are still not getting new System Event Logs, you can 'Clear Log' on the same page.
My System SpecsSystem Spec
09 Dec 2012   #5
WillPC

Windows 7 Home Premium 64bit
 
 

In an attempt to repair my PC, I removed the HDD and installed a new one and did a fresh Windows 7SP1 install. My PC continues to intermittently freeze, hang and go to a complete black screen, although I've not had a BSOD. In reply to your questions:
1. Are you overclocking anything? No.
2. Is this your computer? Yes, HP m9600t, original components per the link HP Pavilion Elite m9600t Desktop PC Product Specifications and Configurable Options 4 x 2GB memory.
3. Do you still have the original PSU? Yes, original PSU.
4. Have you ran memtest86+ again since 24 Jan 2011? I ran a memory diagnostic test from the Win 7 Recovery panel. The panel that begins with the choices System Repair, System Restore etc. The RAM passed this diagnostic test.
5. Have you checked the CPU core temps? The temperature appears to range from 40c to 54c
6. Have you remove the CPU, or the CPU cooler? No, not as yet.

I attach the results from the SF diagnositc tool. This is after the new HDD and Win7 install. I look forward to your thoughts again. Thanks for all the help and advice.
-W
My System SpecsSystem Spec
09 Dec 2012   #6
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

This points to a hardware issue.
That link for specs doesn't specify what you actually have.
Can you fill in your 'My System Specs'?
You can use this app to find them: Speccy Free System information Utility
Then enter them in the 'My System Specs' drop box at the lower left of any of your posts.

What is the age of your computer?
The oldest driver at your support site is from 2009, is this when you got it?

As mentioned, you need to run the tests that we suggest.
For example, Windows memtest is not a good RAM test, it will pass bad RAM, memtest86+ is a much better RAM test and is recommended at all Manufacturers motherboard and RAM support sites.

Run memtest86+ for 7 full passes, with all RAM cards installed.
Best to run overnight as depending on the amount of RAM you have may take several hours.
If you get any errors you can stop the test.
RAM - Test with Memtest86+

Did you install any programs after the new W7 install?
List all programs and drivers you installed.

Answers to your replies.
1. Good, let us know if you make any BIOS changes.
2. It will help if we have the exact specs.
3. This may need to be checked. Have you upgrated the graphics card? This may change the PSU requirement.
4. See above, the Windows memtest is not recommended.
5. If this is at idle, then the temps are very high. When under load it may pass the threshhold limit and reduce the frequency and voltage in order to lower temps. This sometimes will give you CPU errors like you're having.
Get some CPU thermal paste, remove the CPU cooler and CPU, clean off the old paste and apply new thermal paste.
Let me know if you need further details on how to do this.
6. Have you ever removed one?
My System SpecsSystem Spec
10 Dec 2012   #7
WillPC

Windows 7 Home Premium 64bit
 
 

Dave76,

Thanks again for all the help.

What is the age of your computer? April 2009, it was bought new direct from HP.

1. I've made no BIOS changes
2. Attached are my specs using Speccy.
3. I've not upgraded my graphics card. It's the original.
4. I ran Memtest overnight, no errors reported after 9 passes, see attached photo.
5. Would an overheating CPU have hung the PC during the overnight memtest?
6. I did something similar with my son's xBox sometime ago.

Additional troubleshooting, I removed and reinstalled all the RAM cards before the memtest.
My System SpecsSystem Spec
10 Dec 2012   #8
WillPC

Windows 7 Home Premium 64bit
 
 

Software installed:
Windows 7
Office 2007
PDF Viewer
Adobe Reader
IE 9
Chrome
MozBackup
Thunderbird
My System SpecsSystem Spec
11 Dec 2012   #9
Dave76

Microsoft Community Contributor Award Recipient

Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
 
 

Good that it passed memtest86+.

Clean and re-apply the CPU thermal paste, to get lower CPU temps.

Let us know if you get anymore crashes.
My System SpecsSystem Spec
Reply

 HP m9600t Win7 clock interrupt not received on secondary processor




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
A clock interrupt was not received on the secondary processor
Last month I started getting this BSOD, and I'm not sure the reason. I'd love help on what to do to see if anything I did caused this. I know prior to it happening AVG was accidentally set to delete a bunch of things and may have deleted some important files, but I'm not sure if it was just...
BSOD Help and Support
A clock interrupt was not received by a secondary processor
New to building computers... Managed to get it together and works really well.. right up until it doesn't. I am an architect and built a computer for modeling and rendering. The modeling program I use is a 32 bit program, so I wanted to overclock as clock speed makes a huge difference in the...
General Discussion
A clock interrupt was not received on the secondary processor
From time to time im having blue screen crash Heres what it says : ImageShack® - Online Photo and Video Hosting Its new pc so it really bothers me whats wrong.
BSOD Help and Support
bsod, clock interrupt not received on secondary processor + 1 other
am getting 2 bsod on computer after installing a printer? was working without flaw up until then. first (and most persistent) is the one on the subject line and the other is "problem has been detected and windows has been shut down to prevent damage" I've attached photos of both with appropriate...
BSOD Help and Support
BSOD - Clock interrupt not received on secondary processor
I have had a fairly stable system until I decided to leverage 8gb of ram and 64bit through Windows 7. Now daily or more I get greeted with this consistent error that from reading in the various help sites could be one of a million things. I have tried: cleaning extensively with Spybot seek and...
BSOD Help and Support
clock interrupt was not received on secondary processor
I've been getting the BSoD with the error message: "a clock interrupt was not received on secondary processor". I've tried a lot of things, including an update of my BIOS and my video card drivers. The error details I get once I restart Windows 7 follows: Problem signature: Problem Event...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 10:44.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App