Game freezes ad infinitum, then refuses to load.

[TwilightKartman]

To elaborate

I have played with this exact modlist for 4 days (and around 20-30 hours).

I did not face any CTDs, freezes, heavy stutters etc.

Not even fps drops.

No ini files were changed, no new mods added,

_______________

Stage 1.

I enter any location from the Rockwel Pursuit mod's Colorado part.

The game loads this random location. I enter another random location. The game loads it. I enter another random location. The game freezes on loading or gets into an infinite load.

I have to end the prosess with task manager by alt+tab and arrow keys to locate the FNV prosess on the minimized window and then terminating it.

I enter the game.

It gets to the NCR ranger with music and all, but never loads the main menu.

OR

It loads the main menu in 2 minutes (usually only have to wait 10 secs), is very slow and when I click "continue" it freezes not even letting me press "yes"

_______________

Stage 2.

This behaviour persists for a couple of game.exe loads(?) or some time(?) or until I reset my PC(?)

All above work.

After waiting/entering and exiting the game a couple times/reseting my PC the game loads.

It works perfectly, loads in 10 secs, no slowdowns, no fps drops.
I continue playing the mod.
I get back to Stage 1.

The story repeats itself.

_______________

I do not need exact help or ways to fix this, it's just that in my 520 hours of playing I have not seen the game do this.
What I need to know is: can a mod physically do this?

What even could cause this?

[TwilightKartman]

The bug happened when I tried to loot a corpse by opening it's inventory (running loot menu).

I managed to get out of the place at 3 loadscreens per gamefreeze, and the later locations are completely ok.

Guess that one was a horribly done worldspace.

[lStewieAl]

Are you using New Vegas Stutter Remover? It causes crashes and freezing on Windows 10

[TwilightKartman]

Yes I am using NVSR on Win10, but as I mentioned already, the game ran perfectly before and after that rough patch of a location. So most probably not the culprit.
Although as I said - don't guess who's responsible for this, I gave you like 0 info about it.

I just want to know if someone had faced such bugs at all.