BugCheck - The Computer has reboot from a bugcheck

Danilo Rocha 21 Reputation points
2021-03-23T15:18:26.53+00:00

Dear, good morning. I have a VM running windows server 2016 and after adding CPU because of SQL utilization the vm restarted alone and returned me the event id 1001 BugCheck. Error: "The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff80dfd0c9e23). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: f19037b5-cf80-4131-8420-039c2c7abf4e." Could parse the . DMP and point me to the cause of this bug? https://1drv.ms/u/s!AjgKtRsc_hChjRiKu6F88JlGtUZ7?e=v0QAWr![80680-captura-de-tela-2021-03-23-112623.png][1] [1]: /api/attachments/80680-captura-de-tela-2021-03-23-112623.png?platform=QnA

Windows for business | Windows Server | User experience | Other
{count} votes

Accepted answer
  1. Anonymous
    2021-03-23T22:58:26.37+00:00

    Windows debugging is beyond the scope of forums support. You can start a case here with product support.
    https://support.serviceshub.microsoft.com/supportforbusiness

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

4 additional answers

Sort by: Most helpful
  1. Tom Phillips 17,771 Reputation points
    2021-03-23T16:27:26.663+00:00
    0 comments No comments

  2. Danilo Rocha 21 Reputation points
    2021-03-23T17:59:09.56+00:00

    Thanks for the feedback.

    I mentioned the CPU question, why the VM started to restart itself after adding CPU in it.

    On 03/05/2021 we added more resource to this vm, vm restarted (crashed) alone for 4 times in 3 days, on 06/03, 07/03, 08/03, on 08/03 we remove the cpu which was added on 03/05 the machine functioned normally until 03/22, when again we added cpu and the vm started to restart itself.80834-06032021.png80835-07032021.png80823-07032021-2.png80836-08022021.png


  3. Xing Huang (Shanghai Wicresoft Co,.Ltd.) 171 Reputation points
    2021-03-26T08:20:56.283+00:00

    You can use a tool called Winbdg to analyse the dump that you have captured. In the Winbdg, you can know the cause of this issue. How to use Winbdg, you can see Analyzing a Kernel-Mode Dump File with WinDbg - Windows drivers | Microsoft Learn. You can also use Driver Verifier to examine drivers. Please understand due to security policy, we could not provide dump/log analysis. In addition, if this problem is more urgent for you I still recommend that you open a case to Microsoft for further professional help.https://support.microsoft.com/en-us/help/4341255/support-for-busines.

    0 comments No comments

  4. Md. Rubiat Haque 156 Reputation points
    2021-09-12T07:36:16.867+00:00

    Hi, I am Rubiat.

    I have the same problem. Is it solved or not? If it is solved then please explain the solving procedure.

    Thank you


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.