Hyper-V Hotfix for "0x00000101 - CLOCK_WATCHDOG_TIMEOUT" on Nehalem systems
We have just released a new hotfix for Windows Server 2008 R2 that address the issue that users were getting a bluescreen of death on Intel Xeon 5500 series processor-based computers with the following text:
0x00000101 (parameter1, 0000000000000000, parameter3, 000000000000000c)
CLOCK_WATCHDOG_TIMEOUT
You can download the hotfix from here: https://support.microsoft.com/kb/975530
For the curious, this issue is actually caused by a bug (or in Intel terms “erratum”) that causes these processors to generate spurious interrupts. You can read about this in the latest Intel documentation for this process series: https://www.intel.com/assets/pdf/specupdate/321324.pdf
Cheers,
Ben
Comments
Anonymous
October 16, 2009
The comment has been removedAnonymous
October 16, 2009
Is this the same problem that could be avoided with the BIOS change of: Disable the C1E setting in the BIOS?Anonymous
October 16, 2009
Robert - Yes Cheers, BenAnonymous
October 17, 2009
When we first saw this issue a month ago we escalated it through our MS Partner Support and Dell support and they never mentioned the CIE fix until I posted to Expert's Exchange. Thanks for the further insight from Intel, Ben. Will this eventually get pushed as an update rather than a hotfix?Anonymous
October 18, 2009
Is this hotfix also applicable to Hyper-V Server R2?Anonymous
October 19, 2009
Do you know if there is a fix for the same issue on AMD Turion X2 processors? My development laptop has been plagued by this problem for as long as I can remember, and I'd love to get that resolved.Anonymous
October 20, 2009
Thanks for posting this. Just had my Dell R610 with production VM bugcheck this morning. Will be installing this tomorrow night.Anonymous
October 28, 2009
Grant Dawson - I do not know what the plans are here. Joris - Yes, it is applicable to Hyper-V Server R2. Scott - No, it is not applicable there. Note that this bug check can also be caused by problematic drivers. Cheers, BenAnonymous
November 11, 2009
Hello, after the installation of hotfix KB975530 there is no difference to before. We use Windows Server 2008 R2 - Cluster with role Hyper-V and SQL Server 2008. We have the bluescreen in both combinations. The file versions didn't changed: Hvax64.exe 6.1.7600.16431 Hvboot.sys 6.1.7600.16385 Hvix64.exe 6.1.7600.16431 Greetings from germanyAnonymous
November 13, 2009
The comment has been removedAnonymous
November 13, 2009
correction, I meant to say I have gotten the same stop error 0x101 as listed in the kb article only 2 out of the last 3 blue screens. one of BSOD's generated the 0x19 I listed above.Anonymous
November 16, 2009
Hi. I was testing the included Virtual PC in Windows 7 RTM. The PC is AMD Athlon 64x2 and also made a BSOD 0x101. Regards. Alex.Anonymous
November 25, 2009
We have same problem. I hope it solves.Anonymous
December 01, 2009
This didnt work for us.We get BSOD again in 4-5 days.Anonymous
December 02, 2009
We hit this within 24 hours of our first build of Hyper-V Server 2008 R2 on an Intel SR1630HGP with Intel Xeon X3450 CPU. The hotfix went on after the blue screen which happened twice in short order. We shall now see if the server gets beyond the 24 hour mark without blue screening. http://blog.mpecsinc.ca/2009/12/hyper-v-clockwatchdogtimeout-error.html PhilipAnonymous
December 07, 2009
We hit this within a few hours after installing Windows 2008R2 with Hyper-V Role the first time. Than we installed the hotfix but we got the exactly same bugcheck on the following day with hotfix applied. We now applied registry changed to disable ACPI-C2 / C3 and will see if the bluescreens comes again. The Intel specification update mention the C6 state instead of C2/C3 is this also disabled with the registry changes from the kb article? We are using an Intel Xeon 3450 processor, does the hotfix check for the processor id? The BugCheck has a different address 0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff88001e5d180, 0x0000000000000002) Regards, ReinhardAnonymous
December 15, 2009
This hotfix isn't helping. The 0x101 BSOD still happens on Intel Xeon 5500.Anonymous
December 15, 2009
When I download the hotfix and try to extract the files, it fails. It appears the hotfix is corrupted. An error occurred while unzipping. One or more files were not successfully unzipped. The error code is 110 It creates the Windows6.1-KB975530-v3-x64.msu 1kb in size. It doesnt prompt for a password.Anonymous
December 21, 2009
We have installed the fix 975530, but it does not help us, we get the exact same dump every time we use VM's.Anonymous
December 24, 2009
I have an open ticket with MS. They claimed the hotfix is being re-worked and will be released in a month or so. For now, use the workaround.Anonymous
August 29, 2010
Ben, Just received anew Asus G73JH (i-7 processor, specifically 720m), and am experiencing the same problem. I have not yet tried the HotFix since this processor family is not listed. Would you expect this to apply to a 720m? DavidAnonymous
August 29, 2010
The comment has been removedAnonymous
August 31, 2010
David - Have you applied the rollup hotfix that came out through Windows Update recently? (blogs.msdn.com/.../hyper-v-hotfix-rollup-now-available.aspx) If yes - then you already have this fix. Cheers, BenAnonymous
January 03, 2011
We've got a user getting a similar error running XP Mode in Windows 7 Professional 64-bit. The similarities are there there (Windows 7/Server 2008 RS and Virtual PC/Hyper-V), so I'm curious if this is the same root issue. Have there been any hotfixes that address this issue in Windows 7 with Virtual PC?Anonymous
January 05, 2011
aparker_sia - This is the first report I have heard of it with Virtual PC. Can you please contact Microsoft product support with the details? Cheers, BenAnonymous
May 12, 2013
The comment has been removedAnonymous
February 06, 2014
Watch Dogs - Limited Edition включает: Игра Watch Dogs Награды: Костюм «Блюм» Бонус: Модификатор оружия: снижена отдача от выстрелов Погрузитесь в Чикаго, в те времена, когда в повседневную жизнь людей стали активно внедряться технологии, когда мир стал заложником огромной единой компьютерной сети. Имя ей – Центральная Операционная Система, или ctOS. Именно ей принадлежала власть над большей частью базы технологических данных. Ей были доступны все сведения о городе, а также обо всех его жителях. Наш герой – талантливый хакер и мастер в своем деле Эйден Пирс. Его опасные увлечения привели к трагедии, связанной с его семьей. И теперь Эйден считается одним из главных преступников. В поисках правды и справедливости, вы должны помочь нашему герою, преодолевая гигантские пространства цифровой реальности. Получить ключ к игре можно здесь http://buykeys.3dn.ru/