Share via

Event ID 13 occured at time of reoccuring crash. Need help fixing.

Anonymous
2018-04-01T04:20:38+00:00

I'm facing black screen crashes regularly, and this most recent one came during a game, just after I "Reset" Windows 10 without keeping any original system contents. Essentially a fresh installation of Windows 10, almost. 

Event Viewer logged the error at time of crash, Event ID 13, 30 times at the exact moment it occured, and the error description reads identical every time in the general tab, with one variation being under \Device\Video3.

Here's what the two Error descriptions state under General, 1 after another 30 times: 

Event ID 13: 

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.

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

Variable String too Large

the message resource is present but the message is not found in the string/message table"

Event ID 13

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.

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

NVRM: Graphics TEX Exception on (GPC 2, TPC 1):     TEX NACK / Page Fault

the message resource is present but the message is not found in the string/message table

How can I fix this and what is causing it?

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2018-04-05T23:58:59+00:00

    I appreciate the comprehensive response. Based on the information that you've provided, it's clear that you we're able to rule out any software related errors which may possibly contribute to the black screen error. It is a good approach to now engage the graphics card manufacturer regarding this matter to check any underlying issues that's related to the actual unit. Alternatively, you can perform some test using the on-board graphics card to further isolate the issue.

    Feel free to post back should you need further assistance.

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-04-05T00:53:11+00:00

    With all that said, 

    1. As a follow up to your your 3rd question: 

    I've since:

    • "Reset" Windows 10 with personal files
    • "Reset" Windows 10 without personal files, and fresh. 
    • Installed a fresh Windows 10 Live Disc, deleting all original disk partitions during the process. 
    • Inadvertently rolled back display drivers to 388.13 (via fresh OS installation)
    • Thoroughly ran native and non-native System tools to troubleshoot such as
    • Dism Image Servicing Utility
    • System File Checker
    • Windows Memory Diagnostic
    • Apps Diagnostic 10 (for app store related error as shown in Event Viewer)
    • Tweaking.com's Windows Repair AIO
    • and posted over onto Nvidia's forums. Here's my newly revised Nvidia Forum post

    https://forums.geforce.com/default/topic/1045739/geforce-1000-series/i-really-need-help-constant-system-crashes-and-error-code-13-is-this-new-1080ti-faulty-/

    1. For your 2nd question: "Have you made any changes on your device prior to your concern?"

    The system itself was brand new, 3 or so months to be exact. Look to link above for more info on the hardware.

    If by device you're referring to anything other than hardware, nothing out of the ordinary. Bits of software and windows apps that we're not contaminated by anything. With that said I was considering running TronScript sometime soon just to cross that off the list as well... Running out of ideas though. 

    3) For your 1st request, here's my OS: 

    Windows Specifications:

    ^Edition:^ ^Windows^ ^10^ ^PRO^

    ^Version:^ ^1709^

    ^OS^ ^Build:^ ^16299.309^

    4) Regarding the support article and my device drivers

    Thanks for that resource. I've already covered my Drivers in points 1 & 2. Feel free to let me know if there's more info or steps I can provide or take.

    1. My big question is this:

    Does the error listed in Original Post suggest that the problem is in fact software/system related? If not, does that mean that the problem may in fact be due to hardware malfunction? I've already began in a discussion in the Nvidia forums just in preparation for this fact. 

    Thank you so, so much for the reply. I've been at this investigation for a month, with many forum posts across many websites, and your post has undoubtedly been the most constructive and informative. 

    Best of luck to us...

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-04-04T23:56:06+00:00

    Hi none8,

    I'd like to confirm if you're still experiencing the same screen error? If yes, this concern regarding the sudden black screen can be related to a possible driver error or corrupted system file. To effectively assist you with your concern, I'd like to confirm the information below:

    • Which Windows build version is running on your device? Type winver in the search box and press Enter to help you identify.
    • Have you made any changes on your device prior to your concern?
    • What are the step that you've already performed to resolve your concern?

    On the other hand, the Event ID 13 along with the error that you received is related to your display driver. To rule out any driver related issues, I suggest that you update the display driver installed on your device. To do this, follow the steps provided on this support article. In the event that the driver was already updated and still the issue persists, our next option is to reinstall the affected driver as detailed in the same article. Once you're done check if you'll encounter the same error.

    Looking forward to your response.

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-04-05T00:32:24+00:00

    Hi,

    Yes I am still encountering this problem. I've listed a long post explaining more thoroughly the original problem, my original process for troubleshooting, as well as an additional reply responding to your individual questions. My hope is to rule out any internally related problems prior to moving onto hardware solutions. 

    Cheers

    Original Post, from 17 days ago:

    (NOTE: Symptoms of original issue have since been updated in a follow-up post below, in the link to Nvidia's Support Forums.)

    "The issue started last week during a session on Destiny 2. I hadn't been playing long, and I was in my inventory, but out of nowhere the screen froze to green with some intial game audio. I tried to recreate the problem by retracing my steps and repeating, and I was able to, so, I assumed it was perhaps that game. The problem continued, so I went over to Kingdom Come: Deliverance. After a somewhat longer session, green again. After a couple of days, the colors of the freezing changed. I tried out a different monitor (old school TV) in VGA mode and a hard FPS cap of 60 (typically uncapped and 140 FPS AVERAGE), and still, somehow I was getting freezing. Although, the colors were different. Now I was getting gray screens. Eventually, after a few more tests, I began getting black screens.

    I decided after this that it must have been GPU related, so I've taken all day today running rigorous stress tests on my GPU with an ambient temp of 22C, and I've been able to recreate the crash there, thankfully. This has all been on my original gaming monitor. 144HZ, 1440x2560 resolution. After around a 70C, or 6 minutes, is reached in 3dMark (Firestrike Extreme), I get a black screen and I can't get out of it, though I can sometimes still hear audio, and my system continues to labor. The fans don't settle, and the whole system seems to continue as if the stress test was still going.** The only way out of these frozen screens is to force shut down via the power switch**. What's unusual is that on Unigine Valley, while I stress test, the crash happens before temps can ever reach the 70C range, and don't exceed 66C being that the test is not as strenuous as 3dmark, but a crash will still occur after around 10 minutes of looping.

    Anyways, I don't know where to go from here. I've researched the internet for solutions or others in a similar position with similar equipment, and I haven't found that yet. There are a lot of issues with the latest Nvidia drivers, according to the subreddit, but my isssues arose before this. So i'm not too sure.


    Over the course of troubleshooting, so far I have:

    • updated firmware on my monitor. Not the solution.
    • updated to 391.01 Graphic drivers through Nvidia Geforce Experience. Not the solution.
    • rolled back to previous Driver 390.177 after implementing DDU in safe mode. Not the solution.
    • double and triple checked Windows Updates, and everything is. Not the solution.
    • ran System File Checker in case there was an issue there. Not the solution.
    • looked through the AsRock Updater to ensure Bios and Drivers were upto date, and with the exception of the Bios and ME (which I tend to stay away from), all is. Not the solution.
    • tried using an alternate display. Not the solution.
    • tried using a different output port on the GPU in which the results were all still the same, DP & HDMI. Not the solution.

    Please help. I don't know much and have expended all of the ideas I have without RMA'ing."

    0 comments No comments