Jump to content

Random Crash during play


Recommended Posts

Hello,

 

After installing my mods, I tested out my game, only to have it crash at random intervals during play with the Windows error below. Nothing comes up on Google for it, and it's randomly occurring, so I can't determine a cause (sometimes 1 minute, sometimes 20, sometimes 2 hours; whether I stand still, walk/run/sneak, shoot at random objects/people, fast travel/wait/sleep, it doesn't matter) . There are no conflicts in FNVedit, and uninstalling the last installed mods (EVE and WMX) do not prevent it from happening. Can someone help me determine the cause? Here's the error details, my hardware list and mod load order (all mods are up to date as of last week):

 

Problem Details:

Problem Event Name: APPCRASH

Application Name: FalloutNV.exe

Application Version: 1.4.0.525

Application Timestamp: 4e0d50ed

Fault Module Name: FalloutNV.exe

Fault Module Version: 1.4.0.525

Fault Module Timestamp: 4e0d50ed

Exception Code: c0000005

Exception Offset: 006a55a6

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: 0a9e

Additional Information 2: 0a9e372d3b4ad19135b953a78882e789

Additional Information 3: 0a9e

Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

 

Relevant Hardware:

Intel i7 3960X Extreme 3.3Ghz

ASUS Rampage IV Extreme

64GB RAM (DDR3 1600, 10-10-10-30)

x4 600GB Velociraptors in RAID 0

x2 GeForce GTX 580 (3GB) in SLI

 

Programs and Load Order:

Nexus Mod Manager (v0.17.1)

FNVEdit (v3.0.21)

NVSE (v2 beta 12)

BOSS 2.0.1

 

−Recognised And Re-ordered Plugins

 

FalloutNV.esm Active

DeadMoney.esm Active

Bash Tag suggestion(s): {{BASH: Deflst}}

HonestHearts.esm Active

OldWorldBlues.esm Active

LonesomeRoad.esm Active

GunRunnersArsenal.esm Active

ClassicPack.esm Active

MercenaryPack.esm Active

TribalPack.esm Active

CaravanPack.esm Active

Advanced Recon Tech.esm Active

CINEMATECH.esm Active

Detect Traps.esm Active

NSkies URWLified.esm Active

Bash Tag suggestion(s): {{BASH: C.Climate, C.Light}}

Project Nevada - Core.esm Active

Project Nevada - Equipment.esm Active

Bash Tag suggestion(s): {{BASH: Delev, Invent}}

ELECTRO-CITY - CompletedWorkorders.esm Active

oHUD.esm Active

Project Nevada - Rebalance.esp Active

Project Nevada - Cyberware.esp Active

DarNifiedUINV.esp Active

CASM.esp Active

The Mod Configuration Menu.esp Active

Project Nevada - Dead Money.esp Active

Project Nevada - Honest Hearts.esp Active

Project Nevada - Old World Blues (No Cyberware).esp Active

Project Nevada - Lonesome Road.esp Active

Project Nevada - Gun Runners' Arsenal.esp Active

Detect Traps - Perk.esp Active

Detect Traps - Traponator 4000.esp Active

Detect Traps - DLC.esp Active

Advanced Recon Gear.esp Active

Advanced Recon Tech.esp Active

Advanced Recon Tech - Detect Traps.esp Active

IDreamOfElectricSheep.esp Active

Advanced Recon Armor.esp Active

Advanced Recon Desert Ranger Helmet.esp Active

Advanced Recon Range Finder.esp Active

Advanced Recon Gear - Project Nevada.esp Active

FlashlightNVSE.esp Active

WeaponModsExpanded.esp Active

Bash Tag suggestion(s): {{BASH: Invent, Delev, WeaponMods}}

Project Nevada - WMX.esp Active

Bash Tag suggestion(s): {{BASH: Graphics, Invent, Names, WeaponMods}}

WMX-DeadMoney.esp Active

Bash Tag suggestion(s): {{BASH: Invent}}

WMX-HonestHearts.esp Active

Bash Tag suggestion(s): {{BASH: Invent}}

WMX-OldWorldBlues.esp Active

Bash Tag suggestion(s): {{BASH: Invent}}

WMX-LonesomeRoad.esp Active

Bash Tag suggestion(s): {{BASH: Invent}}

WMX-GunRunnersArsenal.esp Active

Bash Tag suggestion(s): {{BASH: Invent}}

WMX-ArenovalisTextures.esp Active

Bash Tag suggestion(s): {{BASH: Graphics, NoMerge}}

WMX-PreOrderPackClassic.esp Active

WMX-PreOrderPackCaravan.esp Active

WMX-PreOrderPackMercenary.esp Active

WMX-PreOrderPackTribal.esp Active

EVE FNV.esp Active

Project Nevada - EVE.esp Active

WMX-EVE.esp Active

FNVEnhancedShaders - AA-DOF Enable.esp Active

Vurt's WFO.esp Active

NSkies URWLifiedOWB.esp Active

Bash Tag suggestion(s): {{BASH: C.Climate, C.Light}}

NSkies URWLifiedHH.esp Active

Bash Tag suggestion(s): {{BASH: C.Climate, C.Light}}

NSkies URWLifiedDM.esp Active

Bash Tag suggestion(s): {{BASH: C.Climate, C.Light}}

DYNAVISION 2 - Dynamic Lens Effect.esp Active

Night Brightness Adjuster.esp Active

ELECTRO-CITY - Imaginator.esp Active

Directors Chair.esp Active

BetterGamePerformanceV4.esp Active

Note: Loaded last so that deleted references stay deleted.

Link to comment
Share on other sites

search for the multi core fix other intel user swear by it , iv never had to use it im an AMD peasant !

 

Are you referring to the fix where I limit the number of cores allowed to 2? If so, I found that one and used it (instructions I used are below for reference), but the results are the same. I've also already swapped out my dx9.dll file as part of a previous mod I'd installed.

 

1. Open fallout.ini file in My Documents\My Games\FalloutNV with a text editor such as Notepad.

 

2. Look for the string bUseThreadedAI=0

 

3. Change it to bUseThreadedAI=1

 

4. Add another line beneath the above, iNumHWThreads=2

 

5. Save and close this file.

 

6. Repeat steps 2-5 for FalloutPrefs.ini in the same directory and fallout_default.ini file in installation dir (default C:\Program Files (x86)\Bethesda Softworks\Fallout New Vegas)

Link to comment
Share on other sites

yep that is the one i was thinking of , and that address looks a little short to me no mention of steamapps etc , Hmmm ?

 

C:\Program Files (x86)\Bethesda Softworks\Fallout New Vegas) default should look somthing like this x86>steam>steamapps>common>fallout new vegas now there is two reasons for this which im not gonna go into ,so im gonna leave it at that .

 

also modified DirectX files are not digitally signed so that means Microsoft havent checked them for stability safety and integretity the use of which is ill advised .

in my understanding these files force the hardware to run nearer their extremes much like red lining an engine might go pop might not !

Edited by davycrockett
Link to comment
Share on other sites

yep that is the one i was thinking of , and that address looks a little short to me no mention of steamapps etc , Hmmm ?

 

C:\Program Files (x86)\Bethesda Softworks\Fallout New Vegas) default should look somthing like this x86>steam>steamapps>common>fallout new vegas now there is two reasons for this which im not gonna go into ,so im gonna leave it at that .

 

Yeah, I'm aware, I just copy/pasted the instructions as appeared on the site I found, but I actually went into my steamapps folder to find the correct file to mod.

 

also modified DirectX files are not digitally signed so that means Microsoft havent checked them for stability safety and integretity the use of which is ill advised .

in my understanding these files force the hardware to run nearer their extremes much like red lining an engine might go pop might not !

 

Wait, you're referring to the d3d9 file that I replaced? It's my understanding that it only affects Radeon graphics cards (fixing some graphic bugs), but as it was combined with one of the mods (I believe it's Project: Nevada, not sure anymore) and since I couldn't find anything about it affecting nVidia in a bad way when I checked, I didn't see a problem. Is this not the case?

Link to comment
Share on other sites

look in c;/ program files(x86) games for windows live and you should find some data cabinets right click em >properties >digital signature you will see all cabs are signed (microsoft )the individual files are not , so this means trusting a file not to damage your machine or not to be viral think it over , i was guilty of this too but we live we learn eh whilst i can't proove the cause of the gpu failure either way, my colleauge who has been in the industry for over 20 years showed me the error of my ways .( he's an MSA )

 

now keep in mind that whilst the nexus staff do their very best to protect us from malicious software they can't protect us from hardware failure being cause by modified files which is why with any ENB series file you get a disclaimer " if your machine breaks ...tough luck ,im not taking the blame " or something along those lines im certain that file is a graphics processing file theres a reason your machine uses the files it does and forcing something other than prescibed on it is not recommended by the pros .

 

"Yeah, I'm aware, I just copy/pasted the instructions as appeared on the site I found, but I actually went into my steamapps folder to find the correct file to mod."

 

ah good an honest mistake i was getting a little concerned as to the validity of your game

 

 

and i think you may of just solved your problem , which gpu is that .dll for AMD or NVIDIA and what gpu do you run ? cos if its an amd file and your nvidia there's your problem and vice versa , tell me thats what it is go on please ! (same goes for on board gpus)

Link to comment
Share on other sites

  • 2 weeks later...

look in c;/ program files(x86) games for windows live and you should find some data cabinets right click em >properties >digital signature you will see all cabs are signed (microsoft )the individual files are not , so this means trusting a file not to damage your machine or not to be viral think it over , i was guilty of this too but we live we learn eh whilst i can't proove the cause of the gpu failure either way, my colleauge who has been in the industry for over 20 years showed me the error of my ways .( he's an MSA )

 

now keep in mind that whilst the nexus staff do their very best to protect us from malicious software they can't protect us from hardware failure being cause by modified files which is why with any ENB series file you get a disclaimer " if your machine breaks ...tough luck ,im not taking the blame " or something along those lines im certain that file is a graphics processing file theres a reason your machine uses the files it does and forcing something other than prescibed on it is not recommended by the pros .

 

"Yeah, I'm aware, I just copy/pasted the instructions as appeared on the site I found, but I actually went into my steamapps folder to find the correct file to mod."

 

ah good an honest mistake i was getting a little concerned as to the validity of your game

 

 

and i think you may of just solved your problem , which gpu is that .dll for AMD or NVIDIA and what gpu do you run ? cos if its an amd file and your nvidia there's your problem and vice versa , tell me thats what it is go on please ! (same goes for on board gpus)

 

Sorry it's been so long since I posted, life suddenly got busy (buying houses does that...) and I must have missed the notification.

 

I've tried replacing the modded file with an unmodded version, but now the game's autoloader won't even start, with the error "The procedure entry point D3DPERF_SetOptions could not be located in the dynmaic link library d3d9.dll", so I switched it back. Looking online, this appears to be a file used by games to run direct x, and looking through the forums shows that others haven't had this kind of problem in spite of running nVidia cards, so I don't believe it's causing any gpu specific problems.

 

Is there anything I can try doing that would narrow down the possible causes any?

 

And again, thanks for all the help!

Link to comment
Share on other sites

so is the game working , i use that word loosely as in back to square one ?

cos if all system and hardware drivers are up to date and steam says all is good it can only leave mods now did you read the "read me" file for each mod im wondering if you have any there which are missing their masters ?

 

FNVedit wont highlight this issue only conflicts but your mod manager will tell you which mods are needed to run any highlighted mod ,it will list them for your convenience have you checked all of them ?

but if you have already run FNVedit with no obvious suspects id suggest deactivating all mods and starting a new game for the sake of the testing process if it starts behaving again then fingers shall point towards mods .

 

"The procedure entry point D3DPERF_SetOptions could not be located in the dynmaic link library d3d9.dll",

 

if it that ones still an issue , at a guess id say reinstall directX .

Edited by davycrockett
Link to comment
Share on other sites

so is the game working , i use that word loosely as in back to square one ?

cos if all system and hardware drivers are up to date and steam says all is good it can only leave mods now did you read the "read me" file for each mod im wondering if you have any there which are missing their masters ?

 

FNVedit wont highlight this issue only conflicts but your mod manager will tell you which mods are needed to run any highlighted mod ,it will list them for your convenience have you checked all of them ?

but if you have already run FNVedit with no obvious suspects id suggest deactivating all mods and starting a new game for the sake of the testing process if it starts behaving again then fingers shall point towards mods .

 

"The procedure entry point D3DPERF_SetOptions could not be located in the dynmaic link library d3d9.dll",

 

if it that ones still an issue , at a guess id say reinstall directX .

 

Nope, still doesn't work, and I'm not missing any of the masters, and no errors in the load order when I check NMM. And I've already started a fresh new game, too.

 

Of interest, though: it only happens AFTER the Doc Holiday sequence is over and I leave the cabin, I think. I'm not sure why this would be: it still happens when I enter other structures and wait, but (so far) not during the Doc Holiday character building section. Perhaps one of the mods is causing a problem with the terrain textures or draw distance...?

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...