Help Fix event 642 [SOLVED]

"...and 4 months later, even if my error report are automatically submitted to them, they didn't even bother fixing it, I had to troobleshoot and fix it by myself."

This is especially frustrating and I know what you mean, but on the same token, it was bound to happen due to the various factors that in addition go into consideration for error reports being sent to Microsoft. Sometimes, what seems like a quick fix to us can be a question of priority for them, when they take into consideration the number of users experiencing the same issue as well as number of users reporting it collectively. It's unfortunate if we fall under the minority in dealing with these particular events as sometimes it's faster to discover for yourself through your own means then to rely on any help given anywhere...but I digress.

I've got exact same thing. I believe computer 'freeze' is actually system processes doing something  tied to event viewer events. What is happening when all these event hit at same time? Here's my log of what is happening when the 'freeze' occurs. BTW when it 'freezes' keep pressing caps lock until it responds, then it is unfrozen.

Freezing keyboard.

1. Keyboard is USB wireless
2. Uses PC front USB 2 port.

Symptoms/What's active

1. Pressing any key does not appear.
2. Caps lock does not work
3. Mouse moves.
4. Can switch to other screens using mouse

5. 

Actions to take

1. WAIT and see if it clears. I keep pressing caps lock until I get the 'light'. All then is cleared to go. If this does not work, it is ot the same problem. May have to wait 10 minutes but no longer.

2.???

PC Info

OS Name Microsoft Windows 10 Pro

Version 10.0.19041 Build 19041

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name MATT-DESKTOP

System Manufacturer System manufacturer

System Model System Product Name

System Type x64-based PC

System SKU SKU

Processor Intel(R) Core(TM) i7-4930K CPU @ 3.40GHz, 3401 Mhz, 6 Core(s), 12 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. 4801, 7/25/2014

SMBIOS Version 2.7

Embedded Controller Version 255.255

BIOS Mode UEFI

BaseBoard Manufacturer ASUSTeK COMPUTER INC.

BaseBoard Product SABERTOOTH X79

BaseBoard Version Rev 1.xx

Platform Role Desktop

Secure Boot State On

PCR7 Configuration Binding Not Possible

Windows Directory C:\WINDOWS

System Directory C:\WINDOWS\system32

Boot Device \Device\HarddiskVolume1

Locale United States

Hardware Abstraction Layer Version = "10.0.19041.488"

User Name Matt-Desktop\Matt

Time Zone US Mountain Standard Time

Installed Physical Memory (RAM) 32.0 GB

Total Physical Memory 31.9 GB

Available Physical Memory 26.2 GB

Total Virtual Memory 65.9 GB

Available Virtual Memory 59.6 GB

Page File Space 34.0 GB

Page File C:\pagefile.sys

Kernel DMA Protection Off

Virtualization-based security Not enabled

Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, Disabled by policy, TPM is not usable

Hyper-V - VM Monitor Mode Extensions Yes

Hyper-V - Second Level Address Translation Extensions Yes

Hyper-V - Virtualization Enabled in Firmware Yes

Hyper-V - Data Execution Protection Yes

These errors seriously led me to buy a mac mini.

As I have been searching the net why my wireless USB mouse keeps getting malfunctioned (windows makes the usb eject sound and get a windows error popup saying USB device malfunctioned) at random for the last month.

Tested on multiple hardware and it does it on every machine.

As I cant find anything about it on the web, this comes actually the most closest to the thing i am encountering. I will exchange the mouse cause with wire it is working and with the receiver it isnt.

However, it is actually Windows that is **** it up?

I have exactly the same Warning message on my Latitude E7450. I just installed from image the official Windows 10 Version 20H2, Build 19042.610.

This Event ID 642 appears twice, right after the boot, after working, no.

On the other hand, I do not see any particular problem, whatever, in the PC Manager the screens open while freezing.