SpyderTracks
We love you Ukraine
Sincere apologies, I saw a notice about this yesterday and got totally sidetracked.I asked about the external drives only because there is a host of "disk n has been surprise removed" warnings, indicating that a USB drive was removed before it was ready. You risk data loss doing this. You should either disable write caching on your USB device(s) or use the "safely remove hardware" system tray icon.
I think your son has a hardware problem. The System log runs from 16th July to 13th Nov (but the application log only runs from 11th Nov to 12th Nov - I wonder why?). In all that time (in the System log) there have been only two BSODs, the two you uploaded dumps for. I can see a whole host of critical error 41 messages indicating that Windows restarted without properly shutting down. These will be the "switching off" that your son complains about.
There don't appear to be any common problems that could account for all these error 41 messages, which strongly suggests a hardware failure. This is supported by several WHEA logger messages (WHEA is the Windows Hardware Error Architecture) reporting a hardware failure. Here's the most recent...
Rich (BB code):Log Name: System Source: Microsoft-Windows-WHEA-Logger Date: 30/10/2022 17:15:30 Event ID: 18 Task Category: None Level: Error Keywords: User: LOCAL SERVICE Computer: The-Beast Description: A fatal hardware error has occurred. Reported by component: Processor Core Error Source: Machine Check Exception Error Type: Cache Hierarchy Error Processor APIC ID: 6 The details view of this entry contains further information.
The reason I suspect, why we don't see WHEA messages for every switch off is because the hardware error crashed the PC before WHEA could log the error.
The highlighted error reason of "cache hierarchy error" is a CPU detected error, as shown by the "processor core" as the reported by component. I don't think this is a CPU error however, I think this is a RAM error. Flaky RAM might explain the sudden switch off, but the problem might also be a PSU issue.
I'm no hardware expert so I'm going to flag @SpyderTracks (who is a hardware expert) and ask him whether that 650W PSU is big enough to drive the CPU/GPU hard in a demanding game like FlightSim. If he thinks the PSU is man enough for the job then I think we need to look at RAM.
We could run Memtest86 on your RAM, but I'm going to suggest you don't do that for a couple of reasons. The first is that to run two sets of 4 iterations of the tests would take many hours on your 64GB of RAM and I doubt your son would want to be without it for that long[!]. The second reason is that even Memtest86 cannot definitively prove that your RAM is good, it's just the best testing tool available.
A better, and 100% reliable, way of testing for bad RAM is to remove one of your RAM sticks and run on the remaining 3 for a few days. 48GB should be more than enough RAM, although you might see the odd paging slowdown if the system does page RAM, but I think that unlikely.
If you still see this sudden switching off then put that RAM stick back and remove one of the others.
Keep swapping RAM sticks until you have either tried will all four out at some point and you still get switching off (in which case it's not RAM), or until it's stable with only 3 sticks - and the one that's out is the flaky one.
The 5700XT and 3800x would normally dictate a minimum PSU of around 600W with recommended of 700W, so it's really on the margins.
There is an outlier case with modern GPUs called Transient Spikes where they can require huge instant demands of around double the GPU TDP, the 5700XT's being around 225W so that would be a spike of around 550W JUST ON THE GPU, not factoring in the rest of the build.
But also, a very important factor is that it is MSFS which is probably the largest system load of any game on the planet and will max out the full system quite happily.
I would say PSU could well be a factor on such a demanding load like MSFS