[SOLVED] Clean Installed W11 to fix BSODs, now they are worse...some help debugging?

[benshares]

I had a trusty install of W10 that would randomly BSOD (almost always while Idle) once ever day or two. After trying to sort some drivers out and cleaning some things with no success, I decided why not, let's clean install Windows 11.

Unfortunately, that has resulted in 5-10 BSODs per day.

I ran Memtest86 and passed after 4 passes with zero errors

I've updated all my drivers (GPU/chipset/onboard LAN/audio, etc.) and it doesn't seem to be getting better. I'm kind of stumped. Attached is a folder of the minidumps from TODAY

https://drive.google.com/drive/folders/1EQoaqor_WdT1tkiEdqeeHK0-MfAthtPz?usp=sharing

here's a summary from WhoCrashed:

On Sat 10/23/2021 8:09:18 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: rt64.sys (rt640x64+0x26a78)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8072C705330)
Error: DPC_WATCHDOG_VIOLATION
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: rt64.sys .
Google query: rt64.sys DPC_WATCHDOG_VIOLATION



On Sat 10/23/2021 6:44:27 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102321-7000-01.dmp
This was probably caused by the following module: rt64.sys (rt640x64+0x2408f)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF80234505330)
Error: DPC_WATCHDOG_VIOLATION
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: rt64.sys .
Google query: rt64.sys DPC_WATCHDOG_VIOLATION



On Sat 10/23/2021 5:15:45 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102321-7078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x412B70)
Bugcheck code: 0xA (0x2F1, 0xFF, 0x0, 0xFFFFF802230EA2DC)
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 Sat 10/23/2021 8:09:18 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102321-7953-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x3a82)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8072C705330)
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 Sat 10/23/2021 8:05:10 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102321-6968-01.dmp
This was probably caused by the following module: rt64.sys (rt640x64+0x2408f)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8035B905330, 0x0)
Error: DPC_WATCHDOG_VIOLATION
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: rt64.sys .
Google query: rt64.sys DPC_WATCHDOG_VIOLATION

Again, any help would be much appreciated. I'm going to try some new RAM just because this feels like a memory issue, but beyond that i'm stumped. Storage? PSU? Motherboard?

 

[zesun]

Do you have any other network card or perhaps multiple onboard network ports?

Anyways, try disabling the realtek one and see what happens.

 

[benshares]

Do you have any other network card or perhaps multiple onboard network ports?

Anyways, try disabling the realtek one and see what happens.

Just the one on the motherboard... without it the PC is pretty much dead in the water. I'll try to disable it and see what happens

 

[zesun]

Just the one on the motherboard... without it the PC is pretty much dead in the water. I'll try to disable it and see what happens

it's just that those dumbs kind of point towards Realtek and i suspect that's your network driver. might also be a SSD/HDD issue. but try to disable the onboard network and also completely remove Realtek drivers. if it is your network Port/driver then a new expansion card with network ports is the answer and a cheap fix.

 

[benshares]

Tried disabling the Realtek device and it seems to have stayed alive overnight. Had to enable it for work this morning, so we'll see. Ordered a $30 Asus networking card and we'll see how that goes.

 

[zesun]

Tried disabling the Realtek device and it seems to have stayed alive overnight. Had to enable it for work this morning, so we'll see. Ordered a $30 Asus networking card and we'll see how that goes.

I hope it works out, since you already ordered a new card
Keep us posted!

 

[benshares]

Sadly... not the networking card. I've got a new Asus card in there and just had a crash. Down to about 1 BSOD/Day but they are pointing at an AMD driver. New memory isn't here yet.

Added three most recent minidumps here: https://drive.google.com/drive/folders/1EQoaqor_WdT1tkiEdqeeHK0-MfAthtPz?usp=sharing

 

[benshares]

... and pulled my old memory and put in new DIMMs - and got a BSOD overnight. This time

This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x7e8cfb)
Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8027DD05330)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\System32\DriverStore\FileRepository\nvmdi.inf_amd64_3bab16edc4978b17\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 496.49

Starting to feel kind of crazy. Motherboard? Power Supply?

 

[alceryes]

It sounds like you have hardware issues. Your system was BSODing in Windows 10 and continues to crash Windows 11 - the frequency is just a sidebar to this fact.

Do you have any kind of overclocking, overvolting, timings adjustments, or power adjustments for any of your components (CPU, motherboard, RAM, GPU)?

 

[benshares]

I don't.

My old ram was running at DDR2133 even though it was 3200, so I set the timings manually. After I started getting BSODs, I reset all settings to default, with XMP on just to set the ram timings.

I just put new memory in, default BIOS settings, no OC

 

[benshares]

On Wed 10/27/2021 4:31:46 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!PsGetThreadId+0xCA9)
Bugcheck code: 0xBE (0xFFFFF8010B6D9028, 0xA000001004001A1, 0xFFFFA500D756CDE0, 0xF)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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.



On Wed 10/27/2021 4:30:09 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102721-8937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x415590)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80774EA3CD5, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 10/27/2021 3:16:38 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102721-7546-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x415590)
Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Wed 10/27/2021 3:11:05 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102721-7984-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x3a82)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8020B105330, 0x0)
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.

Sooo... having swapped memory, what would you try next? CPU? PSU? Motherboard?

 

[alceryes]

Sooo... having swapped memory, what would you try next? CPU? PSU? Motherboard?

Did you try a fresh install of Windows and then use the computer for a while before installing any programs/games/whatever?
Sometimes RAM timings can be an issue. Reset EVERYTHING to default and check stability.

 

[benshares]

So update - I replaced (and ruled out):

• formatting hdd and reinstalling windows
• updating and resetting bios to factory settings
• replacing networking card
• replacing memory
• replacing power supply

Finally, on 11/1 I got a beefy new CPU, swapped out the old one and poof - 48 hours with no crashes