crash at specific ingame time

[grigoriprime]

So I am getting a crash when Tuesday at 8AM rolls around no matter what I do. I've tried dismissing all companions, dropping all my mod gear, waiting (both the wait command and just standing there), and fast traveling, every time 8 am rolls around it CTD. I've gone back several saves and when I catch up to the specific day and time in question, CTD.

 

When I try a split half search technique to find the problem (deactivating half, trying it, halving the bad half, trying it, halving again, etc...) I'm having no luck and am getting other crashes probably related to too many missing esp/esm files all of a sudden.

 

My question is: can I use NVEDIT to find all scripts related to that time and day (or recurring ones like vendors stocking or weekly payouts etc...) or am I going to have to go through the mods one at a time and try and lock it down?

 

Or am I just totally screwed?

 

TIA for any help.

[grigoriprime]

UPDATE:

I've deactivated and reactivated all mods, reinstalled the game, forced the game to make a new .ini, changed the file permissions on all my folders to not be read only...

no luck.

somewhere between 8 and 9 am on tuesday 11/25 my game crashes.

 

i rolled back to a save 7 level ups earlier and have determined that the bug emerges after beginning the house always wins IV (omertas), planting the bug on the lucky 38 terminal but not returning to emily (moon over the tower) and initiating the heartache by the numbers quest phase where you start investigating cass caravan.

 

sooooooo.....

I'm totally f***ed here?

[grigoriprime]

So I'm just gonna assume that this was a corruption introduced by an autosave that rippled through several hard saves and, in solidarity with my Courier, I'm biting the bullet and re doing several hours worth of mohave walking.

 

Other than occasionally saving then running a "set timescale to 30000" and waiting for a few weeks to pass, anyone know how to check for this before I'm stuck again in the future?

 

I am now using CASM with some finely tweaked settings so that should help. Any other prevention tips?

[drkaii]

HAHAHA!!!!

 

Sorry man, I feel for you, really but this has to be the most brilliant, hilarious, and prankish bugs I've ever seen. You have been utterly trolled by your gamebryo xD

 

Nostradamus would be so proud.

 

The only think I can think of is....

 

Well I would use Wrye Bash to export all of the scripts from all of your mods into some massive folder, then use Windows Grep to search all the text files at once for "GetCurrentTime" or "GameHour" or "GetDayofWeek" and all of the other time-related commands and see which one corresponds.

 

Good luck.

[grigoriprime]

It was pretty damn funny, I'll admit. I go into professional troubleshooter mode (I literally am a professional troubleshooter) and it turns out to be a corrupt save.

 

I only had to replay black mountain and the last 2 new bison steve missions (I thought the weekly payout script was involved in the bug but it started before that script would have been added) so not a huge deal.

 

Your advice will come in handy if I get another super weird bug like this again though so thanks.

 

That's what I get for modding a super buggy version of an already buggy engine :)

[grigoriprime]

I also expected the Donny Darko rabbit to pop out and say "at 9:30 am on Tuesday the 25th of December 2285 the world will end" Nostradamus would've been a couple centuries off though. Maybe a postapocalyptic tribal calendar :)