Jump to content

Disabled LOD_ERR


J3tAc3

Recommended Posts

Hello there. I've been having trouble with The Courier's Cache mod that keep generating this in my NVAC log:

13233512 _ DISABLED _LOD_ERR
13233512 e 006FCF03 C0000005 FalloutNV.exe
13233512 _ DISABLED _LOD_ERR
13233512 e 006FCF03 C0000005 FalloutNV.exe
13233512 _ DISABLED _LOD_ERR
13233529 _ 00400000 00000000 FalloutNV.exe

 

What does this mean? Other mods generated Disabled LOD ERR entries as well, even though I did an xEdit QuickAutoClean and reopened and saved the esp's in the GECK. Is it possible to correct this mod or is it simply messed up and fixable only by the author?

Link to comment
Share on other sites

You have two different problems:

 

1) "LOD" stands for "Level Of Detail", referring to the "lesser detail" you see in the mid- to background portion of the rendered image as opposed to the high level of detail you expect to see in the foreground. Recommend you read the 'LOD/VWD Texture Packs' section of the wiki "FNV General Mod Use Advice" article.

 

If you add (or remove) any VWD/LOD textures (such as NMC, Vurt's WFO, or Ojo Bueno), please see the 'Checklist Item #15 & 16' entries in the wiki "Fallout NV Mod Conflict Troubleshooting" guide regarding the need to run both TES4LL and FNVLODGen; or xLODGen - Terrain LOD beta for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL.

 

2) "NVAC - New Vegas AntiCrash" error log entries are described on the "Description" page. This an important log for "in-game" errors. Some are intended to assist mod authors; while others are there to help "you, the player" trying to resolve a problem. You are interested in the entries which are NOT automatically handled successfully by NVAC. Key entries to look for are the following "letter codes":

"_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs
"e" entries are Exceptions handled specifically by NVAC's targeted code changes. In particular, you are getting "0xC0000005" exceptions.

 

"Windows Exception code: 0xc0000005". The "Faulting Application" is often the victim of another program rather than the actual culprit, making it virtually impossible for the user to trace the source. Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running. Run AV from multiple sources when checking for infections. There are a number of free online scanners on the internet (though they are all going to try to sell you their services after the first time).

You may need to exclude FNV from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)". Please see "Issue - NVSE - fails to load after update KB4058043 to Win10 FCU v1709" under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article.

Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode once you have scanned since the last connection), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering. There are also tools (often called "Game Boosters") to help you determine "unnecessary when offline" Windows services you can temporarily shut down.

It is also possible that any recent change to your mods (such as updates) or your existing "load order" (such as additions or removals) have causes a corruption of the current save game file. Try going back to a save game from before the problem started. Often starting a "new game" with a vanilla test character can help confirm if the problem lies in the current load order.

-Dubious-

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...