[SOLVED] BSOD minidump file included (hal.dll + ntoskrnl.exe)

Dirtdog15

Distinguished
Jan 16, 2008
34
0
18,530
I been having increasing crashes since the new build. Usually it happens once a day. My system specs are the following:

i9 9700k
MSI Z390 Pro Carbon AC MB
Gigabyte RTX 2070 Super
Corsair RGB Pro Vengeance 16GB DDR4 3200

When it first started happening the bsod popped up then would restart and now it just restarts after a black screen but still creates the dmp. I included two different crash files just to see if there is a difference. It seems like it happens when I am using chrome or on the desktop. It hasn't happened while gaming. It does have the latest BIOS installed. I did run memtest86 and 0 errors popped up and ran the intel diagnostic tool and 0 errors there too. Any help would be appreciated

https://drive.google.com/file/d/1PB_hPTqDur6DEez6EuDwNh4Rw-kmrluy/view?usp=sharing

https://drive.google.com/file/d/172kieUu2TUk4l8Qdvfmpn0Z_eOqvua_r/view?usp=sharing
 

Md Noman 1

Reputable
Feb 3, 2017
83
5
4,565
I been having increasing crashes since the new build. Usually it happens once a day. My system specs are the following:

i9 9700k
MSI Z390 Pro Carbon AC MB
Gigabyte RTX 2070 Super
Corsair RGB Pro Vengeance 16GB DDR4 3200

When it first started happening the bsod popped up then would restart and now it just restarts after a black screen but still creates the dmp. I included two different crash files just to see if there is a difference. It seems like it happens when I am using chrome or on the desktop. It hasn't happened while gaming. It does have the latest BIOS installed. I did run memtest86 and 0 errors popped up and ran the intel diagnostic tool and 0 errors there too. Any help would be appreciated

https://drive.google.com/file/d/1PB_hPTqDur6DEez6EuDwNh4Rw-kmrluy/view?usp=sharing

https://drive.google.com/file/d/172kieUu2TUk4l8Qdvfmpn0Z_eOqvua_r/view?usp=sharing
boot in to windows repair mode and repair it and do a memtest.
 

Colif

Win 11 Master
Moderator
remove any overclocks
remove MSI Afterburner if you using it

hal.dll + ntoskrnl, blamed in one error, makes me think you got a WHEA error. I can't read dumps but I know those names and they always appear in whea errors.
I will send link toa friend who will convert them for us.
 

gardenman

Splendid
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/84wa.html
File information:101219-6593-01.dmp (Oct 12 2019 - 06:29:31)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: Xbox.exe)
Uptime:0 Day(s), 0 Hour(s), 15 Min(s), and 57 Sec(s)

File information:100519-9046-01.dmp (Oct 5 2019 - 06:57:11)
Bugcheck:WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:GenuineIntel (Process: StorageMonitor.exe)
Uptime:0 Day(s), 11 Hour(s), 43 Min(s), and 09 Sec(s)
Comment: The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner or other MSI software)

BIOS info was not included in the 1st dump file which can sometimes mean an outdated BIOS is being used.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 11 Master
Moderator
i am curious what MSI use this for, its for serial ports? I have seen it before, I guessed motherboard was MSI just by seeing it.
DateDriverDescription
Oct 17 2008 inpoutx64.sys Kernel level port access driver


See if you get any more errors removing MSI afterburner.

storagemonitor.exe is part of Dragon Centre, though not sure what it does as app doesn't appear to show storage - http://download.msi.com/archive/mnu_exe/pdf/Dragon-Center-2.4-User-Guide-EN.pdf - unless that is old.

What storage drives do you have? Try running HD Sentinel trial on them, and in the disk menu, run any tests you can - https://www.hdsentinel.com/hard_disk_sentinel_trial.php

WHEA errors can be any hardware. I suspect drives are okay as both dumps blame a Driver, they just not showing which.
 

Dirtdog15

Distinguished
Jan 16, 2008
34
0
18,530
I decided on just doing a fresh Windows install. I installed the minimum number of programs I use and I'll see if another error pops up. No afterburner but I do have the memory in XMB mode If so, I'll put another minidump file if it helps. Thanks again for the help
 

Dirtdog15

Distinguished
Jan 16, 2008
34
0
18,530
Sadly the crashes have returned. Lately its been hard locking for 10 seconds then going to a black screen. The only way I'm able to shut it down is holding the power button in. The last one actually restarted on its own and since it did it was able to give me a minidump file. I didn't have any MSI Afterburner installed and no overclocking of the CPU. I just have XMP turned on.


Also I forgot to include I am usuing a Samsung 970 Evo M.2 drive.
 

gardenman

Splendid
Moderator
Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/lbqe.html

File information:102219-5937-01.dmp (Oct 22 2019 - 12:20:32)
Bugcheck:MACHINE_CHECK_EXCEPTION (9C)
Probably caused by:ntkrnlmp.exe (Process: System)
Uptime:0 Day(s), 0 Hour(s), 55 Min(s), and 19 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 11 Master
Moderator
what bios version are you on? Normally gardenmans report will show system info but your PC isn't providing it. That can be a sign of an older bios. Bios updates can fix MCE errors

latest bios is 7B17v16 dated August this year
If you update it, also update the Intel chipset driver that can be found here - https://www.msi.com/Motherboard/support/MPG-Z390-GAMING-PRO-CARBON-AC#down-driver as they should match each other

how to flash bios
 
Solution

Dirtdog15

Distinguished
Jan 16, 2008
34
0
18,530
I used the mflash for the bios. Its the same version but I just did the flash anyway to see if it helps. If another minidump pops up I'll post just to see if my system info is shown. I also ran memtest86 overnight and no errors were shown.
 

Dirtdog15

Distinguished
Jan 16, 2008
34
0
18,530
The BSOD returned today. A week went by after the BIOS flash and everything seemed fine. Start the computer up and 2 minutes on the desktop it crashed to the screen. I can give one more file and see if anything changed from the previous. I know last time my system specs weren't showing up. Maybe after the BIOS update something changed.

https://drive.google.com/open?id=1eideqOuA1EqjEdIOHpRXNIuwan86zdxL

Thanks again for trying to help
 

gardenman

Splendid
Moderator
I ran the dump file through the debugger and got the following information: https://pste.eu/p/e8M9.html

File information:103019-8312-01.dmp (Oct 30 2019 - 09:41:12)
Bugcheck:MACHINE_CHECK_EXCEPTION (9C)
Probably caused by:intelppm.sys (Process: System)
Uptime:6 Day(s), 23 Hour(s), 37 Min(s), and 19 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 11 Master
Moderator
I know last time my system specs weren't showing up. Maybe after the BIOS update something changed.

Strangely not.

try running these 2 on CPU (not at same time)
Intel - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

All - https://www.mersenne.org/download/

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.