Windows Server 2012 R2 Keeps Rebooting after bugcheck


  • I have a HP Proliant DL380 Gen 9 server with windows server 2012 R2 operating system.

    The machine keeps rebooting with the message below every ~3 hours.

    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 022018-18187-01.

    Server has all the latest firmware and windows updates applied. Server is ~2 years old and under warranty.

    Hope someone can help.



    Wednesday, February 21, 2018 4:38 PM

All replies

  • Bug Check Code 0x133:

    You should start by installing the latest updates of your drivers. You may get more details by reading the dump file:

    If this does not help, I would advise to check this with your vendor support.

    This posting is provided AS IS with no warranties or guarantees , and confers no rights.

    Ahmed MALEK

    My Website Link

    My Linkedin Profile

    My MVP Profile

    Wednesday, February 21, 2018 4:43 PM
  • I've already installed all the latest drivers as far as I can tell.

    We do not have support through HPE.

    Wednesday, February 21, 2018 5:19 PM
  • You should try reading the dump and see if you can get more information.

    This posting is provided AS IS with no warranties or guarantees , and confers no rights.

    Ahmed MALEK

    My Website Link

    My Linkedin Profile

    My MVP Profile

    Wednesday, February 21, 2018 6:52 PM
  • Hi,

    It is recommended to patch the system fully using Windows Update/Hotfix. And it will be helpful for resolving some known issues and improving the performance. Such as below.

    "0x00000133" Stop error after you install hotfix 3061460 in Windows Server 2012 R2:

    "0x00000133" Stop may occur on systems with Intel processors that are running Windows 8.1 or Windows Server 2012 R2:

    Besides, please open CMD, type “sfc /scannow” and “chkdsk /r /f” to check/repair system files/disks.

    Also, as problem happens regularly, is possible I would recommend you to re-start system in Safe Mode and Clean Boot, do not manually start 3rd party process, and wait for a period of time, it would be helpful for identify whether it is hardware driver, or, 3rd party process relate.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Wednesday, March 07, 2018 2:20 PM
  • Brandon,

    I am having the same exact issue on a brand new HP ML350 Gen 9, although in Windows Server 2016. By any chance have you run the latest SPP (2018.03.0)? I have a feeling that a newer driver that HP released is causing this issue, but have not been able to track down which one. Since this is a similar server, with an exact same problem, it may help narrow it down. Or have you found a solution to this problem?

    Wednesday, March 14, 2018 6:25 PM
  • Well, in my case the issue was the ILO (CHIF) driver as described in the following advisory from HP:

    I am not sure if this will apply to you as it mentioned Server 2016 specifically, but may be worth a shot. However, please note that as of today, I could not locate the updated driver on their website and had to call in to support.

    Thursday, March 15, 2018 8:26 PM
  • Hi,

    i have the same problems after installing the SPP 2018.03 on a brand new DL380Gen9 server. any solutions for this case? OS is Server 2016...

    • Edited by alexnann Saturday, April 28, 2018 10:15 PM
    Saturday, April 28, 2018 10:14 PM
  • Hi, we are encountering the exact same issue on a DL380 Gen9 with Windows 2016 and using SPP 2018.03.  Did you manage to resolve the issue?  I opened a case with HP however we havent had any luck so far.


    Wednesday, May 02, 2018 3:07 PM
  • no we have no solution. Bluescreenview tells me that is caused by Driver "hal.dll". The bluescreen did happend two times. but i cannot say that is Happening i an exact Situation... 
    Thursday, May 03, 2018 11:25 AM
  • We managed to replicate the issue.  Whenever we re-run SPP from Windows the server crashes.  This most probably happens as the server checks all drivers / <g class="gr_ gr_169 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="169" id="169">firmwire</g> and then returns a blue screen.  If you managed to get some information, please let us know :)


    Thursday, May 03, 2018 12:34 PM
  • Thanks for this.  Uninstalling the ILO CHIF driver from Device Manager addressed the issue for me.  Your link doesn't seem to be working for me though; did it get garbled?

    Bryan Berns

    Saturday, May 05, 2018 12:31 PM
  • For those that stumble onto this Forum with Windows 2016 server, suggest you check out following Forum thread with very similar symptoms BSOD 0x133 DPC Watchdog timeout issues


    In Summary for Windows 2016 Server on HP Proliant ML350 Gen9:

    Update the HP iLO 4 Channel Interface Driver 


    (hpqilo3chif.sys ilo 3/4 channel interface driver cp034683.exe

    In my Windows 2016 server, only became stable after updating the v3.31 CHIFS ILO driver.  This driver update does not say compliant with Windows 2012 R2.  

    I am unsure where to latest ILO CHIFS drivers for Windows 2012 R2.   I have not disabled CHIFS driver yet for ILO on my Windows 2012 R2 server that was experiencing same issues in this post.

    For our Windows 2012 R2 Server, I have finally had some stability after HP gave me access to updated Broadcom NX1 embedded drivers.   They are not publicly released yet, but if you would like to test with your own HP server, maybe contact HP and ask to be on the trial to see if it can resolve your issues as well


    1. Update the Broadcom driver to version  HPE Broadcom NX1 1Gb Driver for Windows Server x64 Editions, version -    cp034731.exe

    2. Update the Broadcom firmware    HPE Broadcom NX1 Online Firmware Upgrade Utility for Windows Server x64 Editions, version - cp034766.exe

    NOTE: Both of these components are released, just not publicly published yet.  Contact HP if you believe may help you and you want to trial them.

    • Edited by Rod Arthur Saturday, May 26, 2018 6:00 AM
    Saturday, May 26, 2018 5:51 AM
  • Correction - We had another BSOD on our Windows 2012 R2 server with latest Broadcom drivers listed above.  So now I am trying to get HP to release the v3.31 CHIFS ILO driver for Windows 2012 R2 like they did for Windows 2016 server.  If anyone gets an update before I do, let me know
    Thursday, May 31, 2018 12:15 AM
  • Was your server Windows 2016 or Windows 2012 R2.  I agree the updated ILO Chif driver resolved issues for Windows 2016.  But were you able to get later than v3.30 drivers for Windows 2012 R2?
    Monday, June 11, 2018 6:33 AM