Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


0xc0000409 - nvcpl.dll - NVidia control panel not launching

  • Please log in to reply
1 reply to this topic

#1 execute_me


  • Members
  • 2 posts
  • Local time:10:49 PM

Posted 28 June 2017 - 12:03 PM

The latest Nvidia driver update has broken my Nvidia control panel. The app doesn't even launch.

The driver works fine, it's just the control panel that is not working.

Here is the list of things I tried.

Roll back to my last restore point.

Reinstalling the driver (Including clean install).

Fully uninstall the driver (including deleting the files in program files) and install it again


Windows Version: 10.15063.447 (Version 1703) Education edition.

Here is the error in the event viewer.

Faulting application name: nvcplui.exe, version: 8.1.970.0, time stamp: 0x59388f91
Faulting module name: NVCPL.DLL, version:, time stamp: 0x593888d6
Exception code: 0xc0000409
Fault offset: 0x00000000003b8b28
Faulting process id: 0x33f8
Faulting application start time: 0x01d2f02effe27245
Faulting application path: C:\Program Files\NVIDIA Corporation\Control Panel Client\nvcplui.exe
Faulting module path: C:\WINDOWS\SYSTEM32\NVCPL.DLL
Report Id: 3775a0ce-3fc6-4b60-bf04-734b869a90fe
Faulting package full name: 
Faulting package-relative application ID: 

Any help would be appreciated. Thank you.

BC AdBot (Login to Remove)


#2 execute_me

  • Topic Starter

  • Members
  • 2 posts
  • Local time:10:49 PM

Posted 24 July 2017 - 06:31 AM


The problem still exists in build 16232.100

Edited by execute_me, 24 July 2017 - 06:33 AM.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users