Where to look next if Windows hangs up with a busy cursor for 5 to 10 minutes, with NO errors in Event Viewer

I am familiar with low level issues in Windows (such as, a hard disk failing, or having a physical error) causing a low level lock/freeze in Windows that lasts either forever, or until the error condition clears. What I am not used to is figuring out WHERE to look in Windows diagnostic tools, other than Event Viewer after such a major error, to find any errors.

The number one most useful part of Event Viewer in such a case would normally be the Custom Views > Administrative Events filtered view, which gathers a lot of serious information together. That filter shows NO data for the date today, and its last event was the previous night. The system just recovered after 10 minutes of completely not responding to any keyboard or mouse input. After 10 minutes, Windows recovered, and I was able to at least open task manager.

During that 10 minutes of "hung" time, the mouse cursor moved when I dragged the mouse around, but nothing else appeared to be happening. It did not appear to leave any indication in any of the usual 10 or 20 places in Event Viewer that I checked (every section in Windows Logs, also everything in the top level Applications in Services Logs).

My guess is I should enable some event viewer logs that are currently disabled. If so, which ones. If I should go somewhere OTHER than event viewer, which place would be good to check?

If this was linux, I'd be looking at dmesg and journalctl to look and kernel and system logs, but event viewer is the closest thing to "system logs" that windows actually has.

Update: I have tried to capture ETL trace information with wpr.exe but it is failing with an error writing to the disk. it says the disk is full which it can't possibly be, it has >100 gigs free space, and the wpr trace was only running 5 minutes, so I have a hard time believing it wants to log a 100+ gb .etl file. Also, using CrystalDiskInfo and WD utilities, I have checked the hard disk S.M.A.R.T. status, and there are no disk problems reported by either tool. A sensible explanation for the system wide hang would be a Disk IO problem writing the page file. But then there should be errors in the event viewer. Inability to do a wpr.exe -stop is odd:

wpr.exe -stop C:\hang.etl 
There is not enough space on the disk. 
Profile Id: RunningProfile 
Error code: 0x80070070 There is not enough space on the disk.