Question Constant BSOD involving hal.dll and ntoskrnl.exe

[altafullahu]

Hello and happy Sunday!

I am at wits end trying to troubleshoot this. I have uploaded and uninstalled more drivers than I could count. I believe it may be just a hardware issue but honestly I have no idea. My PC is a custom built one from the ground up with all parts being purchased on-line or in store - PC Specs:

i9 9990k 4.2 ghz
Asus PRIME Z390-A
nVidia GeForce 2070 RTX
nVidia GeForce 1060
Corsair RAM 16 GB (4 x 4)
Razer Black Widow Ultimate
Corsair Glaive RGB Mouse
6 monitors (4 Acers 2 AOC)
6 Internal Hard Drives
1 USB Hub pluged into USB 3.0 port
1 USB Hub plugged into USB Type-C port

The issue has been off / on for the past handful of months. Sometimes it can go a week or so without any issues then one small config and it goes back to crashing.

I have provided the latest minidumps - if anyone can take a look through them and give me an idea it would be truly appreciated!

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffd189cce08028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffd189cce08028

BUGCHECK_P3: be000000

BUGCHECK_P4: 800400

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: c

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: USMAN-DESKTOP

ANALYSIS_SESSION_TIME: 12-01-2019 08:29:49.0885

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

STACK_TEXT:
ffffab007610cd78 fffff80129cfdfe8 : 0000000000000124 0000000000000000 ffffd189cce08028 00000000be000000 : nt!KeBugCheckEx
ffffab007610cd80 fffff8012e181920 : ffffd189c8947da0 0000000000000000 ffffd189cce08028 0000000000000000 : hal!HalBugCheckSystem+0xd8
ffffab007610cdc0 fffff80129540952 : ffffd189c8947da0 ffffab007610ce49 0000000000000000 ffffd189cce08028 : PSHED!PshedBugCheckSystem+0x10
ffffab007610cdf0 fffff80129cff946 : ffffab007610cf10 0000000000000001 ffffd189c8947df0 ffffd189c8947da0 : nt!WheaReportHwError+0x382
ffffab007610ceb0 fffff80129cffdda : 0000000000000010 ffffd189c8947df0 ffffab007610d068 ffffab007610d2b0 : hal!HalpMcaReportError+0x72
ffffab007610d010 fffff80129cffcb4 : ffffd189c82e4520 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandlerCore+0xf2
ffffab007610d060 fffff80129cfff20 : 0000000000000010 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xe0
ffffab007610d0a0 fffff80129cfefc8 : 0000000000000000 ffffab007610d330 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffffab007610d0d0 fffff80129d001a7 : ffffd189c82e4520 0000000000000000 0000000000000000 0000000000000000 : hal!HalpHandleMachineCheck+0x5c
ffffab007610d100 fffff801294a4a20 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x37
ffffab007610d130 fffff801293d04ba : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0x10
ffffab007610d160 fffff801293d0171 : ffffab0000000000 fffff801293d00ae fffff80127922180 0000000000000000 : nt!KxMcheckAbort+0x7a
ffffab007610d2a0 fffff8014815138f : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x271
ffff8188ad22f6a8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : intelppm!MWaitIdle+0x1f


THREAD_SHA1_HASH_MOD_FUNC: 74d6f842f394d0bf91f311b36b5441a27b8e18a2

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7715d22f386f5ddac4d5fb4b9bac1cc78014801d

THREAD_SHA1_HASH_MOD: 48245875d4c5535ecbacf57c10ad759e5c3df6ae

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_MAE_INTERNAL_TIMER

TARGET_TIME: 2019-11-26T00:24:58.000Z

OSBUILD: 18362

OSSERVICEPACK: 476

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2011-12-29 18:28:41

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 1c5b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae_internal_timer

FAILURE_ID_HASH: {dbae0c63-5a7c-cd3f-eccf-de6e68aa7cf2}

---------------------------------------------------------------------------------------------------------

Was having some issues trying to review the minidumps so this was all I could find. Please let me know if more information is needed!

Thanks!

 

[Colif]

actually, you haven't given us the minidumps...

can you go to c:/windows/minidump
copy any minidump files to another folder
upload the copies from new folder to a file sharing website and show links here.

WHEA are hardware errors.
Have you got latest BIOS?
Remove any overclocks
run this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

 

[altafullahu]

actually, you haven't given us the minidumps...

can you go to c:/windows/minidump
copy any minidump files to another folder
upload the copies from new folder to a file sharing website and show links here.

WHEA are hardware errors.
Have you got latest BIOS?
Remove any overclocks
run this on CPU - https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

Oh, sorry about that - OK! The links are below:

https://drive.google.com/open?id=12lio6hhghu1u-hA9T9W8bl7g19-XzdBk

112519-14843-01.dmp

drive.google.com

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

I had some issues opening the minidumps so let me know if I can provide anything else.

Thanks!

 

[Colif]

you need special programs to open the dumps, I don't have them either but I know a few people who can.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/Cv8p.html

File information:	112819-14671-01.dmp (Nov 27 2019 - 22:50:30)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	GenuineIntel (Process: audiodg.exe)
Uptime:	0 Day(s), 6 Hour(s), 24 Min(s), and 19 Sec(s)

File information:	112519-14796-01.dmp (Nov 25 2019 - 19:24:58)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	GenuineIntel (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 52 Min(s), and 53 Sec(s)

Comment: The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

BIOS info was not included in the dump file. This 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]

WHEA = Windows Hardware Error Architecture. Its an error called by CPU but not necessarily caused by it
Do you have latest BIOS for motherboard?

can you remove Asus AI suite? it has drivers that can change CPU settings
remove this as well

May 08 2018

iocbios2.sys

!!! Overclocking Software - Intel(R) Extreme Tuning Utility Performance Tuning driver

these can cause BSOD:

Sep 24 2015	dtlitescsibus.sys	DAEMON Tools Lite Virtual SCSI Bus (Disc Soft Ltd)
Dec 28 2015	dtliteusbbus.sys	DAEMON Tools Lite Virtual USB Bus (Disc Soft Ltd)

I am helping someone else with WHEA errors who also has the exact same Creative drivers you do.. what card is it? It could just be a coincidence but I just thought I mention it.

Jul 06 2017	cthda.sys	Sound Blaster HD Audio driver (Creative Technology Ltd)
Jul 06 2017	cthdb.sys	Sound Blaster HD Audio Controller driver (Creative Technology Ltd)

 

[altafullahu]

First - thank you everyone for your responses. The fact I am able to at least get some insight as to what are causing these now daily BSODs is soooo refreshing.

Having said that - I have not updated the BiOS since I got it last year when I built this computer. I will see if there are any updates to it.

@Colif I will remove Asus AI Suite and the Daemon tools and see what happens. I use my soundcard though so I hope that really isn't it but I will try that as well if the first two items do nothing.

Thanks again, please let me know if you guys can find any additional / potential causes of this BSOD.

Just as an aside - I leave the house daily for work and start my pc up in the morning as it BSODs over night and so far every day when I get back from work I see a BOSD. Super irritating seeing it happening when literally nothing else is happening on the computer.

 

[Colif]

idle times are when windows runs background processes that it only runs when you not using PC. Things like defrag, rebuild search index, run defender, and many others. Some might show in scheduled tasks.

Let us know if you keep getting them as new dumps might show more info

 

[altafullahu]

Here is a link for some additional dumps over the last 3 days:

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

Let me know if anyone can find anything else. I am going to be updating some drivers and my BiOS this weekend as there are newer versions on the Asus site.

 

[gardenman]

The .ZIP file is empty (22 byte long with no files within). It may help to copy the dump files to another folder before trying to ZIP them up.

 

[altafullahu]

The .ZIP file is empty (22 byte long with no files within). It may help to copy the dump files to another folder before trying to ZIP them up.

ahh good catch - I had forgotten to move it out of C:

Please find them below. Let me know if there's anything else!

https://drive.google.com/file/d/1wmqCQui8yBWlVz5dnpyJhcjpC7SMNl5Q/view?usp=sharing

https://drive.google.com/file/d/1Po7l2pmRZ5bk5XFBJVIgMKfo-2SaatSY/view?usp=sharing

https://drive.google.com/file/d/15q6B3LtKXIrmeNhfiHPZPJKtjRCOMtTL/view?usp=sharing

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

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://pste.eu/p/fjYT.html

Spoiler

File information:	120619-12343-01.dmp (Dec 6 2019 - 03:47:39)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: audiodg.exe)
Uptime:	0 Day(s), 20 Hour(s), 26 Min(s), and 43 Sec(s)

File information:	120419-16656-01.dmp (Dec 4 2019 - 07:25:45)
Bugcheck:	WHEA_UNCORRECTABLE_ERROR (124)
Probably caused by:	memory_corruption (Process: TwitchAgent.exe)
Uptime:	0 Day(s), 0 Hour(s), 20 Min(s), and 44 Sec(s)

File information:	120319-15296-01.dmp (Dec 3 2019 - 13:22:29)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: UninstallMonitor.exe)
Uptime:	0 Day(s), 7 Hour(s), 03 Min(s), and 16 Sec(s)

File information:	120119-20484-01.dmp (Dec 1 2019 - 19:57:08)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Driver warnings:	*** WARNING: Unable to verify timestamp for CorsairGamingAudio64.sys
Probably caused by:	memory_corruption (Process: audiodg.exe)
Uptime:	0 Day(s), 10 Hour(s), 45 Min(s), and 10 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]

2 of them are audio, last one fingers this as problem

Sep 24 2019

CorsairGamingAudio64.sys

Corsair Gaming Audio 64-bit driver

it might be part of Icue. See if there is a newer version?

 

[altafullahu]

Ok so far this is the update:

• BiOS Updated to latest
• Network drivers updated
• Audio drivers updated (including the Corsair Application mentioned above)
• Chipset driver updated
• uninstalled offending software mentioned above except the audigy soundblaster driver (will uninstall if things continue)
• install Intel RapidStoreTechnology driver

I will post an update later over the weekend if I see any issues. I just finished all this morning so haven't really had enough time to see if the changes have really done anything.

Thank you everyone for your continued support!!!

 

[altafullahu]

Hey all -

PC was working fine for a couple weeks then all of a sudden started giving me the watchdog blue screen again...

Here is another minidump from the most recent crash

https://1drv.ms/u/s!Ajbt4S5WngqJgr4ak_8fBB3XQj0bAg?e=JMk6rv

Let me know if there's anything new someone can point out! Thanks!

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://litigantafricanforestelephant.htmlpasta.com/

File information:	011220-15156-01.dmp (Jan 12 2020 - 12:03:26)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 18 Hour(s), 36 Min(s), and 49 Sec(s)

Possible Motherboard page: https://www.asus.com/us/Motherboards/PRIME-Z390-A/
There is a BIOS update available for your system (Version 1401). It was just released yesterday. You are using version 1302. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

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]

usbaudio!USBType1CompleteCallback+0x9d

what are you plugging in via USB? that error occured after a USB transaction

 

[altafullahu]

@gardenman where did you find that BiOS update? I am looking and the latest one is from December?

@Colif I have a handful of devices plugged into my USB ports / hub - I will have to do some testing and hopefully can figure out which is the offending one.

Thanks - will provide an update as I can.

 

[Colif]

you both looking at same BIOS
Version 1401 - 2019/12/11

BIOS update may add support for USB devices so could help - https://www.asus.com/us/Motherboards/PRIME-Z390-A/HelpDesk_BIOS/

try devices 1st

 

[altafullahu]

https://1drv.ms/u/s!Ajbt4S5WngqJgr4dyCHkgSu--ABkgw?e=nvZpMT

new dump from just a little bit ago

 

[gardenman]

Sorry, it wasn't just released yesterday. It was released a month ago. The version number is different from the one showing in the dump file previous uploaded. You have 1302 installed and the new one is 1401.

I ran the new dump file through the debugger and got the following information: https://cornaceousbluewhale.htmlpasta.com/

File information:	011320-14093-01.dmp (Jan 13 2020 - 09:49:34)
Bugcheck:	IRQL_NOT_LESS_OR_EQUAL (A)
Probably caused by:	ntkrnlmp.exe (Process: System)
Uptime:	0 Day(s), 16 Hour(s), 15 Min(s), and 56 Sec(s)

This dump didn't show BIOS version (sometimes they don't).

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]

dump file isn't really obvious as to cause, its likely a driver since thats what IRQ errors generally are. Its blaming 2 parts of windows which are neither likely to be cause by themselves.

 

[altafullahu]

Hey All.

Here is a fresh minidump from today::

https://1drv.ms/u/s!Ajbt4S5WngqJgr4hay271QBJxJZcZA?e=QROKR1

 

[gardenman]

I ran the dump file through the debugger and got the following information: https://pyriformneanderthal.htmlpasta.com/

File information:	020320-13656-01.dmp (Feb 3 2020 - 01:20:20)
Bugcheck:	DPC_WATCHDOG_VIOLATION (133)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 2 Hour(s), 20 Min(s), and 46 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.

 

[axe0axe0]

Could you run https://www.sysnative.com/forums/pages/bsodcollectionapp/ and upload the zip file so we can get a better look at the situation.