I posted this in the hardware forum, but since I'm unsure if it's a hardware related issue or a mod issue I'm posting here as well, since people come here more often. Please don't delete either thread, mods! I'm upset enough as it is.

So I've been playing for (according to Steam) around 40 hrs of this game with maybe 2 crashes... now, when I fast travel to a spot added by New Vegas Bounties 2, it crashes, and it'll suddenly freeze and crash when I walk around the NCR Sharecropper farms. It's fine everywhere else. I've disabled my mods, tried to walk around that area and it still crashes. I can post a load order if necessary but I am 100% baffled and about to just say screw this game for good.

I just downloaded the someguy.esm , (for the New Vegas Bounties mods) and it still did the same thing - it freezes briefly then CTDs when walking around the Sharecropper farms, or near it. I did fix the AWOP and Arwen issues (or at least the issues I have are not a nuisance) and I created a merged patch with FNVEdit, but I didn't manually merge them - just right clicked and made a merged patch.

I've tried WAY earlier saves and it's still an issue, which leads me to think of a few things. Just curious, what would removing archive invalidation do besides mess up my textures?

1. I noticed when I run FNV my RAM goes above 4 gigs; when idling at the desktop it's around 2 gigs of RAM. This leads me to think it's like Skyrim in that no matter what, if you go over 3.1gb total, it crashes.

2. Somehow ALL my saves got corrupted.

3. There's something in that particular spot that is making me crash (duh), be it a script or another mod.

4. The above can be disproven by the fact that it still crashes in the same spot without mods. Googling this issue seems to conclude that a reinstallation is in order (I'd rather use my balls in a game of ping pong than go through installing everything again)

5. I have too many plugins active, but then, I delete all of them and the problem persists.

So... yeah. No idea. It's been crash free for 30 hours (40, says Steam). Well, it crashed one other time but that was a random crash. Other than that it's been buttery smooth perfect gameplay, and now this happens. Any other thoughts?