Nvidia graphics card no longer works in Windows 10 (error: Code 43) but works in Ubuntu












5














Currently, when I boot into Windows, one monitor stays black (undetected), and the other can only display 800x600 resolution.



When I look at Device Manager > Display Adapters > NVIDIA GeForce GTX 970 > General > Device Status, it says "Windows has stopped this device because it has reported problems. (Code 43)".



Details > Problem Code says "00002b". Details > Status says:



01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER


When I then click into the Events tab, it says "Device PCIVEN_10DE&DEV_13C2&SUBSYS_29763842&REV_A14&25438c51&0&0008 requires further installation."



I have a EVGA Nvidia GeForce GTX 970 graphics card with the latest drivers (376.19 from 12/1/2016).



My Windows 10 Pro has the latest updates and is at Version 1607, OS Build 14393.576.



My ASRock Z170 Pro4 motherboard BIOS is also updated to the latest version (7.00 from 10/4/2016).



I have dual Acer monitors with 1920x1080 resolution.



I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into the Ubuntu operating system instead of Windows. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why my video card has stopped working within Windows.



What I Have Tried




  • I've tried using Display Driver Uninstaller from Guru3d in Safe Mode to delete all drivers and try to install fresh.

  • I've tried many different versions of the driver dating back more than 12 months.

  • I've tried reseating the card.

  • I've tried moving the card to a different slot.

  • EVGA's phone support told me to reinstall windows (Windows > Reset this PC > Keep my files). Unfortunately, I followed their advice (and now don't have any of my programs), and I still get Code 43 with the EVGA Nvidia card.


What I Have NOT Tried




  • I would love to try installing this card onto a different Windows 10 computer to see what happens, but I don't have access to any other computers. If you live northeast of Atlanta, let me know. ;-)


I'd appreciate any other ideas you have!.










share|improve this question
























  • also try older drivers, not the latest one: nvidia.com/Download/Find.aspx?lang=en-us
    – magicandre1981
    Dec 14 '16 at 5:33






  • 1




    also put the GPU into a different PCIe x16 slot . also check if your PSU supports the required power of the GPU.
    – magicandre1981
    Dec 14 '16 at 5:40










  • @magicandre1981 Interesting update: I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into that. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why it stopped working within Windows.
    – Ryan
    Dec 14 '16 at 18:12








  • 1




    You wouldn't be the first to be in that situation. The drivers are different, or the Linux driver ignores the error. Have you looked for interesting errors in the Event Viewer?
    – harrymc
    Dec 17 '16 at 15:04






  • 1




    Another check in linux would be to run glxinfo and look for anything suspicious (Lot of output tho) or just run something that requires 3D acceleration. Maybe the reason it's still working is because it's using safe fallbacks?
    – Shadur
    Dec 20 '16 at 12:47
















5














Currently, when I boot into Windows, one monitor stays black (undetected), and the other can only display 800x600 resolution.



When I look at Device Manager > Display Adapters > NVIDIA GeForce GTX 970 > General > Device Status, it says "Windows has stopped this device because it has reported problems. (Code 43)".



Details > Problem Code says "00002b". Details > Status says:



01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER


When I then click into the Events tab, it says "Device PCIVEN_10DE&DEV_13C2&SUBSYS_29763842&REV_A14&25438c51&0&0008 requires further installation."



I have a EVGA Nvidia GeForce GTX 970 graphics card with the latest drivers (376.19 from 12/1/2016).



My Windows 10 Pro has the latest updates and is at Version 1607, OS Build 14393.576.



My ASRock Z170 Pro4 motherboard BIOS is also updated to the latest version (7.00 from 10/4/2016).



I have dual Acer monitors with 1920x1080 resolution.



I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into the Ubuntu operating system instead of Windows. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why my video card has stopped working within Windows.



What I Have Tried




  • I've tried using Display Driver Uninstaller from Guru3d in Safe Mode to delete all drivers and try to install fresh.

  • I've tried many different versions of the driver dating back more than 12 months.

  • I've tried reseating the card.

  • I've tried moving the card to a different slot.

  • EVGA's phone support told me to reinstall windows (Windows > Reset this PC > Keep my files). Unfortunately, I followed their advice (and now don't have any of my programs), and I still get Code 43 with the EVGA Nvidia card.


What I Have NOT Tried




  • I would love to try installing this card onto a different Windows 10 computer to see what happens, but I don't have access to any other computers. If you live northeast of Atlanta, let me know. ;-)


I'd appreciate any other ideas you have!.










share|improve this question
























  • also try older drivers, not the latest one: nvidia.com/Download/Find.aspx?lang=en-us
    – magicandre1981
    Dec 14 '16 at 5:33






  • 1




    also put the GPU into a different PCIe x16 slot . also check if your PSU supports the required power of the GPU.
    – magicandre1981
    Dec 14 '16 at 5:40










  • @magicandre1981 Interesting update: I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into that. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why it stopped working within Windows.
    – Ryan
    Dec 14 '16 at 18:12








  • 1




    You wouldn't be the first to be in that situation. The drivers are different, or the Linux driver ignores the error. Have you looked for interesting errors in the Event Viewer?
    – harrymc
    Dec 17 '16 at 15:04






  • 1




    Another check in linux would be to run glxinfo and look for anything suspicious (Lot of output tho) or just run something that requires 3D acceleration. Maybe the reason it's still working is because it's using safe fallbacks?
    – Shadur
    Dec 20 '16 at 12:47














5












5








5


3





Currently, when I boot into Windows, one monitor stays black (undetected), and the other can only display 800x600 resolution.



When I look at Device Manager > Display Adapters > NVIDIA GeForce GTX 970 > General > Device Status, it says "Windows has stopped this device because it has reported problems. (Code 43)".



Details > Problem Code says "00002b". Details > Status says:



01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER


When I then click into the Events tab, it says "Device PCIVEN_10DE&DEV_13C2&SUBSYS_29763842&REV_A14&25438c51&0&0008 requires further installation."



I have a EVGA Nvidia GeForce GTX 970 graphics card with the latest drivers (376.19 from 12/1/2016).



My Windows 10 Pro has the latest updates and is at Version 1607, OS Build 14393.576.



My ASRock Z170 Pro4 motherboard BIOS is also updated to the latest version (7.00 from 10/4/2016).



I have dual Acer monitors with 1920x1080 resolution.



I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into the Ubuntu operating system instead of Windows. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why my video card has stopped working within Windows.



What I Have Tried




  • I've tried using Display Driver Uninstaller from Guru3d in Safe Mode to delete all drivers and try to install fresh.

  • I've tried many different versions of the driver dating back more than 12 months.

  • I've tried reseating the card.

  • I've tried moving the card to a different slot.

  • EVGA's phone support told me to reinstall windows (Windows > Reset this PC > Keep my files). Unfortunately, I followed their advice (and now don't have any of my programs), and I still get Code 43 with the EVGA Nvidia card.


What I Have NOT Tried




  • I would love to try installing this card onto a different Windows 10 computer to see what happens, but I don't have access to any other computers. If you live northeast of Atlanta, let me know. ;-)


I'd appreciate any other ideas you have!.










share|improve this question















Currently, when I boot into Windows, one monitor stays black (undetected), and the other can only display 800x600 resolution.



When I look at Device Manager > Display Adapters > NVIDIA GeForce GTX 970 > General > Device Status, it says "Windows has stopped this device because it has reported problems. (Code 43)".



Details > Problem Code says "00002b". Details > Status says:



01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER


When I then click into the Events tab, it says "Device PCIVEN_10DE&DEV_13C2&SUBSYS_29763842&REV_A14&25438c51&0&0008 requires further installation."



I have a EVGA Nvidia GeForce GTX 970 graphics card with the latest drivers (376.19 from 12/1/2016).



My Windows 10 Pro has the latest updates and is at Version 1607, OS Build 14393.576.



My ASRock Z170 Pro4 motherboard BIOS is also updated to the latest version (7.00 from 10/4/2016).



I have dual Acer monitors with 1920x1080 resolution.



I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into the Ubuntu operating system instead of Windows. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why my video card has stopped working within Windows.



What I Have Tried




  • I've tried using Display Driver Uninstaller from Guru3d in Safe Mode to delete all drivers and try to install fresh.

  • I've tried many different versions of the driver dating back more than 12 months.

  • I've tried reseating the card.

  • I've tried moving the card to a different slot.

  • EVGA's phone support told me to reinstall windows (Windows > Reset this PC > Keep my files). Unfortunately, I followed their advice (and now don't have any of my programs), and I still get Code 43 with the EVGA Nvidia card.


What I Have NOT Tried




  • I would love to try installing this card onto a different Windows 10 computer to see what happens, but I don't have access to any other computers. If you live northeast of Atlanta, let me know. ;-)


I'd appreciate any other ideas you have!.







windows-10 drivers graphics-card resolution nvidia-graphics-card






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 27 '16 at 17:06









Dave

23.2k74362




23.2k74362










asked Dec 14 '16 at 4:47









Ryan

46911238




46911238












  • also try older drivers, not the latest one: nvidia.com/Download/Find.aspx?lang=en-us
    – magicandre1981
    Dec 14 '16 at 5:33






  • 1




    also put the GPU into a different PCIe x16 slot . also check if your PSU supports the required power of the GPU.
    – magicandre1981
    Dec 14 '16 at 5:40










  • @magicandre1981 Interesting update: I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into that. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why it stopped working within Windows.
    – Ryan
    Dec 14 '16 at 18:12








  • 1




    You wouldn't be the first to be in that situation. The drivers are different, or the Linux driver ignores the error. Have you looked for interesting errors in the Event Viewer?
    – harrymc
    Dec 17 '16 at 15:04






  • 1




    Another check in linux would be to run glxinfo and look for anything suspicious (Lot of output tho) or just run something that requires 3D acceleration. Maybe the reason it's still working is because it's using safe fallbacks?
    – Shadur
    Dec 20 '16 at 12:47


















  • also try older drivers, not the latest one: nvidia.com/Download/Find.aspx?lang=en-us
    – magicandre1981
    Dec 14 '16 at 5:33






  • 1




    also put the GPU into a different PCIe x16 slot . also check if your PSU supports the required power of the GPU.
    – magicandre1981
    Dec 14 '16 at 5:40










  • @magicandre1981 Interesting update: I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into that. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why it stopped working within Windows.
    – Ryan
    Dec 14 '16 at 18:12








  • 1




    You wouldn't be the first to be in that situation. The drivers are different, or the Linux driver ignores the error. Have you looked for interesting errors in the Event Viewer?
    – harrymc
    Dec 17 '16 at 15:04






  • 1




    Another check in linux would be to run glxinfo and look for anything suspicious (Lot of output tho) or just run something that requires 3D acceleration. Maybe the reason it's still working is because it's using safe fallbacks?
    – Shadur
    Dec 20 '16 at 12:47
















also try older drivers, not the latest one: nvidia.com/Download/Find.aspx?lang=en-us
– magicandre1981
Dec 14 '16 at 5:33




also try older drivers, not the latest one: nvidia.com/Download/Find.aspx?lang=en-us
– magicandre1981
Dec 14 '16 at 5:33




1




1




also put the GPU into a different PCIe x16 slot . also check if your PSU supports the required power of the GPU.
– magicandre1981
Dec 14 '16 at 5:40




also put the GPU into a different PCIe x16 slot . also check if your PSU supports the required power of the GPU.
– magicandre1981
Dec 14 '16 at 5:40












@magicandre1981 Interesting update: I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into that. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why it stopped working within Windows.
– Ryan
Dec 14 '16 at 18:12






@magicandre1981 Interesting update: I downloaded Ubuntu 16.04.1 LTS onto a bootable USB drive and booted into that. Both monitors immediately worked at full 1920x1080 resolution. So the hardware seems functional! My remaining challenge is to figure out why it stopped working within Windows.
– Ryan
Dec 14 '16 at 18:12






1




1




You wouldn't be the first to be in that situation. The drivers are different, or the Linux driver ignores the error. Have you looked for interesting errors in the Event Viewer?
– harrymc
Dec 17 '16 at 15:04




You wouldn't be the first to be in that situation. The drivers are different, or the Linux driver ignores the error. Have you looked for interesting errors in the Event Viewer?
– harrymc
Dec 17 '16 at 15:04




1




1




Another check in linux would be to run glxinfo and look for anything suspicious (Lot of output tho) or just run something that requires 3D acceleration. Maybe the reason it's still working is because it's using safe fallbacks?
– Shadur
Dec 20 '16 at 12:47




Another check in linux would be to run glxinfo and look for anything suspicious (Lot of output tho) or just run something that requires 3D acceleration. Maybe the reason it's still working is because it's using safe fallbacks?
– Shadur
Dec 20 '16 at 12:47










4 Answers
4






active

oldest

votes


















4





+50









I have searched the Web for solutions to the problem of
"Event ID 14 from source nvlddmkm", and it seems to be a problem of the
Nvidia driver. It also happens for you with the Windows generic driver,
because that driver also comes from Nvidia, although
normally behind the one found on the Nvidia website.



The only people who reported success were ones who uninstalled all Nvidia
software (see the utility Display Driver Uninstaller) and installed
an older version of the driver. As they only changed the Nvidia
driver, this is definitely a driver problem, born out by the fact
that it does not happen on Ubuntu.



Solution 1



Since this used to work, but doesn't any more, probably Windows has updated
the driver.
As first try, you could roll the driver back :




  1. Open Control Panel -> Device Manager, or enter Device Manager in WIN+X

  2. Locate the device

  3. Right-click and choose Properties

  4. Click the Driver tab

  5. Click Roll Back Driver

  6. Click Yes and then Close

  7. Your computer will automatically restart


Solution 2



If this does not work for you, you will have the time-consuming task
of finding a driver version that works.
Your current driver version is 376.33 from 2016.12.14.
Here are some driver versions that were reported as working:





  • 353.06 from 2015.5.31, reported as working here, but later retracted here.


  • 347.88 from 2015.3.17, reported as working here together with
    the procedure used


Prevent Windows Update from reinstalling the bad driver



Once you find a driver version that works for you, you will have the
problem of preventing Windows from automatically updating it again.
See this answer of mine for how to block these updates.






share|improve this answer























  • For the GTX 1080, use driver 368.25 - nvidia.com/content/DriverDownload-March2009/…
    – Erhannis
    Oct 11 '17 at 2:40



















3














Removed answer From OP




The RMA replacement just arrived from EVGA on 2016-12-27, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows







share|improve this answer























  • OP had put the answer in the post, so moved it to an answer!
    – Dave
    Dec 27 '16 at 17:08



















1














Your GPU may have hardware failure and need to be RMA'd or replaced.



Re: your comment https://superuser.com/a/948795/149636, my similar problem was caused by a faulty GPU. I had to RMA it, and the new one works great.



[What I could never figure out was either my bad one went bad at the same time as I did my upgrade to Win10 from Win7, or Win10 is using some (bad) part of the GPU that Win7 wasn't. I didn't try any other OS with the GPU, sorry. I did not have any other indication that the GPU was bad before I upgraded. It just literally stopped working the same week I upgraded.]






share|improve this answer



















  • 1




    ok, thanks for reporting that your GPU was damaged.
    – magicandre1981
    Dec 16 '16 at 5:17






  • 1




    I should have been more clear: my proposed answer to the OP's GPU problem is to RMA/replace his GPU because I believe it is due to hardware failure. I am definitely not requesting clarification from or critiquing the OP. I have clarified my answer.
    – mach
    Dec 19 '16 at 2:14










  • @mach The RMA replacement just arrived from EVGA, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows. This has been a painful 2-3 weeks. But the only remaining step is to get refunded from EVGA, and I'll be back to normal!
    – Ryan
    Dec 27 '16 at 16:50






  • 1




    @Ryan Good to hear!! Very interesting that you had such a similar experience.
    – mach
    Dec 28 '16 at 17:08



















0














I was getting same (Code 43) and tried everything. The problem has gone when I plugged monitor's HDMI from integrated graphics to actual video card HDMI.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1156317%2fnvidia-graphics-card-no-longer-works-in-windows-10-error-code-43-but-works-in%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    4





    +50









    I have searched the Web for solutions to the problem of
    "Event ID 14 from source nvlddmkm", and it seems to be a problem of the
    Nvidia driver. It also happens for you with the Windows generic driver,
    because that driver also comes from Nvidia, although
    normally behind the one found on the Nvidia website.



    The only people who reported success were ones who uninstalled all Nvidia
    software (see the utility Display Driver Uninstaller) and installed
    an older version of the driver. As they only changed the Nvidia
    driver, this is definitely a driver problem, born out by the fact
    that it does not happen on Ubuntu.



    Solution 1



    Since this used to work, but doesn't any more, probably Windows has updated
    the driver.
    As first try, you could roll the driver back :




    1. Open Control Panel -> Device Manager, or enter Device Manager in WIN+X

    2. Locate the device

    3. Right-click and choose Properties

    4. Click the Driver tab

    5. Click Roll Back Driver

    6. Click Yes and then Close

    7. Your computer will automatically restart


    Solution 2



    If this does not work for you, you will have the time-consuming task
    of finding a driver version that works.
    Your current driver version is 376.33 from 2016.12.14.
    Here are some driver versions that were reported as working:





    • 353.06 from 2015.5.31, reported as working here, but later retracted here.


    • 347.88 from 2015.3.17, reported as working here together with
      the procedure used


    Prevent Windows Update from reinstalling the bad driver



    Once you find a driver version that works for you, you will have the
    problem of preventing Windows from automatically updating it again.
    See this answer of mine for how to block these updates.






    share|improve this answer























    • For the GTX 1080, use driver 368.25 - nvidia.com/content/DriverDownload-March2009/…
      – Erhannis
      Oct 11 '17 at 2:40
















    4





    +50









    I have searched the Web for solutions to the problem of
    "Event ID 14 from source nvlddmkm", and it seems to be a problem of the
    Nvidia driver. It also happens for you with the Windows generic driver,
    because that driver also comes from Nvidia, although
    normally behind the one found on the Nvidia website.



    The only people who reported success were ones who uninstalled all Nvidia
    software (see the utility Display Driver Uninstaller) and installed
    an older version of the driver. As they only changed the Nvidia
    driver, this is definitely a driver problem, born out by the fact
    that it does not happen on Ubuntu.



    Solution 1



    Since this used to work, but doesn't any more, probably Windows has updated
    the driver.
    As first try, you could roll the driver back :




    1. Open Control Panel -> Device Manager, or enter Device Manager in WIN+X

    2. Locate the device

    3. Right-click and choose Properties

    4. Click the Driver tab

    5. Click Roll Back Driver

    6. Click Yes and then Close

    7. Your computer will automatically restart


    Solution 2



    If this does not work for you, you will have the time-consuming task
    of finding a driver version that works.
    Your current driver version is 376.33 from 2016.12.14.
    Here are some driver versions that were reported as working:





    • 353.06 from 2015.5.31, reported as working here, but later retracted here.


    • 347.88 from 2015.3.17, reported as working here together with
      the procedure used


    Prevent Windows Update from reinstalling the bad driver



    Once you find a driver version that works for you, you will have the
    problem of preventing Windows from automatically updating it again.
    See this answer of mine for how to block these updates.






    share|improve this answer























    • For the GTX 1080, use driver 368.25 - nvidia.com/content/DriverDownload-March2009/…
      – Erhannis
      Oct 11 '17 at 2:40














    4





    +50







    4





    +50



    4




    +50




    I have searched the Web for solutions to the problem of
    "Event ID 14 from source nvlddmkm", and it seems to be a problem of the
    Nvidia driver. It also happens for you with the Windows generic driver,
    because that driver also comes from Nvidia, although
    normally behind the one found on the Nvidia website.



    The only people who reported success were ones who uninstalled all Nvidia
    software (see the utility Display Driver Uninstaller) and installed
    an older version of the driver. As they only changed the Nvidia
    driver, this is definitely a driver problem, born out by the fact
    that it does not happen on Ubuntu.



    Solution 1



    Since this used to work, but doesn't any more, probably Windows has updated
    the driver.
    As first try, you could roll the driver back :




    1. Open Control Panel -> Device Manager, or enter Device Manager in WIN+X

    2. Locate the device

    3. Right-click and choose Properties

    4. Click the Driver tab

    5. Click Roll Back Driver

    6. Click Yes and then Close

    7. Your computer will automatically restart


    Solution 2



    If this does not work for you, you will have the time-consuming task
    of finding a driver version that works.
    Your current driver version is 376.33 from 2016.12.14.
    Here are some driver versions that were reported as working:





    • 353.06 from 2015.5.31, reported as working here, but later retracted here.


    • 347.88 from 2015.3.17, reported as working here together with
      the procedure used


    Prevent Windows Update from reinstalling the bad driver



    Once you find a driver version that works for you, you will have the
    problem of preventing Windows from automatically updating it again.
    See this answer of mine for how to block these updates.






    share|improve this answer














    I have searched the Web for solutions to the problem of
    "Event ID 14 from source nvlddmkm", and it seems to be a problem of the
    Nvidia driver. It also happens for you with the Windows generic driver,
    because that driver also comes from Nvidia, although
    normally behind the one found on the Nvidia website.



    The only people who reported success were ones who uninstalled all Nvidia
    software (see the utility Display Driver Uninstaller) and installed
    an older version of the driver. As they only changed the Nvidia
    driver, this is definitely a driver problem, born out by the fact
    that it does not happen on Ubuntu.



    Solution 1



    Since this used to work, but doesn't any more, probably Windows has updated
    the driver.
    As first try, you could roll the driver back :




    1. Open Control Panel -> Device Manager, or enter Device Manager in WIN+X

    2. Locate the device

    3. Right-click and choose Properties

    4. Click the Driver tab

    5. Click Roll Back Driver

    6. Click Yes and then Close

    7. Your computer will automatically restart


    Solution 2



    If this does not work for you, you will have the time-consuming task
    of finding a driver version that works.
    Your current driver version is 376.33 from 2016.12.14.
    Here are some driver versions that were reported as working:





    • 353.06 from 2015.5.31, reported as working here, but later retracted here.


    • 347.88 from 2015.3.17, reported as working here together with
      the procedure used


    Prevent Windows Update from reinstalling the bad driver



    Once you find a driver version that works for you, you will have the
    problem of preventing Windows from automatically updating it again.
    See this answer of mine for how to block these updates.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 20 '17 at 10:17









    Community

    1




    1










    answered Dec 18 '16 at 11:34









    harrymc

    252k12259560




    252k12259560












    • For the GTX 1080, use driver 368.25 - nvidia.com/content/DriverDownload-March2009/…
      – Erhannis
      Oct 11 '17 at 2:40


















    • For the GTX 1080, use driver 368.25 - nvidia.com/content/DriverDownload-March2009/…
      – Erhannis
      Oct 11 '17 at 2:40
















    For the GTX 1080, use driver 368.25 - nvidia.com/content/DriverDownload-March2009/…
    – Erhannis
    Oct 11 '17 at 2:40




    For the GTX 1080, use driver 368.25 - nvidia.com/content/DriverDownload-March2009/…
    – Erhannis
    Oct 11 '17 at 2:40













    3














    Removed answer From OP




    The RMA replacement just arrived from EVGA on 2016-12-27, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows







    share|improve this answer























    • OP had put the answer in the post, so moved it to an answer!
      – Dave
      Dec 27 '16 at 17:08
















    3














    Removed answer From OP




    The RMA replacement just arrived from EVGA on 2016-12-27, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows







    share|improve this answer























    • OP had put the answer in the post, so moved it to an answer!
      – Dave
      Dec 27 '16 at 17:08














    3












    3








    3






    Removed answer From OP




    The RMA replacement just arrived from EVGA on 2016-12-27, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows







    share|improve this answer














    Removed answer From OP




    The RMA replacement just arrived from EVGA on 2016-12-27, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows








    share|improve this answer














    share|improve this answer



    share|improve this answer








    answered Dec 27 '16 at 17:06


























    community wiki





    Dave













    • OP had put the answer in the post, so moved it to an answer!
      – Dave
      Dec 27 '16 at 17:08


















    • OP had put the answer in the post, so moved it to an answer!
      – Dave
      Dec 27 '16 at 17:08
















    OP had put the answer in the post, so moved it to an answer!
    – Dave
    Dec 27 '16 at 17:08




    OP had put the answer in the post, so moved it to an answer!
    – Dave
    Dec 27 '16 at 17:08











    1














    Your GPU may have hardware failure and need to be RMA'd or replaced.



    Re: your comment https://superuser.com/a/948795/149636, my similar problem was caused by a faulty GPU. I had to RMA it, and the new one works great.



    [What I could never figure out was either my bad one went bad at the same time as I did my upgrade to Win10 from Win7, or Win10 is using some (bad) part of the GPU that Win7 wasn't. I didn't try any other OS with the GPU, sorry. I did not have any other indication that the GPU was bad before I upgraded. It just literally stopped working the same week I upgraded.]






    share|improve this answer



















    • 1




      ok, thanks for reporting that your GPU was damaged.
      – magicandre1981
      Dec 16 '16 at 5:17






    • 1




      I should have been more clear: my proposed answer to the OP's GPU problem is to RMA/replace his GPU because I believe it is due to hardware failure. I am definitely not requesting clarification from or critiquing the OP. I have clarified my answer.
      – mach
      Dec 19 '16 at 2:14










    • @mach The RMA replacement just arrived from EVGA, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows. This has been a painful 2-3 weeks. But the only remaining step is to get refunded from EVGA, and I'll be back to normal!
      – Ryan
      Dec 27 '16 at 16:50






    • 1




      @Ryan Good to hear!! Very interesting that you had such a similar experience.
      – mach
      Dec 28 '16 at 17:08
















    1














    Your GPU may have hardware failure and need to be RMA'd or replaced.



    Re: your comment https://superuser.com/a/948795/149636, my similar problem was caused by a faulty GPU. I had to RMA it, and the new one works great.



    [What I could never figure out was either my bad one went bad at the same time as I did my upgrade to Win10 from Win7, or Win10 is using some (bad) part of the GPU that Win7 wasn't. I didn't try any other OS with the GPU, sorry. I did not have any other indication that the GPU was bad before I upgraded. It just literally stopped working the same week I upgraded.]






    share|improve this answer



















    • 1




      ok, thanks for reporting that your GPU was damaged.
      – magicandre1981
      Dec 16 '16 at 5:17






    • 1




      I should have been more clear: my proposed answer to the OP's GPU problem is to RMA/replace his GPU because I believe it is due to hardware failure. I am definitely not requesting clarification from or critiquing the OP. I have clarified my answer.
      – mach
      Dec 19 '16 at 2:14










    • @mach The RMA replacement just arrived from EVGA, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows. This has been a painful 2-3 weeks. But the only remaining step is to get refunded from EVGA, and I'll be back to normal!
      – Ryan
      Dec 27 '16 at 16:50






    • 1




      @Ryan Good to hear!! Very interesting that you had such a similar experience.
      – mach
      Dec 28 '16 at 17:08














    1












    1








    1






    Your GPU may have hardware failure and need to be RMA'd or replaced.



    Re: your comment https://superuser.com/a/948795/149636, my similar problem was caused by a faulty GPU. I had to RMA it, and the new one works great.



    [What I could never figure out was either my bad one went bad at the same time as I did my upgrade to Win10 from Win7, or Win10 is using some (bad) part of the GPU that Win7 wasn't. I didn't try any other OS with the GPU, sorry. I did not have any other indication that the GPU was bad before I upgraded. It just literally stopped working the same week I upgraded.]






    share|improve this answer














    Your GPU may have hardware failure and need to be RMA'd or replaced.



    Re: your comment https://superuser.com/a/948795/149636, my similar problem was caused by a faulty GPU. I had to RMA it, and the new one works great.



    [What I could never figure out was either my bad one went bad at the same time as I did my upgrade to Win10 from Win7, or Win10 is using some (bad) part of the GPU that Win7 wasn't. I didn't try any other OS with the GPU, sorry. I did not have any other indication that the GPU was bad before I upgraded. It just literally stopped working the same week I upgraded.]







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 20 '17 at 10:16









    Community

    1




    1










    answered Dec 15 '16 at 21:14









    mach

    1093




    1093








    • 1




      ok, thanks for reporting that your GPU was damaged.
      – magicandre1981
      Dec 16 '16 at 5:17






    • 1




      I should have been more clear: my proposed answer to the OP's GPU problem is to RMA/replace his GPU because I believe it is due to hardware failure. I am definitely not requesting clarification from or critiquing the OP. I have clarified my answer.
      – mach
      Dec 19 '16 at 2:14










    • @mach The RMA replacement just arrived from EVGA, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows. This has been a painful 2-3 weeks. But the only remaining step is to get refunded from EVGA, and I'll be back to normal!
      – Ryan
      Dec 27 '16 at 16:50






    • 1




      @Ryan Good to hear!! Very interesting that you had such a similar experience.
      – mach
      Dec 28 '16 at 17:08














    • 1




      ok, thanks for reporting that your GPU was damaged.
      – magicandre1981
      Dec 16 '16 at 5:17






    • 1




      I should have been more clear: my proposed answer to the OP's GPU problem is to RMA/replace his GPU because I believe it is due to hardware failure. I am definitely not requesting clarification from or critiquing the OP. I have clarified my answer.
      – mach
      Dec 19 '16 at 2:14










    • @mach The RMA replacement just arrived from EVGA, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows. This has been a painful 2-3 weeks. But the only remaining step is to get refunded from EVGA, and I'll be back to normal!
      – Ryan
      Dec 27 '16 at 16:50






    • 1




      @Ryan Good to hear!! Very interesting that you had such a similar experience.
      – mach
      Dec 28 '16 at 17:08








    1




    1




    ok, thanks for reporting that your GPU was damaged.
    – magicandre1981
    Dec 16 '16 at 5:17




    ok, thanks for reporting that your GPU was damaged.
    – magicandre1981
    Dec 16 '16 at 5:17




    1




    1




    I should have been more clear: my proposed answer to the OP's GPU problem is to RMA/replace his GPU because I believe it is due to hardware failure. I am definitely not requesting clarification from or critiquing the OP. I have clarified my answer.
    – mach
    Dec 19 '16 at 2:14




    I should have been more clear: my proposed answer to the OP's GPU problem is to RMA/replace his GPU because I believe it is due to hardware failure. I am definitely not requesting clarification from or critiquing the OP. I have clarified my answer.
    – mach
    Dec 19 '16 at 2:14












    @mach The RMA replacement just arrived from EVGA, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows. This has been a painful 2-3 weeks. But the only remaining step is to get refunded from EVGA, and I'll be back to normal!
    – Ryan
    Dec 27 '16 at 16:50




    @mach The RMA replacement just arrived from EVGA, and as soon as I installed the new hardware, both of my monitors worked at full resolution. So I guess even though the hardware seemed to work on Ubuntu, replacing the hardware was a solution for making it work on Windows. This has been a painful 2-3 weeks. But the only remaining step is to get refunded from EVGA, and I'll be back to normal!
    – Ryan
    Dec 27 '16 at 16:50




    1




    1




    @Ryan Good to hear!! Very interesting that you had such a similar experience.
    – mach
    Dec 28 '16 at 17:08




    @Ryan Good to hear!! Very interesting that you had such a similar experience.
    – mach
    Dec 28 '16 at 17:08











    0














    I was getting same (Code 43) and tried everything. The problem has gone when I plugged monitor's HDMI from integrated graphics to actual video card HDMI.






    share|improve this answer


























      0














      I was getting same (Code 43) and tried everything. The problem has gone when I plugged monitor's HDMI from integrated graphics to actual video card HDMI.






      share|improve this answer
























        0












        0








        0






        I was getting same (Code 43) and tried everything. The problem has gone when I plugged monitor's HDMI from integrated graphics to actual video card HDMI.






        share|improve this answer












        I was getting same (Code 43) and tried everything. The problem has gone when I plugged monitor's HDMI from integrated graphics to actual video card HDMI.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 24 '17 at 23:54









        Andrei

        173117




        173117






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1156317%2fnvidia-graphics-card-no-longer-works-in-windows-10-error-code-43-but-works-in%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Mouse cursor on multiple screens with different PPI

            Agildo Ribeiro

            Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”