Crash occurs whenever I get near the giant outside Whiterun

[jedi7000nathan/sevenbillionjedi]

Ok I've gone thru my crashlog now all my previous crashes have been tied in some way to plug-ins I've corrected those but now I'm getting this repeatitive crash whenever I try to get rid of the giant outside Whiterun. Here is a the code from Crash log. EXCEPTION_ACCESS_VIOLATION" at 0x7FF7D511F19F I've no idea what is causing this but it happens whenever I get close to the fight hell even sitting back taking a cheeky arrow shot and killing the guy with console commands causes a crash. I've no idea what the issue is. Should I do a restart of my run and hope that fixes it. Because I think it may be the case that my save has gotten corrupted to some degree.

[smr1957]

Rocky の投稿を引用：

smr1957 の投稿を引用：

As we keep telling people, crash logs are actually not much help.

This is a weird take you have. Have you read crash logs? And understand them? They can pinpoint you the issue to the dot. Crash logs most certainly are helpful.

Not to get off topic, as, again, this is not the place for it (there is a better place to discuss this than in someone's thread), but the experience over years that myself and others who have thousands of hours experience of helping in the forums, has been that they are, in the vast majority of cases, of no use, and if the individual had done troubleshooting the classic way, they would have discovered the issue, where as with using a "crash log" which often does NOT indicate the cause, they are still trying to figure things out days later. (And even where they were of use, the issue still could have been solved quicker using classic troubleshooting as described in the link I provided for troubleshooting the load order in post #10.)

As to OP, I can understand your frustration, however, if you are having issues continuously where you have needed troubleshoot 4 times in the past three months, you are doing something wrong. As to talking of doing this methods on a build of 1000+ mods, well this is EXACTLY how I would troubleshoot my 2300 mod build - of course, I basically never have these issues because I am extremely careful in my creating of a build (which is totally stable and CTD free) - but the few times I did, that is exactly how I went about troubleshooting, and I would find the issue in just a few hours.

Bottom line, I would STRONGLY suggest you review the guides linked in post #12. And, of course, never forget that Golden Rule of Modding.

[alexander_dougherty]

OP would be better advised to post their load order than a crash log.

[smr1957]

alexander_dougherty の投稿を引用：

OP would be better advised to post their load order than a crash log.

Though with a load order as large as the OP says (1000+ mods), it is assumed that the individual knows how to troubleshoot it for themself - if not, than the individual should not be making a build of that size. A person should never create a build that is larger than their ability to troubleshoot - and if they cannot, they need to make a smaller build.

Not to seem salty, but as the OP has said that they have had continuing issues, it would seem that they are exceeding their ability when it comes to modding the game - and there is nothing wrong with not being able to create a stable/CTD free game of that size, most cannot. Hence why I strongly recommend that they read the guides and start fresh with a much smaller build or a build using and following Vlad's guides.

[jedi7000nathan/sevenbillionjedi]

smr1957 の投稿を引用：

Rocky の投稿を引用：

This is a weird take you have. Have you read crash logs? And understand them? They can pinpoint you the issue to the dot. Crash logs most certainly are helpful.

Not to get off topic, as, again, this is not the place for it (there is a better place to discuss this than in someone's thread), but the experience over years that myself and others who have thousands of hours experience of helping in the forums, has been that they are, in the vast majority of cases, of no use, and if the individual had done troubleshooting the classic way, they would have discovered the issue, where as with using a "crash log" which often does NOT indicate the cause, they are still trying to figure things out days later. (And even where they were of use, the issue still could have been solved quicker using classic troubleshooting as described in the link I provided for troubleshooting the load order in post #10.)

As to OP, I can understand your frustration, however, if you are having issues continuously where you have needed troubleshoot 4 times in the past three months, you are doing something wrong. As to talking of doing this methods on a build of 1000+ mods, well this is EXACTLY how I troubleshoot my 2300 mod build - of course, I basically never have these issues because of am extremely careful in my creating of a build - but the few times I did, that is exactly how I went about troubleshooting, and I would find the issue in just a few hours.

Bottom line, I would STRONGLY suggest you review the guides linked in post #12. And, of course, never forget that Golden Rule of Modding.

Look one of those times wasn't my fault I had a VERY stable build then the in-game Bethesda mod manager messed everything up. What I don't understand is that this is virtually the same build as the one I used before the last order broke and I haven't added anything that touches that area of Skyrim that wasn't in my previous load-order and I didn't have a single crash with this specific area at all, I had even gotten halfway thru the companions chain on one playthrough.
I know the golden rules, here but I simply am not wanting to do something that would take me a week to get done correctly as that's about how long it took me to do it the last four times each time by the way; there has to be a better way to fix the problem then throwing the entire load order out and starting from scratch I've had enough of doing that to last me a life time, it didn't help that Vortex went and deleted my installed mods after the second attempt and I had to reinstall every single one of them. This is by the way the only issue I've had that I haven't been able to fix, the game works perfectly fine I can go to any part of the map I've tested it on Solstheim, Eastmarch Hjaalmarch, Falkreath and Riverwood along with Helgan and the Rift, everywhere except that specific spot at Pelegia Farms and Jorravaskr works perfectly normal no crashes no lag no unstabilty, its not even tied to the Companions or the Giant I've teleported them away from that spot and done the battle a good distance away talked to them normally had the conversation they always do no crashes. I go near Pelegia farm after that it crashes, I try to use live another life to start as a member of the Companions it crashes loading into Jorravaskr; everywhere else in the game works fine, so I'm 100% convinced at point that it is a script issue and tied specifically to the Companions chain and that should make sure that instead of having to sift thru a massive load-order destroying and rebuilding it from the ground up that my efforts should be directed at that specific area.

[smr1957]

Since you know exactly where the issue occurs, and it is specific to that one location, it should be easy to troubleshoot using the method outline in my linked Troubleshooting outline - which actually is quicker than every thing else. Simply put, there are no shortcuts when it comes to troubleshooting, no magic wands or quick fixes - unless it is a specific known unique issue that one of us recognizes. If you follow the linked outline there is no need to uninstall anything - you are just disabling everything, making a save in the problematic area with a vanilla game (after testing to ensure that it works), and then enabling them in groups till the crash occurs, and then isolating it to the specific mod in that group - all following that linked outline.

As I said, I apologize if I seem a little abrupt about this, but this really is the best way if you want to fix the game with your current build.

[smr1957]

Okay, here is a possibility. If you think it is tied to one of the Companions (maybe a facegen issue?), then, with your full load order, use the moveto player command for each Companion individually. If it is one of them, the game will CTD upon you using that command for the NPC that is causing the issue - and then you can check for any mod in your build that is changing that NPC. Also, you can test in the same manner with any NPC that is in that specific area, if it is not one of the companions.

[Rocky]

smr1957 の投稿を引用：

Rocky の投稿を引用：

This is a weird take you have. Have you read crash logs? And understand them? They can pinpoint you the issue to the dot. Crash logs most certainly are helpful.

Not to get off topic, as, again, this is not the place for it (there is a better place to discuss this than in someone's thread), but the experience over years that myself and others who have thousands of hours experience of helping in the forums, has been that they are, in the vast majority of cases, of no use, and if the individual had done troubleshooting the classic way, they would have discovered the issue, where as with using a "crash log" which often does NOT indicate the cause, they are still trying to figure things out days later. (And even where they were of use, the issue still could have been solved quicker using classic troubleshooting as described in the link I provided for troubleshooting the load order in post #10.).

You keep setting up arguments. jESUS christ. You dont like crash logs fine. if only i could give a ♥♥♥♥ about your self claimed expertise. are we not not trying to help. you can disagree about it all you want, but shut the ♥♥♥♥ up about it and suggest another way instead.

im not gonna rip apart my load order everytime a crash occur when testing, i look at the log and find the issue,

[Corinze]

I don't know about this one. If you have 1000 mods with Vortex you are in GOD mode anyway. I can't get Vortex to handle over 400 mods without getting pissed with it's sorting system. This is where MO2 really shines and I personally prefer Vortex.

If it is only one spot you are crashing, re-install any mod that you think effects that area. Verify those mods are loaded is a good way and double check your merged mods with SEEdit that effect that area.

It might help to just list what you have tried so far and what events stranspired before you noticed the crash.

[Freak4games989]

For everyone thinking it's a mod problem it's not. I'm having the same problems just playing normal skyrim.

[Liquid Inc]

Freak4games989 の投稿を引用：

For everyone thinking it's a mod problem it's not. I'm having the same problems just playing normal skyrim.

just because your having "the same problems" doesn't mean it's the same cause of those problems.
OP's seemed to be a mod issue, which is unrelated to yours....

If you want help, your best making a new thread on it, and ofcourse following SMR's links above on clean installing and verifying files.

[Vlad 254]

Corinze の投稿を引用：

I don't know about this one. If you have 1000 mods with Vortex you are in GOD mode anyway. I can't get Vortex to handle over 400 mods without getting pissed with it's sorting system. This is where MO2 really shines and I personally prefer Vortex.

If it is only one spot you are crashing, re-install any mod that you think effects that area. Verify those mods are loaded is a good way and double check your merged mods with SEEdit that effect that area.

It might help to just list what you have tried so far and what events stranspired before you noticed the crash.

Vortex can handle it just fine. The variable is us.

[jedi7000nathan/sevenbillionjedi]

I've given up on trying to fix the issue and found a workaround that deals with the main problems of the CTDs, first of I can COC into the Living Quarters of Jorrvaskr with no crashes or stability issues AT ALL and as such I can do the companion quest line thru the help of console commands as the chain actually has the living quarters as the main hub, also the Whiterun approach from the western side is safe it is only going near Pelegia Farm that causes a crash but if I arrive at Whiterun from any other direction no CTDs, Whiterun proper also works without CTDs and I'm able to complete the first quest of the Companions chain without issues thru console command travel in and around Whiterun. Granted I know that there is going to be a specific point regarding Kodlak in the Mainhall but I'll just advance the quest using console commands to avoid the problem. Call this a lazy mans workaround but when the rest of the game baring these two areas works fine I'm going to take the lazyman's approach.

[Corinze]

It's ok Vlad, I'm thick skinned you can say it unfiltered ~.~

I got so mad one day I deleted all of Vortex just a little over 500 Gs and used MO2 for about month before going back to Vortex 😑 lol.

[jedi7000nathan/sevenbillionjedi]

♥♥♥♥♥♥♥♥♥! I managed to fix it. All I had to do was remove the read-only flag on Skyrim folder for it and all the files inside it AND no more crashes I can get into Jorrvaskr's main hall no problem and I'm fairly certain that the Pelagia farm crash is resolved too. All of this was due to some random post I found that said its an exception access error and that the fix was to unforbid all the files for my Skyrim Folder and the folder it was installed in. Problem solved AND I am so happy about it.