Educad
asked on
Hardware Malfunction
Hi,
There have been BSOD showing this three times on one physical PC:
*** Hardware Malfunction
Call your hardware vendor for support
*** The system has halted ***
The client PC is running Windows 7 64bit pro, HP-6300 i5 3.2GHz 4GB RAM, and I installed Virtual PC 2007 on this PC. Two users are using the physical machine at the moment.
Bugcheck code was 101.
mini dump file:
There have been BSOD showing this three times on one physical PC:
*** Hardware Malfunction
Call your hardware vendor for support
*** The system has halted ***
The client PC is running Windows 7 64bit pro, HP-6300 i5 3.2GHz 4GB RAM, and I installed Virtual PC 2007 on this PC. Two users are using the physical machine at the moment.
Bugcheck code was 101.
mini dump file:
Probably caused by : ntoskrnl.exe
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: fffff880031d7180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002c5e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 531590fb
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You can try checking Memory. Look for memtest86.org, create a bootable CD, start with this and run memory tests.
After doing this, remove peripherals and try running with only memory and hard drive. Remove CD (DVD) and any other peripherals.
After doing this, remove peripherals and try running with only memory and hard drive. Remove CD (DVD) and any other peripherals.
CLOCK_WATCHDOG_TIMEOUT points to a CPU issue; either it wasn't responding or became deadlocked
Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx
Bug Check 0x101: CLOCK_WATCHDOG_TIMEOUT
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx
Virtual machines used hardware virtualization. Does your mainboard have a latest firmware?
it mentions IRQ d:
you can lookup what device is using the irq D:
you can lookup what device is using the irq D:
ASKER
I have updated all outdated drivers and ran hardware diagnostic tools from HP. It said all components passed. So I have a feeling that this might relate to Virtual PC 2007. I left local admin user logged in as this account is used to run Virtual PC 2007, and another person logs into the PC with his account. And another person logs into the virtual PC which is running on the physical pc. Would this be an issue?
noxcho,
I am not sure how to check mainboard has a latest firmware. BIOS is still latest version according to HP site.
nobus,
IRQ d: I am not sure how to check this either, could you please let me know how?
noxcho,
I am not sure how to check mainboard has a latest firmware. BIOS is still latest version according to HP site.
nobus,
IRQ d: I am not sure how to check this either, could you please let me know how?
So I have a feeling that this might relate to Virtual PC 2007. <-- I only use VMware but I have never had a virtual machine cause a host hardware malfunction.
If the BIOS is the latest that should be sufficient.
If the BIOS is the latest that should be sufficient.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Open the System Information utility (msinfo32.exe), and navigate to System Summary\Hardware Resources\IRQs to view the IRQs in use on your system, and the devices using them.
ASKER
After driver updates no issues have been found yet.. but still need more time to make sure that was driver issue.
ASKER
Open in new window