Daily Freezing on Vista 64-bit (Clock interrupt...)

M

mpic92

Limp Gawd
Joined
Dec 9, 2006
Messages
155
I own an HP Pavilion e9180t desktop computer.
-Windows 7 (64-bit)
Intel Core i7 CPU 920 @ 2.67 GHz
8 GB RAM
nVidia GeForce GT 220

The computer origionally came with Windows Vista 64-bit. I upgraded to Windows 7, and later did a complete re-install, this time abandoning all the software/files on the computer.

Throughout my entire time owning the computer (w/ both Vista and 7), the computer will freeze daily. It seems to be related, or at least I notice it's coming, when I'm listening to audio like in iTunes, and the music will stop skipping/acting funny. Also the mouse may lag for a second or so, and I notice the processing ticker on the desktop chugging away. Eventually, it will get to a point where the computer will suddenely completely crash, the ticker light goes out, and nothing will move. The image is just frozen, and I frequently get the following error message:

A Clock interrupt was not received on a secondary processor within the allocated time interval.

Technical information:

STOP: 0x00000101 (0x0000000000000019), 0x000000000000000, 0xFFFFF88003100180, 0x000000000000006)
Click to expand...

The problem is incredibly annoying and I see no way around it. I have researched that error message but haven't found a real solution. I haven't ever messed with the hardware of the system since I ordered it from HP. Any help would be greatly appreciated.
 
Upload one of the dump files that Windows is making when you get the BSOD. If it doesn't make one, set it to do so. Start, advanced system settings, 3rd Settings button, select anything but None under Write debugging information.
 
It says it's at %SystemRoot%\MEMORY.DMP

Where do I find this to upload?
 
Don't upload.

From the same place you checked that "write debugging information" was set, change it to "Kernel memory dump"
Install windbg from http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx
Next time you blue screen, after reboot, launch windbg as admin
Press Ctrl+D
Open %SystemRoot%\MEMORY.DMP

From the windbg command line, execute the following
.symfix
.reload
!analyze -v

Paste the output
 
Where do I find the %SystemRoot%\MEMORY.DMP file? What folder is it in?

Thanks
 
You can type %SystemRoot% into the address bar as it resolves to an actual directory name.
Most of the time, though, it's C:\Windows.
 
Windbg says I need to log on as an admin and don't have permission... but I am on an admin account, the only account on the computer...?
 
Don't think this worked as correctly as it should have, but this is what I got:

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032a4e50
Debug session time: Thu Dec 31 15:23:44.988 2009 (GMT-5)
System Uptime: 0 days 0:29:01.096
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................Missing image name, possible paged-out or corrupt data.
.*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {19, 0, fffff880009b2180, 4}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntkrnlmp.exe

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

0: kd> .symfix
0: kd> .reload
Loading Kernel Symbols
...............................................Missing image name, possible paged-out or corrupt data.
.*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147

WARNING: .reload failed, module list may be incomplete
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: fffff880009b2180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

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

Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete
Missing image name, possible paged-out or corrupt data.
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - NTSTATUS 0xC0000147
WARNING: .reload failed, module list may be incomplete

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: d

STACK_TEXT:
fffff880`009a9768 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: ZEROED_STACK

Followup: MachineOwner
---------
Click to expand...
 
You need to run .symfix first, then do .reload and !analyze -v
 
I am. I've tried multiple times. Nothing happens when I enter .symfix.
 
You must log in or register to reply here.
Back
Top