BSOD: 0x00000124 (WHEA_UNCORRECTABLE_ERROR)

S

snodkobbel

Member
Joined
Jun 10, 2019
Posts
8
Find the dump files attached. (I had to exclude the other files for now because some of them contain personally identifying info. But if you require any of them, let me know which ones, I'll redact the PI info, and post them here.)

System = Dell Intel-based (CPU + video) laptop. Apx 3 years old.
OS = Windows 7 SP1 x64.

The last time this BSOD occurred, I tested the RAM and no problems were found.
I've also checked the hdd's SMART status, and the health rating is "good".

As you can see from the dumps, it's happened 6 times in apx 2 years, so an average of every 4 months. Which is notable for being infrequent enough that perhaps something other than failing hardware is at fault.

The only pattern that's emerged from my recollection of previous BSOD's is web-browser related: either the display of large web pages, or playing certain media content. I realize that seems an unlikely cause, but maybe certain type of (media) content could lead to a conflict with audio and/or video drivers, etc (?)

Thanks for any help.
 

Attachments

Hi snodkobbel,

Welcome to Sysnative! :-)

Could you specify what kind of personal information you mean was collected?

There are quite a few files we need aside from the dumps, from my experience dumps are about 50% of what is needed.
 
Hello, and thanks for responding.

Just so there's no misunderstanding, let me first clarify my remark above: I’m not saying that the tool intentionally collects personal info. It doesn't. It just happened to capture some info that in my case I'd like to exclude.

That said, the tool does collect data for diagnosing a variety of different issues, and only some of that data is going to be relevant for a given situation. For example, my issue doesn't involve networking, so right there we can omit Hosts.txt, IPconfigAll.txt, NetSHLAN1.txt, NetstatJcgriff2, Tracert.txt, and perhaps 1-2 others.

Can you look at the dumps and tell me which files you require afterwards?
 
No worries, the BSOD app was designed to collect only that which is necessary for troubleshooting and nothing more. Still, it is does happen that, as in your case happened, some private/personal information is collected as well (such as the actual name of a user).

Some files are actually necessary to have. Hosts file, for example, is there in regards to piracy, it is the most common method we have come across for piracy and when we detect piracy we do not provide support per the forum's rules (+ other reasons).
If I'm not mistaken, some of the other files you mentioned are there for troubleshooting when something's wrong with the app, please note that this is just a mere assumption, I am not aware of the actual reason.

I know that I need at least systeminfo.txt, msinfo32.nfo, hosts.txt, evtxappdump.txt, evtxsysdump.txt, hkcusoftmswincvuuninstall.txt, hklmsoftmswincvuinstall.txt, kerneldumplist.txt, raminfo.html, dxdiagx86.txt, driverqfo.txt, driverqsi.txt and driverqv.txt, preferably unmodified.
 
No, I really mean systeminfo.txt, if it isn't there please run the tool again.
 
I ran it again but no dice. I watched the console window, and noticed "systeminfo" mentioned, but there's no file...
 
Please run the below command in a command prompt or powershell, it creates the systeminfo.txt file.
Code: 
systeminfo > "%USERPROFILE%\Desktop\systeminfo.tmp"&findstr /v "Owner." "%USERPROFILE%\Desktop\systeminfo.tmp" > "%USERPROFILE%\Desktop\systeminfo.txt"&del "%USERPROFILE%\Desktop\systeminfo.tmp"
 
I just used Dell's built-in utility to test the memory. (Dell has a system-wide testing suite that's launched from the BIOS start-up options, and runs in a pre-OS environment. I can't speak to the quality of that utility, but presumably Dell would have to offer a return under warranty if some component failed its tests.)
 
Ah, Dells built-in reasonably advanced hardware tests (in my opinion), had to use it myself on my laptop to find out why my laptop wouldn't boot a few years ago. To what extend did you run Dell's tests? Unless Dell has changed the tests over the years you have an option to run an extended test.
 
It's been awhile, but I seem to recall running the Dell memory test over night. Since I'm not sure about that though, I probably ought to re-run it. Or should I use MemTest86 instead (if that's still the industry standard)? And if so, is there a recommended config?

I also have another BSOD to report. Happened last night. Same bug check. Find the dump attached. This one occurred much closer to the last one - 2 weeks ago, vs months apart for previous BSODs.
 

Attachments

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_cache

Check the CPU temp with a program like CPUz's Hardware Monitor.
Run the Intel CPU diagnostic utility > Download Intel® Processor Diagnostic Tool
Update the Intel drivers using the Intel Update utility> Download Intel® Driver & Support Assistant

Code: 
Debug session time: Sat Jun 22 19:57:12.934 2019 (UTC - 4:00)
Loading Dump File [C:\BSOD APP\SysnativeBSODApps\062219-20560-01.dmp]
Built by: 7601.24441.amd64fre.win7sp1_ldr.190418-1735
System Uptime: 12 days 21:46:57.881
*** WARNING: Unable to verify timestamp for igdkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
Probably caused by : GenuineIntel
BugCheck 124, {0, fffffa800aa54028, be000000, 100110b}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Bugcheck code 00000124
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800aa54028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110b, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
MaxSpeed:     2400
CurrentSpeed: 2394
BiosVersion = A12
BiosReleaseDate = 05/21/2018
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 7352
BaseBoardProduct = 0N0DFW
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


*** 3rd PARTY DRIVER LIST ***
*** 3rd PARTY DRIVER LIST ***



Code: 
Netwsw04.sys                Wed Jan 24 11:40:38 2018 (5A68E136)
RTKVHD64.sys                Thu Jan  5 02:19:52 2017 (586E1DC8)
RimSerial_AMD64.sys         Mon Oct 22 13:51:51 2012 (5085B1E7)
SbieDrv.sys                 Tue Apr 23 10:17:24 2019 (5CBF48A4)
SynTP.sys                   Fri Jul 10 12:34:22 2015 (55A01E3E)
TeeDriverx64.sys            Wed Nov 16 11:50:22 2016 (582CB87E)
USBD.SYS                    Wed May  2 08:32:25 2018 (5AE9DA09)
USBPORT.SYS                 Wed May  2 08:32:31 2018 (5AE9DA0F)
VIDEOPRT.SYS                Thu Apr 18 19:11:35 2019 (5CB92E57)
VMNET.SYS                   Wed Aug 23 16:39:29 2017 (599E1231)
WDFLDR.SYS                  Wed Jul 25 19:29:04 2012 (5010AB70)
WMILIB.SYS                  Mon Jul 13 16:19:51 2009 (4A5BC117)
WUDFRd.sys                  Wed Jul 25 19:26:06 2012 (5010AABE)
Wdf01000.sys                Fri Jun 21 20:13:05 2013 (51C51641)
WudfPf.sys                  Wed Jul 25 19:26:45 2012 (5010AAE5)
amdxata.sys                 Fri Mar 19 09:18:18 2010 (4BA3A3CA)
btmaud.sys                  Thu Oct 26 14:42:08 2017 (59F256B0)
btmaux.sys                  Thu Oct 26 14:42:13 2017 (59F256B5)
btmhsf.sys                  Thu Oct 26 14:43:05 2017 (59F256E9)
dptf_acpi.sys               Fri Oct 23 12:24:17 2015 (562A8961)
dptf_cpu.sys                Fri Oct 23 12:24:21 2015 (562A8965)
dptf_pch.sys                Fri Oct 23 12:24:20 2015 (562A8964)
esif_lf.sys                 Fri Oct 23 12:24:35 2015 (562A8973)
hcmon.sys                   Thu Aug 30 21:19:53 2018 (5B88C1E9)
iaStorA.sys                 Wed Nov  4 02:27:49 2015 (5639DDA5)
iaStorF.sys                 Wed Nov  4 02:27:52 2015 (5639DDA8)
ibtusb.sys                  Fri Dec  1 14:26:56 2017 (5A21D730)
igdkmd64.sys                Mon Oct 16 11:17:12 2017 (59E4F7A8)
intelppm.sys                Thu Apr 18 19:07:47 2019 (5CB92D73)
iusb3hcs.sys                Mon Jun 20 04:02:03 2016 (5767CD2B)
iusb3hub.sys                Mon Jun 20 04:00:59 2016 (5767CCEB)
iusb3xhc.sys                Mon Jun 20 04:01:02 2016 (5767CCEE)
npcap.sys                   Fri Jan 11 07:44:05 2019 (5C38B9C5)
pwdrvio.sys                 Mon Jun 15 18:43:45 2009 (4A36F8D1)
speedfan.sys                Sat Dec 29 12:59:35 2012 (50DF59B7)
tap0901.sys                 Thu Apr 21 02:10:05 2016 (571898ED)
umbus.sys                   Sat Nov 20 02:44:37 2010 (4CE7A695)
usbccgp.sys                 Wed May  2 08:32:35 2018 (5AE9DA13)
usbehci.sys                 Wed May  2 08:32:31 2018 (5AE9DA0F)
usbhub.sys                  Wed May  2 08:32:57 2018 (5AE9DA29)
usbvideo.sys                Fri Jul 12 03:41:34 2013 (51DFDD5E)
vdrvroot.sys                Thu Apr 18 19:17:41 2019 (5CB92FC5)
vga.sys                     Mon Jul 13 16:38:47 2009 (4A5BC587)
vmci.sys                    Sat Jun  4 01:08:06 2016 (57528C66)
vmnetadapter.sys            Wed Aug 23 16:39:33 2017 (599E1235)
vmnetbridge.sys             Wed Aug 23 16:39:34 2017 (599E1236)
vmnetuserif.sys             Wed Aug 23 16:39:33 2017 (599E1235)
vmx86.sys                   Tue Sep  4 05:24:47 2018 (5B8E798F)
volmgr.sys                  Thu Apr 18 19:07:50 2019 (5CB92D76)
volmgrx.sys                 Fri Jul  7 07:53:40 2017 (595FA074)
volsnap.sys                 Sat Nov 20 01:20:08 2010 (4CE792C8)
vsock.sys                   Wed May 16 01:19:52 2018 (5AFBE9A8)
vstor2-x64.sys              Tue Aug 15 00:45:56 2017 (5992A6B4)
vwifibus.sys                Mon Jul 13 17:07:21 2009 (4A5BCC39)
vwififlt.sys                Mon Jul 13 17:07:22 2009 (4A5BCC3A)
vwifimp.sys                 Mon Jul 13 17:07:28 2009 (4A5BCC40)
wanarp.sys                  Fri Dec  7 18:47:22 2018 (5C0B30BA)
watchdog.sys                Mon Jul 13 16:37:35 2009 (4A5BC53F)
wd.sys                      Mon Jul 13 16:19:55 2009 (4A5BC11B)
wfplwf.sys                  Mon Jul 13 17:09:26 2009 (4A5BCCB6)
wmiacpi.sys                 Sat Feb 10 09:25:26 2018 (5A7F2B06)
ws2ifsl.sys                 Mon Jul 13 17:10:33 2009 (4A5BCCF9)
 
I ran the Intel Processor Diagnostic (IPD) Tool, and my CPU passed all of the tests.

The IPD tool lists the max temp for my CPU as 110 C (woah), and the max temp reached during testing was 83 C. But outside of the test, I've never noticed the CPU get much above 70 C for too long. Then again, I'm only casually glancing at the (SpeedFan) temp monitor if the system is bogging down under a heavy load, or when it's exposed to Summer heat. Both of which are seldom, and weren't factors at the time of the last two BSODs.

However! My Intel drivers (video, storage, wifi, and bluetooth) are indeed out of date. So I will update those, and then I guess it's wait and see if the BSODs return.

Thanks very much for your help.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top