Multi Commander Support Forum

Multi Commander => Support and Feedback => Topic started by: Ulfhednar on January 24, 2018, 14:49:36

Title: Nvidia driver causing MC lockup Win10
Post by: Ulfhednar on January 24, 2018, 14:49:36
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 :-

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?
Title: Re: Nvidia driver causing MC lockup Win10
Post by: Mathias (Author) on January 24, 2018, 17:26:44
Maybe..
You can upload it at  http://multicommander.com/upload/
Title: Re: Nvidia driver causing MC lockup Win10
Post by: Ulfhednar on February 02, 2018, 15:06:46
I've been experimenting with nvda drivers & haven't yet found a 100% fix.
I still have usb device issues with the newest builds.
I have tried hooking VS to MC & tracking the crash - it doesn't seem to give much info.  Mostly the OS file version numbers are listed & nothing definite is revealed (like an exception or sth).
I used WinDBG on the mc.dmp & got only this -
Code: [Select]
Loading Dump File [...MultiCommander.DMP]
User Mini Dump File with Full Memory: Only application data is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
OK                                             \Symbols
Symbol search path is: srv*;\Symbols
Executable search path is:
Windows 10 Version 15063 MP (16 procs) Free x64
Product: WinNt, suite: SingleUserTS
15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Debug session time: Tue Jan 30 14:32:21.000 2018 (UTC + 0:00)
System Uptime: 0 days 0:09:00.749
Process Uptime: 0 days 0:05:40.000
................................................................
................................................................
.........
Loading unloaded module list
....................
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for KERNELBASE.dll -
ntdll!NtQueryAttributesFile+0x14:
00007fff`36025b44 c3              ret

Is it worth uploading the <300mb?  What else is contained in the dmp?  (e.g. could the dmp compromise data on my machine if it was taken by a malicious user?)
Title: Re: Nvidia driver causing MC lockup Win10
Post by: Mathias (Author) on February 06, 2018, 22:41:31
Sorry. did not see that I did not answer this

Hmm Useful maybe.. We can try

Pack it and upload it to http://multicommander.com/upload/
Title: Re: Nvidia driver causing MC lockup Win10
Post by: Ulfhednar on February 12, 2018, 15:18:57
I just received some new mobo drivers from ASUS.
They seem to have resolved the USB issue.  I am having to go through the nvda drivers one by one to see if the latest builds still cause problems.
This may have saved you!  :) :P