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: BSOD Starting Vmware workstation, Error: CLOCK_WATCHDOG_TIMEOUT

18 Jul 2014   #1
wqwave

Windows 7 Pro SP1 64bit
 
 
BSOD Starting Vmware workstation, Error: CLOCK_WATCHDOG_TIMEOUT

Hi All,

I've been getting blue screen whenever I start any VM on my VMware workstation. This had happened in the past, but not so frequent, perhaps once a month. But since two days ago, this had happened whenever I click on starting my virtual machine. It blue screens within 2seconds.

I recently updated some drivers on my laptop. It is a Lenovo T430. I suspect it is my drivers causing the problem, but I can't pinpoint anything.

Here's the stuff I tried doing but to no avail:
1. Reinstalled VMware workstation.
2. Reset Bios settings.
3. Disabled Anti Virus
4. Run Vmware workstation as administrator.
5. Rollback both my Graphics drivers.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 18/7/2014 4:27:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071914-7612-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF8800AF65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 18/7/2014 4:27:13 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF8800AF65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 18/7/2014 4:23:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071914-7035-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF8800AFD7180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 18/7/2014 4:19:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071914-5304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x4A (0x76D7132A, 0x2, 0x0, 0xFFFFF8802CBA0B60)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 18/7/2014 2:53:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071814-28220-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF8800AF65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 18/7/2014 3:41:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071814-6474-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF8800AF65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 18/7/2014 3:08:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071814-8923-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF8800AF65180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. No offending third party drivers have been found.


My System SpecsSystem Spec
.
18 Jul 2014   #2
wqwave

Windows 7 Pro SP1 64bit
 
 

Another thing to mention.. When I start up vmware workstation, it doesn't starts up. Everytime, I have to run the application again before it starts.
My System SpecsSystem Spec
Reply

 BSOD Starting Vmware workstation, Error: CLOCK_WATCHDOG_TIMEOUT




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD while running vmware workstation
I hope you guys can help me with this issue, already ran memory test 7 passes in each memory no errors.
BSOD Help and Support
Dell M6400 VMWare Workstation, error 0xf4
Hi Folks, I found your website with a search that led to a very similar problem I am having, found it in this post: http://www.sevenforums.com/bsod-help-support/149704-dell-precision-m6400-bsod.html I have a Dell Precision M6400, and I am trying to get VMWare workstation to run but it BSODs...
BSOD Help and Support
BSOD after installing VMWare Workstation
Hi, My laptop is a HP 8470p Elitebook, Windows 7 32bit, 4GB ram, Windows Enterprise. I recently installed VMWare workstation and all was well for a day or 2. Unfortunately I was had to force powering off (holding down power button) because my laptop was not responding whatsoever and ever...
BSOD Help and Support
VMware Player 4 & Workstation 8 Error 1920 or MSI failed at install
Hi all I have been trying for the past couple of hours to install either VMware Player 4 or Workstation 8 and keep getting the same error on both of them. I've tried some of the stuff on the VMware website like regedit and deleted the temp folder and that but it doesn't seem to work for me. ...
Virtualization
vmware server vs vbox vs vmware workstation
Hi all W7 x-64 host 4GB RAM dual core 2.3 ghz cpu. Host CPU usage with 1 XP pro SP3 2GB Virtual machine running a file copy of a 2GB file. Host machine not running any other app. Virtual Box 24% Vmware workstation 19% Vmware server 11%. Now this shouldn't be taken as a rigorous...
Virtualization


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 01:26.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App