HI everyone, XTheOutCastedX here. i just recently purchased fallout 3 game of the year edition and every time i walk into the vault 101 entrance area where i remove the door and escape (i have fallout 3 for xbox so i know what happens) every time i take a step out of the door from the overseer's room my game crashes either right away or after a few seconds. i uninstalled the game and reinstalled it then i tried console commands to teleport me to megaton, unfortunatley my game went black screen and the music still played, so i assume when you come out of the vault that is some sort of scripting where your game will crtach is you use "coc"? i don't know, anyway after my awesome story here can anyone give me tips or any ideas on what might be going on? I have a good acer predator series computer that i got for christmas thaty works amazingly with high graphics on new vegas so i'm really not sure what to do. any ideas?

-XtheOutCastedX

Inside the vault, many graphics effects aren't being used, then when they are switched on leaving the vault, the load can trigger a variety of problems. Start from point one and work your way through. Here is the hardware component rundown. Fill it in.

Basic Hardware Specification Chart (Empty so far)

Processor Manufacturer: AMD / Intel
Processor Name / Type: Athlon X2 / Pentium D / C2D / dual core / quad, etc.
Processor Speed: ?.? Ghz
Operating System / Service Pack: WindowsXP with SP #?, Win7, Vista ?
System RAM: ? ? GBs (MBs, if less than 1024 ? )
Video (GPU) Manufacturer: ATI / Nvidia (only those two are supported, PERIOD, so please answer which of them you have)
Video Card Model: (examples) Radeon HD 6670 / Geforce GTS 450
Video Card Driver Version: Catalyst ?.? / Nforce ??.??
. . (please use the numbers, and dates, *not* the word "latest")
Video display's default screen resolution
Video Card onboard RAM: ? ? ? MBs
Sound Card Manufacturer:
Sound Card Driver IDs:
Sound Card Model:

(And this is only for the raw hardware & driver variations. Potential software conflicts are far more likely to be game play problems, and developers cannot test for all possible program loads.)

I looked around this sute a little but after i posted this to see if anyone else had this problem (which i should have done before) and saw that when i went into the fallout 3 document and i changed something from 0 to 1 then added another line it worked without a hitch! thank very much though!