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 7, 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 2, 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 3, 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 3, 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 5, 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
    • Proposed as answer by Simon Andersen Monday, June 18, 2018 6:10 PM
    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
  • You are the best - thx :)

    Monday, June 18, 2018 6:11 PM
  • Had this issue occur over a month ago, temporarily put on backup server, put this issue asside for awhile, google the issue again and found this thread. HP Gen 9 server running Windows Server 2016. Same server worked fine before SPP 3 -2018. Just upgraded too CHIF driver 3.31, will report back if issue is fixed.
    Tuesday, June 26, 2018 7:07 PM
  • If anyone has any BSOD related problems they often can be fixed by debugging the dump files and troubleshooting the computer files.

    For any BSOD please open a new thread and post the link into this thread.

    1) To evaluate the BSOD please post logs for troubleshooting.

    2) Using administrative command prompt copy and paste this whole command.

    3) Make sure the default language is English so that the logs can be scanned and read.

    4) The command will automatically collect the computer files and place them on the desktop.

    5) Then use one 7zip and one drive or drop box to place share links into the thread for troubleshooting.

    6) This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    7) Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    8) There are two files for you to find manually: 

    a) C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

    b) Dxdiag:  In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread




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




    Tuesday, June 26, 2018 8:43 PM
  • Just an update, Windows 2012 R2 ran fine for many week without the iLO CHIF driver v3.30 installed.  HPE contacted me and asked me to trial the following procedure as they have not officially released a driver upgrade package for Windows 2012 R2 like they did for Windows 2016 yet.  But they advise the Driver for Windows 2016 will work on Windows 2012 R2.  Just can not use the installer package.

    Assuming at this point the iLO CHIF driver is *not* installed.
    1. Get a copy of cp034683, “iLO 4 Channel Interface Driver for Windows Server 2016”, version 
    3. The component will not install on 2012 R2 as-is.  Instead, run the component, select “Extract”, and provide a folder name.
    4. Run Windows Device Manager.  Under “Other Drivers”, right-click on “Base System Device” (in my case it was "Unknown Device") and use the “Update Driver Software” option and provide the folder name from the above step.
    5. Windows might prompt you to reboot.  (DID NOT PROMPT TO REBOOT.  But I decided to complete latest windows updates and reboot anyway to make sure all applied correctly outside of business hours)
    When the time comes to uninstall the driver, this will need to be performed from Device Manager.  There will be no entry in 'Programs and Features'.
    1. Run Windows Device Manager. Under “System Management”, right mouse on “iLO 4 (CHIF)” and select "Uninstall".

    Wednesday, June 27, 2018 12:03 AM
  • ML110 Gen9, new OS install of 2012 R2, then installed SPP 2018.06.  The blue screens began 12 hours later, ~10 crashes within 1 day, error is DPC_Watchdog_Violation.

    After researching I uninstalled the following, crashes stopped after these changes.

    iLO 3/4 Channel Interface Driver v3.30.0.0
    PowerChute Business Edition Agent 

    Server was stable overnight after new OS install but wasn't being used either.  PowerChute app was installed 1 hour before crashes started but dump analysis shows hpqam.exe as process.

    Ticket is open with HPE, I don't find a newer iLO 3/4 CID driver for 2012 R2.

    Dump analysis:


    BUILD_VERSION_STRING:  9600.19035.amd64fre.winblue_ltsb_escrow.180522-1700
    SYSTEM_PRODUCT_NAME:  ProLiant ML110 Gen9
    SYSTEM_SKU:  799111-S01
    BIOS_DATE:  05/21/2018
    BASEBOARD_PRODUCT:  ProLiant ML110 Gen9
    DUMP_TYPE:  1
    BUGCHECK_P1: 0
    BUGCHECK_P2: 501
    BUGCHECK_P3: 500
    BUGCHECK_P4: 0
    CPU_COUNT: 6
    CPU_MHZ: 63e
    CPU_VENDOR:  GenuineIntel
    CPU_MODEL: 3f
    CPU_MICROCODE: 6,3f,2,0 (F,M,S,R)  SIG: 3D'00000000 (cache) 3D'00000000 (init)
    BUGCHECK_STR:  0x133
    PROCESS_NAME:  hpqams.exe
    ANALYSIS_SESSION_TIME:  07-18-2018 19:08:12.0553
    ANALYSIS_VERSION: 10.0.15063.468 amd64fre
    LAST_CONTROL_TRANSFER:  from fffff8022538d5ec to fffff802253642a0

    Thursday, July 19, 2018 4:52 PM
  • Zach H,

    Please open a new thread to troubleshoot the BSOD and post a link into this thread.

    See the post in this thread:  Tuesday, June 26, 2018 8:43 PM

    In the new thread post one drive or drop box share links for the computer files to troubleshoot the BSOD.

    Thursday, July 19, 2018 5:37 PM
  • Hello,

    I'm not looking for help, just confirming or reinforcing, that the iLO Channel Interface Driver 3.30.0 is a problem installed on Server 2012 R2 on an ML110 Gen9. 

    HPE support has recommended:
    1. Reset and reconfigure iLO.
    2. Reinstall current iLO CID driver 3.30.0
    3. "See what happens"

    Support was not interested or able to look at the .dmp file.  They suggested opening a case with Microsoft since it's a Microsoft .dmp file.  Worse than useless advice.

    Monday, July 23, 2018 8:41 PM
  • The telephone and chat Microsoft support are not trained in BSOD debugging.

    There are three tiers of support and you would have to spend time to climb the levels.

    They mostly troubleshoot failed updates, upgrades, activation, etc.

    HP support refers Windows problems to Microsoft and are primarily troubleshooting hardware problems.

    Monday, July 23, 2018 9:09 PM