Results 1 to 9 of 9

Hybrid View

  1. #1
    Player
    Judge_Xero's Avatar
    Join Date
    Mar 2011
    Location
    Ul'dah
    Posts
    2,228
    Character
    Divine Gate
    World
    Exodus
    Main Class
    Marauder Lv 60
    Just wanted to add, that after doing some research it seems in some cases that parts of the Driver Install are blocked by Windows.

    You can try this as well.

    Download Drivers -> Right Click -> Run as Administrator -> Custom -> Clean Install

    That should allow it to fully install without any parts of the Driver being blocked.

    The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    (0)
    "I don't always drink beer, but when I do, it's often."
    Temp Forum Ban - July 7th 2016 *** I promise to never call out scrub players again due to it causing a toxic community

  2. #2
    Player
    Kuraran's Avatar
    Join Date
    Sep 2013
    Posts
    169
    Character
    Shalltear Bloodfallen
    World
    Shiva
    Main Class
    Machinist Lv 70
    Quote Originally Posted by Judge_Xero View Post
    Just wanted to add, that after doing some research it seems in some cases that parts of the Driver Install are blocked by Windows.

    You can try this as well.

    Download Drivers -> Right Click -> Run as Administrator -> Custom -> Clean Install

    That should allow it to fully install without any parts of the Driver being blocked.
    I've installed several older drivers this way now, after uninstalling them with DDU but I'm still getting the same errors over and over again.
    I've never had these kinds of errors on my old PC.
    From what I've heard from my friend (who has the said old PC now) is, that after he installed everything completely new, he also got the same errors generated.

    So I'm not sure if the fault is with the drivers themselves or if there is a driver conflict somewhere between drivers, or if the HW may be faulty (I sure as hell hope it's not the last) but it's really getting frustrating.

    Been in contact with Nvidia Support for the past weeks because of this but still haven't got a solution on this @.@
    (0)