BSOD on Windows Server 2012 Datacenter VM

Jeff Ault 1 Reputation point
2022-06-16T11:20:21.87+00:00

I recently had a BSOD on a Windows Server 2012 Datacenter VM

Here is the dump file:

https://netorgft5226080-my.sharepoint.com/:u:/g/personal/jault_trucoretg_com/EVzIzxrdqi9JpOdn-hYWp4wB7jPXOycA0TmWOhxpCk7QEw?e=4iZ65h

Thanks in advanced for any help.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,563 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Docs 15,556 Reputation points
    2022-06-16T16:59:03.757+00:00

    Please run the DM log collector and post a share link into this thread using one drive, drop box, or google drive.

    If the server is able to run the V2 log collector it will collect more useful logs for the troubleshooting.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

  2. Jeff Ault 1 Reputation point
    2022-06-16T17:12:44.697+00:00
    0 comments No comments

  3. Docs 15,556 Reputation points
    2022-06-16T22:49:23.98+00:00

    There were two BSOD mini dump files with bugcheck 3B.
    Only one was able to be debugged and it did not display any misbehaving drivers.

    If you're able to create some downtime then run Windows Driver Verifier (WDV):
    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

    After a BSOD to recover and be able to return to the desktop boot to safe mode.
    Open administrative command prompt and type or copy and paste the first command to turn off the tool.
    If the first command fails to turn off the tool then use the second command.
    If both commands fail to turn off the tool then use system restore.

    verifier /reset
    or
    verifier /bootmode resetonbootfail

    When back on the desktop run the V2 log collector.

    If there is no immediate BSOD then open administrative command prompt and type or copy and paste: verifier /querysettings
    Post a share link into this thread.

    WDV customized tests may be modified as needed to create BSOD with dump files.

    If there is a BSOD while using WDV then post a new V2 share link into the newest post.

    If you're not able to create downtime then post a new V2 for any new BSOD.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

  4. Limitless Technology 39,781 Reputation points
    2022-06-17T13:19:54.907+00:00

    Hi there,

    These crashes are related to memory corruption and are probably caused by a driver. You can follow these below articles to find the driver and memory leak which is causing you this BSOD.

    Driver verifier is a utility built into the OS that will often find the driver/drivers that are the underlying cause of BSOD/Crashes.

    Driver Verifier-- tracking down a mis-behaving driver.
    https://answers.microsoft.com/en-us/windows/forum/all/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    Memtest is easy to use and is an accurate test of your computer memory. It can tell you if your memory is bad, a motherboard slot is bad, etc.

    Memory problems.
    https://answers.microsoft.com/en-us/windows/forum/all/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461

    Once you find the faulty drivers you can then update or reinstall the specific driver to rectify this issue.

    The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.BSOD Windows Server 2012 R2 https://learn.microsoft.com/en-us/answers/questions/389778/bsod-windows-server-2012-r2.html

    Server 2012 Virtual Machine BSOD after hardware crash - 4 times https://social.technet.microsoft.com/Forums/windowsserver/en-US/4222ba73-64e6-47e6-807b-e8cd98c7f130/server-2012-virtual-machine-bsod-after-hardware-crash-4-times?forum=winserverhyperv

    -----------------------------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer–

    0 comments No comments

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.