Taken me a while to figure this one out... My clue was that
NvFBCPlugin would hang any attempt to restart the pc!
I noticed that MC would :-
- hang on startup flag if a USB device was connected at boot;
- lockup if I connected a USB drive;
- sometimes not see a drive even if it was visible/usable in Win Explorer.
MC usually cannot be terminated by TM or ProcExp once it has entered
not responding state. If MC thread is apparently terminated (no longer shown in TM list) GUI or start-up flag remains on-screen.
Attempting to restart the OS normally will hang the PC.
System needs to be fully powered-off to recover the OS. Hitting Reset not enough even with USB devices unplugged & w10 fast boot disabled to recover a working OS.
NVDA
390.65-desktop-win10-64bit-international-whql seems to be the cause. Clean install back to
388.71 so far resolves these issues.
Whilst this issue is
probably HW specific, I think its worth sharing the info...
I am using
MC x64 7.7 b2404 on
Win10 x64 b170317-1834 on
Asus B350M-A
Ryzen 1800x
TEAMGROUP-UD4-3200
Mathias - would a MC.dmp made by TM help you?