My platform: i7 13700k, MSI Tomahawk Z790. RTX 4080, 2 x 16G 5600 Corsair, NZXT Z73 AI cooler.
I think I have the same problem, but it may have mutated a little. No solution as yet. I've got as far as suspecting drivers and mostly ruling out hardware. Everything said on this forum reinforces that. Too many hardware permutations. Even happening in Win10.
Problem mutated a little. Originally lots of nvidia issues, still get some, but mostly resolved by reinstalling windows, re-seating 4080 and adjusting the stand (can't use supplied bracket on case).
Now normally crashes a few minutes after booting the system, frequently at idle when I'm reviewing the event log. Then an error in the log saying that the system had not shutdown properly. But timing indicates that it appears to have crashed during the previous boot where it was unable to write dump file. Oddly during this the Windows Spotlight cache gets corrupted, so I login from the default screen.
Memory checked (memtest86). CPU under load fine (cinebench) and gaming for hours. But crashes at idle after boot. If it survives 10 mins, its probably OK . BIOS and GPU flashed. All drivers up to date. Clean Win 11 install, shutdown and boot every time. Still crashing, but a little more stable.
Initially, had to sort out fans and the LED light show. Ended up installing MSI command center, NZXT Cam and iCue (1GB seriously). When problems started, assumed just too much contention. Flashed BIOS for a second time. Cleaned disk. Install Windows 11. Seemed fine. Intended to build gradually. Win 11 decided licence no longer active after BIOS upgrade. Annoyed by pestering. Contacted helpdesk. Activated Windows. Everything working. Fixed!!!
Next day issue returned. Maybe coincidence. MS Store proactively pushed updates. Started getting issues again. Disabled Intel Command Center. Seems a little more stable, but suspect it is not the root cause. The system is very fragile. Now mostly OK, but installed Gigabyte tool to underclock GPU which decides to start on boot, and PC becomes unstable.
The number of people, and platforms that are experiencing a very similar issues, suggest that this is not directly hardware related, but driver / windows related. Still investigating.