Server 2016 Hyper-v Rebooting on BugCheck 0x000000d1 at start of Windows Server Backup


hi have single lenovo x3550 server dual-intel cpu , 128gb ram lenovo v3700 das storage , dual sas controller cards. hyper-v host installed on server raid1 drives vm's installed on v3700 drives.

we ran 2 years windows server 2012 r2 , hyper , upgraded (clean install) to windows server 2016 datacenter. after enabling windows server backup and scheduling backups late evening have bsod on following bugcheck. attempted 2 methods of backup 1 separate volume on attached das stoarage , 1 last evening external usb drive. appears tho backup starting @ scheduled 10:00pm throws error "eventid 51 warning of \device\harddisk1\dr1 during paging operation" 3 minutes process , the bugcheck , reboot. appreciated.

before backups system seems function fine. 

log name:      system
source:        microsoft-windows-wer-systemerrorreporting
date:          8/21/2017 10:53:39 pm
event id:      1001
task category: none
level:         error
keywords:      classic
user:          n/a
computer:      hvsrv
description:
computer has rebooted bugcheck.  bugcheck was: 0x000000d1 (0x0000000000000828, 0x0000000000000002, 0x0000000000000000, 0xfffff807d7cc56dd). dump saved in: c:\windows\memory.dmp. report id: 86a3d8f0-bcef-4f70-b561-9c8f29d009c3.
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="2017-08-22t05:53:39.557101600z" />
    <eventrecordid>10491</eventrecordid>
    <correlation />
    <execution processid="0" threadid="0" />
    <channel>system</channel>
    <computer>hvsrv</computer>
    <security />
  </system>
  <eventdata>
    <data name="param1">0x000000d1 (0x0000000000000828, 0x0000000000000002, 0x0000000000000000, 0xfffff807d7cc56dd)</data>
    <data name="param2">c:\windows\memory.dmp</data>
    <data name="param3">86a3d8f0-bcef-4f70-b561-9c8f29d009c3</data>
  </eventdata>
</event> we have enabled , use purely hyper-v host


jttechie - jim

hi jttechie,

please check dump file locates in c:\windows\memory.dmp detailed information why bsod occurs.

here blogs how read dump files, reference:

https://social.technet.microsoft.com/wiki/contents/articles/6302.windows-bugcheck-analysis.aspx

https://blogs.technet.microsoft.com/juanand/2011/03/20/analyzing-a-crash-dump-aka-bsod/

besides, we may turn third-party tools key information of dump file:

http://www.osronline.com/page.cfm?name=analyze

(note: third-party tool, not guarantee safety since may change content without notification, reference.)

best regards,

anne


please remember mark replies answers if help.
if have feedback technet subscriber support, contact tnmff@microsoft.com.



Windows Server  >  Windows Server 2016 General



Comments

Popular posts from this blog

CRL Revocation always failed

Failed to query the results of bpa xpath

0x300000d errors in Microsoft Remote Desktop client