Fallout 1 memory error

Обновлено: 08.02.2023

Enneagon: Wow, this is really weird.
I can’t see who would benefit if he started a duplicate tread for problem he experienced.
Well, now this off topic ranting ensures next one should.
Oh well.

almabrds: I don’t know what is worse, the guy which revived the thread, or you, which just did a totally useless bump to the ancient thread without adding anything interesting to the conversation.
But at least Gawdzilla informed us that the bug also happens in Fallout 2.
So his post wasn’t a complete waste of time.
The same I can’t say about yours, unfortunately.

If he had created a new topic (which would be the right thing to do), it would not really be a duplicate, since it’s a bug in another game.
Fallout 2 is not Fallout 1, dude.

«Think twice before you speak, because your words and influence will plant the seed of either success or failure in the mind of another.»

I can’t believe you guys debated this for another page and a half.

Gotta make a few points —

1) Fallout 1 and Fallout 2 used the same engine. A bug in one game appearing in another is noteworthy, as one of you did point out — players of both games have an interest in resolving the bug

2) Despite saying I contributed «NOTHING» to the thread, in fact I posted a detailed workaround for the problem in FO2. Apparently the only part of posts some of you guys read is the date/time signature

3) Necroing is bringing back a concluded post. This one is clearly marked at the very top with the following words: «No posts in this topic were marked as the solution yet. If you can help, add your reply.»

4) For games that came out 15+ years ago, it shouldn’t be a surprise many posts, bug discussions, support questions, etc. are «old.» Honestly, GOG forums is the only place I’ve run across where anyone makes a stink about such a thing.

5) No one cares what some permarage user thinks are the «rules» for posting on the Internet. If an actual Admin here says I messed up I’ll accept that.

Happy holidays, everyone

I couldn’t help myself from «necroing» this post after I saw how the people above reacted to the 2nd OP. I hope you all see this and get annoyed again.

On to the topic, on FO2 + Killap restoration, this issue is still present and UNSOLVED. I thought I have been managing it with doing things slightly differently every time I encounter it. But it finally caught up with me and now I have a «corrupted save». This is my probably around 10th play through of the game and first time losing significant amount of progress, I am not sure if it will happen again in this run so kinda considering ending this run here.

There is no permanent fix to this, just some suggestions to try to avoid it. Any new suggestions are welcome, this game is not played much so I doubt this will ever be solved completely but I am willing to try anything new.

Oddly enough I’m getting this error in Fallout 2 but before actually getting the game running. My instance of it seems to be tied to graphical troubles.

Specifically I’m getting «Instruction at 00366fd1 referenced memory at 00000000», although I doubt the specific memory address matters.

Interestingly Fallout 2 isn’t available for macOS on GOG at the time of writing. It’s still available for me to download for macOS though (presumably I’m grandfathered in). The initial download runs although it’s the unmodified, low resolution 1.02 version. It’s packaged using Wineskin.

Install the Fallout 2 Restoration Project appears to break it. I’ve removed the registry entries that enforce compatibility mode to get past the «Fallout appears to be running in compatibility mode» issue and then used the resolution selection program from the bundled hi res patch to set an appropriate resolution. Launching after that gives the error.

I suspect this is an issue with the updated Wine bundle as I’ve had the game running happily before. However, there is also good news. I’ve managed to get the sneaky blighter to behave.

First off this involved going into the application (right-clicking to do «Show Package Contents») and opening up the contained Wineskin executable. From there I pressed the middle button on the bottom row, «Set Screen Options» and told it to run at my full resolution, in a 24 bit colour depth, full screen, with the Direct3D boost. I’m not sure how many of those are needed but you can always experiment.

Closing that particular menu I used another tool from the Wineskin executable — Task Manager. Browsing into the Fallout 2 directory I was able to run the high resolution patch (it’ll let you launch any Windows executable really) and tinker with the settings there.

After a bit of testing it would also seem there’s issues in the ddraw.ini file. At least for me if GPUBlt is set to 0 or 1 then the game will not launch. Setting it to 2 so that the CPU is used for palette conversion worked. I didn’t notice any difference when it came to the Mode= parameter. Both 0 and 4 worked.

It seems like issues with graphics and Wine can cause this error in addition to other things. Yay!

Edit: It also seems that by downgrading the engine used by Wineskin to 1.7.x performance was much improved, although that did involve me creating a new instance of Wineskin and dumping the GOG files into it.

(Also reading a load of you moaning about forum etiquette was a real blast from the past. There’s a time and a place for it and neither of those are in a thread dealing with complex errors in 20+ year old games. People are going to be playing these games for many years to come, they’re classics. Having threads covering potential errors and solutions for them is super useful. I’m pretty much providing the info I am here so that future me can get some help from past me.)

у меня когда играю в доту вылетает ошибка(может в начале. конце когда угодно):
war3
This application has encountered a critical error:

Program E:GAMESwarcraftIIIwar3.exe
Exception: 0xc0000005(ACCESS_VIOLATION)at 001B:6F4CBDBB5
Thi instruction at ‘0x6F4CBDB5’ referenced at ‘OxXE8873AC’
This memory could not be ‘read’.

Press OK to terminate the application

Умоляю помогите.
Я с етим оч долго мучаюсь.

Наблюдал такое очень давно на версии 1.21. Но там с критом в доте вышибало вообще всех игроков. На патчах начиная с 1.22 такое у меня никогда не происходило. Попробуй переустанови игру, поставь последний патч и загрузчик. Даже и не знаю чем помочь.

То что я перепробовал:
переставлял варик, систему, добавил озу, менял всё в настройках, включал, отключал антивирус, скачивал и ставил разные патчи

Аналогичная проблема у друга. Принес ему свой вар ( у меня не было пока что ни одной ошибки ) а у него точно также в любой момент может выдать фатал ерор. Даже после переустановки ОС тоже самое. Скорее всего тогда проблема в железе, и опять же хз точно.
Самому интересно узнать что и как сделать чтобы убрать это.

а теперь он стал просто вылетать без ошибок. помогите плз

НАРОД У КОГО ПРОБЛЕМЫ С ВАРОМ КОГДА ФАТАЛ ЭРРОР.
ВНИМАНИЕ: УБИРАЕМ ЗВУКИ В ИГРЕ(галочки в настройках) играем без звука но играем, была такая ересь походу несовместимость со звуковой или дровами

там не совсем звук, или звуки, неахота лезть. [Cube]._R_ прав, поотключайте галочки там.

Ну блин без звука как то уныло. Пусть уж лучше вылетает иногда. У меня это происходит где то раз в 5-7 игр.

Я тут посмотрел в инете решение проблемы, так вот несколько вариантов:
1. Надо увеличить оперативную память;
2. Надо улучшить видюху и звуковую карту и дрова на них;
3. http://ftp.blizzard.com/pub/war3/other/war3.reg — жми «Сохранить как. » и открой, тем самым добавив инфу в реестр.

А также, кто знает англ, советую прочитать:

HELLWOLF’S GUIDE TO FIXING FATAL ERRORS — AN ADDON TO N_’s INFORMATION

Greetings Forum Surfers and newcomers. If N_’s guide doesn’t help you with the problem (Trust me, it won’t). My LONG guide of solutions should be able to fix your solutions. This will work with generally any 0x8E (Unhandled Exception) or 0xC4 error. How I know these will work? I have written this guide thru experience since my first computer suffered like this. I fixed it with a new PSU and DRAM Voltage, now it crashes from triggers . However, I have no assurance whatsoever that your problem will get worse, you decided to do this so do the advanced issues at your own risk .

-Bad Drivers
Update your video card when new drivers come out. Go to your manufacturer’s website to download the latest. For ATI, its Catalyst. For nVidia it’s Forceware. Just remember you need a 32 bit version of Windows XP or Vista or 2000 to operate these drivers properly. There are no real 64 Bit ones yet, and your drivers will fail to install on a 64 bit machine.

-Insufficient or Ineffective RAM
Get more RAM, make sure its of the right frequency so it doesnt lead to incompatibility. Eg. If you can support DDR 400, then get them both at DDR400 and have the same voltage. You will need to look at the sticker that comes on the RAM and break down the format to extract this information.

If you think it’s a certian stick of RAM and you have more than 1, take out one, and run Warcraft III. Then repeat for your other RAM. If one stick is causing the crash, then replace it with one that works. If it’s 1, then you will need to replace it. The best way to detect this problem is checking your crash logs and looking for the memory address that crashed. You can also install and run MemTest86 to find out which addresses aren’t complying and which ones are.

-Motherboard Conflicts
This is one nasty mother ****er. You would need to either update your current drivers. Or even go as far as Flashing a new BIOS (requires reinstall and hopes that it doesnt crash in reinstallation). Or even to disect your computer and install a new motherboard (4-5 hrs. you dont want to do). This is a rare occurance, I have never seen a Motherboard conflict, unless you did something stupid like drop a magnet on it or broke a piece of it.

-PSU not strong enough (STRONG POSSIBILITY)
This is the most common problem that is often overlooked. It happened to me when I owned a JGE 300W PSU before I got it replaced. It wasn’t passing enough volts through the 12V Line (15A). Open your case, and look at your PSU label for the 12V line(not colour, the AMPS). If the number is below 20-22A, then you need to get it replaced. Its not sending a powerful enough current through the motherboard to power everything! For watts, aim towards 450+ to your PSU. However, brand will determine how AWESOME it is. Get a well known name brand (Antec for example), otherwise the PSU could fry or explode if the parts are cheap or defective (we can’t have that). Plus, some brands don’t have good warranties, so you cannot get a proper replacement should anything happen to it.

-Your running 3D sound with a card that doesnt support it (makes a different error message)
This will make a different error message. Saying that the mp3 was failed to initialize. Users running a RealTek Audio chipset will have to turn off 3d sound to avoid this problem. If your sound card/chipset supports it, then you are safe and can turn it on. I recommend Sound Blaster Audigy or X-Fi to operate 3D Sound.

-You have anti-aliasing on (wc3 hates this feature, water.blp doesnt load right)
This was a bad issue back when ATI Catalyst was around 4.5-4.8. Anti-aliasing was always on and Warcraft III is a real prick when dealing with Anti-aliasing, mostly because the water models wouldnt be able to work properly. Find a way to turn it off, or install 4.10+ (anti-aliasing wasnt on default in those versions).

-You’re running openGL (remove -opengl tag) from Properties
If you right click on your shortcut and select Properties, you’ll find where your shortcut is running to. Look at the end of it, for the -openGL tag. This shouldn’t be here. We live in a world of Direct3D now. The only purpose OpenGL servers is probably playing Unreal Tournament 1999 and Doom II, since these games actually looked better in OpenGL than Direct3D. Other games may not take OpenGL kindly.

-Virus (STRONG)
You could have a virus that is plaguing your system. You can run an anti-virus scan or reformat your hard disk. Reformating clears everything (requiring Windows reinstall) but you will have nuked the viruses. Use Norton (if you want a virus within itself) or AVG (it’s free), Proxomitron or Spybot to keep these threats neutralized.

-Too Many programs running at once (STRONG)
Control Alt Delete > Close off any programs that you don’t want running. To free up physical memory so your RAM doesn’t overload and close Warcraft III. The only situation this is a problem is with programs that conflict with each other or if you blew your Virtual Memory cache (The portion of the Hard Drive that writes page files should you inflate your RAM).

-Models could be rendered incorrectly (updates and fixes, custom models)
Not really a common problem, was in DOTA. Some custom models may have not been done incorrectly and the game will crash. Not much you can do, update your game and use models that work properly for best effects.

-DRAM Voltage TOO LOW!!
Another problem, it requires you to tamper with your BIOS settings. Load up the BIOS the way would do it. Then find the option called DRAM Voltage (should be in Power Management). Set it to the maximum value. If your BIOS warns you about it being unsafe, just do it anyways. Be sure your PSU can take the heat.

-AGP Aperture Size
The value of this must be half of what your video card is (Eg. if its 256MB, then set Aperture to 128MB, and so on). If you use the full value, your card will stop working properly! By default, the Aperture of the card is usually set to Auto, which adjusts based on the card installed.

-Fast Writes and XAGP
My old Windows XP machine usually had this at 4x and Fast Writes on. If your computer can support it, go 8x and Fast Writes. However, your motherboard needs to have the feature. BIOS has an option called AGP Fast Writes within it, it must be enabled to work properly. Check your motherboard specs to make sure you know what the limits are.

-Overheating
If parts get too hot, they will stop functioning properly. Use better fans or cooling systems to operate these parts and keep them cooled. It can also help to open your case to regulate hot air. Just make sure you keep the open side away from your feet, your dog or whatever. I recommend you only open the case when you want to install new parts.

-Internal Engine issues:
This happens to me in The last Sylvannas mission and the older versions of DOTA. It could preform an operation that the system really hates. Wait until future versions of the map come, it could solve the problem about whats happening. For me, this also happens sometimes when I cast Storm, Earth and Fire in Melee or when I transition a hero unit to something like a bear or a storm crow (hero > unit or unit > hero by skill, not trigger). As patches go on, some of these bugs are corrected.

-CD Cracks (for you warez boys out there )
You most likely have a CD key or an illegal burned copy that needs libraries or certain files that would appreciate it if you had the real version. Do us all a favor and buy the REAL expansion, reinstall Wc3, and that should fix your problem.

If you decide to reinstall Wc3, keep your maps you want to keep in a seperate folder so you can copy them to the map folder later. The only reason you may want to reinstall is if you reformat your Hard Drive.

If you need any further questions, PM me or contact me on MSN. If you do so in a inpolite way, have had the problem only occur once or rarely; I will NOT! answer you back, I may even block you. I want to help, but I am a busy person sometimes and I don’t appreciate getting **** yous or assholes when I want to explain how to fix your motherboard problems.

У кого вылазиют такие ошибки:
1)your system does not have sufficient video memory to play this game
please exit some applications and try again
2)d3d error your monitors aspect ratio of 683:384 is incompatible with this game

Делаем следующее:
1) Жмём пуск.
2) Вписываем в поиске %appdata%
3) Открываем папку MKKE
4) Находим и открываем файл dxdiag
5) Находим строчку dedicated memory и меняем её значение на 1024
6) В свойствах файла ставим галочку «Только для чтения».
7) PROFIT.

Проблема с игрой на Windows 7. А точнее проблема с цветом. Вся картинка установки, роликов и главного меню в разноцветную крапинку. Сама игра путает цвета. Кто-нибудь с таким сталкивался? У кого-нибудь игра на Windows 7 нормально работает?

P.S. Проблема возникает как на Fallout 1-2 от Фаргуса, так и на Fallout 1-2 от 1С.

Если что непонятно будет с ним — пиши, скажу как что делать.

Shifroval
Совместимости выставлял все какие есть. Попробую через твою прогу.

Там в Сфолле можно выбирать другой рендер и разрешение, в отличие от стандартного и глючного DirectDraw. Плюс он правит скорость передвижения по Пустошам(и для многоядерников!) и работу перков Снайпер и ещё какого то.

Помогает избавится от многих глюков с графикой.

Для Ф1 и Ф2 Сфоллы разные!

Не помогло Похоже придётся играть на ноутбуке, а там экран сильно сжимается

Так. ты точно сменил в инишнике параметр
Mode в разделе [Graphics] на Mode=4?

Можешь ещё TextureFilter=1 поставить.

Т.е ты прописал 4й mode и фильтр?
И всё?

Просто на будущее, мало ли, вдруг тут будут подобные ситуации возникать.

З.Ы. Лови плюс в рейтинге по халфе второй)))

Скорость попробуй порегулировать скейлом, повыставляй
ScaleFilter=0
от 1 до 5

А вообще тут бы фреймскип, но как написано в инишнике, с дх9 он не пашет.
Но там внизу можно как то замапить коды клавиш и там есть скорость и фреймскип.
Нужны сканкоды директикса, я их не знаю :))

Тааакк.
Параметр
;Increase/decrease frame skip.
IncreaseFrameSkip=0x51
DecreaseFrameSkip=0x4f

Это правый шифт и F10, судя по всему.
И вроде ещё нужно альт держать при этом. О_О
Короче, я в этом ничего не понимаю хDD

Насколько медленно?
Ты уверен, что это именно медленно? И разве когда то было быстро?
Вот на машине да, быстро. А пешкодрапом ползти и ползти.

Хз. Играю в первый раз). До установки SFall переход между локациями был быстрый).

Ну так там то глюк, от того, что проц быстрый(и двухъядерный), а то что ты видишь с sfall — настоящая скорость передвижения.
Как будто запускаешь Ф2 на старом пеньке 3 или 2.

скорость передвижения хорошо видна первом фоле — с такойже скоростью передвигается как при сфолле во втором

на хр все нармально идет но можешь поставить прогу для выше перечисленного

так поставь хп,а такую древность можно и не играть поиграй в 3 часть у тя комп норм.?

слышь фол2 самая лутчая игра а третий просто не дорозумение

меня выводит из себя одно название этого ужаса

Да а ты у будущего поколения спроси а мне 13 и еслиб не зборник всех фалаут я б пожизнено в 3 шпилил а?

Xaker 23
Поиграй во вторую или в первую. Или мозгов, больше чем на тупую казуальщину aka третья часть, не хватает а?

из-за таких людей как ты люди начинают думать что все что старше пяти лет можно назвать прошлым

я играю в фолл2 округленно со второго класса и возрост ни очень у нас разный(я старши)

тут собрались фаны 2 фола а он говорит что игра не очень

я же не говорю что игра Brothers in Arms: Road to Hill 30 говно на форуме про нее

Я не только тебе говорил, я говорил всем, и этому хакеру тоже.

Спасибо, вcе работает правда для 1ой части пришлось качать патч 1.2

Скачал,распаковал, изменил занчения на 4 и 1, 5 и 1, тут же закрывается. не помогло

У кого проблемы ещё есть с цветом в вин7, качайте Resolution Patch v2.2, для каждой части свой патч.

У меня второй фолл вообще запускаться отказываеться на W7 хомяк, на секунду загорается экран загрузки и сразу вылет без коментов. Режим совместимости XP, 256 цветов, разрешшение 640х480, запуск от админа не помогают. Устанавливал глобал мод в составе которого есть sfoll, тоже самое. Фича с запуском на фоне открытого диалога выбора разрешения экрана не помогает. Батник убивающий оформление рабочего стола перед запуском, не помогает. Установка directx9_feb2010_redist не помогла. Полные права доступа екзешнику не помогло.

У когонибудь есть еще идеи? =0

З.Ы. Снести нах семеру и поставить XP не предлагать, у самого руки давно чешуться, останавливает только то что она была мне насильно втюхана вместе с компом =(

качал Sfall. выдает надпись не думая что «Fallout appears to be running in compatibillity mod». Виндоус ХР, ставлю на версию 1.2 от 1С.
Изначально — проблемы с цветом

качал Sfall. выдает надпись не думая что «Fallout appears to be running in compatibillity mod». Виндоус ХР, ставлю на версию 1.2 от 1С.

Тоже самое только у меня от фаргуса версия а если совместимость убрать в ярлыке он пишет *You’re trying to use sfall with an incompatible version of fallout Was expecting ‘Fallout 2 v1.02 US’

Читайте также:

  

• Как убрать траву в unturned

  

• Ошибка сталкер чистое небо точка входа в процедуру

  

• Как поменять гудок в forza horizon 4

  

• Mass effect 3 системные требования

  

• State of decay вылетает