The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0x0000000000000000, 0x0000000000000000).

家濠 胡 1 Reputation point
2021-06-24T04:02:15.893+00:00

My server 2012 R2 system has rebooted with this bug check

The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP.

Any thoughts on how to fix this?

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

2 answers

Sort by: Most helpful
  1. Docs 15,136 Reputation points
    2021-06-24T05:03:01.857+00:00

    Please run V2 > post a share link into this thread
    https://www.windowsq.com/resources/v2-log-collector.8/
    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    Open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp > if the file size is < 1.5 GB then > save to the downloads folder > zip > post a separate share link into the thread using one drive, drop box, or google drive

    .
    .
    .
    .
    .

    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: Vote = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

  2. Carl Fan 6,836 Reputation points
    2021-06-24T09:35:26.54+00:00

    Hi,
    This error is down to Windows Server 2012 not being able to communicate with the hardware device correctly with the drivers that are installed, most of the time the error is caused by incompatible storage controller drivers. First run all Windows Updates and then make sure that you have compatible drivers from your vendor.
    Hope this helps and please help to accept as Answer if the response is useful.
    Best Regards,
    Carl