RecktalBear Posted February 4 Share Posted February 4 I am just now getting heavier into modding and am starting to read logs to stay my hand at a million posts you can look up on forums. I have look around for a couple days and cant find the Indian guys on youtube explaining mods lol. Long story short I am having trouble identifying what mod is in error on the SKSE log. For example... -------------------------------------------------------------------------------------------------------------------- PROBABLE CALL STACK: [ 0] 0x7FF77C9D160C SkyrimSE.exe+046160C -> 28503+0x9C movzx r12d, byte ptr [r13+0x1A] [ 1] 0x7FF77C9D1155 SkyrimSE.exe+0461155 -> 28501+0x255 nop [ 2] 0x7FF77C9D0E94 SkyrimSE.exe+0460E94 -> 28499+0x54 mov rbx, [rsp+0x30] [ 3] 0x7FF77C9FEF68 SkyrimSE.exe+048EF68 -> 29472+0x28 cmp byte ptr [rdi+0x20], 0x00 [ 4] 0x7FF77C9F47C6 SkyrimSE.exe+04847C6 -> 29262+0x326 cmp byte ptr [rsp+0x58], 0x00 (It goes 0-34, I'm assuming its 34 mods in error?) -------------------------------------------------------------------------------------------------------------------- Is "0x7FF77C9D160C" the identifier? If so how do I search or figure it our? Is there an easier way and I'm like a caveman banging rocks? Thank you, please school me in anything else you can teach me! Link to comment Share on other sites More sharing options...
Hietanen Posted February 4 Share Posted February 4 Either post the log for us to decipher, or use an analyzer like this one: https://phostwood.github.io/crash-analyzer/skyrim.html 1 Link to comment Share on other sites More sharing options...
scorrp10 Posted February 4 Share Posted February 4 Sorry, both of your assumptions are entirely wrong. 34 is the call stack depth and has absolutely nothing to do with 'number of mods'.(just google "call stack trace") And the large hex number is address of the instruction in memory - generally a useless info without a debug symbol table. With a table, a stack trace might look something like: #0 0x00007f5aa69cc387 in raise () from /lib64/libc.so.6 #1 0x00007f5aa69cda78 in abort () from /lib64/libc.so.6 #2 0x0000000000592297 in failFast (abort=true, sendHPOpenViewNotificationIfEnabled=false) at error_utils.cpp:77 #3 0x00000000005aa343 in check_available_memory(int, const char *, typedef __va_list_tag __va_list_tag *) (new_total_alloc_size=2097152256, entity=0x7bf3f8 "enqueueing derive message", args=0x7ffebb4e5610) at g_memory_x.cpp:869 #4 0x00000000005a889a in cfts_v_g_real_alloc(int, const char *, typedef __va_list_tag __va_list_tag *) (byte_size=632, entity=0x7bf3f8 "enqueueing derive message", args=0x7ffebb4e5610) at g_memory_x.cpp:259 #5 0x00000000005a9171 in cfts_v_g_alloc(int, const char *, typedef __va_list_tag __va_list_tag *) (byte_size=130, entity=0x7bf3f8 "enqueueing derive message", args=0x7ffebb4e5610) at g_memory_x.cpp:478 #6 0x00000000005a8be7 in cfts_g_alloc (byte_size=130, entity=0x7bf3f8 "enqueueing derive message") at g_memory_x.cpp:357 #7 0x00000000005a9513 in Dbg_g_alloc (byte_size=130, pFileName=0x7beb45 "common_funcs.cpp", LineNum=1738, entity=0x7bf3f8 "enqueueing derive message") at g_memory_x.cpp:571 #8 0x0000000000597bdd in enqueueDerive (ptPrmTrdSys=0x7ffebb4e5ab0, ptPrmFifoHeader=0x7ffebb4e5840) at common_funcs.cpp:1738 #9 0x0000000000597e4a in enqueueDeriveMarketUpdate (tsID=1050, instrumentName=0x7f59c4e3c7ec "AUCTION_SECID_1663060", instUsage=0, auctionAction=AUCTION_ACTION_NONE, trdSys=0x7ffebb4e5ab0) at common_funcs.cpp:1790 #10 0x00000000005451d9 in CTradeManager::UpdateMarketUserId (this=0xb28c00 <CTradeManager::Instance()::s_AdminManager>, ulPrmTsId=1050, ulPrmUserId=380242307) at trade.cpp:1544 (And no, THAT is not from Skyrim) 1 Link to comment Share on other sites More sharing options...
RecktalBear Posted February 4 Author Share Posted February 4 2 hours ago, Hietanen said: Either post the log for us to decipher, or use an analyzer like this one: https://phostwood.github.io/crash-analyzer/skyrim.html Oh wow! Thank you for this! What a time to live in. Link to comment Share on other sites More sharing options...
RecktalBear Posted February 4 Author Share Posted February 4 2 hours ago, scorrp10 said: Sorry, both of your assumptions are entirely wrong. 34 is the call stack depth and has absolutely nothing to do with 'number of mods'.(just google "call stack trace") And the large hex number is address of the instruction in memory - generally a useless info without a debug symbol table. With a table, a stack trace might look something like: #0 0x00007f5aa69cc387 in raise () from /lib64/libc.so.6 #1 0x00007f5aa69cda78 in abort () from /lib64/libc.so.6 #2 0x0000000000592297 in failFast (abort=true, sendHPOpenViewNotificationIfEnabled=false) at error_utils.cpp:77 #3 0x00000000005aa343 in check_available_memory(int, const char *, typedef __va_list_tag __va_list_tag *) (new_total_alloc_size=2097152256, entity=0x7bf3f8 "enqueueing derive message", args=0x7ffebb4e5610) at g_memory_x.cpp:869 #4 0x00000000005a889a in cfts_v_g_real_alloc(int, const char *, typedef __va_list_tag __va_list_tag *) (byte_size=632, entity=0x7bf3f8 "enqueueing derive message", args=0x7ffebb4e5610) at g_memory_x.cpp:259 #5 0x00000000005a9171 in cfts_v_g_alloc(int, const char *, typedef __va_list_tag __va_list_tag *) (byte_size=130, entity=0x7bf3f8 "enqueueing derive message", args=0x7ffebb4e5610) at g_memory_x.cpp:478 #6 0x00000000005a8be7 in cfts_g_alloc (byte_size=130, entity=0x7bf3f8 "enqueueing derive message") at g_memory_x.cpp:357 #7 0x00000000005a9513 in Dbg_g_alloc (byte_size=130, pFileName=0x7beb45 "common_funcs.cpp", LineNum=1738, entity=0x7bf3f8 "enqueueing derive message") at g_memory_x.cpp:571 #8 0x0000000000597bdd in enqueueDerive (ptPrmTrdSys=0x7ffebb4e5ab0, ptPrmFifoHeader=0x7ffebb4e5840) at common_funcs.cpp:1738 #9 0x0000000000597e4a in enqueueDeriveMarketUpdate (tsID=1050, instrumentName=0x7f59c4e3c7ec "AUCTION_SECID_1663060", instUsage=0, auctionAction=AUCTION_ACTION_NONE, trdSys=0x7ffebb4e5ab0) at common_funcs.cpp:1790 #10 0x00000000005451d9 in CTradeManager::UpdateMarketUserId (this=0xb28c00 <CTradeManager::Instance()::s_AdminManager>, ulPrmTsId=1050, ulPrmUserId=380242307) at trade.cpp:1544 (And no, THAT is not from Skyrim) Kick ass, thank you! That's gives me a lot to google and learn up on. I appreciate it! Link to comment Share on other sites More sharing options...
RecktalBear Posted February 4 Author Share Posted February 4 3 hours ago, Hietanen said: Either post the log for us to decipher, or use an analyzer like this one: https://phostwood.github.io/crash-analyzer/skyrim.html Well, after a couple hours, I got the log to be a lot smaller by reinstalling or re-prioritizing them on the list, but there are a couple eluding me If you could help? or anyone. Attached is the log. Im seeing KERNEL32.DLL and ntdll.dll. [2] (KERNEL32.DLL ... unlikely culprit) [2] (ntdll.dll ... unlikely culprit) I did a health check and fsc scan to see If there were errors, none. Google is near useless on saying "Its Windows", but knowing computers its not that simple yeah? Not to spam alert you Hietanen! CrashLogger.log Link to comment Share on other sites More sharing options...
Hietanen Posted Wednesday at 04:44 PM Share Posted Wednesday at 04:44 PM The Crash Logger log you attached is not the actual crash log, so it is of no use to me. Please if you need help, attach the other crash logger log. Link to comment Share on other sites More sharing options...
RecktalBear Posted Wednesday at 09:52 PM Author Share Posted Wednesday at 09:52 PM 5 hours ago, Hietanen said: The Crash Logger log you attached is not the actual crash log, so it is of no use to me. Please if you need help, attach the other crash logger log. I Pm'ed it, thank you! Link to comment Share on other sites More sharing options...
Recommended Posts