Random BSOD's with either 156 or 292 as BugCheckCode

Attachment 279152Attachment 279153

Microsoft Windows [Version 10.0.18363.836]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.836

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18363.836

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is System.

Stage 1: Examining basic file system structure ...
642048 file records processed.
File verification completed.
11268 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
1252 reparse records processed.
838732 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
1252 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
98343 data files processed.
CHKDSK is verifying Usn Journal...
34885848 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

249397247 KB total disk space.
84582556 KB in 498371 files.
256952 KB in 98344 indexes.
0 KB in bad sectors.
754603 KB in use by the system.
65536 KB occupied by the log file.
163803136 KB available on disk.

4096 bytes in each allocation unit.
62349311 total allocation units on disk.
40950784 allocation units available on disk.

C:\Windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-E6C97SD\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk3\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-E6C97SD\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk3\\Partition3"'
Property(s) update successful.

C:\Windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\Windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\Windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

V2: DESKTOP-E6C97SD-(2020-05-17_21-02-08).zip - Google Drive

DM: DESKTOP-E6C97SD-Sun_05_17_2020_212827_34.zip - Google Drive

The log bugchecks were:
9C
124
CE
50

For Windows driver verifier restart the tool with the 3 customized test settings in the Ten Forums link.
Increase the number of customized tests by 3 - 5 / hour up to the 19 in the Microsoft link.
Plan to run the tool for 48 hours and then 36 hours after the last BSOD.
If there are no further BSOD that will complete the use of the tool.

Once misbehaving drivers are eliminated hardware stress tests can be performed.

Often swap testing may be required to rule in and / or rule out malfunctioning hardware.


Turn off Windows fast startup:
Turn On or Off Fast Startup in Windows 10

Code:

Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.

Code:

Windows failed fast startup with error status 0xC00000D4.

After completing zbook's suggestions (and posting the results), I'd suggest starting on these free hardware diagnostics while waiting for a reply. The bugchecks that zbook cited in their post may be suggestive of a hardware problem. The 9C and 124 are definitely suggestive, as is the random distribution of error codes.

First step is to ensure that you can monitor your temps. I suggest one of these free tools:
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer

- MemTest86 (4 passes): MemTest86 - Official Site of the x86 Memory Testing Tool

- Seagate Seatools for Windows (long/extended test on ALL drive): SeaTools for Windows |
Seagate

- OCCT (all tests): OCBASE / OCCT Run until the temps level out.
Each test is different, so you'll have to keep an eye on the temps while running each test.

- Furmark (run until temp's level out or there are problems - whichever comes first): FurMark > Home

- Prime95 Stress Testing (run for at least an hour - or until the temp's level out. If you get errors you can stop the testing): GIMPS - Free Prime95 software downloads - PrimeNet

- Intel Processor Diagnostic Tool (if equipped w/Intel CPU): The Intel(R) Processor Diagnostic Tool

Finally, troubleshoot by hardware stripdown (this is an older post and some of the links are broken - but it's still relevant to your situation): Hardware Stripdown Troubleshooting

These links include the Ten forums and Microsoft links for Windows driver verifier:


Create System Restore Point in Windows 10


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983


Boot into Safe Mode on Windows 10

I enabled Driver Verifier and waited for the inevitable crashing, but strangely the system has now been perfectly stable for several days. I thought the Verifier was supposed to increase the chance of a crash by stressing the driver system out? Sooner or later there is bound to be one though. Or does this indicate that there's something wrong with a driver that the verifier is keeping in check?

For Windows driver verifier start with the 3 customized test settings in the Ten Forums link.
Increase the number of simultaneous customized tests by 3 - 5 / hour up to the 19 customized tests in the Microsoft link.

For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Alright. Still no crashes, despite 40+ hours of continuous operation. Is there any downside to always having the Driver Verifier on? And does that mean that there's a corrupt driver at fault somewhere here? It seems like it can't be a coincidence, compared to how it was before.

Open administrative command prompt and type or copy and paste:
verifier /querysettings

When this has completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


Upload a new V2.

Microsoft Windows [Version 10.0.18363.836]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Windows\system32>verifier /querysettings

Verifier Flags: 0x00100610

Standard Flags:

[ ] 0x00000001 Special pool.
[ ] 0x00000002 Force IRQL checking.
[ ] 0x00000008 Pool tracking.
[X] 0x00000010 I/O verification.
[ ] 0x00000020 Deadlock detection.
[ ] 0x00000080 DMA checking.
[ ] 0x00000100 Security checks.
[ ] 0x00000800 Miscellaneous checks.
[ ] 0x00020000 DDI compliance checking.

Additional Flags:

[ ] 0x00000004 Randomized low resources simulation.
[X] 0x00000200 Force pending I/O requests.
[X] 0x00000400 IRP logging.
[ ] 0x00002000 Invariant MDL checking for stack.
[ ] 0x00004000 Invariant MDL checking for driver.
[ ] 0x00008000 Power framework delay fuzzing.
[ ] 0x00010000 Port/miniport interface checking.
[ ] 0x00040000 Systematic low resources simulation.
[ ] 0x00080000 DDI compliance checking (additional).
[ ] 0x00200000 NDIS/WIFI verification.
[ ] 0x00800000 Kernel synchronization delay fuzzing.
[ ] 0x01000000 VM switch verification.
[ ] 0x02000000 Code integrity checks.

Internal Flags:

[X] 0x00100000 Extended Verifier flags (internal).

[X] Indicates flag is enabled.

Boot Mode:

Persistent

Rules:

All rules are using default settings

Verified Drivers:

iastorac.sys
smartdefragdriver.sys
pwdrvio.sys
nldrv.sys
hwinfo64a.sys
glckio2.sys
ene.sys
asio2.sys
asupio.sys
nvlddmkm.sys
teedriverw8x64.sys
smb_driver_intel.sys
e1d68x64.sys
ialpss2i_gpio2_cnl.sys
nvvad64v.sys
nvvhci.sys
lgbusenum.sys
lgjoyxlcore.sys
nvhda64v.sys
rtkvhd64.sys
rtwlanu.sys
lgsusbfilt.sys
lgshidfilt.sys
dump_diskdump.sys
dump_iastorac.sys
dump_dumpfve.sys
lgcoretemp.sys
speedfan.sys
lgvirhid.sys
ascfilefilter.sys
ascregistryfilter.sys
mpksldrv.sys

C:\Windows\system32>

DESKTOP-E6C97SD-(2020-05-25_21-06-13).zip - Google Drive

The above post displayed 3 customized tests.

How come the number of simultaneous customized tests were not increased by 3 - 5 / hour up to the 19 customized tests in the Microsoft link?