Question several BSOD issues, 0x0000001e, 0x000000d1. All ntoskrnl.exe related.

[timmy_tissue]

I need some help working out what the issue is with these BSOD issues. I have run a memtest86 (just one pass) and it was fine. I could run more if ram seems to be the issue.

This all started after I reset the cmos cause I changed my memory speed by a tiny bit and it bricked the bios. I then downloaded the drivers on the motherboard website.
After this I added 2 sticks of ram.
I also installed windows on a different boot drive.

I know I shouldn't have made all these changes at once cause it makes it hard to diagnose.

b450 tomohawk max, r5 3600, 1060 6gb, corsair vengeance 4x8.

I have a bunch of dump files but I'm not sure how to attach them. I see the insert options but not one for a file.

I recently did a disk cleanup or windows install cleanup in powershell and it said it found issues and resolved them but I'm skeptical that the issue is really resolved cause I was having it on the other windows install.

Spoiler: dump 01

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\030823-5296-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Path validation summary *
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff8027c200000 PsLoadedModuleList = 0xfffff8027ce13450
Debug session time: Wed Mar 8 03:10:43.253 2023 (UTC - 5:00)
System Uptime: 0 days 0:23:56.889
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff8027c628c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe581cf4fa0f0=000000000000001e
2: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8027c63228b, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------

*

• 
  
  • *
  
  
  • *
  
  
  • Either you specified an unqualified symbol, or your debugger *
  
  
  • doesn't have full symbol information. Unqualified symbol *
  
  
  • resolution is turned off by default. Please either specify a *
  
  
  • fully qualified symbol module!symbolname, or enable resolution *
  
  
  • of unqualified symbols by typing ".symopt- 100". Note that *
  
  
  • enabling unqualified symbol resolution with network symbol *
  
  
  • server shares in the symbol path may cause the debugger to *
  
  
  • appear to hang for long periods of time when an incorrect *
  
  
  • symbol name is typed or the network symbol server is down. *
  
  
  • *
  
  
  • For some commands to work properly, your symbol path *
  
  
  • must point to .pdb files that have full type information. *
  
  
  • *
  
  
  • Certain .pdb files (such as the public OS symbols) do not *
  
  
  • contain the required information. Contact the group that *
  
  
  • provided you with these symbols if you need this command to *
  
  
  • work. *
  
  
  • *
  
  
  • Type referenced: ExceptionRecord *
  
  
  • *

*
*

• 
  
  • *
  
  
  • *
  
  
  • Either you specified an unqualified symbol, or your debugger *
  
  
  • doesn't have full symbol information. Unqualified symbol *
  
  
  • resolution is turned off by default. Please either specify a *
  
  
  • fully qualified symbol module!symbolname, or enable resolution *
  
  
  • of unqualified symbols by typing ".symopt- 100". Note that *
  
  
  • enabling unqualified symbol resolution with network symbol *
  
  
  • server shares in the symbol path may cause the debugger to *
  
  
  • appear to hang for long periods of time when an incorrect *
  
  
  • symbol name is typed or the network symbol server is down. *
  
  
  • *
  
  
  • For some commands to work properly, your symbol path *
  
  
  • must point to .pdb files that have full type information. *
  
  
  • *
  
  
  • Certain .pdb files (such as the public OS symbols) do not *
  
  
  • contain the required information. Contact the group that *
  
  
  • provided you with these symbols if you need this command to *
  
  
  • work. *
  
  
  • *
  
  
  • Type referenced: ContextRecord *
  
  
  • *

*
*

• 
  
  • *
  
  
  • *
  
  
  • Either you specified an unqualified symbol, or your debugger *
  
  
  • doesn't have full symbol information. Unqualified symbol *
  
  
  • resolution is turned off by default. Please either specify a *
  
  
  • fully qualified symbol module!symbolname, or enable resolution *
  
  
  • of unqualified symbols by typing ".symopt- 100". Note that *
  
  
  • enabling unqualified symbol resolution with network symbol *
  
  
  • server shares in the symbol path may cause the debugger to *
  
  
  • appear to hang for long periods of time when an incorrect *
  
  
  • symbol name is typed or the network symbol server is down. *
  
  
  • *
  
  
  • For some commands to work properly, your symbol path *
  
  
  • must point to .pdb files that have full type information. *
  
  
  • *
  
  
  • Certain .pdb files (such as the public OS symbols) do not *
  
  
  • contain the required information. Contact the group that *
  
  
  • provided you with these symbols if you need this command to *
  
  
  • work. *
  
  
  • *
  
  
  • Type referenced: ExceptionRecord *
  
  
  • *

*
*

• 
  
  • *
  
  
  • *
  
  
  • Either you specified an unqualified symbol, or your debugger *
  
  
  • doesn't have full symbol information. Unqualified symbol *
  
  
  • resolution is turned off by default. Please either specify a *
  
  
  • fully qualified symbol module!symbolname, or enable resolution *
  
  
  • of unqualified symbols by typing ".symopt- 100". Note that *
  
  
  • enabling unqualified symbol resolution with network symbol *
  
  
  • server shares in the symbol path may cause the debugger to *
  
  
  • appear to hang for long periods of time when an incorrect *
  
  
  • symbol name is typed or the network symbol server is down. *
  
  
  • *
  
  
  • For some commands to work properly, your symbol path *
  
  
  • must point to .pdb files that have full type information. *
  
  
  • *
  
  
  • Certain .pdb files (such as the public OS symbols) do not *
  
  
  • contain the required information. Contact the group that *
  
  
  • provided you with these symbols if you need this command to *
  
  
  • work. *
  
  
  • *
  
  
  • Type referenced: ContextRecord *
  
  
  • *

*

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3406

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4016

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 171

Key : Analysis.Init.Elapsed.mSec
Value: 5047

Key : Analysis.Memory.CommitPeak.Mb
Value: 97

Key : Bugcheck.Code.DumpHeader
Value: 0x1e

Key : Bugcheck.Code.Register
Value: 0x1e

Key : Dump.Attributes.AsUlong
Value: 1008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0


FILE_IN_CAB: 030823-5296-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8027c63228b

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: fffff8027cf1c468: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: Descenders.exe

STACK_TEXT:
ffffe581cf4fa0e8 fffff8027c7392aa : 000000000000001e ffffffffc0000005 fffff8027c63228b 0000000000000000 : nt!KeBugCheckEx
ffffe581cf4fa0f0 fffff8027c633ec2 : ffffe581cf4fa900 ffffe581cf4fa1c0 fffff8027c200000 fffff8027c62db26 : nt!HvlpVtlCallExceptionHandler+0x22
ffffe581cf4fa130 fffff8027c40fac3 : ffffc10955653c00 ffffc109556539c8 fffff8027c62db26 fffff8027c2e9ca8 : nt!RtlpExecuteHandlerForException+0x12
ffffe581cf4fa160 fffff8027c413907 : ffffffffffffffff ffffc10955653a70 ffffc10955653a70 ffffe581cf4fa900 : nt!RtlDispatchException+0x2f3
ffffe581cf4fa8d0 fffff8027c629e12 : 0000000000000000 0000000000000000 000000006d4b634f 0000000000000020 : nt!KiDispatchException+0x317
ffffe581cf4fafb0 fffff8027c629de0 : fffff8027c63e3f5 0000000000000000 ffffe581cf4d9180 0000000000000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffc10955653888 fffff8027c63e3f5 : 0000000000000000 ffffe581cf4d9180 0000000000000000 ffffc10955653ac0 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffc10955653890 fffff8027c639483 : fffff8027c624b70 fffff8027c54c6ea 000000035874140d 0000000000000000 : nt!KiExceptionDispatch+0x135
ffffc10955653a70 fffff8027c63228b : ffffe581cf4d9180 0000000000000000 ffff808d07c76080 fffff8027c62da0a : nt!KiGeneralProtectionFault+0x343
ffffc10955653c00 fffff8027c62db26 : 0000000000000000 ffff808cf88b9040 ffff808d07c76080 ffff808d06b99080 : nt!SwapContext+0xcb
ffffc10955653c40 0000000000000000 : ffffc10955654000 ffffc1095564e000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x176


SYMBOL_NAME: nt!SwapContext+cb

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.1265

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: cb

FAILURE_BUCKET_ID: AV_R_nt!SwapContext

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {73940a07-e238-0cb7-73a8-c9e01fdee4d3}

Followup: MachineOwner
---------

Link to dump files: https://drive.google.com/file/d/1i-U_jmfIjxqgvqrFn7Q-QWR2FRU77RNs/view?usp=sharing

 

[johnbl]

I looked at all the bugchecks, It looks like the cpu is messing up but I do not know why. maybe update the chipset drivers.
one bugcheck was a watchdog timeout but I could only see one core since it was a minidump. that core was running some network functions and audio functions nothing that looked wrong to me.

looking at the bugcheck on 3-8-2023
it looks like a access violation the code was trying to read some register in the amd cpu. I would expect some error in the chipset driver. I would install the amd chipset drivers from here:
B450 TOMAHAWK MAX | Motherboard | MSI Global
date should be 2023-02-24


BIOS Version 3.F0
BIOS Release Date 07/23/2022
Manufacturer Micro-Star International Co., Ltd
Product B450 TOMAHAWK MAX (MS-7C02)

Processor Version AMD Ryzen 5 3600 6-Core Processor
Processor Voltage 8bh - 1.1V
External Clock 100MHz
Max Speed 4200MHz
Current Speed 3600MHz

 

[timmy_tissue]

looking at the bugcheck on 3-8-2023
it looks like a access violation the code was trying to read some register in the amd cpu. I would expect some error in the chipset driver. I would install the amd chipset drivers from here:
B450 TOMAHAWK MAX | Motherboard | MSI Global
date should be 2023-02-24


BIOS Version 3.F0
BIOS Release Date 07/23/2022
Manufacturer Micro-Star International Co., Ltd
Product B450 TOMAHAWK MAX (MS-7C02)

Processor Version AMD Ryzen 5 3600 6-Core Processor
Processor Voltage 8bh - 1.1V
External Clock 100MHz
Max Speed 4200MHz
Current Speed 3600MHz

I installed this chipset driver before the issue began. Is it possible it's installed incorrectly? I actually havent had any crashes today so I'm thinking the windows system file repair might have fixed it somehow.

If drivers are the issue, I think this chipset driver may have actually caused the issue.

 

[johnbl]

here are some of the dates for your amd files:

amdgpio2.sys Thu Feb 7 01:32:20 2019
amdgpio3.sys Mon Mar 14 03:19:36 2016
AMDPCIDev.sys Mon May 17 22:18:23 2021
amdppm.sys (from microsoft no date shown)

mcupdate.dll Thu Dec 5 19:02:39 2030
(strange date of file, not the correct name for amd mc update)

in general microsoft no longer puts a date on its files, just a build indicator.

microsoft generally will put a cpu specific microcode update to patch out bugs in the amd cpu. this file should be called:
mcupdate_AuthenticAMD.dll and gets installed when you do not already have a microcode patch installed. you do not have it installed on your system for some reason.
here is info on the microcode updates:
Demystifying Microcode Updates for Intel and AMD P... - AMD Community

BIOS Release Date 07/23/2022
dentifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 5 3600 6-Core Processor
Update Status = REG_DWORD 3

 

[johnbl]

I installed this chipset driver before the issue began. Is it possible it's installed incorrectly? I actually havent had any crashes today so I'm thinking the windows system file repair might have fixed it somehow.

If drivers are the issue, I think this chipset driver may have actually caused the issue.

I think you will just have to give the system some time to see if you still get bugchecks. I would make sure that you have run the windows updates. the old memory dump looked like you have amd files from different sources/dates.

 

[timmy_tissue]

here are some of the dates for your amd files:

amdgpio2.sys Thu Feb 7 01:32:20 2019
amdgpio3.sys Mon Mar 14 03:19:36 2016
AMDPCIDev.sys Mon May 17 22:18:23 2021
amdppm.sys (from microsoft no date shown)

mcupdate.dll Thu Dec 5 19:02:39 2030
(strange date of file, not the correct name for amd mc update)

in general microsoft no longer puts a date on its files, just a build indicator.

microsoft generally will put a cpu specific microcode update to patch out bugs in the amd cpu. this file should be called:
mcupdate_AuthenticAMD.dll and gets installed when you do not already have a microcode patch installed. you do not have it installed on your system for some reason.
here is info on the microcode updates:
Demystifying Microcode Updates for Intel and AMD P... - AMD Community

BIOS Release Date 07/23/2022
dentifier = REG_SZ AMD64 Family 23 Model 113 Stepping 0
ProcessorNameString = REG_SZ AMD Ryzen 5 3600 6-Core Processor
Update Status = REG_DWORD 3

Most of this went over my head. I seem to not be getting issues anymore but it's just been a day.

 

[johnbl]

I guess the point is that the various files are coming from different vendors. I do know that microsoft has changed some of the power management defaults for the cpu. this would be the file amdppm.sys from microsoft update.
if it is this file causing the problem I would try this:
open registry editor and find this location:
computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7

find the entry called Attributes and set the value to 0

this will turn on a extra option in windows control panel
so open control panel and find this option:

=> Open Power Options ——> Change plan settings ——> Change advanced power settings ——> Processor power management ——> Processor performance boost mode ——> Set it to "Aggressive" and "Enabled"

I don't know if it will fix the problem but it will override the new default setting that microsoft sent out with windows update.

it should give the cpu a bit more power.

 

[timmy_tissue]

I guess the point is that the various files are coming from different vendors. I do know that microsoft has changed some of the power management defaults for the cpu. this would be the file amdppm.sys from microsoft update.
if it is this file causing the problem I would try this:
open registry editor and find this location:
computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7

find the entry called Attributes and set the value to 0

this will turn on a extra option in windows control panel
so open control panel and find this option:

=> Open Power Options ——> Change plan settings ——> Change advanced power settings ——> Processor power management ——> Processor performance boost mode ——> Set it to "Aggressive" and "Enabled"

I don't know if it will fix the problem but it will override the new default setting that microsoft sent out with windows update.

it should give the cpu a bit more power.

Another dump file. I'm getting different errors each time.
https://drive.google.com/file/d/1el1gLPT4OUHZr0xjBDQRonhK2o5AzGBj/view?usp=sharing

 

[johnbl]

Another dump file. I'm getting different errors each time.
https://drive.google.com/file/d/1el1gLPT4OUHZr0xjBDQRonhK2o5AzGBj/view?usp=sharing

nt!SwapContext called then a
stack pointer error
system running for 10 hours

have you tried the regedit to turn on the power menu in control panel?
still looks like a issue with the processor settings

looks like a bunch of the amd files were updated.
xbox gaming drivers look modified, you might uninstall and reinstall them.

not sure what
ssudbus2.sys
does

-maybe set the system to run in high performance mode and see if it has any effect (not sleeping)

-maybe google how to delete the pagefile.sys on shutdown. this will force a new pagefile to be created on each boot and force windows to reload all the files from disk on each startup. I can help if something is hacking your pagefile.sys images.

dism.exe command should have fixed the files on disk.
but it does not fix the image in ram or in the pagefile.sys.
dism.exe /online /cleanup-image /restorehealth

you might consider a clean windows reinstall.
is windows defender still running? looks like its drivers have been modified.

 

[timmy_tissue]

nt!SwapContext called then a
stack pointer error
system running for 10 hours

have you tried the regedit to turn on the power menu in control panel?
still looks like a issue with the processor settings

looks like a bunch of the amd files were updated.
xbox gaming drivers look modified, you might uninstall and reinstall them.

not sure what
ssudbus2.sys
does

-maybe set the system to run in high performance mode and see if it has any effect (not sleeping)

-maybe google how to delete the pagefile.sys on shutdown. this will force a new pagefile to be created on each boot and force windows to reload all the files from disk on each startup. I can help if something is hacking your pagefile.sys images.

dism.exe command should have fixed the files on disk.
but it does not fix the image in ram or in the pagefile.sys.
dism.exe /online /cleanup-image /restorehealth

you might consider a clean windows reinstall.
is windows defender still running? looks like its drivers have been modified.

I'm currently running driver verifier and seeing if I can reproduce the crash. I notice many times I crash when I land in Descenders (a game on steam) and the controller is stuck on vibrate. I wonder if that could have anything to do with it. You mention Xbox game drivers, could it be that the xbox controller driver is messed up? I'm only verifying non Microsoft drivers right now though.

I haven't tried the processor regedit yet. I'm really suspecting the chipset driver could be the issue though but I don't know how to switch to a different version or fix that driver. The amd software just installs the latest one.

I have a windows installed on a different SSD in the system. I could go back to that one. Would it be able to roll back the chipset drivers?

 

[johnbl]

I'm currently running driver verifier and seeing if I can reproduce the crash. I notice many times I crash when I land in Descenders (a game on steam) and the controller is stuck on vibrate. I wonder if that could have anything to do with it. You mention Xbox game drivers, could it be that the xbox controller driver is messed up? I'm only verifying non Microsoft drivers right now though.

I haven't tried the processor regedit yet. I'm really suspecting the chipset driver could be the issue though but I don't know how to switch to a different version or fix that driver. The amd software just installs the latest one.

I have a windows installed on a different SSD in the system. I could go back to that one. Would it be able to roll back the chipset drivers?

Microsoft made a change to lower the CPU power usage. They did this by updating the file amdppm.sys and pushed it out to your machine via windows update.
making the registry change to enable the menu in control panel can allow you to run the processor with proper power.
(at least in theory) I have talked to one person who had similar issues that looked like the CPU was messing up. This was the only change that helped.

the only away around it would be a more current bios update or installing amd ryzen master driver for overclocking, it is more likely to provide proper power levels since they did not get a government mandate to make PC save more power.

you could look for a powershell script to uninstall the xbox gaming drivers then reinstall them again.
then find out why the windows virus scanner has been modified.
(or just clean install windows again)

the driver verifier might find something, but if amdppm.sys is not providing enough power to the CPU then the info in the debugger will just look strange.
it tends to look like a memory dump from a cpu that was overheated, or a system that is infected with malware. it is hard to figure out since you only get a snapshot of the drivers running and the stack on one cpu.

this might help with the xbox drivers:
How to Delete/Remove/Uninstall/Disable Xbox Apps Windows 11? (minitool.com)
maybe this to reinstall windows defender
Fix: Windows Defender is Missing in Windows 11 (windowsreport.com)
(or you can see if it is still working, malware tend to try to break it to prevent it from running)

I am not sure why you are not getting the windows cpu microcode update installed. Normally, it would come via windows update.
Is windows update working on your computer?
only thing that would normally block the install of the cpu microcode update would be if another custom version was installed. (like amd ryzenmaster driver)
AMD Ryzen™ Master Utility for Overclocking Control | AMD

you might also consider changing the memory dump type to kernel, this will force the system to save info on all of the running cpu cores and the internal logs. it could help with one of the minidumps where the system took to long to process some driver data. (watchdog timeout)
in that case the faulting core did not have any real strange problems. Maybe something would have shown up on the other cores if the dump was a kernel dump . also some systems already save the kernel dump as c:\windows\memoy.dmp file
you should check to see if there is already one.

 

[timmy_tissue]

Microsoft made a change to lower the CPU power usage. They did this by updating the file amdppm.sys and pushed it out to your machine via windows update.
making the registry change to enable the menu in control panel can allow you to run the processor with proper power.
(at least in theory) I have talked to one person who had similar issues that looked like the CPU was messing up. This was the only change that helped.

the only away around it would be a more current bios update or installing amd ryzen master driver for overclocking, it is more likely to provide proper power levels since they did not get a government mandate to make PC save more power.

you could look for a powershell script to uninstall the xbox gaming drivers then reinstall them again.
then find out why the windows virus scanner has been modified.
(or just clean install windows again)

the driver verifier might find something, but if amdppm.sys is not providing enough power to the CPU then the info in the debugger will just look strange.
it tends to look like a memory dump from a cpu that was overheated, or a system that is infected with malware. it is hard to figure out since you only get a snapshot of the drivers running and the stack on one cpu.

this might help with the xbox drivers:
How to Delete/Remove/Uninstall/Disable Xbox Apps Windows 11? (minitool.com)
maybe this to reinstall windows defender
Fix: Windows Defender is Missing in Windows 11 (windowsreport.com)
(or you can see if it is still working, malware tend to try to break it to prevent it from running)

I am not sure why you are not getting the windows cpu microcode update installed. Normally, it would come via windows update.
Is windows update working on your computer?
only thing that would normally block the install of the cpu microcode update would be if another custom version was installed. (like amd ryzenmaster driver)
AMD Ryzen™ Master Utility for Overclocking Control | AMD

you might also consider changing the memory dump type to kernel, this will force the system to save info on all of the running cpu cores and the internal logs. it could help with one of the minidumps where the system took to long to process some driver data. (watchdog timeout)
in that case the faulting core did not have any real strange problems. Maybe something would have shown up on the other cores if the dump was a kernel dump . also some systems already save the kernel dump as c:\windows\memoy.dmp file
you should check to see if there is already one.

This dump file from my old windows install actually lists amdppm.sys as the cause.
https://drive.google.com/file/d/1ofnM4GtPGBUFANXIzja-5hJTiBrPq57B/view?usp=sharing

I saw some people suggest going to balanced performance in power settings. Does that make any sense to you? It seems like you think I need to give the cpu more power.

I do have ryzen master on the old install.

I dont see "attributes" in be3372..... I see a bunch of folders and non have attributes in them.

 

[johnbl]

you might also consider cha

This dump file from my old windows install actually lists amdppm.sys as the cause.
https://drive.google.com/file/d/1ofnM4GtPGBUFANXIzja-5hJTiBrPq57B/view?usp=sharing

I saw some people suggest going to balanced performance in power settings. Does that make any sense to you? It seems like you think I need to give the cpu more power.

I was thinking: if microsoft reduced the cpu power then increasing it might resolve the problem. Ie go back to the old state. That is why I would enable the registry setting to turn on the new power option.
it is hard to say, so many of these setting depend on the chip set driver, and the bios version you have installed.
then the various overclocking drivers tend to override the settings anyway. Older CPUs tend to take more power than the newer versions. I think your cpu came on in 2019 so there are lots of bios patches and microcode updates to fix or block certain CPU functions. with all of the CPU security hacks there should be a bunch more bios updates coming. I could see hackers blocking the cpu microcode patches from installing.
but I do not keep up with malware/virus attacks. It is not fun remote debugging when something is trying to hide from you.

 

[timmy_tissue]

you might also consider cha


I was thinking: if microsoft reduced the cpu power then increasing it might resolve the problem. Ie go back to the old state. That is why I would enable the registry setting to turn on the new power option.
it is hard to say, so many of these setting depend on the chip set driver, and the bios version you have installed.
then the various overclocking drivers tend to override the settings anyway. Older CPUs tend to take more power than the newer versions. I think your cpu came on in 2019 so there are lots of bios patches and microcode updates to fix or block certain CPU functions. with all of the CPU security hacks there should be a bunch more bios updates coming. I could see hackers blocking the cpu microcode patches from installing.
but I do not keep up with malware/virus attacks. It is not fun remote debugging when something is trying to hide from you.

I did a complete clean instal of windows. It seems to have stopped the bsod issues. I am getting this crash in Elden Ring though which is the only game I've tested.

Faulting application name: eldenring.exe, version: 1.8.1.0, time stamp: 0x6396cee8
Faulting module name: nvwgf2umx.dll, version: 31.0.15.3118, time stamp: 0x63f92111
Exception code: 0xc0000005
Fault offset: 0x0000000001602f62
Faulting process id: 0x0x2F58
Faulting application start time: 0x0x1D9537E0B5A1FEA
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\ELDEN RING\Game\eldenring.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_abf7e4e84f20581c\nvwgf2umx.dll
Report Id: 928ff5a1-6ffb-4639-b48c-76df7229d51d
Faulting package full name:
Faulting package-relative application ID:

It seems like it's related somehow. I ruled out memory as the issue. My only idea is that the motherboard, cpu, or gpu is shot. I did get some strange graphical bug on one loading screen that looked like a faulty gpu but I'm not sure.

 

[johnbl]

C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_abf7e4e84f20581c\nvwgf2umx.dll

I do not know what nvwgf2umx.dll actually does, I converted the format of the date to something you can read: Time stamp: Fri Feb 24 12:41:53 2023
version number : 31.0.15.3118
looks like a 32bit nvidia file loading for a game and getting an access violation.
maybe make sure you are using a standard video format and frequency.
ie 1024 @60hz and see if it still faults

Since you did a clean install of windows, I guess the first thing I would look for is a permissions problem. Maybe try to run the game as an administrator and see if it still fails.
maybe uninstall the driver and use a different (newer or older version)

sometimes new setup programs do not put all of the registry settings in. fix is to run a older stable version to get the registry settings correct then update to get the updated drivers. (just a guess)


if you reinstalled and you have a realtek sound card on your motherboard, make sure you have updated the driver to one dated in 2020 or newer.

edit: guess I would also check to see if all of your windows updates have been applied since you clean installed.

 

[timmy_tissue]

C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_abf7e4e84f20581c\nvwgf2umx.dll

I do not know what nvwgf2umx.dll actually does, I converted the format of the date to something you can read: Time stamp: Fri Feb 24 12:41:53 2023
version number : 31.0.15.3118
looks like a 32bit nvidia file loading for a game and getting an access violation.
maybe make sure you are using a standard video format and frequency.
ie 1024 @60hz and see if it still faults

Since you did a clean install of windows, I guess the first thing I would look for is a permissions problem. Maybe try to run the game as an administrator and see if it still fails.
maybe uninstall the driver and use a different (newer or older version)

sometimes new setup programs do not put all of the registry settings in. fix is to run a older stable version to get the registry settings correct then update to get the updated drivers. (just a guess)


if you reinstalled and you have a realtek sound card on your motherboard, make sure you have updated the driver to one dated in 2020 or newer.

edit: guess I would also check to see if all of your windows updates have been applied since you clean installed.

Issue solved: Posting for anyone who finds this.

I did three things which has resolved the issue.

Windows reset (I doubt this did anything as I had already cleaned and re installed windows.)
Deleted all my files from onedrive, which was making me feel like the install wasnt clean because it was copying stuff from my old appdata folder before I could uninstall onedrive.
I unplugged three sata cables from the motherboard, 2 of which were connected to drives, one was connected to nothing. (this is what I believe solved the issue)

In hindsight, I did try removing all the peripherals but I never considered the drives, which seems obvious to me now.

I will experiment with plugging in the drives later. I think it could be a bad sata cable, as I did switch one recently (just because it had a right angled plug).