Question Random Blue Screen and Reboot On New Build

[mkcsit]

Hello,

I purchased parts to build a computer with my son back in March. Here is the build list:

LIANLI 205 MESH TG RGB ATX BLACK
MSI PRO Z690-A WIFI ATX D4
INTEL INTEL I5-12600K BOXIPSG 2TB PREMIUM QLC SATA SSD
SAMSUNG E 1TB 970EVO+NVME M.2 SSD
G.SKILL 32G 2X16 D4 3200 CL16 RJ
COOLMAST HYPER 212 RGB BLK COOL V2
EVGA 850 GT 80+G FM ATX PSU
ASUS DUAL RTX3060 V2 OC
INTEL INTEL I5-12600K BOX
MICROSOFT WIN PRO FPP USB FLASH

About a week after putting it together and installing Windows 11, the PC would randomly reboot showing a blue screen before shutting down that shows Stop code: WHEA Uncorrectable Error. There does not seem to be a pattern to pinpoint when this will happen. Sometimes it will run a week with no issues. It happens randomly while playing a game, surfing the net, or just browsing through Windows Explorer. When it happens I notice that everything on the screen freezes for a second or two (can't move mouse) and then the blue screen flashes followed by reboot. The Windows system logs only show a generic error that basically says Windows crashed and is not very helpful. Sometimes the PC will boot to the login screen after restarting but sometimes it will restart multiple times in a row and go to the recovery screen. All the latest drivers have been installed or reinstalled. Some of the steps I’ve taken to this point include:

1. Reinstalled Windows 11
2. Uninstalled and clean install of Nvidia drivers
3. Wiped M2 and installed Windows 10 instead
4. Removed GPU and used onboard (still randomly crashed)
5. Remove one memory stick at a time (still crashed)
6. Try each memory chip in the first slot (still crashed)

I'm down to this being the motherboard, the CPU, or a driver still. I’m attaching the Windows crash mini dump file. This seems like a driver issue to me and the dump file even seems to indicate that but I’m not sure which one. Any help would be appreciated. All parts are under warranty and I can go back to where I purchased them but I really want to try to understand what the heck is happening here.


Mini Crash Dump:

Microsoft (R) Windows Debugger Version 10.0.22621.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff80653a07000 PsLoadedModuleList = 0xfffff80654631290
Debug session time: Mon Sep 19 19:11:19.031 2022 (UTC - 4:00)
System Uptime: 0 days 0:51:26.667
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
..............................
For analysis of this file, run !analyze -v
12: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, BugChecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: ffffd883088e33c8, name of the driver having the issue.
Arg3: ffffd883226d0950, verifier internal structure with driver information.
Arg4: 000000000000046e, total # of (paged+nonpaged) allocations that weren't freed.
Type !verifier 3 drivername.sys for info on the allocations
that were leaked that caused the bugcheck.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 6614

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

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

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


FILE_IN_CAB: 091922-18750-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: c4

BUGCHECK_P1: 62

BUGCHECK_P2: ffffd883088e33c8

BUGCHECK_P3: ffffd883226d0950

BUGCHECK_P4: 46e

IMAGE_NAME: SYMEFASI64.SYS

MODULE_NAME: SYMEFASI64

FAULTING_MODULE: fffff806afb90000 SYMEFASI64

VERIFIER_DRIVER_ENTRY: dt nt!_MI_VERIFIER_DRIVER_ENTRY ffffd883226d0950
Symbol nt!_MI_VERIFIER_DRIVER_ENTRY not found.

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: services.exe

STACK_TEXT:
ffff8185eeb571b8 fffff806543d5e24 : 00000000000000c4 0000000000000062 ffffd883088e33c8 ffffd883226d0950 : nt!KeBugCheckEx
ffff8185eeb571c0 fffff806543e5159 : ffffd883226d0950 ffff8185eeb572b0 ffffd883088e3240 ffffd8835e69e820 : nt!VerifierBugCheckIfAppropriate+0xe0
ffff8185eeb57200 fffff80653e92e24 : ffffd883226d0950 ffffd883088e32e0 0000000000000001 ffffd8835e69e800 : nt!VfPoolCheckForLeaks+0x49
ffff8185eeb57240 fffff806543c74f2 : 0000000000203000 ffffd883088e3240 fffff80654623c00 fffff80654623c00 : nt!VfTargetDriversRemove+0x11afd8
ffff8185eeb572c0 fffff806540c672b : ffffd883088e3240 ffff8185eeb573f0 0000000000000001 00000000ffffffff : nt!VfDriverUnloadImage+0x3e
ffff8185eeb572f0 fffff8065416ab31 : 0000000000000000 00000000ffffffff fffff09500000001 ffff8f846e5b1f40 : nt!MiUnloadSystemImage+0x2eb
ffff8185eeb57490 fffff8065416aa5e : ffffd8831cdcaa60 ffff8185eeb577c0 0000000000000000 ffff8185eeb57930 : nt!MmUnloadSystemImage+0x41
ffff8185eeb574c0 fffff806540190d0 : ffffd8831cdcaa60 ffff8185eeb577c0 ffffd8831cdcaa60 fffff806540992ff : nt!IopDeleteDriver+0x4e
ffff8185eeb57510 fffff80653c15c07 : 0000000000000000 0000000000000000 ffff8185eeb577c0 ffffd8831cdcaa90 : nt!ObpRemoveObjectRoutine+0x80
ffff8185eeb57570 fffff80653c15b2e : ffffd8831cdcaa90 ffff8185eeb57930 ffffd8831cdcaa60 00000000000a0000 : nt!ObfDereferenceObjectWithTag+0xc7
ffff8185eeb575b0 fffff80654163cf4 : ffffd8831cdcaa90 ffff8185eeb577c0 ffff8185eeb57930 00000000c0000001 : nt!HalPutDmaAdapter+0xe
ffff8185eeb575e0 fffff8065429fc9b : ffffd88315049080 0000000000000000 ffff8f8565738f01 ffffd8831cdcaa90 : nt!IopUnloadDriver+0x250
ffff8185eeb57710 fffff80653e119b5 : ffffd88315049080 ffff8185eeb577c0 0000006c4bb7e580 ffff8185eeb577d0 : nt!NtUnloadDriver+0xb
ffff8185eeb57740 fffff80653e03e30 : fffff80654247634 ffffd88315049080 0000006c4bb7e4a8 0000006c4bb7e4f9 : nt!KiSystemServiceCopyEnd+0x25
ffff8185eeb578d8 fffff80654247634 : ffffd88315049080 0000006c4bb7e4a8 0000006c4bb7e4f9 fffff8065429fc90 : nt!KiServiceLinkage
ffff8185eeb578e0 fffff8065429fc9b : ffffd88315049080 0000000000050246 ffff8185eeb57a00 0000000000000018 : nt!IopUnloadDriver+0xe3b90
ffff8185eeb57a10 fffff80653e119b5 : ffffd88315049000 ffffd882fa1d1aa0 ffff8185eeb57ac0 0000000000000000 : nt!NtUnloadDriver+0xb
ffff8185eeb57a40 00007ffb504708b4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
0000006c4bb7e558 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffb`504708b4


STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0xc4_62_LEAKED_POOL_IMAGE_SYMEFASI64.SYS

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {bd777d82-c1b7-071a-f998-319d64c05b94}

Followup: MachineOwner



Thank You

 

[Colif]

SYMEFASI64.SYS

Do you have Norton Antivirus as that is a file from it
https://www.sysnative.com/forums/drivers/4297/driver

try updating or removing Norton

 

[mkcsit]

I do have norton antivirus installed. I will remove that and update after. Thank you for the response.

 

[mkcsit]

Uninstalling Norton did not work. I even removed all registry entries for Norton. Now, it only boots to the BIOS.

 

[Colif]

Removing Norton shouldn't have left you unable to boot so clearly that isn't cause.

I only looked at your report, I didn't see this before

WHEA Uncorrectable Error.

That can be drivers but it is often a Hardware Error. WHEA - Windows Hardware Error Architecture
Its an error called by CPU but not necessarily caused by it, can be any hardware
can be caused by heat
can be caused by overclocking so remove any you have
can be fixed by updating BIOS - https://www.msi.com/Motherboard/PRO-Z690-A-WIFI-DDR4/support
sometimes it is drivers but normally for devices such as storage drives, for example.

Were you getting a dump for each crash? or just some of them?
is the m.2 still showing in bios?

You could run this to check CPU, will also check RAM while its at it.
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

 

[mkcsit]

I went through the registry and removed all things Norton and I think that screwed things up more. So, I did a complete reinstall with Windows 11 with all hardware installed back in the pc. I installed all drivers with chipset first and the latest Nvidia driver for this card. I did not install Norton. It's been one day without any blue screen reboots but there are some interesting things to note since the reinstall. When we ran Fortnite after downloading it there was a prompt to install Easy Anti Cheat. When we clicked Yes it began installing but then the PC rebooted (no blue screen). When I clicked Fortnite again after reboot the Easy Anti Cheat screen came up with a button to Repair Service. So, something went wrong with the install. Clicked Repair Service and it started working fine after that. I wonder if this might have had an issue with Norton. I noticed posts all over the web mentioning issues with this service. Something else that happened separately last night is while playing a game the screen suddenly went black. There were some green dashed lines that appeared on the screen but that was it. After rebooting the screen came back fine. The error log showed Error 1000 and the source of a critical failure at that time was dwm.exe. I have not made any changes yet and am waiting to see if this issue and the error returns.

So, in short, I may have been having multiple issues with this build both hardware and software. I will continue to update but any thoughts or suggestions in the meantime would be welcome and appreciated. Thanks

 

[Colif]

dwm.exe - Windows Desktop Manager
I think there were new drivers for Nvidia released today, could try them,

 

[mkcsit]

The blue screens returned yesterday while playing a game. After it restarted it went through a blue screen loop several times until we shut it down. I booted pc after it had been sitting for a bit and got tot he Windows 11 login screen. I logged in and after about a minute the screen locked up and blue screen happened. It went through a few restarts and eventually landed on another blue screen that said boot volume unmountable. I shut it down waited a minute and powered it back on. I again got o the login screen and was able to log in and retrieve the dump file which pointed to the Nvidia driver. I'm not convinced this is the root cause because I had the card removed for a week and continued to get blue screens with the WHEA Uncorrectable Error message. I was going to uninstall/install the latest driver you mentioned above but I simply could not boot the machine to the OS. It would either blue screen at boot or shortly after logging in. I even tried to get to Safe Mode and it just hung at the screen that lets you choose the Safe Mode option. I then tried a clean install of Windows 11. I wiped the drive and performed secure erase from the Bios. When trying to install Windows 11 this time it would install to about90%, reboot, but then throw an error that Windows installer failed. I clicked OK, the computer would reboot and go back to this same message. I couldn't even get to BIOS so I shut it down, unplugged it. Powered it back on after a few minutes and was able to enter BIOS. I tried reinstalling Windows again but got the same error and now this is all it does. It's one issue after another with this thing and I'm to the point of bringing it back where I got all the parts and making them figure it out. I just cant put any more time into this. At one point, as I stated above, I only had one memory stick in and it was still blue screening. So, I'm convinced it's either, memory, CPU, or board.

Something else to note. I previously brought it back to where I bought the parts and had them run a diagnostic on it. It came back clean with no issues. I'm not sure what that means if anything. The issue continued a week after I brought it home. Something is wrong with this build and when I think I'm close to solving it something else goes wrong. It may even be a power issue. Either way all parts are under warranty and I even purchased additional warranty coverage for cpu and gpu so I'm hoping I can get his resolved. I've spent a lot of time around computers and never run into anything close to this.

Thank you for your feedback. Here is the latest dump file I was able to get if interested:


Microsoft (R) Windows Debugger Version 10.0.22621.1 X86

Copyright (c) Microsoft Corporation. All rights reserved.





Loading Dump File [E:\Software And Scripts\Jack PC Win Dump\Dump File 9-27\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



Dump completed successfully, progress percentage: 100



Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22000 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 22000.1.amd64fre.co_release.210604-1628

Machine Name:

Kernel base = 0xfffff8040c600000 PsLoadedModuleList = 0xfffff8040d229770

Debug session time: Mon Sep 26 20:52:17.754 2022 (UTC - 4:00)

System Uptime: 0 days 4:31:37.358

Loading Kernel Symbols

...............................................................

................................................................

...............................................................

Loading User Symbols



Loading unloaded module list

.....................

For analysis of this file, run !analyze -v

2: kd> !analyze -v

***

* *

* Bugcheck Analysis *

* *

***



PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except.

Typically the address is just plain bad or it is pointing at freed memory.

Arguments:

Arg1: ffffbc813acba000, memory referenced.

Arg2: 0000000000000002, value 0 = read operation, 1 = write operation.

Arg3: fffff8042cfab706, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000000, (reserved)



Debugging Details:

------------------



Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_47917a79b8c7fd22\nvlddmkm.sys, Win32 error 0n2



KEY_VALUES_STRING: 1



Key : AV.Type

Value: Write



Key : Analysis.CPU.mSec

Value: 8640



Key : Analysis.DebugAnalysisManager

Value: Create



Key : Analysis.Elapsed.mSec

Value: 15063



Key : Analysis.Init.CPU.mSec

Value: 4108



Key : Analysis.Init.Elapsed.mSec

Value: 201131



Key : Analysis.Memory.CommitPeak.Mb

Value: 96



Key : WER.OS.Branch

Value: co_release



Key : WER.OS.Timestamp

Value: 2021-06-04T16:28:00Z



Key : WER.OS.Version

Value: 10.0.22000.1





FILE_IN_CAB: MEMORY.DMP



DUMP_FILE_ATTRIBUTES: 0x1000



BUGCHECK_CODE: 50



BUGCHECK_P1: ffffbc813acba000



BUGCHECK_P2: 2



BUGCHECK_P3: fffff8042cfab706



BUGCHECK_P4: 0



READ_ADDRESS: ffffbc813acba000



MM_INTERNAL_CODE: 0



IMAGE_NAME: nvlddmkm.sys



MODULE_NAME: nvlddmkm



FAULTING_MODULE: fffff8042c7b0000 nvlddmkm



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXNTFS: 1 (!blackboxntfs)





BLACKBOXPNP: 1 (!blackboxpnp)





BLACKBOXWINLOGON: 1



PROCESS_NAME: System



TRAP_FRAME: ffffba856c7d6ff0 -- (.trap 0xffffba856c7d6ff0)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=ffffbc813acb8000 rbx=0000000000000000 rcx=0000000000000800

rdx=000000004c3c007f rsi=0000000000000000 rdi=0000000000000000

rip=fffff8042cfab706 rsp=ffffba856c7d7180 rbp=0000000000000000

r8=00000000ffffffdc r9=000000004b9c007e r10=ffffd1085fe30858

r11=ffffba856c7d71c0 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl zr na po nc

nvlddmkm+0x7fb706:

fffff8042cfab706 893488 mov dword ptr [rax+rcx*4],esi ds:ffffbc813acba000=????????

Resetting default scope



STACK_TEXT:

ffffba856c7d6d48 fffff8040caa35d1 : 0000000000000050 ffffbc813acba000 0000000000000002 ffffba856c7d6ff0 : nt!KeBugCheckEx

ffffba856c7d6d50 fffff8040c866626 : 0000000000000005 0000000000000002 ffffba856c7d6f50 0000000000000000 : nt!MiSystemFault+0x1b44f1

ffffba856c7d6e50 fffff8040ca298f5 : fffff8042167ebb2 0000000000000001 0000000000000000 0000000000000000 : nt!MmAccessFault+0x2a6

ffffba856c7d6ff0 fffff8042cfab706 : 0000000000000064 00000000000f0028 fffff8042cfdcf69 fffff8042c7c0100 : nt!KiPageFault+0x335

ffffba856c7d7180 fffff8042d3f969f : ffffd1085fe02000 ffffd1085fe02000 000000000000007f 0000000000000006 : nvlddmkm+0x7fb706

ffffba856c7d71d0 fffff8042c7c3629 : ffffd1085fe02000 ffffba856c7d72a9 ffffd1085a1e3000 0000000000000000 : nvlddmkm+0xc4969f

ffffba856c7d7200 fffff8042d3462d0 : 0000000000000001 ffffba856c7d72a9 ffffd1085a1e3000 ffffba856c7d1000 : nvlddmkm+0x13629

ffffba856c7d7240 fffff8042d34ed2e : 0000000000000000 0000000000000005 0000000000000001 ffffd1085a1e3000 : nvlddmkm+0xb962d0

ffffba856c7d7310 fffff8042d623886 : 0000000000000001 0000000000000005 ffffd10859202000 0000000000000001 : nvlddmkm+0xb9ed2e

ffffba856c7d7390 fffff8042d6230a7 : 0000000000000000 0000000000000000 0000000000000000 a58d80b900000002 : nvlddmkm+0xe73886

ffffba856c7d7460 fffff8042d64e4a6 : ffffd10859202000 ffffba856c7d75d0 0000000000000001 0000000000000007 : nvlddmkm+0xe730a7

ffffba856c7d74c0 fffff8042d6615f1 : fffff8042d64e34f 0000000000000001 0000000000000002 00000000ffffffff : nvlddmkm+0xe9e4a6

ffffba856c7d7600 fffff8042167ebb2 : 0a0111531e4c3800 1200202020202020 ffff606ed0551fd9 0000000100000800 : nvlddmkm+0xeb15f1

ffffba856c7d7640 fffff8042167e44e : 0000000000000080 ffffba856c7d7701 0000000000000000 fffff80400000000 : dxgkrnl!DpiDxgkDdiSetPowerState+0x5a

ffffba856c7d76a0 fffff8042167f02a : ffffd1086beb1010 0000000000000000 0000000000000001 0000000000000000 : dxgkrnl!DpiFdoSetAdapterPowerState+0x17a

ffffba856c7d7760 fffff8042167e6c1 : ffffd10859192030 ffffd10859116600 ffffd108554bbd30 ffffd1086beb1000 : dxgkrnl!DpiFdoHandleDevicePower+0x2ea

ffffba856c7d7800 fffff80421680031 : ffffd1086beb1010 ffffd10859192180 ffffd10859192030 0000000000000000 : dxgkrnl!DpiFdoDispatchPower+0x21

ffffba856c7d7830 fffff8042d65e3f0 : 0000000000000000 ffffba856c7d79f9 0000000000000000 ffffd10859202000 : dxgkrnl!DpiDispatchPower+0xe1

ffffba856c7d7950 fffff8042d65d7ee : ffffd10859192030 ffffd10859202000 ffffd1086614c040 ffffd10800000000 : nvlddmkm+0xeae3f0

ffffba856c7d7a60 fffff8040c9aec87 : ffffd1086614c040 ffffba856c7d7b10 0000000000000000 0000000000000000 : nvlddmkm+0xead7ee

ffffba856c7d7a90 fffff8040c964995 : fffffffffa0a1f00 fffff8040c9aea80 ffffd108619e5ed0 0000000000000148 : nt!PopIrpWorker+0x207

ffffba856c7d7b30 fffff8040ca1ed74 : ffffbc8137640180 ffffd1086614c040 fffff8040c964940 0000000000000000 : nt!PspSystemThreadStartup+0x55

ffffba856c7d7b80 0000000000000000 : ffffba856c7d8000 ffffba856c7d1000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34





SYMBOL_NAME: nvlddmkm+7fb706



STACK_COMMAND: .cxr; .ecxr ; kb



BUCKET_ID_FUNC_OFFSET: 7fb706



FAILURE_BUCKET_ID: AV_W_(null)_nvlddmkm!unknown_function



OS_VERSION: 10.0.22000.1



BUILDLAB_STR: co_release



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



FAILURE_ID_HASH: {838100fa-f28b-2ef7-d702-e31713cb338c}



Followup: MachineOwner

---------

 

[Colif]

I'm convinced it's either, memory, CPU, or board.

its always possible but

ffffba856c7d7180 fffff8042d3f969f : ffffd1085fe02000 ffffd1085fe02000 000000000000007f 0000000000000006 : nvlddmkm+0x7fb706

that ones blaming Nvidia

If you want to check other things, thats fine.

LIANLI 205 MESH TG RGB ATX BLACK
MSI PRO Z690-A WIFI ATX D4
INTEL INTEL I5-12600K BOXIPSG 2TB PREMIUM QLC SATA SSD
SAMSUNG E 1TB 970EVO+NVME M.2 SSD
G.SKILL 32G 2X16 D4 3200 CL16 RJ
COOLMAST HYPER 212 RGB BLK COOL V2
EVGA 850 GT 80+G FM ATX PSU
ASUS DUAL RTX3060 V2 OC
INTEL INTEL I5-12600K BOX
MICROSOFT WIN PRO FPP USB FLASH

CPU - Run this - https://www.intel.com/content/www/us/en/download/15951/19792/intel-processor-diagnostic-tool.html?
RAM = 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
Motherboard... alas, no tests. You test everything else first and once you sure it all works, its a process of elimination and last thing should be Motherboard.
Did I ask if you have latest BIOS as they can help with WHEA errors.

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

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 . . .

just so i can look at dumps instead as they can show more.

 

[mkcsit]

Hello,

Thank you Colif for your replies. They were much appreciated. I wanted to take a moment and follow up on this thread to potentially help someone else who might be banging their head against the wall. The issue turned out to be a bad power supply. I didn't really consider that to be a factor because it would run for long periods of time without any issues. In short, I brought it back to the retailer we purchased the parts from and had them stress test the hardware. At first, they came back and said everything was fine. Their tests only covered a short time. I had them continue testing over a couple of days and within the second day the PSU failed. I got it replaced from EVGA under warranty. They actually sent the Titanium version of the 850 model (not sure if that means they are aware of an issues with the one I had or not). I've had it in the machine now for just over two weeks and it's been running everything without issues. So, that was definitely it. There wasn't anything that ever really pointed to the power supply as the issue. I was convinced, after getting dump files, that it was one of the other components. The dump file never points to the PSU, only the last thing Windows was trying to do before it crashed.

I have seen one minor issue. If my son is playing a game, pauses it, and comes back after say 30 minutes, the machine restarts. It almost seems like the power supply doesn't like the load transients from the cpu after being idle. I will check the Windows power settings and also check to see if there's a related setting in BIOS to prevent this.

 

[Colif]

The dump file never points to the PSU, only the last thing Windows was trying to do before it crashed.

Windows can't tell if its the PSU. There isn't any direct link between windows and the power supply. Unless you have specific power supplies, most of them don't tell the PC what is going on inside them. Only thing a motherboard records off the PSU is voltages. Only way to figure out if its PSU is to test the PSU.

LIANLI 205 MESH TG RGB ATX BLACK
MSI PRO Z690-A WIFI ATX D4
INTEL INTEL I5-12600K BOXIPSG 2TB PREMIUM QLC SATA SSD

I have seen one minor issue. If my son is playing a game, pauses it, and comes back after say 30 minutes, the machine restarts. It almost seems like the power supply doesn't like the load transients from the cpu after being idle. I will check the Windows power settings and also check to see if there's a related setting in BIOS to prevent this.

I am not aware of a fault like that for Intel systems. I know it can occur on older PSU that don't like how AMD Ryzen systems behave at idle but I haven't heard of it happening in Intel systems

What model PSU is it now? EVGA Titanium 850? this one? https://www.evga.com/products/product.aspx?pn=220-T2-0850-X1
I wouldn't expect a Titanium PSU to have a problem with transient loads.

ASUS DUAL RTX3060 V2 OC

especially since its not a high level card.

 

[mkcsit]

The new PSU is the one you sent in the link.

Some more detail: The two times this happened it was the same game left paused for more than 30 minutes. I did not witness it either time but he said he turned the monitor back on and as soon as he moved the mouse the pc restarted. I have not been able to replicate this issue since. I left the pc on all night last night to see what would happen. Turned the monitor on this morning and no issues. So, this may be nothing. I figured it was worth mentioning with all the other weirdness we've experienced over the last several months. Overall, it's been stable with this new pc.

 

[mkcsit]

Just following up on this post for anyone experiencing similar issues. This was in fact the PSU. Haven't had any issues since the last post.