BSOD, bug check 0x124. Tested parts, completely lost.

Here's another, this one with a barebones install. Only CPU, one RAM stick, a different (confirmed working) PSU, a display and keyboard hooked up. I had set up a clean boot a while ago so it should still be the same; any additional files would have been installed with drivers after the issue appeared and would not be the culprit. It should functionally be a clean boot though.

Beta log attached, memory.dmp here; MEMORY2.zip - Google Drive

Since the issue persists now with a different working PSU, we can now eliminate that. RAM, GPU, PSU, and mouse and related drivers do not appear to be the issue. Again, CPU was tested but not by me (purchased from Micro Center, still has store warranty, they tested) and checked out.

EDIT: for the record, since it was a barebones test no ethernet was connected and the driver is actually still uninstalled.

1) In the latest memory dump there were no drivers seen with the common debugging commands.

2) Using a less common debugging command these two Intel drivers appeared in the debugging:

Code:

iaStorA  iaStorA.sys  Tue Sep 13 07:45:46 2016 (57D8111A)
igdkmd64 igdkmd64.sys Thu Sep 20 12:49:09 2018 (5BA3F9B5)

The chipset driver was dated 2016.

3) Windows has a feature to automatically perform Windows updates and can install non-Microsoft drivers.

4) The logs displayed that the Intel Ethernet driver e1d65x64.sys had been reinstalled and was temporally related to the log entries for a WHEA 0 x 124 crash.

5) There were other BSOD though that did not have this temporal relationship.

6) Temporarily turn off Windows updates of non-Microsoft drivers:
Enable or Disable Driver Updates in Windows Update in Windows 10 | Tutorials

7) Uninstall and reinstall these Intel drivers:

Updating a driver. - Microsoft Community

igdkmd64.sys (25.20.100.6323) IGFX Intel GPU
iastora.sys (15.2.0.1020) Intel(R) 200 Series Chipset Family SATA AHCI Controller

PRIME Z270-A Driver & Tools | Motherboards | ASUS USA


8) There is a lot of free space on the drive where the memory.dmp files can be temporarily saved:

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 441.8 GB
Total Space: 476.0 GB
File System: NTFS
      Model: Samsung SSD 850 EVO 500GB

Open system control panel > startup and recovery system failure > under dump file uncheck overwrite any existing file > reboot to maintain settings

9) For each BSOD inaddition to the BETA zip please post a zipped memory dump using a share link if the file size is < 1.5 GB

10) Uninstall: e1d65x64.sys

Code:

Event[6662]:
  Log Name: System
  Source: Microsoft-Windows-UserPnp
  Date: 2019-02-11T19:39:01.901
  Event ID: 20003
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-O0Q329Q
  Description: 
Driver Management has concluded the process to add Service e1dexpress for Device Instance ID PCI\VEN_8086&DEV_15B8&SUBSYS_86721043&REV_00\3&11583659&0&FE with the following status: 0.

Event[6663]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2019-02-11T19:39:02.429
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-O0Q329Q
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xffffdd0d9e953028, 0x00000000f2003a40, 0x0000000000010005). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: daeb6e94-566e-45be-8b02-075afc178d75.

Event[6664]:
  Log Name: System
  Source: Microsoft-Windows-UserPnp
  Date: 2019-02-11T19:39:02.509
  Event ID: 20001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-O0Q329Q
  Description: 
Driver Management concluded the process to install driver e1d65x64.inf_amd64_bca18ddfcfc6b361 for Device Instance ID PCI\VEN_8086&DEV_15B8&SUBSYS_86721043&REV_00\3&11583659&0&FE with the following status: 0x0.

Code:

Name	[00000001] Intel(R) Ethernet Connection (2) I219-V
Adapter Type	Ethernet 802.3
Product Type	Intel(R) Ethernet Connection (2) I219-V
Installed	Yes
PNP Device ID	PCI\VEN_8086&DEV_15B8&SUBSYS_86721043&REV_00\3&11583659&0&FE
Last Reset	2/12/2019 6:31 PM
Index	1
Service Name	e1dexpress
IP Address	Not Available
IP Subnet	Not Available
Default IP Gateway	Not Available
DHCP Enabled	Yes
DHCP Server	Not Available
DHCP Lease Expires	Not Available
DHCP Lease Obtained	Not Available
MAC Address	‪2C:4D:54:55:67:13‬
Memory Address	0xDF100000-0xDF11FFFF
IRQ Channel	IRQ 4294967293
Driver	c:\windows\system32\drivers\e1d65x64.sys (12.17.8.7, 534.06 KB (546,880 bytes), 10/25/2016 4:03 PM)

Code:

e1dexpress	Intel(R) PRO/1000 PCI Express Network Connection Driver D	c:\windows\system32\drivers\e1d65x64.sys	Kernel Driver	No	Manual	Stopped	OK	Normal	No	No

Code:

e1d65x64.sys Mon Sep 25 05:45:31 2017 (59C8FA6B)

Code:

igfx         igfx                   igfx                   Kernel        Manual     Stopped    OK         FALSE       FALSE        16,384            7,225,344   0          9/20/2018 3:49:09 PM   C:\WINDOWS\system32\DriverStore\FileRepository\i 8,192

Code:

iaStorA      iaStorA                iaStorA                Kernel        Boot       Running    OK         TRUE        FALSE        4,096             696,320     0          9/13/2016 10:45:46 AM  C:\WINDOWS\system32\drivers\iaStorA.sys          4,096

I've done all you asked but e1d65x64.sys keeps reinstalling itself after a restart.

Has the computer been stable without BSOD in safe mode, normal boot, or clean boot since the one day steps?
If it has been stable in safe mode then switch to normal boot or clean boot to check stability / instability.
For any BSOD > post a memory dump.

xekushnr said:

Here's another, this one with a barebones install. Only CPU, one RAM stick, a different (confirmed working) PSU, a display and keyboard hooked up. I had set up a clean boot a while ago so it should still be the same; any additional files would have been installed with drivers after the issue appeared and would not be the culprit. It should functionally be a clean boot though.

Beta log attached, memory.dmp here; MEMORY2.zip - Google Drive

Since the issue persists now with a different working PSU, we can now eliminate that. RAM, GPU, PSU, and mouse and related drivers do not appear to be the issue. Again, CPU was tested but not by me (purchased from Micro Center, still has store warranty, they tested) and checked out.

EDIT: for the record, since it was a barebones test no ethernet was connected and the driver is actually still uninstalled.

Based on your latest report I believe you are now looking at a defective CPU or motherboard. You will only know by replacing the current CPU with another one and testing. Perhaps the store will do this for you to confirm the diagnosis and if the CPU is found to be the culprit they should change it under warranty.

I should be able to procure another MB by the end of the weekend. I'm pretty sure at this point that it's the issue. I will check in after I know to update.

Which mode is in current use: safe mode, clean boot or normal boot?
Have there been any bsod in the different modes since the most recent changes?
If so please post a memory.dmp zip

Okay, so I tried a different motherboard but the issues still continue. With this motherboard installed, the PC will now blue screen in safe mode as well.

One thing I have noticed; if I boot and then run Prime95 to keep the CPU loaded, it will NOT blue screen. It only seems to be when the CPU is idle, but like I've said it will blue screen every time when it's idle.

I'm away from the computer for the weekend; I had some fresh minidumps and a memory.dmp saved to a thumbdrive but left the damn thing at home, you will have to wait till Sunday for me to upload them.

What could it mean that the CPU will blue screen while idle but not while under load?

Was only the motherboard or were the CPU or other hardware components swapped?

When the log files are available they can be debugged to see if there is new information.

Please update on the status of finding a CPU to swap.

For the WHEA it is often useful to test and rule in or rule out each hardware component.

When available please post images of each of these test results for the steps in post #6

Everything has been tested AND swapped to make double sure, all except the processor which has just been tested (I do not have access to another one). All the hardware is fine. I've even swapped all the cables and PSU just in case. Nothing has changed, BSOD in a minute in a half in windows unless processor is under load.