Idiotinfrontofadesk Posted April 1, 2018 Share Posted April 1, 2018 31103234 M 76A772CB 80000001 KERNEL32.DLL31103234 r 00A31E4D 00000001 FalloutNV.exe31103234 M 00A31E51 80000001 FalloutNV.exe31103234 r 004AD22A 0000000E FalloutNV.exe31103234 n 00000000 0019001C31103234 r 004AD22A 0000000E FalloutNV.exe31103234 h 004AD22A 8945E4EB FalloutNV.exe Link to comment Share on other sites More sharing options...
dubiousintent Posted April 1, 2018 Share Posted April 1, 2018 They are described in general on the NVAC description page under "Deciphering the nvac.log file", with the letter codes below that. Using the first line of your log as an example:* The first number is a "timestamp". Not particularly significant except to tell when something occurred.* The letter code (e.g. "M") is a code for the "type of exception" (error). You need to look up this detail.* The second number (e.g. "76A772CB") is a memory address; for most entries this is the address of an exception (crash). Unless you are a skilled programmer with a "debugger" this won't be of any help to you.* The third number (e.g. "80000001") is an informative value; in this example, the version number of KERNEL32.DLL.* The last bit of information (e.g. "KERNEL32.DLL") is the module loaded at the logged address. In other words, this is the module that reported the error. It is not always the "cause" of the problem, but rather the victim of the effect (e.g. a memory leak by another program). When you combine the "module loaded at the logged address" with the "type of exception", you can search the web for other reports (from all sorts of programs, not just your game) and their solutions. Note that letter code"w" entries are informative, relaying exception information as it passes through New Vegas's final exceptionThis means the "third number" in such instances is the "Windows exception code" which can be even more precise in pinning down the exception type in your search. In very general terms I would say you have a problem with "memory leaks" causing things to point to areas of memory they are not allowed to modify. Please see 'Solutions to "Crash To Desktop" (CTD) problems' section in the wiki "Fallout NV Mod Conflict Troubleshooting" guide. You should also want to check out the "Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)" entry if you are on Win10. -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts