Quote:
Originally Posted by CWatkinsNash
What errors are showing in Event Viewer when this happens?
Also, something that completely slipped my mind - check Device Manager and make sure your monitor was detected correctly just in case we're blaming the wrong thing. It took 2 days before Win 10 could properly ID my TV, and things were interesting in the meantime. No black screens, but oddball resolutions changing and other nonsense.
|
My monitor looks fine in Device Manager.
I'm struggling to work out from the Event Viewer which are the relevant events before the crash. It could be (under the Error section):
Metadata staging failed, result={4E6B7047-D315-5E65-9E3E-79FA17D41B03} for container '0x80070490'
or:
The description for Event ID 11 from source nvraid 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.
or:
Faulting application name: OHub.exe, version: 16.0.6106.2350, time stamp: 0x55c40ea1
Faulting module name: ntdll.dll, version: 10.0.10240.16430, time stamp: 0x55c59f92
Exception code: 0xc0000374
Fault offset: 0x00000000000ea28c
Faulting process ID: 0x948
Faulting application start time: 0x01d0dab608464aac
Faulting application path: C:\Program Files\WindowsApps\Microsoft.MicrosoftOfficeHub_17. 6106.23501.0_x64__8wekyb3d8bbwe\OHub.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 1e981092-8506-4e62-9826-4533f7660d41
Faulting package full name: Microsoft.MicrosoftOfficeHub_17.6106.23501.0_x64__ 8wekyb3d8bbwe
Faulting package-relative application ID: Microsoft.MicrosoftOfficeHub
I really don't know how to read the Event Viewer Log to make any sense of it.