[SOLVED] BSOD after a few minutes in Windows; bug check 0x124. Many parts tested. Completely lost.

[xekushnr]

Before I get going, here are the specs;

CPU: i7-7700k

MB: Asus Prime Z270-AR

GPU: Asus GTX1070 DUAL OC 8GB

RAM: 2 x GSkill Trident Z 8GB

HDD: Samsung 850 EVO 500GB

PSU: Thermaltake Toughpower Grand RGB 650W

OS: Win10 Home

All parts were purchased new ~20 months ago.

This started last Thursday. On Wednesday I updated my graphics driver, restarted, gamed for about three hours with no problems. Thursday I went to use the computer after work and within a few minutes in Windows it BSODs. This has continued till now and the computer is unusable. The code it gives me is WHEA_UNCORRECTABLE_ERROR (big help there) but when I view the crash logs it comes up with bug check 0x124 with hal.dll, ntoskrnl.dll and pshed.dll crashing.

The computer is not overclocked.

Here's what I have done;

GPU: Uninstalled drivers, removed from computer and plugged HDMI into motherboard. Issue persists. Observed fans running.

MB: Observed voltages in BIOS. All slightly over stated voltages. Upgraded BIOS to current version. Reset all settings to default. Verified no overclock.

RAM: Tested one stick at a time. Ran Memtest86 6 passes, no errors. Tried sticks in slots 2 and 4 (was originally in 1 and 3) Issue persisted

HDD: Ran check disk, no errors. Swapped in another drive. Issue persisted.

OS: Tried Windows reset feature. Think it's supposed to reset OS to what it was like when first installed. Issue persisted. Went to format and do a straight fresh install but it even bluescreens in the damn Windows installer.

CPU: I ran the Intel processor tool and it passed. Temps good, never gets over 80C under load. Only part with a replacement plan, so I brought it to Micro Center. They ran Prime95 for ~45 minutes and said it worked flawlessly.

PSU: Unplugged every connection and replugged. Checked voltages in BIOS, all were a bit over the stated voltage. Observed fan running. Lights up normally.

Every part has been physically checked for damage. Every component has been reseated in the motherboard and every harness pulled and reinserted. The entire computer and every component has been blasted out with air.

I've just now done something I should have a while ago and booted into safe mode. The computer DOES run in safe mode, been on for an hour.

Zip with minidumps; https://drive.google.com/open?id=129--DUkwdszx9F_BYHVm8zqbx3IR92gm

BlueScreenView summary; https://drive.google.com/open?id=1IvAbMpJV9NY-cK633vLeoFmlnpsqgQXO

Screen from BSV with the errors and info; https://drive.google.com/file/d/1onZF0Wb2agd2rrJnI_y1O303XzXpTVMU/view?usp=sharing

Please help! Any info is much appreciated, I miss using my computer. If you need any additional info let me know. Keep in mind I can only operate in Windows for minutes at a time for the moment.

 

[Colif]

I can't read dumps but will get a friend to convert them into a format I can read.

Have you tried running with bare minimums, so 1 stick of ram, no gpu, only boot drive. If you still get WHEA errors then, it has to be one of the items attached. Or a driver. It shouldn't be GPU driver if you still get the BSOD without GPU attached.

ntoskrnl = windows kernel
hal.,dll = Hardware Abstraction Layer
PSHed.dll = Platform Specific Hardware Error driver

all 3 parts of windows. All commonly blamed for WHEA errors.

WHEA = Windows Hardware Error Architecture.
WHEA errors called by CPU but not necessarily caused by them. About only software that can cause them are overclocking software. Like MSI Afterburner or Asus GPU Tweak 2. Other programs like Intel Extreme Tuning Utility or Asus AI Suite can also cause these errors, even if not being used.

 

[gardenman]

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

Spoiler

File: 020519-5593-01.dmp (Feb 5 2019 - 00:34:16)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 35 Sec(s)

File: 020519-5453-01.dmp (Feb 5 2019 - 17:22:41)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 35 Sec(s)

File: 020519-5359-01.dmp (Feb 5 2019 - 18:03:16)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Probably caused by: Unknown_Image (Process: https://www.google.com/search?q=)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 39 Sec(s)

File: 020519-5015-01.dmp (Feb 5 2019 - 18:00:59)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 45 Sec(s)

File: 020519-3781-01.dmp (Feb 5 2019 - 17:37:00)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 50 Sec(s)

BIOS information wasn't included in the dump files. This can sometimes mean an outdated BIOS is being used.

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[xekushnr]

Have you tried running with bare minimums, so 1 stick of ram, no gpu, only boot drive. If you still get WHEA errors then, it has to be one of the items attached. Or a driver. It shouldn't be GPU driver if you still get the BSOD without GPU attached.

I have not done this all at once, but tested everything separately. No GPU, still blue screens. One RAM, then the other, then in different slots, still blue screens. I only have one drive, I put one from another (working) computer in this unit and it still blue screened. Come to think of it, I put the SDD from the computer with the BSOD into the working computer and it ran fine...

 

[xekushnr]

BIOS information wasn't included in the dump files. This can sometimes mean an outdated BIOS is being used.

During all of this, the BIOS was updated to the current version listed on ASUS' support site.

 

[Colif]

The consistent 2 minute uptimes seems to suggest it is something it tries to do just after login, maybe set PC up in clean boot and see if it still does same thing - make sure NOT to disable any Microsoft services or Windows won't boot right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows - should be able to set that up from safe mode.

Since it works in safe mode it could mean the problem is a driver but then safe mode doesn't stress the PC out and some devices will work perfectly fine in safe mode and not when you try to run windows on them.

Every WHEA errors blames a Driver (its saying DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT but it sees Win 10 drivers as Win 8 drivers)

None of the running drivers strike me as being obvious causes of the BSOD.
oldest are lan drivers, there are newer on Asus site
razer is old as well, be tempted to see if you get whea errors using different mouse/kb (which ever uses razer)

Could be a newer version of Intel Management Engine Interface, this normally gets updated when BIOS released but newest is older than latest BIOS... still newer than what you have.

https://www.asus.com/au/Motherboards/PRIME-Z270-AR/HelpDesk_Download/

If PC stayed on for longer than 2 minutes, I would suggest running driver verifer.

 

[xekushnr]

I've tried the clean boot, but since I formatted and did a fresh install of Windows it didn't really help.

I'm about to leave the house and won't be back till Sunday; when I get back I'll update the LAN/Razer mouse/IMEI drivers and what else I can find.

I have run the driver verifier in my brief time allotted in Windows, it only found one driver (rspndr.sys) that was supposedly for an older version of Windows; I copied the one from my Win10 DVD and now the blue screen won't pop up, but the screen goes black and the system restarts. Everything else is the same, including the 1.5-2 minute up times.

 

[Colif]

Microsoft Windows link-layer topology responder driver - https://en.m.wikipedia.org/wiki/Link_Layer_Topology_Discovery

it was introduced in Vista but its still part of windows 10. Looks like its used for network discovery

it is strange for a windows file to be pulled up by Driver verifer. I wonder if lan drivers make difference

 

[Colif]

Since safe mode works, try running this

right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:
Repair-WindowsImage -Online -RestoreHealth and press enter
SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

if you type 2nd command out, make sure spacing is the same or you get an error 87

that should fix the driver that ticked off verifer

 

[xekushnr]

Yup, that did fix the rspndr.sys issue. The BSOD is still here though. I grabbed the memory.dmp after it died again; https://drive.google.com/file/d/16oh6Pr7IAfnV8mfodlhiT0bIigUrjYte/view?usp=sharing

 

[gardenman]

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

File: MEMORY.DMP (Feb 10 2019 - 22:49:08)
BugCheck: [WHEA_UNCORRECTABLE_ERROR (124)]
Probably caused by: GenuineIntel (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 33 Sec(s)

Possible motherboard page: https://www.asus.com/us/Motherboards/PRIME-Z270-AR/
It appears you have the latest available BIOS already installed.

I can't help you with this. Someone else will post with more information soon. Please wait for more answers. Good luck.

 

[Colif]

sorry if I am slow but I was waiting for forum software to change and had a list of the posts I had to answer, this was one of them

try running driver verifer again.

only drivers running at time of crash were

Sep 13 2016	iaStorA.sys	Intel SATA Storage Device RAID Controller
Oct 05 2016	e1d65x64.sys	Intel(R) Gigabit Adapter NDIS 6.x driver https://downloadcenter.intel.com/
Oct 26 2016	rzendpt.sys	Razer RzEndPt driver https://www.razerzone.com/
Oct 26 2016	rzudd.sys	Razer Rzudd Engine Driver https://www.razerzone.com/
Apr 04 2017	TeeDriverW8x64.sys	Intel Management Engine Interface driver https://downloadcenter.intel.com/
Oct 23 2018	nvhda64v.sys	Nvidia HDMI Audio Device http://www.nvidia.com/
Jan 11 2019	nvlddmkm.sys	Nvidia Graphics Card driver http://www.nvidia.com/

Nothing stands out, it could be any of them.