Funny thing installing the latest WinMerge beta when it got to registering the shell extensions. A system freeze.
Looking at it later, could have been an after effect of any of or all of this involving APCupsd uninstallation and installation of PowerChute Personal Edition (and an upgrade from an older to a newer legacy of that product, an earlier Event 7031 followed later by Event 61456, as well as switching the UPS port connectors.
Earlier that day there was Event 225:
The application \Device\HarddiskVolume3\Program Files (x86)\APC\PowerChute Personal Edition\dataserv.exe with process id 11220 stopped the removal or ejection for the device HID\VID_051D&PID_0002\7&36b985e7&0&0000.
Process command line: “C:\Program Files (x86)\APC\PowerChute Personal Edition\dataserv.exe”
List of affected devices:
HID\VID_051D&PID_0002\7&36b985e7&0&0000
Around 15 minutes prior to the freeze was an app hang logged with DLLHost, same again 15 minutes on.
The program dllhost.exe version 10.0.26100.9549 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
On checking the Security and Maintenance panel after reboot, the active item was something like “reset USB device” with a button attached. Clicking the button made it go away.
And directly after was the big one:
The description for Event ID 14 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video3
CMDre 00000002 00000200 00000000 00000005 0000001b
The message resource is present but the message was not found in the message table
Now what is most intriguing is the reboot Event 6008:
The previous system shutdown at 16:47:42 on 22/10/2026 was unexpected
That time was the time of the first DLLHost hang, thus things were already in a pickle without any obvious tell-tale signs.
Good news is that the event log and the system have been very quiet and well behaved since the reboot. 🙂
.
