Fallout 3 Evil CTD

[SteelPipboy]

There is this annoying random Crash to Desktop depending on what it is it can vary from an animation to steam Im not sure whats causing it until today. Ive tried "Every fix" possible and it still crashes. EVEN on New Vegas there is that same "F-------" CTD.

 

Here is the error from windows event viewer...

 

Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b

Faulting module name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b

Exception code: 0xc0000005

Fault offset: 0x000dd595

Faulting process id: 0xc6c

Faulting application start time: 0x01cbd6f3e6c98b59

Faulting application path: E:\Steam\steamapps\common\fallout 3 goty\Fallout3.exe

Faulting module path: E:\Steam\steamapps\common\fallout 3 goty\Fallout3.exe

Report Id: b98f448f-42e8-11e0-a902-005056c00008

 

If anyone know about the codes listed or a "working" fix please let me know.

[proconsu1]

That exception code is a very generic access violation error. That means that either the app in question, FO3, is trying to access a memory space it has no rights to, OR some other code, like Steam or Windows itself, is accessing FO3's working memspace and hosing it. The former is more likely, because many mods employ extensive scripting, and their scripts can sometimes trigger these kinds of access violations if they are not running in the environment they were written for, e.g. something has broken compatibility or there is a version mismatch with FO3 itself. It might be helpful if you posted the load order for your mods. More info on exactly when the error began cropping up and what had changed immediately prior would also be good. Edited February 28, 2011 by proconsu1

[SteelPipboy]

I usually play the game without using FOMM to launch it and New Vegas doesnt have any mods attached to it. The only two mods Im running are the unofficial patch and an object placement fix patch.

 

Unofficial Fallout 3 Patch.esm

Zeta.esm

PointLookout.esm

ThePitt.esm

Anchorage.esm

BrokenSteel.esm

Fallout3.esm

Unofficial Fallout 3 Patch - Operation Anchorage.esp

Unofficial Fallout 3 Patch - The Pitt.esp

Unofficial Fallout 3 Patch - Broken Steel.esp

Unofficial Fallout 3 Patch - Point Lookout.esp

Unofficial Fallout 3 Patch - Mothership Zeta.esp

ObjectPlacementFix.esp

 

Total active plugins: 13

Total plugins: 13

 

Heres one from New Vegas launcher, same code

 

Faulting application name: FalloutNVLauncher.exe, version: 1.2.14.0, time stamp: 0x4d5f0be3

Faulting module name: GameOverlayRenderer.dll, version: 1.4.54.93, time stamp: 0x4d669662

Exception code: 0xc0000005

Fault offset: 0x00012d03

Faulting process id: 0xaf8

Faulting application start time: 0x01cbd6d939d362cd

Faulting application path: e:\steam\steamapps\common\fallout new vegas\FalloutNVLauncher.exe

Faulting module path: E:\Steam\GameOverlayRenderer.dll

Report Id: 78ffec35-42cc-11e0-a902-005056c00008

 

An earlier crash of Fallout 3 Goty

 

Faulting application name: Fallout3.exe, version: 1.7.0.3, time stamp: 0x4a40f18b

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x3eccccce

Faulting process id: 0x11f4

Faulting application start time: 0x01cbd6c103c9456a

Faulting application path: E:\Steam\steamapps\common\fallout 3 goty\Fallout3.exe

Faulting module path: unknown

Report Id: e657b3ff-42b7-11e0-a902-005056c00008

 

All I know is when the game saves, loads, or during in the middle of an animation it will crash. Sometimes I cant even leave rivet city once I make a save there. In fallout new vegas It will crash for the same reasons.

[SteelPipboy]

The only other errors I see hours before the crash are these...

 

The UPnP Device Host service depends on the SSDP Discovery service which failed to start because of the following error:

The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

 

DCOM got error "1068" attempting to start the service upnphost with arguments "" in order to run the server:

{204810B9-73B2-11D4-BF42-00B0D0118B56}

 

Service 'WMPNetworkSvc' did not start correctly because CoCreateInstance(CLSID_UPnPDeviceFinder) encountered error '0x80070422'. Verify that the UPnPHost service is running and that the UPnPHost component of Windows is installed properly.

 

The following boot-start or system-start driver(s) failed to load:

RxFilter

 

 

These Errors happen every time on startup.

[proconsu1]

That file that is failing to load is a decryption and decompression minifilter, prolly part of Roxio (but I think Easy Media Creator uses it too, by the same company). Its failure to load at boot usually means one of three things:

 

1. You are infected with a virus or other malware. That particular executable is a popular target for them because it is a security weakness.

 

2. Problem with Windows memory handling, either due to low memory capacity, badly fragmented swap file or bad or conflicting registry info. And remember that you cannot defrag the swap file, you must recreate it after you defrag a large enough drive space for it to occupy.

 

3. There is a conflict in Roxio itself, possibly due to incompatibility with your hardware or with some other software that is running before it during bootup.

 

Any of these are possible, and any of them could be symptomatic of larger issues which could be related to why you keep getting memory access violations in FO3. You need to run a full virus and malware sweep with a utility OTHER THAN the one you usually use (since it either can't recognize what you have or it is infected itself, assuming you have an infection at all). Then you need to move your swap to another drive letter, reboot, defrag the drive it was on before, then move it back and reboot again. Then uninstall Roxio and switch to something less buggy like Nero or some freeware utility that duplicates the functions of whichever Roxio tools you are actually using. Last, get and run a good free system optimizer like IObit Advanced System Care or the like, and have it clean up your registry, system settings and such. I cannot be sure that this stuff will have any effect on your FO3 problem, but it will definitely help fix the very real problems you are seeing during bootup. (Edit: got the order wrong above: get rid of Roxio or Easy Media, whichever you have, first off, before running the virus scan or defrag.)

 

Oh, and there is one problem with your load order: fallout3.esm should always be at the top. You have five official mods (the DLCs) and one unofficial one (the unofficial patch) all loading in before the master file on which they all depend. Not good. You should use FOMM to fix that so that fallout3.esm is first in your load order.

Edited February 28, 2011 by proconsu1

[SteelPipboy]

Sorry for the long wait but, I re-installed windows on a new drive. The drive that my game was on isnt in the best condition so maybe that was interfering with FO3 and new vegas. Im not sure if a faulty drive can cause a memory violation error but a friend of mine suggested to use the newer drive.

[SteelPipboy]

Fixed :D