Fallout 3 on Windows 7.

[Nevada]

Hello there.

While looking for a quick fix to my Fallout 3 problem, I was using this forum as a guide quite a bit. Anyways, I figured I might as well contribute to the thread, and maybe help out a bit for others having the same problem.

Now, my Fallout gets stuck on the launcher, as in the screen turns black after I click play, and then crashes, and I have to click in the center of the black screen and hit enter to return back to the desktop. Now, I have tried the drivers that came with the Windows 7 RC1 install disk, the updated drivers that came from the windows update, the drivers from ATI a few weeks ago, and then the drivers from the 25th. I'm running an ATI Mobility Radeon HD3650 with 1026MB of VRAM and 4 GB of RAM, and back when I ran Vista x64, Fallout 3 ran like a serrated knife through butter, choppy in some places, but nothing that turning off AA couldn't fix. I tried cracking the launcher files. I've tried installing and running my Steam Version of fallout, that didnt work, and then I pirated a ISO of Fallout to see if that version would work also. As previously stated, the both don't work. Now, I also tried setting permissions, but that wasn't the problem. I even tried doing the compatibility settings, not that that would have done anything anyways, I thought it was worth a try. Windowed mode also yields ZERO results, and I don't even get the sound thing people were describing.

I'm out of Ideas and about ready to kill someone. How did you guys get yours working? I read through all 14 pages, but most of it was irrelevant to my interests.

Thanks a million
Oh, and first post!

Nevada

 

[PhoneyVirus]

ATI Mobility Radeon HD3650 this vidoecard is not for gaming with ya you may of got some games to work, but at the end of the day it all comes down to is you got a Laptop, this gear is just taking us backwards if you want to game get a Desktop PC look at the specs on the game ATI x850 Minimum nvidia Geforce 6800 Not a Mobility Radeon HD3650 15 Pages over a Laptop Hope this Helps!

Look at his Profile Nvidia 8400 your not gaming with this I feel your pain.
If you can drop $400 on a stupid Xbox360 or PS3 then you can drop that on a videocard. That's what I did and never again will I buy a videocard Under $300 Minimum, lets just say you get what you pay For!

 

[TripOG]

ATI Mobility Radeon HD3650 this vidoecard is not for gaming with ya you may of got some games to work, but at the end of the day it all comes down to is you got a Laptop, this gear is just taking us backwards if you want to game get a Desktop PC look at the specs on the game ATI x850 Minimum nvidia Geforce 6800 Not a Mobility Radeon HD3650 15 Pages over a Laptop Hope this Helps!

Look at his Profile Nvidia 8400 your not gaming with this I feel your pain.
If you can drop $400 on a stupid Xbox360 or PS3 then you can drop that on a videocard. That's what I did and never again will I buy a videocard Under $300 Minimum, lets just say you get what you pay For!

i think the 360s are only 180 or 200 for entry level and they make great windows media center extenders

 

[PhoneyVirus]

If you want a media center build your own not a stupid 360 or PS3 for the price it can be $0.2 and I wouldn't get one i got 3 PCs now that's not been used well 1 is my girlfriends an two under me I can turn in a media server or FTP server or anything i want not like a stupid Xbox 360 or PS3 never will I wast my Money on the Beeping Beep again.

 

[Nevada]

Not to sound like an ass, but this thread isn't exactly about freaking media centers, it's about people with issues with Fallout 3.

Now, when I ran Windows Vista, I was able to run Fallout 3 on High settings, and, for all intents and purposes, it ran smooth. Smooth enough that I honestly couldn't be happier. Now, on 7, my video card gets some added balls, and I can actually play FarCry 2 on DX10 (Something Vista wasn't able to handle) at around 20FPS, not to say that was great, but, it was indeed playing it at a, uh, playing framerate. Now, many of my other games are cut through like butter in 7, I can play BluRay movies when I'm connected via my HDMI output with extreme detail, and hell, I can even render my rocketlauncher models for the mod of Postal 2 I'm working on from 3DS Max.

However, I am digressing from the topic, excuse me.

The problem persists with Fallout 3 and I dont think it could be the drivers, especially since I just installed the drivers meant for windows vista ontop of my old drivers using the "use unsigned drivers" options from boot.


You know, I'm actually about ready to quit 7. I mean it's nice and all, but it is a Beta, and unless I can get Fallout 3 to work, the only game that I really play, I don't see the point in staying on an operating system that doesn't like Alcohol 120% or any of my Virtual Machine software.

Nevada

EDIT: Also, as far as I'm concerned, I've got a pretty good gaming laptop. 4GB of DDR3 RAM, An INTEL CORE 2 DUO T9400 @ 2.53GHz, a Radeon HD 3650 with 1GB of GDR3 Video Ram, and 320 GBs of Space. For $1000, this laptop was worth every penny. Except for the keyboard lag in Vista and 7, I don't like that.

EDIT2: I'm upgrading to the new 7086 x64 Build, I'm going to see if that helps...at all... And if that doesn't work, then a full reinstall of 7 is in order.

 

[error]

clean install of 7068 here yesterday...nvidia 7 drivers, firefox, kaspersky preview only programs installed. FO3 crashes after around 30 seconds (outside)

 

[smarteyeball]

I'm out of Ideas and about ready to kill someone.

I know how you feel mate. Sorry if you've tried this, but did you try running it as admin?

It doesn't actually need compatibility mode, but without 'run as admin' it was hanging when loading.

 

[PhoneyVirus]

It be alright if they where not running it off a laptop, and what's with the 64Bit OS like I said 1. You tell them 2. Your going to tell them 3. Your going to tell them what you told them... What the Beep do you have 64 Bit OS for, and trying to play games off of it. This is how it go's again STOP try to play games off a 64 Bit OS if you don't own a Recording studio or some such bull Beep to use the full pipe. It took them 10 YEARS to come out with a 32bit OS after the first 32 CPU so you can take that and double it. The first 32 OS was Windows 95 go back 10 YEARS to the CPU that support it I'm not telling you do your Homework...

 

[smarteyeball]

Phoney, who or what are you talking about? :huh:

What exactly is wrong with owning a 360?

and

Are you saying people who use x64, don't run home recording apps etc and try to game on said x64, are somehow stupid for trying to do so?

If so, I've got news for you, I've never encountered a single game issue that was caused by x64.

 

[Mark]

Phoney, who or what are you talking about? :huh:

What exactly is wrong with owning a 360?

and

Are you saying people who use x64, don't run home recording apps etc and try to game on said x64, are somehow stupid for trying to do so?

If so, I've got news for you, I've never encountered a single game issue that was caused by x64.

Fully agree with you Smarteyeball, I can play all my games in Windows 7 and Vista on x64 and they all run great aside from the issues with Punk Buster on Windows 7, but that's Punk Buster's problem not the OS.

I don't understand why you guys are having these problems with Fall Out, every time I've just installed normally and done nothing special except for using the no cd patch and it's worked perfect every time.

 

[Vimes]

For some reason when I try and play the fully patched game (using the no-cd patch) on my 7068 x64 it will randomly stop working, no other fault than the fallout3.exe has stopped responding (Faulting application Fallout3.exe, version 1.4.0.6).

Usually just before it stop responding I have noticed in my crash logs that Games for Windows - LIVE DLL has a problem (yellow warning triangle and not the red circular error warning within the applications logs), about 3 minutes or so before the game locks up.

Title Fallout3.exe (1.4.0.6) XLive 2.0.0673.0 (PANORAMA_V2.00_RTM.081028-1714) C:\Windows\system32\xlive.dll
0x80004005

Games for Windows - LIVE DLL
C:\Windows\system32\msidcrl40.dll 5.000.737.6

I have installed the latest Windows Live but still the problem occurs.

Using the same build of the game and same load order and Vista 32 it runs without any errors and no crashes.

Strange and yet I find that due to the above I now need to run Vista 32 as I want to continue my Fallout campaign but it is too problematic under Win 7.

EDIT:

I might have found a solution to this, still trying it out though...

I am using 2 x 2GB sticks of OCZ PC 8000 memory @ 1000mhz and I have now upped the voltage to 2.1v from 1.8v. As I was getting a stop message 0xc0000005 within the application logs that could be indicative of a memory problem.

 

[smarteyeball]

Probably a silly question, but if you suspect the memory have you run memtest86+?

 

[PhoneyVirus]

smarteyeball may be right run Memtest86+ to see if that could be it. I know that FO3 needs Games For Windows to get Ach's but try installing the game with out the Games for Windows then try the NoDVD Patch hope this help! Tip don't play with voltages you will lose something.

 

[Vimes]

Thanks for the suggestion, yes I have left the PC running memtest all night and checked the following day to find zero errors.

Alas it caused another problem - again crashing as above but this time the error was only with the live dll.

I am now booted to Vista and the game plays without fault.

A shame really as W7 is perfect in every way, my other games and applications work without any issues, but Fallout just so happens to be the game that I'm playing at the moment and typically it is that one that W7 is having some issues with.

As for the memory it is rated at 2.1v but my motherboard sets it at 1.8v as default and then needs 0.3v adding. I never bothered with the 0.3v as it passed running memtest for over 12 hours and all other stress testing has been fine. It was more of a desperate measure to up the voltage to the recommended specification, which didn't work anyway.!

 

[Nevada]

Yea, a mighty shame.
The only thing that's pissing me off about Windows 7 is just...Fallout...

Everything, minus Alcohol 120%, just seems to work with Windows 7. And, having to work with computers running 64 bit Operating Systems on a daily basis, I can say that they are extremely stable, contrary to what everyone else says regarding, well, anything. Granted some applications cant run on the 64 bit platform, that's a minor setback to being able to fully utilize over 4gb of ram. Same goes for Vista. I havn't encountered a single problem with it, I just don't get what the hype is.

Anywho...


I'm going to use one of the application loggers like what Vimes was using and see if I cant find a problem. I'm starting to suspect that it is a Game For Windows problem, but that wouldnt make sense because I can play GTAIV just fine.

A special note to PhoneyVirus:
Grammar, it's your friend. So are periods, spaces, commands, semicolons, and, well, just about every other part of the English Langage you butchered in your past few posts. As, as for why I'm running 64bit Vista, I need it for not only work, but also to utilize all 4GBs of my RAM. So, try to find a different way to be an ass.

EDIT: I tried to run Fallout and it ran! April Fools! Didn't work. But here's the appcrash data.
Problem signature:
Problem Event Name: APPCRASH
Application Name: Fallout3.exe
Application Version: 1.4.0.6
Application Timestamp: 4981c35c
Fault Module Name: Fallout3.exe
Fault Module Version: 1.4.0.6
Fault Module Timestamp: 4981c35c
Exception Code: c0000005
Exception Offset: 007ee0b5
OS Version: 6.1.7057.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 1c1f
Additional Information 2: 1c1fa4195bb39b2113309d4e178cab0a
Additional Information 3: 667a
Additional Information 4: 667afb58659e2cd6bb69b460ebe0ae14
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[Vimes]

full sized image here...

http://www.imagebam.com/image/32d69831497380



@Nevada - have a look within the above logs to see if you too experience any issues with xlive preceding your crashes with Fallout.

The red Error one above the yellow xlive issue is similar to the error message that you have noted in your post.

Whilst it is good news that you can run GTA IV fine using xlive you will appreciate that the interaction between xlive and any particular game doesn't mean because one can run fine then all your others will be ok.?

Did you also need to install the latest version of xlive to get the game to even run with W7..?

I am tempted to test out the x86 version of build 7068 to see if that produces the same errors as I'm finding with the 64bit version.

Whilst I like the fact that all of my 4GB can be addressed and utilised when I use 32bit OS then 3.5GB is available, the difference in practical terms for me is meaningless.

 

[Nevada]

Nope.
I just get the error upfront, no warnings for the XLIVE app. I'm actually going to install Vista over windows 7 right now and go back to running Vista 64 Until new drivers can be released for my card.

 

[Ki Shodar]

Just installed 7068 with the latest nvidia win7 beta drivers and experiencing the same crashes in Fallout 3 as other people have mentioned. Worked fine indoors but outdoors once I use VATS it crashes.

Also seeing the xlive error in the event log.

Is anyone using the latest nvidia Vista drivers in Win 7?

 

[Vimes]

FWIW I have an ATI 4870 with the 9.3 CATS. I have gone back to Vista 32 and Fallout works perfectly. I still have W7 7068 x64 on my other hard drive to boot to but trying to play Fallout is too problematic.

 

[Ki Shodar]

I just installed the 182.06 vista x64 drivers, replacing the 181.71 win7 beta's and took a quick run around outside using VATS and fast travelling without any crashes.

I can even use my main soundcard now (had to use my onboard earlier, else I couldnt even get in-game)

I'll have to test it out more later.