Atomfix | NVIDIA GeForce Forums

Update avatar

or drag an image

PNG, GIF, JPG, or BMP. File must be at least 160x160px and less than 600x600px.

Atomfix

User

15

Total Comments

0

Total Topics

15 Comments 0 Topics

ManuelGuzmanNV said:
Atomfix said:Any news on the Code 43 errors and Event ID 14 on 1000 series GPU's? When playing Titanfall 2 for some period of times, the PC either hangs or just restarts with no BSOD. Still not fixed. Looking at the first OP post at known issues "2434721-Eventid 14 error on boot with Turing cards if CSM is disabled" This also happens on my 1070 Ti which is a Pascal.
The event ID I mentioned in the open bugs is specific to RTX 20 series cards as far as I can tell. It is fixed and will be in our next driver. As for the code 43 issue, it sounds like possibly a hardware issue with your card and it falling off the bus after some period.
Any idea how I could fix it? I've stressed test both GPU and CPU at the same time for well over an hour without any problems. But as soon as I play Titanfall 2, it crashes at random intervals, sometimes it will play fine. PC will either hang or restart with no BSOD. Logged in event viewer in Windows.

Any news on the Code 43 errors and Event ID 14 on 1000 series GPU's? When playing Titanfall 2 for some period of times, the PC either hangs or just restarts with no BSOD. Still not fixed. Looking at the first OP post at known issues "2434721-Eventid 14 error on boot with Turing cards if CSM is disabled" This also happens on my 1070 Ti which is a Pascal.

I have a 650W Superflower Leadex PSU. I also get this Code 43. Defo not a PSU issue I don't think.

MoKiChU said:Hi, This is a known issue :
2434721-Eventid 14 error on boot with Turing cards if CSM is disabled
I also get this error on my GTX 1070 Ti card. Whether CSM is disabled or enabled. It doesn't seem that Nvidia want's to fix this issue.

Sora said:that sounds like a power flow issue, how old is the psu?
If your on about mine. The PSU is 2 years old. It used to power my old 1055T @ 4.2GHz and a GTX 770 but the PSU doesn't even have a years runtime yet, Even though I've owned it for 2 years, the old Crosshair V mobo I had died before I replaced it with the Ryzen system a year later.

Sora said:that sounds like a power flow issue, how old is the psu?
If your on about mine. The PSU is 2 years old. It used to power my old 1055T @ 4.2GHz and a GTX 770 but the PSU doesn't even have a years runtime yet, Even though I've owned it for 2 years, the old Crosshair V mobo I had died before I replaced it with the Ryzen system a year later.

I've got a Superflower Leadex 650W PSU myself paired up with a Ryzen 1700 and a GTX 1070 Ti. I've also been getting this code 43 in event viewer after playing Titanfall 2 for such and such a time. Computer either hangs, or just restarts with no BSOD. A clean install of Windows 10 with the latest driver from Nvidia still resulted in the same.

I've got a Superflower Leadex 650W PSU myself paired up with a Ryzen 1700 and a GTX 1070 Ti. I've also been getting this code 43 in event viewer after playing Titanfall 2 for such and such a time. Computer either hangs, or just restarts with no BSOD. A clean install of Windows 10 with the latest driver from Nvidia still resulted in the same.

With HDR enabled, the older and new drivers, it can change the colour of the text in the game to blue or black "Titanfall 2"

Sora said:
MrAgapiGC said:Update # everytime i lock the computer and put my pin, and enter event viewer same error apperar twice The description for Event ID 14 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. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000002 000000c0 ff1fe208 00000007 00000000 The message resource is present but the message was not found in the message table ------------------- The description for Event ID 14 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. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000001 000000c0 ff1fe203 00000007 00000000 The message resource is present but the message was not found in the message table
thats a uefi support issue in the present driver can work around it with the csm module support.
CSM is enabled for me, still I get the occasional hangs. Also the same with the users of Overclock.net.

With CSM enabled in BIOS. I just had another hang whilst playing Titanfall 2, upon checking event viewer, it's once again "nvlddmkm" Event 14. Had no BSOD when it hang.

Undon3 said:
Atomfix said:Not sure if it's been disccussed yet. I've recently bought a new 1070Ti, Using the latest drivers from Nvidia and playing Titanfall 2, I sometimes get random crashes that causes my computer to hang, or reboot with no BSOD. Checking Event Viewer in Windows 10, it shows the error to be "nvlddmkm" when it hang. Card is not overclocked.
Is this the last BIOS? This error happened before (including on my PC) without any instability and was fixed with a new driver. Now all is fine though and I pretty much always use UEFI only booting and Secure Boot. If there's a new BIOS for your motherboard you can give that a shot or just wait for the next driver, that is if Manuel saw these errors returning. By the way, that Event 14 is not the crash. That should be another event. You should do a bit more digging in the Reliability History and Event Viewer, also use the AppCrashView and BlueScreenView apps see what they say about the actual crash cause. Launch them as admin.
Yeah, using the latest BIOS for my K5 X370, I would screen shot my Event Viewer, but all the old logs have now been overwritten. Looking at the Event Viewer, there's at least 20 or so related errors that bears the name of "nvlddmkm" right before it hangs, all of them has the Event 14 code

Sora said:turn on CSM, or use an older driver.
Enabled CSM. So far so good, no hangs yet. Is this driver fixable or is it a case of an AGESA update?

Sora said:that event is due to a UEFI boot issue, but this time its manifesting as stability issues too.
Is there an official fix for it? Or do we wait for a driver update?

Not sure if it's been disccussed yet. I've recently bought a new 1070Ti, Using the latest drivers from Nvidia and playing Titanfall 2, I sometimes get random crashes that causes my computer to hang, or reboot with no BSOD. Checking Event Viewer in Windows 10, it shows the error to be "nvlddmkm" when it hang. Card is not overclocked. I've even tried a clean install of Windows 10 and the Nvidia drivers and it's still the same. I've used MSI Kombuster for 30 minutes without error or artifacts. I've made a thread about this on Overclock.net, and another user with the same error has also made a thread relating to "nvlddmkm" 1080Ti Crashing 1070Ti Crashing At first I thought it was MSI Afterburner, but It's started again even with Zotac Firestorm installed. I'll try Nvidia's hotfix driver. But I doubt that will fix it.
[The description for Event ID 14 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. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: \Device\Video3 CMDre 00000000 00000080 00000000 00000005 0000001a The message resource is present but the message was not found in the message table

append * for a wildcard search

All Results

0 communities

0 support

0 discussion

0 feature requests

Filters

This site requires Javascript in order to view all its content. Please enable Javascript in order to access all the functionality of this web site.Here are the instructions how to enable JavaScript in your web browser.