Absovec Posted April 12, 2020 Share Posted April 12, 2020 I'm trying to find out what mod makes my game crash, nvac.log has very poor info 12195739 _ NewVegasAntiCrash FalloutNV.exe 12195739 _ 0AF30000 07050000 nvac.dll 12195739 p 00C44280 9272FBE9 FalloutNV.exe 12195739 ! SPOT_CHE CK_FAIL_ FalloutNV.exe 12195739 p 00401170 0441B60F FalloutNV.exe 12195739 ! SPOT_CHE CK_FAIL_ FalloutNV.exe Link to comment Share on other sites More sharing options...
dubiousintent Posted April 13, 2020 Share Posted April 13, 2020 In general, unless you are the mod author, most error codes are not going to help you beyond pointing to the file encountering the problem. When the file in question is "FalloutNV.exe" (the main game executable), you need to look for Windows "Eventlog" messages to get a clearer idea. That is usually an indication that the game is the "victim" of some other program rather than the "cause". Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article."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":* "e" entries are Exceptions handled specifically by NVAC's targeted code changes* "h" entries are exceptions identified Heuristically by NVAC's "global" exception handler, sometimes handled unsuccessfully.* "m" entries are "Middle of nowhere" exceptions, sometimes handled unsuccessfully.* "ñ" entries are Null instruction exceptions, sometimes handled unsuccessfully.* "n" entries are Null pointer call exceptions, sometimes handled unsuccessfully.* "o" entries are stack Overflow exceptions, usually handled unsuccessfully.* "q" entries are program self-termination information; these are effectively crashes.* "u" entries are Unhandled exceptions reported from the Unhandled Exception Filter; these are crashes (and the NVAC author wants to hear about them).* "v" entries are unhandled exceptions reported by NVAC's "global" exception handler; these are crashes.* "w" entries are informative, relaying exception information as it passes through New Vegas's final exception handler.* "x" entries are critical errors in Windows exception data; these entries should never occur.* ":" entries are output from OutputDebugString calls.* ";" entries are output from the game's own error checking.Other codes may be of interest, but are not things the player is likely to be able to resolve, They are useful for informing the author of the mod to aid them in fixing their plugin. In particular, pass along the* "_" entries are informative, relaying that NVAC was loaded and the base address of various DLLs* "!" entries are informative, relaying human-readable text for the userentries.Any error codes found in the log but not listed on the mod "Description" page should be reported to the NVAC comments page. -Dubious- Link to comment Share on other sites More sharing options...
lStewieAl Posted April 15, 2020 Share Posted April 15, 2020 (edited) Unfortunately the log you posted contains no useful information, there are no other mods than NVAC that provide such logs. Edited April 15, 2020 by lStewieAl Link to comment Share on other sites More sharing options...
Recommended Posts