I just had a screen freeze.  Had to hold the power button again.
 
Event Viewer
Critical -
Event ID, 41 - Kernel-Power - System
Error -
Event ID, 2 - Kernel-EventTracing - Microsoft-Windows-Kernel_EventTracing/Admin - 1
Event ID, 161 - volmgr - System - 2
Event ID, 1001 - BugCheck - System - 1
Event ID, 6008 - EventLog - System - 1
Event ID, 10010 - DistributedCOM - System - 1
Warning -
Event ID, 17 - i8042prt - System - 1
Event ID, 27 - e2fnexpress - System - 4
Event ID, 37 - Kernel-Processor-Power (Microsoft-Windows-Kernel-Processor-Power) System - 4
Event ID, 63 - WMI - System - 3
Event ID, 200 - DeviceSetupManager - Microsoft-Windows-DeviceSetupManager/Admin - 1
Event ID, 201 - DeviceSetupManager - Microsoft-Windows-DeviceSetupManager/Admin - 1
Event ID, 202 - DeviceSetupManager - Microsoft-Windows-DeviceSetupManager/Admin - 3
Event ID, 360 - User Device Registration - Microsoft-Windows-User-Device Registration/Admin - 1
Event ID, 1014 - DNS Client Events (Microsoft-Windows-DNS-Client) - System - 1
Event ID, 10016 - DistributedCOM - System - 11
 
This was from the "Last Hour" column.
 
No blue screens.
 
hwinfo is not set to start up when I turn the PC on.

I agree with rjohnson11, as that's a good approach to get some more info.
 
As for the codes you posted, that last hour column in the view you're in is a nice summary, but doesn't give all the details. you can double click on those and get a little bit more info about what they are or what they mean. The ones you care about in this case are in the system log and there they are kept in order of time, so you can more easily look at the log of time-stamps and figure out which ones happened right before it crashed. You get to those by clicking on "Windows Logs" folder on the left, then "System".
Looking at your codes, I found this one interesting:
 
Event ID, 37 - Kernel-Processor-Power (Microsoft-Windows-Kernel-Processor-Power) System - 4
^I'd be curious what it said if you double clicked on that. Microsoft defines it: "Event ID 37 is logged when the hardware platform determines that the OS can't use some frequency range that the processor supports. This Warning event notifies the user that the processor or CPU core can't support running at full speed." So that almost seems to indicate there's some issue with the frequency the CPU is trying to run at. 
 
I can't tell from this view what happened first.
 
The other thing that may or may not be helpful is that it ran a bugcheck in relation to this set of events (could have been checking for actual issue, could just be investigating why the power suddenly went away (you pressing the button)). It saves those in C:\Windows folder, but you'd have to double click on that event to see the specific locaiton with a report ID, which may be the most recent one. I'm not sure if there'll be anything useful there, but sometimes you can follow the rabbit hole actually find a rabbit lol. That said, you need to use a debug tool to look at those files, so posting what rjohnson had suggested is likely easier to do.
 

Here is more info from the Event Viewer.  They go back in time as you read down the list.  These were the Warnings/Error/Critical messages from last night:
 
Several were similar to this, occurring at different times in the evening.   They were "DistributedCOM" source:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-O9FHL7U\***** ***** SID (S-1-5-21-1011883860-3519979277-506640619-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
 
This was an Error...another "DistributedCOM" 8:50pm
The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout.
 
Here is a DNS Client Event (Microsoft-Windows-DNS-Client) 8:49pm:
Name resolution for the name clientconfig.akamai.steamstatic.com timed out after none of the configured DNS servers responded. Client PID 4312.
 
Here are the four Kernel_Processor_Power logs, all at 8:49pm
- The speed of processor 16 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
- The speed of processor 17 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
- The speed of processor 18 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
- The speed of processor 19 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
 
Six warnings for "e2fnexpress" starting from 4:52pm - 10:46pm yesterday:
Intel(R) Ethernet Controller (3) I225-V
Network link is disconnected.
 
Here was probably one of the rebooting I had.   It was under "BugCheck" 8:48pm
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff80740505330, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: becc7b07-c72b-46b0-a4c5-525caecb009a.
 
Here's a warning for "i8042prt"  8:48pm
The device sent an incorrect response(s) following a keyboard reset.
 
A couple of Error messages for "volmgr  8:48pm
Dump file creation failed due to error during dump creation.
 
A Critical for Kernel-Power  8:48pm
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
 
An Error for "EventLog"  8:48
The previous system shutdown at 8:23:48 PM on ‎9/‎14/‎2022 was unexpected.
 
Error on Server  8:42pm
The server could not bind to the transport \Device\NetBT_Tcpip_{1C3BBD96-C8F7-4C70-96FB-77CBFC395284} because another computer on the network has the same name.  The server could not start.
 
A Warning for DNS Client Event (Microsoft-Windows-DNS-Client)
Name resolution for the name account-public-service-prod.ak.epicgames.com timed out after none of the configured DNS servers responded. Client PID 9816.
 
Warning for "Time-Service"  8:42pm
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
 
 
I hope that is what you were needing to see.

I have the HWiNFO64.  But I keep tab of the CPU temp on the board and it rarely goes over 60C.  At most, it goes up to 72C when Minecraft starts up, but then it goes back down.
 
Looking at HWiNFO64, this is what I'm seeing.  Right now, CPU is 29C.
 
I'll be back on Saturday morning to check here.
 
Thanks for the ongoing help you have given.  It is so appreciated!

RAVENEVGA
I have the HWiNFO64.  But I keep tab of the CPU temp on the board and it rarely goes over 60C.  At most, it goes up to 72C when Minecraft starts up, but then it goes back down.
 
Looking at HWiNFO64, this is what I'm seeing.  Right now, CPU is 29C.
 
I'll be back on Saturday morning to check here.
 
Thanks for the ongoing help you have given.  It is so appreciated!

OK. Well, doing a little bit more digging, it might be normal for your system (as it's running intel's stock speed-stepping rules, where mine is not doing that). A lot of people see that when their laptop is trying to conserve power, or when they're running some really hot task. That's not you, so that's why I was a bit confused by it at first.
 
 

redteamgo
hi raven, have you reinstalled windows yet?

 
I'm curious, what evidence has RAVEN provided that would lead people to think that the Windows installation is corrupt? What is re-installing going to achieve? They did a fresh install a few months ago. It's just a whole lot of hoops to jump through and I don't see what it's supposed to solve. The system randomly freezes and reboots with no BSOD, no relevant error messages as far as I can see, and it apparently isn't overheating. The corrupted Windows theory Bee presented was based on the incorrect assumption that RAVEN had been pulling the power cord out while the system was running regularly. They were not (they were actually just unplugging the keyboard and plugging it back in).
 
If we're trying to isolate the problem, it seems there's no freezing or locking up of the video driver, which rules that out (but we've already asked them to clean install that driver anyway, which they've done).
 
If there was a memory glitch, I would also think there'd be a BSOD. If Windows was corrupt and freezing, I'd still think there'd be a BSOD or an error in the event log.
 
I'm not sure about anybody else, but I'm really not sure what would cause their computer to behave this way. A sudden shut-down with reboot would point me to the power supply tripping for some reason. Maybe the OCP or OPP is malfunctioning. That said, it wouldn't explain the situation where the computer actually freezes for a minute (with an audio loop), then reboots. That sounds more like a video card problem (driver error or overheating). Well, I suppose we may investigate that one further.
 
So RAVEN, can you take a look at the GPU hot spot and Memory junction temperatures in HWiNFO? I'm curious if those are doing something unexpected.

redteamgo
Hey B0ba, I got the impression that the mobo was swapped after the original windows install. If you guys already tried a fresh install, I gotcha. I saw where he said he did a clean driver install but didn’t see where he said there was a fresh windows. Some of those kernel messages are pretty ominous. Overall if there is no hard fault in event viewer at time of crash, it smells like PSU or windows imo. Im probably wrong 😑 . Cheers!

I'd have to dig through the old thread to be certain (I have CRS sometimes...ok more than sometimes lol), but this was a brand new computer build and I believe they did a fresh install of Windows on their OS drive. Then we walked them through drivers, BIOS updates, etc.
 
Also, I wasn't flat out saying you were wrong. I was just trying to figure out the logic behind the suggestion. It may be the next move, I just didn't want to ask them to do that (as they have been honest about being a novice with computers and that can be quite a burdensome task for beginners) without some clear indication that it is probably a Windows problem.
 
Does Windows 11 still let you do a repair? I wonder if that's an option they could try with an install media (USB drive). Last time I tried to do that it said it couldn't be repaired or something so I was wondering if they basically disabled that ability.
 
As for the kernel messages, one is specifically saying power was interrupted, which is what it will always say if your computer freezes and you have to hold the power button to get it to reboot (which they have had to do). They had some corrupted files I guess...but it said it repaired them. I guess we could wait to see if they continue to have issues now. The other kernel message indicates the speed of the CPU changed. That's why I suspected it was running hot, because the firmware will shift the CPU frequency for either temperature or power reasons. If they have it set on defaults, I'm not sure when that happens (I don't run on defaults lol).

Another test would be to run a really heavy GPU load and watch the GPU temperatures to see if the graphics card is getting hot. It would also put a good load on the PSU to see if that causes a crash. Sometimes the PSUs real issue is when the GPU requests a short burst of current for sudden frequency changes, even if the GPU isn't fully loaded down. Loading the GPU in a benchmark or something puts a more constant current load on the power supply and then you don't get a crash. It's a bit tricky to nail down. I'm kind of leaning towards the power supply having a problem, causing the video card to not get power, which eventually causes the system to freeze and/or reboot suddenly. You could try to download 3DMark demo from Steam and run Port Royal or Time Spy through a couple loops and keep an eye on some temperatures and power levels in HWiNFO on the other screen. It may be hard to catch, but I think the main concern is going to be watching the graphics card for temperatures and the +12VDC rail. If that voltage fluctuates a bunch, it'd be a big clue.

redteamgo
I see ok. Didn’t realize that other thread was the prologue to this. True. I agree tho, at this point I’d be stripping everything out of the system incrementally to find the faulty components. It is always a bummer when this happens. GPU is as good of a place to start as any.

Raven the good news is that build problems like this are very unusual. You’re in good hands. My watch is ended lol

Hey, don't go disappearing on us lol. Sometimes with these quirky issues it's better to have a few more people with their different backgrounds to weigh in 

What if you watch those temperatures and the +12V numbers for the GPU while you run some Graphics benchmark like port royal or time spy?

So I was watching a YouTube video and had just went from full screen back to the normal YouTube window, as the video was ending, and the system froze.  I was looking at temps and such, giving it a bit before holding the power button, which was strobing the light, as was the light under the temp on the motherboard [I think they're doing the same thing all the time anyway].  Then the PC rebooted.  
 
HWiNFO64 showed:
Memory Junction Temp averaging 38C, and at the time it froze, it was 44C
Hot Spot average was around 39C, and at the time it froze, it was 43.8C
Voltage average was .763, and at the time it froze, it was 1.075
 
When the system came back up, the keyboard was working, but again had to press the NUM LOCK to turn it back on. 
 
Looking at Event Viewer, I got the same four Kernel Warning messages as before.  More of the DistributedCOM Warnings. The same e2fnexpress "network link is disconnected" Warning.   
 
From the start, this morning:
First: were two Warning for the e2fnexpress "network link is disconnected" - 8:10:36 AM
Next: Warning - Time-Service  - 8:10:38 AM
"NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)"
 
Error: Server 8:10:41 AM
"The server could not bind to the transport \Device\NetBT_Tcpip_{1C3BBD96-C8F7-4C70-96FB-77CBFC395284} because another computer on the network has the same name.  The server could not start."
 
Two of the DistributedCOM at 8:10:42 
 
Warning - i8042prt - 8:10:47
The device sent an incorrect response(s) following a keyboard reset.
 
Another couple of DistributedCOM Warning
 
Error: DistrubutedCOM, but saying the same thing about "application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID "
 
Error - WindowsUpdateClient 8:30:15
Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience.
 
Error - DistributedCOM - 8:32:28
The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout.
 
Error - EventLog - 9:16:49
The previous system shutdown at 8:53:32 AM on ‎9/‎17/‎2022 was unexpected.   I don't recall any shutdown at 8:53.
 
Error - volmgr - 9:16:29
Dump file generation succeded.
 
Critical - Kernel-Power - 9:16:29
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
 
Warning - i8042prt - 9:16:41
The device sent an incorrect response(s) following a keyboard reset.
 
Two Warnings - e2fnexpress - 9:16:41
Intel(R) Ethernet Controller (3) I225-V
Network link is disconnected.
 
Another same at 9:16:49
 
Error - BugCheck - 9:16:52
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8010c905330, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 656d36bc-019a-4f57-b6c3-30eaac277bda.
 
Then a few more of the DistributedCOM and e2fnexpress, followed by the Kernel-Processor-Power, at the 9:17 AM.
The speed of processor 16 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
The other three were the same, just "processor 17", "processor 18", "processor 19".

Just had reboot happen.  When it happened, I looked at my phone and it was 10:15am
 
Error - EventLog - 10:16:14am
The previous system shutdown at 9:56:49 AM on ‎9/‎17/‎2022 was unexpected.
 
Error - volmgr - 10:15:55am
Dump file generation succeded.
 
Critical - Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
 
Warning - i8042prt - 10:16:08am
The device sent an incorrect response(s) following a keyboard reset.
 
Two Warnings - e2fnexpress - 10:16:08am and a third at 10:16:14am
Intel(R) Ethernet Controller (3) I225-V
Network link is disconnected.
 
Error - BugCheck - 10:16:15am
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000116 (0xffff80017f5ac010, 0xfffff80375481b20, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 134a702e-0f8d-473a-9161-cc45d9d7c03a.
 
Two Warnings - DistributedCOM - 10:16:25am
 
After this, more of the same e2fnexpress, DistributedCOM, and the four Kernel-Processor-Power Warnings.
 
Might be something that isn't a part of this, but often, when the PC boots into Windows, I'll here the sound a PC makes when you disconnect something, but I haven't.

Raven I didn’t re-scour this thread but have you tried a different keyboard just for giggles?

It’s possible your usb plugs are faulty. You could try different usb plugs. Do you have an actual ps2 device plugged in or all Bluetooth and usb?

Did you install or reinstall unleash rgb for keyboard firmware updates?

I know this isn’t an answer you want to hear but it might be RMA time, esp given recent events.

redteamgo
Raven I didn’t re-scour this thread but have you tried a different keyboard just for giggles?

It’s possible your usb plugs are faulty. You could try different usb plugs. Do you have an actual ps2 device plugged in or all Bluetooth and usb?

Did you install or reinstall unleash rgb for keyboard firmware updates?

I know this isn’t an answer you want to hear but it might be RMA time, esp given recent events.

Currently just have this keyboard.  But I've put it in several of the USB on the back.  And yes, I do have Unleash RGB for the keyboard.  I only have Bluetooth and USB.
 
What do you suppose needs to be RMA-ed?

RAVENEVGA

redteamgo
Raven I didn’t re-scour this thread but have you tried a different keyboard just for giggles?

It’s possible your usb plugs are faulty. You could try different usb plugs. Do you have an actual ps2 device plugged in or all Bluetooth and usb?

Did you install or reinstall unleash rgb for keyboard firmware updates?

I know this isn’t an answer you want to hear but it might be RMA time, esp given recent events.

Currently just have this keyboard.  But I've put it in several of the USB on the back.  And yes, I do have Unleash RGB for the keyboard.  I only have Bluetooth and USB.
 
What do you suppose needs to be RMA-ed?

the z690 classy mb
 
this is a desperation move but if i were you, my final steps here would be to systematically eliminate each component.  first, remove the video card, plug the main monitor into onboard video, remove 1 stick of ram, get a different keyboard (simple, cheap, no lights or widgets, media buttons etc) and then see if you still crash.  That config is about as basic as you can get for testing the motherboard.  that probably won't run fortnite very well but its enough for youtubing, basic productivity for sure.  maybe 720p / 1080p fortnite.
 
if you don't crash after an interval that is at least as long as your last usage with a crash after you strip the system, readd a stick of RAM and repeat the process.  operate the system for at least as long as that last usage without a crash, re-adding components one by one (one by one, don't cheat!).  once both of the ram sticks are in, do the GPU.  then finally switch back to the Z15 kb.  if you crash at any point during this process, revert to the most recent, basic hardware configuration and start the test usage period over.
 
if you still crash on a barebones system running on the 12700k's onboard video and just 1 stick of RAM, try switching to the other RAM blade in the same DIMM.  if that doesn't work, try using the a different DIMM on the z690 classy.  repeat with other stick if necessary.  if that doesnt work, i'd probably buy a QVL'd RAM kit to test and i'd start the RMA that motherboard for a cross shipped replacement.  I read through both threads, you have done everything right and have true experts here trying to figure this out.  for a basic overclock and your usage, you're wayyyyyyyyyyyyy past regular trouble shooting for an RMA imo.  but you want to know the result of this systematic elimination test before you RMA the motherboard otherwise you'll have the same issues if the mobo wasn't actually faulty and it was a different component.  so for your own sanity and wallets sake, do the test.  It might be your RAM, might be the keyboard.  some of the errors you posted sound like a USB hardware conflict failure but RAM errors can be all over the place too.  honestly, its not your problem LOL.  you just need to know what to return.  EVGA will cross ship (if they have inventory) for a temporary fee on your card so you dont have to have any down time beyond reinstalling the board, whether keyboard, mobo, psu etc.  
 
I had a similar issue in 2020 with a newly built system.  it turned out to be just one of the four sticks of RAM in the kit.  it took testing the combinations of hardware in certain slots to know for sure.  once you can reproduce the problem, you have reached your conclusion from systematic testing on what to do next.  you know this of course.  I returned the fault kit in my little anecdote there and got a replacement which was all good.
 
you have spent a lot of coin on your system - it is top notch.  you deserve to enjoy it without these annoyances.  they are not in spec with expected performance.
 
maybe as a last resort, and only if you have cash to burn, just order replacement RAM and PSU for the test so you have some control variables to eliminate in the course of evaluating a mobo RMAing and then other returns later.  you may end up with waste and extra parts though... or an extra HTPC for your tv!
https://www.gskill.com/qvl/165/374/1652689669/F5-5600J2834F32GX2-TZ5RK-F5-5600J2834F32GA2-TZ5RK-QVL
this kit for example has been tested with the z690 classy and kingpin.  but I am getting ahead of myself, we don't know the RAM is bad.  this would be the lazy way to do the above test.  just order new everything and return/scrap the old.
 
 
B0ba what do you think?
 
cheers

true, agree the PSU should be tested if possible.  keep us posted Raven

Okay.....found a very basic...bare bones...HP keyboard and have plugged it in...and am now typing this out on.  I guess this constitutes the first test then.
 
So if I have to take out the GPU, I'm guessing there is a BIOS setting that will have to be changed?  I thought I recalled something about onboard video?  I could be wrong.