7thsealord

Thank you for responding, TT. Lessee, running through System Properties - Windows XP Pro, SP 3, Athlon 64 X 2 Dual Core Processor 3800+, 2.01 Ghz, 3.0 Gb of RAM. Assuming I have looking for the right thing as regards display drivers (probably not ;) ), that's NVIDIA GeForce 6600 GT. Now, for all I know (bugger all, I freely admit) people are throwing their hands up about now, and asserting that FO3 CANNOT be stabily run on the above. Fact is, I have. Gotten at least one character up to level 20+ with a buttload of small-to-middling mods and with no problems other than a very occasional random crash - and the big problem mentioned above (which doesn't happen always, but when it does ...). When the latter happens, it is as if a switch has been thrown - doesn't matter if I literally take a chainsaw to all the mods added up until then, the problem will persist for all games saved up to that point. If I want to keep playing the game when this happens, the only option so far has been to make copies of my Save and Data files, then do a total uninstall / reinstall of the entire game, pray that my clean-up has been thorough enough (the problem can persist), then move the saved files back into position and (hopefully) carry on. I should also add that the message ONLY crops up for FO3, not for any other program on my system (admittedly, none are likely to be nearly as demanding as FO3, but there you go). Also, it SEEMS to be connected with adding sizable mods ('sizable' being 1 meg or more), but not always. Suppose I could stop using any mods, sure, but I have no way of knowing whether or not this problem will sneak up on me regardless. Also, there have been a couple of VERY large mods ('AFS Brisbane', for example) successfully run without triggering this problem. Googling '0x00627180' turns up a number of results directly connected with FO3. Seems that this may not be a one-off problem as such. A few vague solutions offered, a couple upholding the virtues of adding the 'd3d9.dll', but I thought that if anybody knew for sure, they would be here on this forum. Whilst there may be something rattling around in my computer that is part of the problem, it is very hard to get away from the idea that most of the problem is on FO3's side. Any advice (other than "Get a better computer" or "Perform radical surgery on a system that is otherwise working very very well" ) would be greatly appreciated.

*Sigh* Anybody?

May well be that this problem has been thoroughly solved elsewhere on this forum (Ghod I hope so!). If so, I apologize, and could somebody please refer me to the right place? Fallout3 GOTY (plus FO3E, FOMM, Archive Invalidation and G4WL Disabler). Windows XP. Computer a few years old but, with settings pared back, I have no major problems running FO3. Except this specific problem, natch. Keep getting the following message. ----------------------------- FALLOUT3.exe - Application Error ----------------------------- The instruction at "0x00627180" referencedmemory at "0x00000000". The memory could not be "run". Click on "OK" to terminate the program Click on "cancel" to debug the program (Followed by Microsoft's usual 'Error Report') Frankly, the above has become the bane of my existance - if my FO3 game goes bad, it is via this exact same message every single frackin' time. It seems to crop up after I install a largish mod, but persists even after that mod had been completely removed. So far, the only "solution" seems to have been to do a total uninstall / reinstall (saving the Save and Data files separately). Needless to say, that's gotten old real fast. This time, I re-did the whole game from the ground up - everything, and that #$%^&* message turned up within the first 2 or 3 rounds of saves. Tried Google, which referred me to the 'd3d9.dll'. Assuming I placed it right (in the Fallout3 folder, right?), all this seemed to do was prevent FOMM's FO3 launcher from working and keep the game stuck in a permanent state of loading. Any help would be greatly appreciated.