Registry/Windows or Fallout Problem?

[kevlardude]

Well, hi there.

 

I searched the forums but i figured that considering my recent actions i want to create a new topic.

 

This is gonna be a story.

 

My Specs:

Win 7 64 Bit

Processor: AMD FX-8350 Eight-Core

Mainboard: ASRock 990FX Extreme

Memory: 16 Gb DDR3

Graphic: NVIDIA GeForce Gtx 770 (4 Gb)

 

 

First of all my game ran great. Until one point.

 

I never had it installed before.

 

I installed it correctly via Steam - worked fine.

I installed the Marts mutant mod and Wanderers Edition - worked fine.

 

I installed everything correctly and adjusted the mod loading order.

 

Then i had those freezes from time to time, so i adapted the .ini like we all do (did), adding the 2 Lines to enable better multicore performance. -it worked.

 

Then after 30 minutes the game crashed. Started again and after a while it crashed again.

I searched the internet for a crash fix and found a d3d9.dll or something like that. Added it and hold on to your hats, it didn´t even start. Startup crash.

 

Now, i removed the .dll from the data folder and started again. Same result.

 

After this i deinstalled the whole game. Downloaded and reinstalled just the vanilla game, didn´t work. Startup crash.

 

Deinstalled again, removed manually all files that were still existing, started ccleaner and cleaned the registry.

 

All those things won´t change anything, i really can´t get the point here. It´s freaking me out.

 

What do you guys think of that? What could possibly be going on here?

 

I have the latest Crash report, but i can´t figure out what it wants to tell me...

 

It´s german but i translated the important things to english, since there are more ppl understanding engl here i guess.

 

Version=1
EventType=APPCRASH
EventTime=130542206019582963
ReportType=2
Consent=1
UploadTime=130542206024393238
ReportIdentifier=17a0eb48-3365-11e4-9f94-bc5ff4f9a52a
IntegratorReportIdentifier=17a0eb47-3365-11e4-9f94-bc5ff4f9a52a
WOW64=1
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=Fallout3.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=1.5.0.22
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=49cd1e54
Sig[3].Name=Fehlermodulname
Sig[3].Value=Fallout3.exe
Sig[4].Name=Fehlermodulversion
Sig[4].Value=1.5.0.22
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=49cd1e54
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=007eeac5
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=F:\Steam\SteamApps\common\Fallout 3 goty\Fallout3.exe
UI[3]=Fallout3 doesn´t work anymore
LoadedModule[0]=F:\Steam\SteamApps\common\Fallout 3 goty\Fallout3.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll
LoadedModule[5]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[11]=C:\Windows\syswow64\GDI32.dll
LoadedModule[12]=C:\Windows\syswow64\USER32.dll
LoadedModule[13]=C:\Windows\syswow64\LPK.dll
LoadedModule[14]=C:\Windows\syswow64\USP10.dll
LoadedModule[15]=C:\Windows\system32\d3d9.dll
LoadedModule[16]=C:\Windows\system32\VERSION.dll
LoadedModule[17]=C:\Windows\system32\d3d8thk.dll
LoadedModule[18]=C:\Windows\system32\dwmapi.dll
LoadedModule[19]=C:\Windows\system32\XINPUT1_3.dll
LoadedModule[20]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[21]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[22]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[23]=C:\Windows\syswow64\ole32.dll
LoadedModule[24]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[25]=C:\Windows\system32\xlive.dll
LoadedModule[26]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[27]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[28]=C:\Windows\system32\Secur32.dll
LoadedModule[29]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[30]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[31]=C:\Windows\system32\WINHTTP.dll
LoadedModule[32]=C:\Windows\system32\webio.dll
LoadedModule[33]=C:\Windows\syswow64\IMM32.dll
LoadedModule[34]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[35]=C:\Windows\system32\d3dx9_37.dll
LoadedModule[36]=C:\Windows\system32\WINMM.dll
LoadedModule[37]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[38]=C:\Windows\syswow64\NSI.dll
LoadedModule[39]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[40]=C:\Windows\system32\WINNSI.DLL
LoadedModule[41]=C:\Windows\system32\msidcrl40.dll
LoadedModule[42]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[43]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[46]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[47]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[48]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[49]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[50]=C:\Windows\syswow64\iertutil.dll
LoadedModule[51]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[52]=C:\Windows\syswow64\USERENV.dll
LoadedModule[53]=C:\Windows\syswow64\profapi.dll
LoadedModule[54]=C:\Windows\system32\OLEACC.dll
LoadedModule[55]=C:\Windows\system32\SensApi.dll
LoadedModule[56]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[57]=C:\Windows\system32\DSOUND.dll
LoadedModule[58]=C:\Windows\system32\POWRPROF.dll
LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll
LoadedModule[60]=C:\Windows\system32\d3dx9_38.dll
LoadedModule[61]=C:\Windows\system32\WSOCK32.dll
LoadedModule[62]=C:\Windows\system32\DINPUT8.dll
LoadedModule[63]=F:\Steam\SteamApps\common\Fallout 3 goty\binkw32.dll
LoadedModule[64]=F:\Steam\SteamApps\common\Fallout 3 goty\libvorbisfile.dll
LoadedModule[65]=F:\Steam\SteamApps\common\Fallout 3 goty\libvorbis.dll
LoadedModule[66]=C:\Windows\system32\uxtheme.dll
LoadedModule[67]=C:\Windows\system32\nvspcap.dll
LoadedModule[68]=C:\Windows\system32\nvapi.dll
LoadedModule[69]=C:\Windows\SysWOW64\ctagent.DLL
LoadedModule[70]=C:\Windows\system32\HID.DLL
LoadedModule[71]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[72]=C:\Windows\System32\MMDevApi.dll
LoadedModule[73]=C:\Windows\System32\PROPSYS.dll
LoadedModule[74]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[75]=C:\Windows\system32\nvd3dum.dll
LoadedModule[76]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[77]=C:\Windows\System32\msxml3.dll
LoadedModule[78]=C:\Windows\system32\XLive\sqmapi.dll
LoadedModule[79]=C:\Windows\system32\credssp.dll
LoadedModule[80]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[81]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[82]=C:\Windows\system32\mswsock.dll
LoadedModule[83]=C:\Windows\System32\wshtcpip.dll
LoadedModule[84]=C:\Windows\System32\wship6.dll
LoadedModule[85]=C:\Windows\system32\DNSAPI.dll
LoadedModule[86]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL
LoadedModule[87]=C:\Windows\system32\rasadhlp.dll
LoadedModule[88]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[89]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[90]=C:\Windows\system32\rsaenh.dll
LoadedModule[91]=C:\Windows\system32\wdmaud.drv
LoadedModule[92]=C:\Windows\system32\ksuser.dll
LoadedModule[93]=C:\Windows\system32\AVRT.dll
LoadedModule[94]=C:\Windows\system32\msacm32.drv
LoadedModule[95]=C:\Windows\system32\MSACM32.dll
LoadedModule[96]=C:\Windows\system32\midimap.dll
LoadedModule[97]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[98]=C:\Windows\system32\ncrypt.dll
LoadedModule[99]=C:\Windows\system32\bcrypt.dll
LoadedModule[100]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[101]=C:\Windows\system32\GPAPI.dll
LoadedModule[102]=C:\Windows\system32\cryptnet.dll
LoadedModule[103]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[104]=C:\Windows\system32\ntmarta.dll
FriendlyEventName=No longer functional
ConsentKey=APPCRASH
AppName=Fallout3
AppPath=F:\Steam\SteamApps\common\Fallout 3 goty\Fallout3.exe

Any help would be much aprecciated.

 

 

[Purr4me]

in the games ROOT folder, where the executable sits, look for this file name 'FALLOUT3.EXE.CFG" delete that, delete the user view settings in the user/apps/fallout3/folder.

reboot. launch the gme with the launcher "only" reset the systems grids.....the display drivers "grids" for the game."

 

this data is stored in that file, C:\Program files and folders\Bethesda\fallout3\fallout3.exe.cfg

 

when you run the game now, it will recreate a new one.

if there is any live data. xlive data sintting in the game folder? delete that. the xlive dll you need in sitting else where in windows ....care of steam.

system32 xlive.dll is a required display driver asset for fallout 3, and it must be "32bit"

 

kitty

[Purr4me]

If you get stumped? use the OS to create a brand new user profile ,log on, set it up as an administrator as well.

reset the graphics first ,get the user system online and ready for this old game, make a plan of it.

To be perfectly clear here, your PC, not the nexus profile but the PC's user profiles.

(Control Panel\All Control Panel Items\User Accounts\Manage Accounts) create a new account there on that PC.

you will find it completely brand new, screen display settings, every thing, this includes any online stuff will be gone, no browsers any thing, no connections or device drivers except what the system shares across the domain your on or in.

 

 

have a lot of hard drive space cuz your gonna need it.

install the game to a folder .....C:\YOUR name\ fallout3

keep things off line,. ......if the game is a steam game? copy the existing game software into that folder.

run steam from the new profile, steam will see this new profile and reset your system for that new profile, so now, you have two different sets of games to play with.

 

make sure.....you isolate what you do, keep track of every thing you install.

"Do NOT use any online installers. Manual only" ? Got it?

 

this includes Mod Organizer as well. use only Original 2008 methods to make darn sure, it's not a network bug casing the problems.

 

there is a method to the madness. Not only does this give you a better understanding of what is going on, you now have two types of permissions assigned to the OS, Your PC.

 

Divide and conquer....Bethesda games.

kitty

Edited September 4, 2014 by Purr4me

[kevlardude]

Alright.

 

A quick update.

 

I considered your ideas and thoughts regarding the game and it´s working now. Even with the 2 mods :)

 

The only problem left is the freezing from time to time.

 

Guess that´s a multi-core issue as discussed in many topics in countless forums.

 

I already tried the .ini modificationi but it stll freezes after about 40 minutes of the game. I think theres nothing more i could do. Just have to accept it.

 

Or what do you guys think?

 

Don´t want to mess around again with the game, putting a .dll file in there since that´s the point where it broke the last time.

[Purr4me]

Alright.

A quick update.

I considered your ideas and thoughts regarding the game and it´s working now. Even with the 2 mods :smile:

The only problem left is the freezing from time to time.

Guess that´s a multi-core issue as discussed in many topics in countless forums.

 

I already tried the .ini modificationi but it stll freezes after about 40 minutes of the game. I think theres nothing more i could do. Just have to accept it.

Or what do you guys think?

 

Don´t want to mess around again with the game, putting a .dll file in there since that´s the point where it broke the last time.

1rst, I need some back ground on just exactly what you did, Here, I have to assume you followed the advice.

If your on a "new profile" then it is established partly that internet / networking is involved. Thus CUT, you have been able to reclainm the game but still have a limited time issue, run time? this means I need just a little more information.

 

what Mods? post a load order, and the oreder of install and method used.

many of my most recent posts here hae the needed information to deal with your issues.

 

NOTE: some editing software , users use, clients, mod authors use, have downloaded a 64 version due to their preferences of the system.

because this is known, the architecture of the outcome of thedata produced is some times not converted t obe 32bit.

DDS files, and some *.nif files....these weird files I have found do indeed cause exactly your bug.

 

So much so, it can even lock up the most powerful machines made. The game see's the file name, it see's the extention, it will foruce process the file because of this fact, but, once it hit's the GPU and Main processor and it is not what it is supposed to be? the game will just freeze. PC too.

 

where, what, how, and in what way ar ethe files being cared for?

Tools used "if any" a perfectly clean , legit looking file with zero errors in it, loads up in all tools but seriously locks up the machine means there is code in it not meant for the games engine to process. the plugin can contain bad information and sttill be legit.

 

support files.can be legit too but the wrong format. all of this tells the tale.

skill to find the bad things requires time. Even skilled ....users have troubles with these kinds of files. they jump from mod to mod as t osay, are used by every one....over and over again. the most sever files that can kill the game are common files, weapon mods contain these types.

 

armor mods can contain the same types. the plugin is only the binary instruction code t oinitciate the data on screen, That data needs to be legit and the right kind.

 

Thoughts?.........way too many "thoughts?". the flag on some plugins can cause the game to freeze up too. esm verses esp, or an esm file not flaged as such. a fake master file. or a fake esp master. lot's of ground to cover, so the question is rather loaded? !!!

kitty