[SOLVED] Major BSOD issues

[Rstipton]

Started getting BSODs regularly with a variety of errors. Most errors pointed to driver issues. Had no luck with new drivers so I concluded it was a corruption of Win 10. I wiped the SSD and opted for a clean install of Win 10 via flash drive. Now it will not complete the initial Win setup. I get as far as the screen where you enter your email and password.

List of BSOD errors I have seen:
Irql not less or equal
Kernel auto boost lock acquisition with raised irql
Memory management
Resource management
Dpc watchdog violation
Driver irql not less or equal
Event tracing fatal error
Critical process died
Pfn list corrupt
Kmode exception not handled
system thread exception not handled
kernel security check failure
unexpected kernel mode trap
multiple irp complete requests

Troubleshooting thus far:
Multiple Win reinstall attempts
Reset CMOS to defaults
Disabled networking in CMOS
Disabled audio in CMOS
Reseated GPU
Reseated Ram
Attempted boot on one stick of Ram then the other
Moved RAM to other slots.
Attempted boot with known working RAM
Have reseated SSD and tried both m.2 slots
Examined motherboard for blown or swollen capacitors and other obvious defects

I was able to get the install to complete by creating a guest account, probably because it loads faster, but still got the BSOD once windows was started. I next tried a spare SATA HDD I had that already had Win on it. Machine boots to this other drive but still getting regular BSODs with same errors.

My hardware includes:
AMD Ryzen 5 3600 3.6 GHz 6-Core Processor
MSI B550-A PRO ATX AM4 Motherboard
Corsair Vengeance RGB Pro 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory
Silicon Power P34A80 1 TB M.2-2280 NVME Solid State Drive
Gigabyte GeForce GTX 1650 SUPER 4 GB WINDFORCE OC Video Card

I am concluding that this is a hardware error although I am not sure which piece. This machine was built exactly one year ago with all new components so nothing is really old on it. The RAM has already been replaced once under warrantee. At this point is it more likely to be the motherboard, processor or something else? Any help is appreciated as my hair is all but pulled out. 😕

 

[Colif]

too many bsod codes, i seen all those too but not on one pc.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

if you suspect cpu or mb, I would suggest having a repair store look at PC as while there is a test for CPU, MB doesn't have any tests. One way to check is to put all the equipment on another MB and see if you still crash

Prime 95 bootable - https://www.infopackets.com/news/10113/how-fix-bootable-prime95-stress-test-hardware
Prime 95 how to Guide: http://www.playtool.com/pages/prime95/prime95.html

edit: removes request for BSOD reports since it won't even get that far in the install.

 

[Rstipton]

Ran memtest86. 4 passes
Stress tested as suggested in the post 24 hrs
tried several "good" sticks of memory
Tried another video card
Tried to install Win 10 and win 11 on a different hdd

Finally after an insane number of attempts got win 10 installed on the ssd. Still getting BSODs but at least I can see the mem dumps. Below is the latest mini dump. Can someone please take a look?

Spoiler

Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\010122-3593-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: Invalid relocation block size 0x0 * WARNING: Unable to verify timestamp for ntoskrnl.exe 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: nt!_EPROCESS Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff8030aa00000 PsLoadedModuleList = 0xfffff8030b62a270 Debug session time: Fri Dec 31 15:46:05.881 2021 (UTC - 8:00) System Uptime: 0 days 0:00:22.508 Invalid relocation block size 0x0 * WARNING: Unable to verify timestamp for ntoskrnl.exe * * 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: nt!_EPROCESS Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ...... Symbol Loading Error Summary * Module name Error ntoskrnl The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. For analysis of this file, run !analyze -v nt+0x3f71b0: fffff8030adf71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb306694d5880=000000000000000a 3: kd> !analyze -v * * * Bugcheck Analysis * * * IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000008, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8030ac42166, address which referenced memory Debugging Details: ------------------ Kernel symbols are WRONG. Please fix symbols to do analysis. * 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: nt!_IMAGE_DOS_HEADER 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: nt!_IMAGE_DOS_HEADER 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: nt!_IMAGE_DOS_HEADER 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: nt!_IMAGE_DOS_HEADER 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: nt!_IMAGE_DOS_HEADER 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: nt!_IMAGE_DOS_HEADER 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: nt!_EPROCESS 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: nt!_KPRCB 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: nt!_KPRCB 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: nt!_MI_SYSTEM_INFORMATION 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: nt!_MI_SYSTEM_INFORMATION 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: nt!_MMPTE 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: nt!_MMPTE 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: nt!_MMPTE 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: nt!_MMPTE 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: nt!_MMPTE 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: nt!_MMPTE 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: nt!_KPRCB 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: nt!_KPRCB KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 452 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 531 Key : Analysis.Init.CPU.mSec Value: 749 Key : Analysis.Init.Elapsed.mSec Value: 6886 Key : Analysis.Memory.CommitPeak.Mb Value: 48 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 FILE_IN_CAB: 010122-3593-01.dmp ADDITIONAL_DEBUG_TEXT: You can run '.symfix; .reload' to try to fix the symbol path and load symbols. WRONG_SYMBOLS_TIMESTAMP: 2f0a239f WRONG_SYMBOLS_SIZE: 1046000 FAULTING_MODULE: fffff8030aa00000 nt BUGCHECK_CODE: a BUGCHECK_P1: 8 BUGCHECK_P2: 2 BUGCHECK_P3: 1 BUGCHECK_P4: fffff8030ac42166 WRITE_ADDRESS: 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: nt!_MMPFN 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: nt!_MMPTE Unable to get size of nt!_MMPTE - probably bad symbols 0000000000000008 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: ffffb306694d5878 fffff8030ae09169 : 000000000000000a 0000000000000008 0000000000000002 0000000000000001 : nt+0x3f71b0 ffffb306694d5880 000000000000000a : 0000000000000008 0000000000000002 0000000000000001 fffff8030ac42166 : nt+0x409169 ffffb306694d5888 0000000000000008 : 0000000000000002 0000000000000001 fffff8030ac42166 0000000000000000 : 0xa ffffb306694d5890 0000000000000002 : 0000000000000001 fffff8030ac42166 0000000000000000 0000000000000000 : 0x8 ffffb306694d5898 0000000000000001 : fffff8030ac42166 0000000000000000 0000000000000000 0000000000000000 : 0x2 ffffb306694d58a0 fffff8030ac42166 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x1 ffffb306694d58a8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt+0x242166 CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt 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: nt!_MMPTE fffff8030ac42000 - nt+242000 [ 00:01 ] fffff8030ac42003-fffff8030ac42007 5 bytes - nt+242003 (+0x03) [ 00 00 00 00 00:48 81 f9 ff 03 ] fffff8030ac4200a-fffff8030ac4200d 4 bytes - nt+24200a (+0x07) [ 00 00 00 00:0f 87 82 01 ] fffff8030ac42010-fffff8030ac4201e 15 bytes - nt+242010 (+0x06) [ 00 00 00 00 00 00 00 00:48 ff 45 a0 48 8d 48 01 ] fffff8030ac42021-fffff8030ac4202b 11 bytes - nt+242021 (+0x11) [ 00 00 00 00 00 00 00 00:48 33 c8 49 89 0b 49 ff ] fffff8030ac42030-fffff8030ac42044 21 bytes - nt+242030 (+0x0f) [ 00 00 00 00 00 00 00 00:80 90 ff ff 48 83 c7 08 ] fffff8030ac42046 - nt+242046 (+0x16) [ 00:10 ] fffff8030ac42049-fffff8030ac42071 41 bytes - nt+242049 (+0x03) [ 00 00 00 00 00 00 00 00:49 b9 f8 17 32 64 c8 90 ] fffff8030ac42077-fffff8030ac4209b 37 bytes - nt+242077 (+0x2e) [ 00 00 00 00 00 00 00 00:94 ff ff 41 8b 44 24 18 ] fffff8030ac4209f-fffff8030ac420a1 3 bytes - nt+24209f (+0x28) [ 00 00 00:e8 4c 20 ] fffff8030ac420a4-fffff8030ac420b2 15 bytes - nt+2420a4 (+0x05) [ 00 00 00 00 00 00 00 00:49 8b d7 48 c1 ea 12 81 ] fffff8030ac420b6-fffff8030ac420bf 10 bytes - nt+2420b6 (+0x12) [ 00 00 00 00 00 00 00 00:40 c8 90 ff ff 48 03 d1 ] fffff8030ac420c1-fffff8030ac420d4 20 bytes - nt+2420c1 (+0x0b) [ 00 00 00 00 00 00 00 00:10 32 64 c8 90 ff ff 48 ] fffff8030ac420d7-fffff8030ac420ec 22 bytes - nt+2420d7 (+0x16) [ 00 00 00 00 00 00 00 00:48 8d 4c 24 50 48 89 5c ] fffff8030ac420ee-fffff8030ac420f8 11 bytes - nt+2420ee (+0x17) [ 00 00 00 00 00 00 00 00:48 c1 eb 0c 48 b8 ff ff ] fffff8030ac420fc-fffff8030ac42115 26 bytes - nt+2420fc (+0x0e) [ 00 00 00 00 00 00 00 00:48 23 d8 48 8d 1c 5b 48 ] fffff8030ac42118-fffff8030ac4211b 4 bytes - nt+242118 (+0x1c) [ 00 00 00 00:0f 84 3e 01 ] fffff8030ac4211e-fffff8030ac42120 3 bytes - nt+24211e (+0x06) [ 00 00 00:f6 87 b8 ] fffff8030ac42124-fffff8030ac42128 5 bytes - nt+242124 (+0x06) [ 00 00 00 00 00:07 0f 85 60 01 ] fffff8030ac4212b-fffff8030ac42148 30 bytes - nt+24212b (+0x07) [ 00 00 00 00 00 00 00 00:41 f6 44 24 18 01 48 8d ] fffff8030ac4214b-fffff8030ac42153 9 bytes - nt+24214b (+0x20) [ 00 00 00 00 00 00 00 00:48 8b c3 48 8b 9c 24 b8 ] fffff8030ac42156-fffff8030ac4215b 6 bytes - nt+242156 (+0x0b) [ 00 00 00 00 00 00:48 8b bc 24 c8 01 ] fffff8030ac4215e-fffff8030ac42163 6 bytes - nt+24215e (+0x08) [ 00 00 00 00 00 00:48 8b b4 24 c0 01 ] fffff8030ac42166-fffff8030ac42175 16 bytes - nt+242166 (+0x08) [ 00 00 00 00 00 00 00 00:4d 89 74 24 08 4d 89 74 ] fffff8030ac42178-fffff8030ac42182 11 bytes - nt+242178 (+0x12) [ 00 00 00 00 00 00 00 00:48 8b 4d 70 48 33 cc e8 ] fffff8030ac42184-fffff8030ac42188 5 bytes - nt+242184 (+0x0c) [ 00 00 00 00 00:48 81 c4 90 01 ] fffff8030ac4218b-fffff8030ac421a7 29 bytes - nt+24218b (+0x07) [ 00 00 00 00 00 00 00 00:41 5d 41 5c 5d c3 cc 45 ] fffff8030ac421a9 - nt+2421a9 (+0x1e) [ 00:0c ] fffff8030ac421ac-fffff8030ac421b3 8 bytes - nt+2421ac (+0x03) [ 00 00 00 00 00 00 00 00:75 1a 48 8b c8 48 8d 96 ] fffff8030ac421b5 - nt+2421b5 (+0x09) [ 00:10 ] fffff8030ac421b8-fffff8030ac421ba 3 bytes - nt+2421b8 (+0x03) [ 00 00 00:48 81 e1 ] fffff8030ac421bc-fffff8030ac421c6 11 bytes - nt+2421bc (+0x04) [ 00 00 00 00 00 00 00 00:f0 ff ff 48 3b ca 0f 84 ] fffff8030ac421c8-fffff8030ac421cf 8 bytes - nt+2421c8 (+0x0c) [ 00 00 00 00 00 00 00 00:44 3b 45 98 0f 83 e5 01 ] fffff8030ac421d2-fffff8030ac421d9 8 bytes - nt+2421d2 (+0x0a) [ 00 00 00 00 00 00 00 00:48 8d 43 ff 48 3d ff 03 ] fffff8030ac421dc-fffff8030ac421e0 5 bytes - nt+2421dc (+0x0a) [ 00 00 00 00 00:0f 87 19 55 1e ] fffff8030ac421e2-fffff8030ac421ee 13 bytes - nt+2421e2 (+0x06) [ 00 00 00 00 00 00 00 00:48 8b d3 48 8d 42 ff 49 ] fffff8030ac421f0-fffff8030ac421f5 6 bytes - nt+2421f0 (+0x0e) [ 00 00 00 00 00 00:f0 ff ff 25 ff 03 ] fffff8030ac421f8-fffff8030ac42226 47 bytes - nt+2421f8 (+0x08) [ 00 00 00 00 00 00 00 00:48 0b c1 48 2b da 48 8b ] fffff8030ac42229-fffff8030ac42243 27 bytes - nt+242229 (+0x31) [ 00 00 00 00 00 00 00 00:48 85 db 0f 84 f5 fd ff ] fffff8030ac42246-fffff8030ac42266 33 bytes - nt+242246 (+0x1d) [ 00 00 00 00 00 00 00 00:41 f6 c3 20 0f 84 d7 fd ] fffff8030ac42268-fffff8030ac4226d 6 bytes - nt+242268 (+0x22) [ 00 00 00 00 00 00:b1 08 66 0f 1f 44 ] fffff8030ac42270-fffff8030ac4227f 16 bytes - nt+242270 (+0x08) [ 00 00 00 00 00 00 00 00:80 c1 ff 0f b6 c1 8b 54 ] fffff8030ac42282-fffff8030ac422a9 40 bytes - nt+242282 (+0x12) [ 00 00 00 00 00 00 00 00:84 c9 75 ea e9 93 fe ff ] fffff8030ac422ab-fffff8030ac422b2 8 bytes - nt+2422ab (+0x29) [ 00 00 00 00 00 00 00 00:0f 86 7a fe ff ff 49 be ] fffff8030ac422b7-fffff8030ac422bd 7 bytes - nt+2422b7 (+0x0c) [ 00 00 00 00 00 00 00:ff ff ff ff 0f 1f 44 ] fffff8030ac422c0-fffff8030ac422d3 20 bytes - nt+2422c0 (+0x09) [ 00 00 00 00 00 00 00 00:48 8b 4c 24 30 4c 8d 4c ] fffff8030ac422d5-fffff8030ac422e7 19 bytes - nt+2422d5 (+0x15) [ 00 00 00 00 00 00 00 00:41 8b 44 24 18 a8 04 74 ] fffff8030ac422ec-fffff8030ac422ef 4 bytes - nt+2422ec (+0x17) [ 00 00 00 00:e8 ff 44 07 ] fffff8030ac422f1-fffff8030ac42304 20 bytes - nt+2422f1 (+0x05) [ 00 00 00 00 00 00 00 00:48 8b 5c 24 38 49 8b cd ] fffff8030ac42306-fffff8030ac42308 3 bytes - nt+242306 (+0x15) [ 00 00 00:49 89 5d ] WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output. 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: nt!_MMPTE 6935 errors : !nt (fffff8030ac42000-fffff8030adf7fff) MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption MEMORY_CORRUPTOR: LARGE STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c} Followup: memory_corruption ---------

 

[Colif]

thats a nice wall of text you have there, can you

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

A friend of mine has a program that can convert dumps into a format I can read easier than above

Are you on latest bios on Motherboard?

 

[Rstipton]

Glad you like my text wall. 😛
Here is the link to a folder with 3 mini dumps in it.
Dump folder
Couple more things... Safe mode works ok for the most part. Regular user mode will crash within just a couple minutes. I also ran 2 different rootkit cleaners but they found nothing. Tried installing Linux on the extra drive I have and it runs fine with no errors that I could see. Thank you so much for you help.

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/xnfe8kzg/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	010122-13609-01.dmp (Jan 2 2022 - 01:49:19)
Bugcheck:	DRIVER_VERIFIER_DETECTED_VIOLATION (C4)
Probably caused by:	memory_corruption (Process: SearchApp.exe)
Uptime:	0 Day(s), 0 Hour(s), 09 Min(s), and 42 Sec(s)

File information:	010122-10265-01.dmp (Jan 2 2022 - 01:17:37)
Bugcheck:	PFN_LIST_CORRUPT (4E)
Probably caused by:	memory_corruption (Process: svchost.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 16 Sec(s)

File information:	010122-10031-01.dmp (Jan 2 2022 - 01:32:01)
Bugcheck:	MEMORY_MANAGEMENT (1A)
Probably caused by:	memory_corruption (Process: wermgr.exe)
Uptime:	0 Day(s), 0 Hour(s), 02 Min(s), and 29 Sec(s)

Possible Motherboard page: https://www.msi.com/Motherboard/B550-A-PRO
You already have the latest BIOS installed.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Rstipton]

Thanks so much. I have a couple more dumps if you need them. I retired as a school tech facilitator and while I couldn't always fix devices I rarely ran into something that I didn't at least have a clue as to the problem. This one has my mind blown although I am leaning toward a motherboard issue.

 

[Colif]

so all the victims are strange things to crash
SearchApp.exe = Windows search
wermge.exe = Windows Error Management
svhost is more normal... service host. doesn't tell me anything.

how many drivers you managed to install? I think its hardware and I wish there were tests for the motherboard besides

1. Use another one (best done by repair store so you don't waste money buying something that doesn't fix it)
2. test everything else and assume (I would go with 1 unless you sure)

no drivers mentioned in dump text, as usual. BSOD with very few drivers installed could be caused from lack of drivers.

ram - passes memtest
CPU - passes stress test (Prime also tests ram so its a 2nd look)
tried different drives
tried different GPU

checked pins on CPU?
What make/model PSU?