Alright, I'm on a port call on the USS abe lincoln, so i dont have alot of time to fix this so please help..

Windows 7 Home premium

Anyway, I bought Fallout 3, game of the year addition and installed it onto my C/drive succesfully.. I have all permissions on the game and the folder. Im the admin, and the only one to use the labtop. I can start up fallout perfectly fine with no problems. I go to the main menu and click "new game". The loading screen comes up for about 4-6 seconds then crashes and says "Fallout 3 has stopped working" "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." From there i have to open task manager because the screen is forzen and wont close any other way.

I've tried numerous things to fix this. Changing permission, compat, etc. None of which is working.

Here are my specs:

HP pavilion dm4 Notebook PC
Intel® Core™ i5 CPU M 450 @2.40GHz 2.40
RAM: 4.00GB
System type: 64-bit OS

Intel® HD graphics

I dont have any real high speed internet that i can acess with my labtop, so DLing patches and such isnt really an option.

PLEASE HELP

Thank you for taking the time to read this. I have almost the same problem.

I have installed Fallout 3 on my new Acer Aspire laptop with windows 7. It has 4GBs of RAM and the Intel i5 core M480 @ 2.67Ghz, and the Nvidia GeForce GT 540M video card. I have directx 11. I have the DLC installed from Games for Windows Live marketplace. I have the 1.7 update installed. I am running the physical game disc, original fallout, not GOTY. Fallout freezes constantly requiring me to bring up task manager and force close it. Almost every five minutes. sometimes less often, but more than likely, more often. No error messages, just freezes.

I have tried uninstalling and re-installing everything. I have looked at a lot of the fixes online. I have tried running in compatibility mode. I have tried disabling visual themes and desktop composition. I have tried changing the privilege level so that all users can run as admin. BTW I'm the only user and the admin. I have tried low visual settings and high visual settings. I have tried windowed mode. I have tried deleting the .ini files in C:\Users\soap\Documents\My Games\Fallout3.

I have tried editing the fallout.ini file located in User\soap\Documents\My Games\Fallout 3 to "bUseThreadedAI=1" and adding the line "!NumHWThreads=1". This doesn't work either.

I have tried all these things at once. I have tried them one at a time. i have tried updating my drivers but there are none available.

I have exhausted every thread and forum on the internet from Microsoft, steam and even less authoritative sites. I'm very frustrated that I've spent an entire night mucking about with this and there is no way to fix this. I have played Bethesda games since Morrowind came out and have been a loyal fan. The internet forum posters say that Bethesda has no plans to fix this problem. If that is true, I think I'll chose to never buy a Bethesda affiliated game again, this is unprofessional.

I read a fourm a few mins ago about a guy who has the Nvidia video card. He said he fixed the problem by updating the drivers and the card itself. Make sure you have all the updates for that card. That could be the problem for you. Im just making a guess though...

Howdy , im not gona be much help ... except that I read in a diff thread here recently. That your Intel HD graphics is the problem. Something about this game doesnt like it. Ill see if I can find it and update here >>> (hmmm , sorry ... it wasnt exactly saying it wouldnt work) Its the thread just below by Duffcreep

On a different note , I noticed you installed in ... C:\ as apposed to (X86) program files.
Thats what I was telling Soap here he might try. A google search brings up a few posts about it specifically solveing the freezeing issue. They'er rare but they there. So I guess its not unheard of to install a 32-bit game outside the (x86) default directory.

I had the exact same problem, but adding the d3d9.dll file along with editing the .ini file in the 'My games' folder, as soapiper desribed, solved it!
Not sure if it was the d3d9 file alone that did the trick, but you can try both.

Hope this helps~