nvidia processes

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

jjjjjj

72 discussion posts

Usually when I install new nvidia drivers, I get a message from DF asking if I want to disable nvidia processes that interfere with DF, and I do so. That didn't happen on my last install of drivers, and I THINK it's because I installed DCH drivers this time, rather than standard drivers. I was able to solve the issue on my own by renaming both nvsmartmaxapp.exe and nvsmartmaxapp64.exe in C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b9ae772eb7ef9895 (had to change permissions on the directory first).

Is this a compatibility limitation with DCH drivers right now, or is there another issue going on here?

Nov 3, 2019 • #1

It could be, yeah. We've never tested with anything but the official NVIDIA drivers. Could you send me the link to where you downloaded them?

Nov 4, 2019 • #2

jjjjjj

72 discussion posts

DCH drivers /are/ official nvidia drivers. They're made to follow the new standards for drivers laid out by microsoft for Windows 10. They can be downloaded from the same Nvidia site for standard drivers, but you have to select DCH drivers rather than standard drivers in the search. The installation will also fail if the standard drivers aren't completely wiped from the system beforehand, and vice versa for standard drivers (DDU suggested).

Nov 12, 2019 • #3

Ah, interesting! Thanks for the extra info, I hadn't seen that DCH option before. We'll do some further testing here and see what we can find out.

Thanks!

Nov 13, 2019 • #4

Just a quick heads up, I was able to reproduce this here and have added it to our list to fix up.

Thanks!

Nov 21, 2019 • #5

jjjjjj

72 discussion posts

Awesome, can't wait! Thanks

Nov 21, 2019 • #6

jjjjjj

72 discussion posts

Quote:

Just a quick heads up, I was able to reproduce this here and have added it to our list to fix up.

Any luck yet? It looks like Nvidia is fully moving over to DCH drivers as of 2019-12-06. Their latest drivers are now DCH by default and can be installed over their standard drivers without wiping first (meaning anyone updating their drivers will most likely get DCH now unless they specifically look for non-DCH drivers as mentioned next). Standard drivers can now only be downloaded via advanced search.

Dec 16, 2019 (modified Dec 16, 2019) • #7

Getting there! We should have this fixed up for 9.6 Beta 8 with any luck

Dec 16, 2019 • #8

jjjjjj

72 discussion posts

Great!

Here's a link to the new Nvidia FAQ page on DCH drivers that came up last week for anyone reading this who's interested: https://nvidia.custhelp.com/app/answers/detail/a_id/4777/~/nvidia-dch%2Fstandard-display-drivers-for-windows-10-faq

Also worth noting for anyone reading this, if your taskbar is stuck up (with auto hide on) after updating Nvidia drivers, that's due to nvsmartmaxapp(64).exe conflicting with DF (assuming you're using DF taskbars). Just rename/delete the two files directly for now. You should see them running in task manager and can right click on them there to find their directory. As stated in my first comment, you'll have to take ownership of the directory and change permissions to be able to do so.

Dec 16, 2019 • #9

Ok, we've just posted 9.6 Beta 8 and this should be all fixed up. Please let us know if not!

Dec 18, 2019 • #10

jjjjjj

72 discussion posts

Quote:

Ok, we've just posted 9.6 Beta 8 and this should be all fixed up. Please let us know if not!

I'm on 9.6.2 beta 1 at the moment and I just updated to the latest nvidia drivers. I'm not seeing any sort of UI for disabling the nvidia processes again.

Feb 15, 2020 • #11

@jjjjjj: Could you send me a copy of your troubleshooting info? Here are the steps:

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

Feb 19, 2020 • #12

jjjjjj

72 discussion posts

Quote:

@jjjjjj: Could you send me a copy of your troubleshooting info? Here are the steps:

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

Sorry, I forgot about this. I'm on 9.7 Beta 5 now and it's still happening with the latest nvidia drivers (downloaded and installed today). Whatever changes were made in 9.6 Beta 8 appear to be completely gone (from a gui/functionality pov anyway).

Here's the export you asked for. I've checked all my settings pretty thoroughly and can't find any issues there as far as I can tell. For now I've just been doing the permissions edit and renaming I mentioned above. I never get prompted by DF to disable nvidia processes after a driver update.

• Attachment [protected]: DisplayFusionDebugInfo.zip [33,228 bytes]

Mar 15, 2020 • #13

Thank you for the information! We're a bit backed-up right now but we'll take a look as soon as we can and get back to you. Thanks!

Mar 19, 2020 • #14

Just a quick update to let you know that we've found the issue here and it will be fixed up in the next beta. We'll follow-up when it's available to try out.

Thanks!

Mar 31, 2020 • #15

We've just released a new DisplayFusion Beta version and this issue should be all fixed up. Please let us know if you run into any trouble after updating.

Thanks!

Apr 8, 2020 • #16

jjjjjj

72 discussion posts

Quote:

We've just released a new DisplayFusion Beta version and this issue should be all fixed up. Please let us know if you run into any trouble after updating.

Thanks!

I just updated my nvidia drivers (to undo my manual renaming) and displayfusion, and rebooted my system. I'm still not seeing any dialog from displayfusion to disable any nvidia processes. I can see from task manager that the processes are still running as well.

Additionally, another tool I use (Peach, available on the microsoft store) is now crashing on launch. Killing DF instantly allows it to run correctly. It was not exhibiting this behavior before this DF update. I'm seeing the following 4 entries in event viewer on every crash:

Code
Copy
Select All

Fault bucket 1331443558009825227, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: 8871PaulC.Betts.Peach_2.3.1.0_x64__axc4dmhnmexv8
P2: praid:Peach
P3: 2.3.1.0
P4: 5dcf0b0b
P5: KERNELBASE.dll
P6: 10.0.18362.535
P7: 50cc8d5a
P8: c000041d
P9: 000000000003a839
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER52E2.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55A2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55B2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55D0.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER55F0.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_8871PaulC.Betts._23e4c5cd316a16c8a83fe528461ea357cff71e_60f14076_5bf3d5a3-d21c-4768-adcb-ca1d542fde36

Analysis symbol: 
Rechecking for solution: 0
Report Id: db823876-a1b6-4232-8b18-de3da6f1dcc2
Report Status: 268435456
Hashed bucket: bcfff853dcccd68da27a3cdc99a867cb
Cab Guid: 0
---------------------------------------
Faulting application name: Peach.exe, version: 2.3.1.0, time stamp: 0x5dcf0b0b
Faulting module name: KERNELBASE.dll, version: 10.0.18362.535, time stamp: 0x50cc8d5a
Exception code: 0xc000041d
Fault offset: 0x000000000003a839
Faulting process id: 0x1ed4
Faulting application start time: 0x01d60e159ea7e716
Faulting application path: C:\Program Files\WindowsApps\8871PaulC.Betts.Peach_2.3.1.0_x64__axc4dmhnmexv8\Peach.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: db823876-a1b6-4232-8b18-de3da6f1dcc2
Faulting package full name: 8871PaulC.Betts.Peach_2.3.1.0_x64__axc4dmhnmexv8
Faulting package-relative application ID: Peach
---------------------------------------
Fault bucket 2064247905938203618, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Peach.exe
P2: 2.3.1.0
P3: 5dcf0b0b
P4: WindowsBase
P5: 4.8.4150.0
P6: 5e1774d1
P7: 6b
P8: 1b
P9: System.ComponentModel.Win32
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4B02.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DD2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DE2.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4DFE.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER4E1E.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Peach.exe_cee124963dcae8fef33ae231cb02c1b68a5e34_60f14076_0371cbad-4647-4863-8900-96a88f61cd7c

Analysis symbol: 
Rechecking for solution: 0
Report Id: 558842b7-b961-4e37-9773-c8967defce2d
Report Status: 268435456
Hashed bucket: 7d732a5369f83551eca5ae8899ca63e2
Cab Guid: 0
---------------------------------------
Faulting application name: Peach.exe, version: 2.3.1.0, time stamp: 0x5dcf0b0b
Faulting module name: KERNELBASE.dll, version: 10.0.18362.535, time stamp: 0x50cc8d5a
Exception code: 0xe0434352
Fault offset: 0x000000000003a839
Faulting process id: 0x1ed4
Faulting application start time: 0x01d60e159ea7e716
Faulting application path: C:\Program Files\WindowsApps\8871PaulC.Betts.Peach_2.3.1.0_x64__axc4dmhnmexv8\Peach.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 558842b7-b961-4e37-9773-c8967defce2d
Faulting package full name: 8871PaulC.Betts.Peach_2.3.1.0_x64__axc4dmhnmexv8
Faulting package-relative application ID: Peach
---------------------------------------
Application: Peach.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
   at MS.Win32.UnsafeNativeMethods.GetWindowText(System.Runtime.InteropServices.HandleRef, System.Text.StringBuilder, Int32)
   at System.Windows.Automation.Peers.WindowAutomationPeer.GetNameCore()
   at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree()
   at System.Windows.ContextLayoutManager.fireAutomationEvents()
   at System.Windows.ContextLayoutManager.UpdateLayout()
   at System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object)
   at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
   at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object)
   at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

EDIT: At this time, I'd like to roll back to beta 6, but I can't find a direct link to it anywhere. Please provide one if possible, thanks!

Apr 9, 2020 (modified Apr 9, 2020) • #17

We're posting 9.7 Beta 8 shortly to fix that crashing issue. After updating to Beta 8, could you send me a new copy of your DisplayFusion troubleshooting info?

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

Apr 9, 2020 • #18

jjjjjj

72 discussion posts

Quote:

We're posting 9.7 Beta 8 shortly to fix that crashing issue. After updating to Beta 8, could you send me a new copy of your DisplayFusion troubleshooting info?

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

here you go

• Attachment [protected]: DisplayFusionDebugInfo.zip [32,200 bytes]

Apr 9, 2020 • #19

I can't figure out what's different here. When we test with the DCH drivers, it prompts correctly and disables them

Could you tell me what folder the nvsmartmaxapp processes are in on your machine?

Apr 10, 2020 • #20

jjjjjj

72 discussion posts

Quote:

I can't figure out what's different here. When we test with the DCH drivers, it prompts correctly and disables them

Could you tell me what folder the nvsmartmaxapp processes are in on your machine?

Both are located in C:\Windows\System32\DriverStore\FileRepository\nvbli.inf_amd64_2d4a5fbb20e2c58d\

I have yet to see a single prompt on recent versions, but back when you first released an update that included this in the change log (before I mentioned that it's broken again in the recent betas), I recall having been prompted once correctly. Though it was a while ago so I could be making things up in my head.

Apr 10, 2020 • #21

Ok, thanks! We'll have another look at it and keep you posted on what we find out.

Apr 14, 2020 • #22

Sorry, one more thing. Could you tell me what the EXE names are in those folders?

Apr 14, 2020 • #23

jjjjjj

72 discussion posts

Same as before, nvsmartmaxapp.exe and nvsmartmaxapp64.exe

Apr 14, 2020 • #24

Hi,

Would you be able to get a new debug log with the newest DisplayFusion beta? We'd love to get to the bottom of this! Here's how to get that to us:

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Reproduce the issue and note the time so we'll know where to check in the log file
Click the "Export Info to File" button on the Settings > Troubleshooting tab
Reply with the file attached
Disable debug logging after sending the log

Thanks!

Apr 16, 2020 • #25

jjjjjj

72 discussion posts

Quote:

Hi,

Would you be able to get a new debug log with the newest DisplayFusion beta? We'd love to get to the bottom of this! Here's how to get that to us:

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Reproduce the issue and note the time so we'll know where to check in the log file
Click the "Export Info to File" button on the Settings > Troubleshooting tab
Reply with the file attached
Disable debug logging after sending the log

Thanks!

To clarify, what exactly am I reproducing? From my understanding, this is a check which should always happen (at least that's how I remember the behavior from the days before DCH drivers).

Apr 16, 2020 • #26

Thanks! Would you be able to update to 9.7 Beta 9, then send us a new L1 debug log?

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Restart DisplayFusion and make sure that the Monitor Splits are enabled
Wait a minute to give the polling a chance to try and detect the NVIDIA helper processes
Click the "Export Info to File" button on the Settings > Troubleshooting tab
Reply with the file attached
Disable debug logging after sending the log

Thanks!

Apr 16, 2020 • #27

jjjjjj

72 discussion posts

Quote:

Thanks! Would you be able to update to 9.7 Beta 9, then send us a new L1 debug log?

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Restart DisplayFusion and make sure that the Monitor Splits are enabled
Wait a minute to give the polling a chance to try and detect the NVIDIA helper processes
Click the "Export Info to File" button on the Settings > Troubleshooting tab
Reply with the file attached
Disable debug logging after sending the log

Thanks!

Sorry things got busy around here and I didn't get to this. I do have some more data though. I just built a brand new system, which I of course promptly installed the latest DF on (beta 10). Upon launching, it instantly detected that nvidia processes were running (latest drivers) and asked if they should be disabled. I selected the option to disable them, but nothing happened, the processes remained running, and I had to manually disable them using the method I mentioned before. Could it be a permissions issue?

May 3, 2020 • #28

We did find an issue in a code review with this, so this should hopefully be working in Beta 11. We'll let you know as soon as it's available to try out

Thanks!

May 5, 2020 • #29

Ok, we've just posted 9.7 Beta 11, could you give it a try and let me know how it works out?

Thanks!

May 7, 2020 • #30

jjjjjj

72 discussion posts

Quote:

Ok, we've just posted 9.7 Beta 11, could you give it a try and let me know how it works out?

Thanks!

Happy to report that upon reinstalling my drivers, DF immediately detected the processes on the next boot and was able to properly disable them this time. Checked the directory to be certain and sure enough, they were renamed. Thanks for getting this working!

May 13, 2020 • #31

Excellent, glad to hear it! Thanks for following up to let us know!

May 14, 2020 • #32

Vortexic

1 discussion post

Hey I'm just popping in to say I'm really impressed with the interaction on this issue. I've been Watching it develop over the months and this is a testament to the quality of your team. All seems to be working for me as well.
Thanks!

Jul 26, 2020 • #33

Glad to hear it! We finally isolated this issue right after we released 9.7.1 Beta 2 so the fix will be included in Beta 3 this week.

Jul 26, 2020 • #34

joeg

6 discussion posts

Hi. Found this post searching for the error message I'm getting, "nVidia processes have been detected on your computer that may cause issues with DisplayFusion monitor splitting. Would you like to disable them now?"

As far as I've been able to tell, the monitor splitting is working. At least as well as I should probably expect; I'm new to DF.

I'm running Trial 9.7 currently, have a EVGA 3080 XC3 Ultra and installed their latest driver pack, which contains the nVidia driver version number 27.21.14.5730. I'm running my three monitors using the nVidia Surround PhysX feature to make it a wide 7680x1440.

With all that said, my question is: Should I just ignore this error message? Or is there something that wouldn't be working? If I agree to disable things per DF request, what is actually changed/lost? I need more info to make a decision WRT to this message. Thanks

Nov 26, 2020 • #35

If everything is working fine, you can ignore it. The NVIDIA helper processes try to hook windows and the taskbar to fit them to each display, so it can interfere with DisplayFusion's ability to do the same.

The biggest thing you might run into if you don't disable the helpers is that the Windows taskbar may move around on the display when entering/exiting full screen games.

There shouldn't be any downside to disabling them.

Thanks!

Nov 27, 2020 • #36

jjjjjj

72 discussion posts

Per my earlier comment (https://www.displayfusion.com/Discussions/View/nvidia-processes/?ID=6e976c8e-4e67-4e16-aa1b-fe309971f902#9)

Quote:

Also worth noting for anyone reading this, if your taskbar is stuck up (with auto hide on) after updating Nvidia drivers, that's due to nvsmartmaxapp(64).exe conflicting with DF (assuming you're using DF taskbars).

there are definitely some more serious/annoying issues you'll run into.

Nov 27, 2020 • #37

joeg

6 discussion posts

Ah so this might relate to a couple peculiarities I've experienced then.

I have nVidia Surround feature on. The Windows taskbar at the bottom middle screen sometimes shows up "behind" the DF taskbars either on the right or left screens. I've had to manually fix when this happens by setting the DF taskbar to Autohide and then dragging the Windows one back to the center. Annoying, but manageable.

The more frustrating thing that's happened once now is that the Windows taskbar in the center screen "floats" above the bottom of the screen with a margin equal to that of another taskbar, as if the DF taskbar were there below it. When I drag the Windows taskbar around - like to the top of the screen, the DF taskbars move in kind. But putting the Windows bar back at the bottom does not fix. When this has happened I could only resolve by rebooting.

I guess next time I see that notice about the nVidia processes I will tell DF to disable them. Hopefully that remedies both of these peculiarities. I just wanted to make sure it isn't meant to disable the nVidia Control Panel, Surround features, etc.

Thanks! Enjoying this software and appreciate the forum here.

Nov 27, 2020 • #38

Yep, those would definitely be caused by the conflict with the NVIDIA helpers

If DisplayFusion doesn't prompt you again, check the DisplayFusion Settings > Advanced Settings to make sure the "Don't Check nVidia Processes" is not enabled.

Dec 2, 2020 • #39

Was this helpful?

(1)

(-)