Mrrrr
AdMiN
 Inregistrat: acum 18 ani
Postari: 2320
|
|
Today I made some updates to my NVidia GPU since GeForce Experience provided new GeForce Game Ready Drivers.
Everything went smooth for a while until I tried to right click my Desktop and it froze. Again. As it happened before (a few times) and I always got the computer to freeze entirely having to actually reset it via the reset button. All the other programs seem to work fine - YouTube, starting Task Manager, starting Event Viewer - except for Windows Explorer. Task Manager actually doesn't show it as Not Responding unless you click the Desktop a few times - which today I did not.
Today I decided to have patience and locate the problem once and for all. The right click goes through after 2-3 minutes, even though I am writing this post as the Desktop had frozen. Now I have the Desktop right click menu on top of my GeForce Experience which I opened on the other monitor. And the right click menu won't go away by clicking GeForce Experience. Unless I choose something in the the right click menu. Display Settings. Okay, now it's gone and Desktop seems back to normal. Until I right click it again (the time I was telling you about just now was my 3rd in a row - a fourth should lead to another freeze of course).
After unsuccessfully trying to find a solution online (I remember trying in the past as well), even though a few new ones popped up today (looking for DCOM Config), I decided to go through the issue step by step.
1. Open Start - Run by pressing Win + R, then type eventvwr and press Enter.
2. Click on Windows Logs - System and in the Level column check for any red exclamation marks next to the word Error. I located 3 - the 3 I was mentioning above.
3. Click on either of them and check out the description under the General tab: "The server {DCAB0989-1301-4319-BE5F-ADE89F88581C} did not register with DCOM within the required timeout."
4. Since DistributedCOM (DCOM) is mentioned, Event ID 10010, first we're gonna go to DCOM Settings to look for that CLASID above. Open Start - Run by pressing Win + R, then type dcomcnfg and press Enter.
5. Under Component Services, double click Computers, then My Computer, then DCOM Config. Look for the CLASID above in the list. I didn't find it in there.
6. On the Component Services menu bar, I noticed the Large Icon button is pressed by default, so I switched to the Show Detail button and on the right side the Application ID CLASID showed up. Looking through that is a mess since you cannot sort it alphabetically and they're more than 500 items in the list.
7. So, where else did I see CLASIDs? Yes, in the Windows Registry. Open Start - Run by pressing Win + R, then type regedit and press Enter.
8. Under HKEY_CLASSES_ROOT look for a key named CLSID, then for a key named {DCAB0989-1301-4319-BE5F-ADE89F88581C}, or in the Registry Editor address bar simply paste the following: HKEY_CLASSES_ROOT\CLSID\{DCAB0989-1301-4319-BE5F-ADE89F88581C}
- by clicking the {DCAB0989-1301-4319-BE5F-ADE89F88581C} key I can find out the AppID which is {C5EDFC9D-B018-41A4-9877-39AB18469C3A} (remember the Application ID column from step 6?)
- within the {DCAB0989-1301-4319-BE5F-ADE89F88581C} key, click on subkey named LocalServer32 and check the (Default) value by double clicking on it. This points to NVDisplay.Container.exe.
- wait, didn't I just update my drivers and didn't I just skip restarting my PC since the update program never offered a restart? Yep.
9. But having to restart the PC upon every driver update when the update program doesn't specifically require you to restart doesn't sound like a solution to me.
- so let's look the AppID up under Component Services by going straight to NV* in the Name column, then looking for that AppID in the Application ID column.
- in DCOM Config the AppID points to NvXDCore - double clicking that won't do anything though, so I must right click it and select Properties
- I checked NvCpl to see if the same settings are applied and something is different under Security - Access Permissions. Specifically NvCpl has "Use Default" checked, while NvXDCore has "Customize" checked
- so the way in NvCpl "Use Default" is selected under Access Permissions, I could also select that in NvXDCore, but should I? Since I never came in here and changed anything like this, I am going to assume the "Customize" check is OK for NvXDCore. For now. I'm gonna try the next step first and see if it solves my problem without having to change DCOM Settings, then come back here if the issue persists.
10. Since I always skip the "Perform a clean installation" option provided when updating drivers, how about I select it now and do a clean install of the drivers - maybe not doing a clean install since I last installed Windows became an issue one day.
- but first, let's back up my NVidia Control Panel settings so I can set them back as they are right now.
- click Start then search for Nvidia Control Panel and click it. Nothing happens. It looks like... it's... an app? Like a Windows Store installed app? WTF, really? Okay, well, let's go to App Settings then instead of opening it, and there are a few options here: Terminate, Repair, Reset (but this reset deletes the app data which I want to backup). So I'm gonna click Terminate first, see what happens, then Repair if I sill cannot start the app, then ultimately Reset and go look on YouTube for the NvCpl settings one must do for smooth game running.
11. So let us Terminate! Clicked, now it shows the big "thinking" hourglass. Waiting for it to go away. And it did in about 15-20 seconds. Starting the app with Open - nothing happens. Starting the app by Running as administrator - nothing happens. Damn.
12. Moving on to Repair. Clicked, and that was the quickest repair I've seen in my life. The app still doesn't work when pressing Open. Why did they make it an app?
13. Well, moving on to Reset... but wait, before I reset, shouldn't there be a services.msc service? Open Start - Run by pressing Win + R, then type services.msc and press Enter.
14. Look for NVIDIA Display Container LS, it should be Running and already set to Automatic. Restart it (right click - Restart)
15. Opening Nvidia control Panel once again from start menu aaand Eureka! I click on Manage 3D Settings and it looks like I have to make a few screen snips to backup the settings. Old school, I like it! (Nope!)
16. After several snips and snaps, let's go back to performing a clean installation of the Nvidia Drivers. In GeForce Experience - Drivers, by clicking the 3 vertical dots to the right of the GeForce Game Ready Driver showing the version and release date, I get the unique option to Reinstall drivers.
17. I pick Custom installation, wait for it to prepare, put a check on "Perform a clean installation" and click Install.
- now this will reset the NVidia settings I just backed up old school style, and maybe other settings too, but hopefully it will fix the problem with DCOM event ID 10010
- I will have to see if the problem comes back when the next Game Ready Driver update is released in a few days or weeks
Will be back with feedback.
_______________________________________
|
|
