I just received my first BSOD on a Windows Server 2008 R2, which is part of a two node Hyper-V cluster. Here are the Events it generated, below are dumps. The server was last touched/updated as far as any installs on 26.2. when patches were installed. Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 8.3.2011 10:38:28 Event ID: 1001 Task Category: None Level: Error Keywords: Classic User: N/A Computer: server1 Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff880022a4180, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 030811-12292-01. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-03-08T09:38:28.000000000Z" /> <EventRecordID>936375</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>System</Channel> <Computer>server1</Computer> <Security /> </System> <EventData> <Data Name="param1">0x00000101 (0x0000000000000019, 0x0000000000000000, 0xfffff880022a4180, 0x0000000000000007)</Data> <Data Name="param2">C:\Windows\MEMORY.DMP</Data> <Data Name="param3">030811-12292-01</Data> </EventData> </Event> Log Name: System Source: Microsoft-Windows-Kernel-Power Date: 8.3.2011 10:38:18 Event ID: 41 Task Category: (63) Level: Critical Keywords: (2) User: SYSTEM Computer: server1 Description: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>2</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000002</Keywords> <TimeCreated SystemTime="2011-03-08T09:38:18.400006900Z" /> <EventRecordID>936377</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>server1</Computer> <Security UserID="S-1-5-18" /> </System> <EventData> <Data Name="BugcheckCode">257</Data> <Data Name="BugcheckParameter1">0x19</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0xfffff880022a4180</Data> <Data Name="BugcheckParameter4">0x7</Data> <Data Name="SleepInProgress">false</Data> <Data Name="PowerButtonTimestamp">0</Data> </EventData> </Event> Here's a mini-dump: http://cid-8af2f67a3f3cd55b.office.live.com/self.aspx/.Public/030811-12292-01.dmp I also have a full dump, which I loaded up in WinDB and executed !analyze -v t. This is what I got: http://cid-8af2f67a3f3cd55b.office.live.com/self.aspx/.Public/memory.txt Please let me know if additional information should be provided to assist in troubleshooting this.

According to the error message, it seems to be system crash issue and need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file here in the forum. Therefore, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Hope the issue will be resolved soon. http://www.virmansec.com/blogs/skhairuddin

Thank you for the quick reply. While we have SA part of our VLSC it appearantly doesn't include CSS, it's a shame no additional pointers can be provided on the forums.

take a look here: http://support.microsoft.com/kb/975530/en-us

Bug Check Code 101: The CLOCK_WATCHDOG_TIMEOUT bug check has a value of 0x00000101. This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. Cause: The specified processor is not processing interrupts. Typically, this occurs when the processor is nonresponsive or is deadlocked. For more information, refer to this Microsoft article. As this is a minidump and not a full dump, I am unable to get many informations about the BSOD. Try the hotfix proposed by FZB. If it does not fix the problem, please configure your system to generate full dumps or contact your manufacturer technical support. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Thank you all for your suggestions. The link FZB provided just might be the issue. I should add that only a single socket is installed on this server and that a full dump was generated (I can provide it if an e-mail is given).

Zip it and use Microsoft Skydrive to upload it. Try the Microsoft hotfix and tell us the result. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration