Recently our windows 2012 Hyper-V server (which is running 1 2012, 2 2008R2, and 1 2003 virtual servers) experienced a kernel power issue. Event ID 41 Task Category 63.

The HTML of the error we received is as follows

- <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>3</Version>   <Level>1</Level>   <Task>63</Task>   <Opcode>0</Opcode>   <Keywords>0x8000000000000002</Keywords>   <TimeCreated SystemTime="2015-06-19T05:43:18.025501300Z" />   <EventRecordID>84795</EventRecordID>   <Correlation />   <Execution ProcessID="4" ThreadID="8" />   <Channel>System</Channel>   <Computer>XXX-HYPERV</Computer>   <Security UserID="S-1-5-18" />   </System> - <EventData>   <Data Name="BugcheckCode">245</Data>   <Data Name="BugcheckParameter1">0x6d</Data>   <Data Name="BugcheckParameter2">0xfffffa80821e43f0</Data>   <Data Name="BugcheckParameter3">0xfffffa80821e4390</Data>   <Data Name="BugcheckParameter4">0x0</Data>   <Data Name="SleepInProgress">0</Data>   <Data Name="PowerButtonTimestamp">0</Data>   <Data Name="BootAppStatus">0</Data>   </EventData>

 </Event>

So far this is the 5th time we've experienced this issue, looking though the backup and error logs we've noticed that this error occurs every so often when our Symantec server starts its back up. Has anyone else experienced this issue during backups specifically? And would anyone know of some other troubleshooting techniques we could use to narrow down exactly what in these specific backups may be causing this error?

Thanks much!

Hi,

Above all, try to manually perform a backup to ensure if Symantic backup is the cause. If so you can search for any update for the Symantec app. I also saw similar cases which are caused by different application such as antivirus application.

For a deep analysis you may need to collect dump when the issue occurs. As it will be difficult to troubleshoot such an issue via forum, it is recommended to contact Microsoft online support to open a case.