• Our team is working to address issues posting quotes or media to the forums. Please bear with us as we get this sorted out.

Question BSOD - Bugcheck 0x00000139 Windows Server 2016

Jul 16, 2021
4
0
10
0
Hello,
Please i need you help !!!
We have a Windows Server 2016 with 2 Vms ,The Psychical Server sometimes suddenly doing restart with BSOD.The event Viewer says

Here a picture result Debug Analisys memory.dmp.
https://ibb.co/F8Y11b1

Any proposed solution would be appreciate

Event Viewer
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 16/07/2021 09:40:52
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8000ea39540, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 33599ee5-41bc-48c0-bd0d-d5d083088bcb.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-07-16T06:40:52.712957300Z" />
<EventRecordID>104997</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>NGSERVER7.NGroup.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8000ea39540, 0x0000000000000000)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">33599ee5-41bc-48c0-bd0d-d5d083088bcb</Data>
</EventData>
</Event>
 

Colif

Win 10 Master
Moderator
The bugcheck was: 0x00000133
139?

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x133-dpc-watchdog-violation

these steps are for 10, I assume its similar in Server 2016
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

not sure if this part will be the same

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
if you can also give us some info on the machine its running on.
 

gardenman

Distinguished
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/qhzy5gj6/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:071621-16312-01.dmp (Jul 15 2021 - 21:05:03)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Driver warnings:*** WARNING: Unable to verify timestamp for hpqilo3chif.sys
Probably caused by:memory_corruption (Process: conhost.exe)
Uptime:2 Day(s), 5 Hour(s), 31 Min(s), and 34 Sec(s)

File information:071621-14625-01.dmp (Jul 16 2021 - 02:27:49)
Bugcheck:DPC_WATCHDOG_VIOLATION (133)
Probably caused by:memory_corruption (Process: powershell.exe)
Uptime:0 Day(s), 5 Hour(s), 09 Min(s), and 43 Sec(s)
Possible Server support page: https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04441832

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 
Jul 16, 2021
4
0
10
0
Thank you for the time you waste about my problem. I read the dump file you debug result -analysis . At first glance what I understood is that there is a problem with memory, Am i right? if so then i have to find the wrong ram module. And replace it.
 

gardenman

Distinguished
Moderator
Colif asked me to post the results here so he can look at them and give you more info about what to try next. Give him a day or so to reply.

In the first dump, hpqilo3chif.sys was the probable cause of the crash. If you look that driver up, it's an HP driver. This may provide a little more info: http://systemexplorer.net/file-database/file/hpqilo3chif-sys With drivers, sometimes trying a different version (newer or older) will help. Sometimes it's the hardware itself that caused the crash. Sometimes it's something else completely. Wait for more answers.
 

Colif

Win 10 Master
Moderator
Sorry, we had bad weather yesterday and I didn't get a chance to get back in.

I don't see many PC with 16 memory slots. Never done a server before so my help might be limited.

hpqilo3chif.sys appears to be HP ProLiant iLO 3 Channel Interface Driver
Jul 29 2016hpqilo3chif.sysHP ProLiant iLO 3 Channel Interface driver
Jul 29 2016hpqilo3core.sysHP ProLiant iLO 3 Management Controller Core driver
possible there are newer drivers now.

I don't know how you get drivers for servers. Maybe from https://support.hpe.com/hpesc/public/docDisplay?docId=c05029674&docLocale=en_US
 
Reactions: panos v

ASK THE COMMUNITY