Windows 10: New machine getting BSOD at random times

Hi folks. Working with a new machine that has been blue screening slightly more frequently over the last few weeks. Have tried updating all drivers & flashing bios to most recent version but the BSOD persists. Have also tried reseating hardware components without any luck.


Blue screens are varied but they tend to be windows kernel errors. Here are a few from WhoCrashed reports:



On Mon 11/23/2020 9:40:18 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112320-7921-01.dmp
This was probably caused by the following module: amdppm.sys amdppm+0x2ec7
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF8031FCFB320
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
The crash took place in a Microsoft module. The description of the module may give a hint about a non responding device in the system.



On Mon 11/23/2020 9:40:18 AM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nvlddmkm.sys nvlddmkm+0x9a413
Bugcheck code: 0x133 0x0, 0x501, 0x500, 0xFFFFF8031FCFB320
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5dcb5bbf5c3edcf2\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 457.30
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 457.30
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys NVIDIA Windows Kernel Mode Driver, Version 457.30 , NVIDIA Corporation.
Google query: nvlddmkm.sys NVIDIA Corporation DPC_WATCHDOG_VIOLATION



On Sun 11/22/2020 1:53:15 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\112220-7765-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x139 0x3, 0xFFFFFB0431CD16C0, 0xFFFFFB0431CD1618, 0x0
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time



On Thu 11/19/2020 10:50:26 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111920-7890-01.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0xA 0x102, 0x2, 0x1, 0xFFFFF80525EDEB8E
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 11/19/2020 8:13:41 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\111920-8125-02.dmp
This was probably caused by the following module: ntoskrnl.exe nt+0x3F5210
Bugcheck code: 0x1 0x7FFE1D6EBE24, 0x0, 0xFFFF, 0xFFFFEA0F9D068B80
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


MSconfig link here:

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


Would appreciate any help. Thanks.

:)

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.

 

Random BSOD on new machine, SSD not found after each BSOD

Yes, your assumptions should be right.
- latest BIOS/UEFI - running latest BIOS from Asus
- memory passed diagnostics - yes mem diagnostic test results are OK
- HDD/SSD likely good - but haven't run diagnostics (only SFC and chkdsk)
SSD looks good. here are some screenshots from HD Tune







- OS was repaired w/DISM, and was "clean" installed - yes
- all components are new (?unknown warranty/RMA status) - yes all components are new with valid warranty

Additionally, I tried using Windows Driver Verifier.
Followed the steps here :
https://answers.microsoft.com/en-us/...3-c48669e4c983
Results:
1. Following the steps, I selected ALL drivers except Windows drivers and reboot.
2. After reboot, windows 10 crashes instantly even before login page comes.
3. Eventually windows goes to troubleshoot mode, and I load windows 10 in safe mode.
4. In safe mode, I disabled verifier via cmd, and reboot again. Windows 10 boots normally now.

Additional link I referred to:
https://docs.microsoft.com/en-sg/win...ectedfrom=MSDN

Could it be a faulty/incompatible driver that has been installed?

- - - Updated - - -

Yes, your assumptions are right.
1. BIOS is running latest version from ASUS
2. mem diagnostics are OK
3. SSD looks good.







4. OS is repaired and clean
5. all components are new with valid warrently

I tried using Windows Driver Verifier.
Following these steps :
https://answers.microsoft.com/en-us/...3-c48669e4c983

Steps done:
1. Selected all drivers except Microsoft to verify.
2. reboot
Results:
1. Upon reboot, windows 10 instantly crashes before login screen. Loops
2. Eventually ends up at troubleshoot mode, perform reboot on safe mode
3. on safe mode, disable verifier and reboot
4. windows 10 runs again (until next BSOD)

Could it be caused by a faulty/defective/non-compatible driver?

 

Random BSOD on new machine, SSD not found after each BSOD

This is the Furmark's test.
Temps maintain at around 72C after 6minutes of runtime.
GPU looks OK. No errors.




Will look into the stripdown as soon as I get the chance