cossayos

Look at what your system log says. There's obviously still some glitch. I got to a nearly crash free game, once I observed what my system told me.

The Papyrus log doesn't really tell you much. The system log is what you should be looking at. What warnings does it put out when you crash? It tells you what part of your system didn't agree with you game, causing it to crash. In my case it was GPU related and underclocking it a few notches took care of my constantly crashing game. BTW, I had the same errors in my papyrus log. But they aren't the underlying reasons.

Do you by any chance use enboost? If so, remove every last trace of it.

Just hit the windows button on your keyboard, type event viewer and if that pops up, go to windows protocolls/system. Double click system and wait till it loads in a seperate window. There will be a warning at the time of your crash. That's the one and only location that can given anyone any idea why it's happening.

Just hit the start button, type "event viewer" and look what it says under windows protocols/system

A windows event. Tied to the crash. It should tell you what didn't agree with your game.

Have you looked at your event viewer? Under System there should be a warning at the time of the crash. What does it say?

So I still got a lot of CTDs even with a freshly installed vanilla game. Old files have been removed down to the registry level previously. Now can anyone make heads or tails of the papyrus log. I seem to get a lot of errors with hostile robots and Codsworth shrubbing/trimming. But since I'm still in Sanctuary after leaving vault 111, this doesn't make any sense to me. For some reason I'm not allowed to upload a simple txt file, so here's some of the errors in the file. error: Property Valuables03 on script dlc03:dlc03dialoguev118script attached to DLC03DialogueV118 (030316F2) cannot be bound because <nullptr alias> (28) on quest DLC03DialogueV118 (030316F2) is not the right type [04/14/2019 - 04:27:13PM] error: Property Valuables02 on script dlc03:dlc03dialoguev118script attached to DLC03DialogueV118 (030316F2) cannot be bound because <nullptr alias> (27) on quest DLC03DialogueV118 (030316F2) is not the right type [04/14/2019 - 04:27:13PM] error: Property Valuables01 on script dlc03:dlc03dialoguev118script attached to DLC03DialogueV118 (030316F2) cannot be bound because <nullptr alias> (25) on quest DLC03DialogueV118 (030316F2) is not the right type [04/14/2019 - 04:27:13PM] warning: Property DLC04GZMainQuest on script DLC04:DLC04_GZSetConsciousOnHit attached to (06029626) cannot be initialized because the script no longer contains that property [04/14/2019 - 04:27:13PM] warning: Property ProtectronPodStatus on script DLC04:DLC04_GZSetConsciousOnHit attached to (06029626) cannot be initialized because the script no longer contains that property

Or to use hide pipboy. At least I used it in every Fallout game, since that oversized piece of equipment always bothered me.

I don't know what it is, since I own the game since it first came out and clocked off more than 2000 hours playing it with the exact same setup - hardware and software. But since last fall, the game has become virtually unplayable for me. I'm crashing every few seconds. Sometimes at cell trasitions, where the game simply freezes up and throws me back to desktop, but as of recently, when intiating any kind of dialogue. The first line is spoken and the game freezes as soon as the reply options pop up. Seeing as I already did several clean installs (with all game remnantsand mods, down to registry level removed) and the problem still persists, I'm totally at a loss. I'm well aware that my hardware isn't top notch, but previously I could play the game with medium to high settings without any major problems occuring. Now it even crashes at the lowest possible video settings. Hardware: AMD A8-6600K 3,9 Ghz Ram 8 Gigabite Nvidia GeForce GTX 650 Ti

Nevermind - wrong section - delete

Well, it is scrap everything. Have you the numerous patches for scrap everything installed? They usually take care of the clipping.

You may need to launch steam as an admin to get it to work. Right-click on the shortcut and there should be a "Run As Administrator" choice. In Win7 at least. Yeah, thanks. I figured it out in the meantime. Starting it from the task bar was my mistake. I had to start it from desktop as admin to get the console.

OK, I followed the above video and went through the motions. But I can't make steam recognize the console. Whenever I try to change the path (-console) as Hexi describes I get the message that I need admin rights to make changes. Klicking OK doesn't solve the issue. It says "access denied". The path in the shortcut features the new entry, but the client still doesn't feature the header "console".

Since the last three or four beth updates the game has become virtually unplayable for me. CTDs happen randomly, when initiating conversations, opening containers or going into vats. I did a few reinstalls from scratch but nothing works anymore. Seems like I have to can the game for good.

Has it been updated again? Well, maybe then I can play the game again without crashing every five seonds as the last update reduced me to.

I haven't got that folder. Maybe it's only created once you actually purchase CC stuff, which I never did.

Where's that manifest file hiding? I haven't got loading issues but very frequent CTDs and my Papyrus log shows that the game tries to load CC stuff although I never had any.

Don't have to tell me. The nexus is a wonderful place to get great mods for free. No need for paid stuff and to support a model that's geared at milking every last penny out of an old game.

Simply disabling the mods doesn't say there's no mod remnant still causing problems. Only a clean reinstall could tell you more. But that's a lot of effort. I would wait for the next bethesda update. As for me, I got problems since the latest beth update. My game, even a clean vanilla install, turned into a crash fest.

It does nothing else than making the Papyrus log visible in a seperate window. No new informations.

As a last desperate resort, you could try to disconnect your ethernet cable, so that the game can't communicate. Silly as it may sound, that's still one of the official Bethesda tips for people who's game doesn't even start.

All I can say is that I'm unable to play the game since the latest cc update. I don't use any of the paid stuff, but they must have sneaked something in that makes my game crash every five to ten seconds. Maybe you got hit by a similar problem.

It might be the latest Bethesda patch causing trouble. Your problems obviously started when exiting vault 111. That's where my game started to become unplayable since the latest CC upgrade. CTDs by the numbers, before even reaching Sanctuary.

Let me guess, they never answered. Or pointed you to the one year old thread where they say, they're looking into the problem. Yeah, I uninstalled and reinstalled five times. Tried every trick in the book, from running totally vanilla to fiddling with the inis. Nothing worked. I'm pretty sure it's the last cc update. Funny thing is, the update before last, actually made my game more stable. The last one shot it down.