Fatal error address life is strange

Life is Strange has a unique story that might seem complex at first. As you progress into the game, you will get more and more invested in the story and the game will keep getting interesting. There are many twists and turns to the game and the rewind feature is very unique. The game is divided into episodes that last for a few hours each depending upon your gameplay.

Unfortunately, some players are experiencing difficulty in launching their game. If you keep getting Fatal Error in “Life is Strange” as soon as you launch the game, then here are a few methods that can help you with the error.

1. Check Config Files

If you’re lucky then you’ll be able to get around this error by validating your game files. That way your client will download the files that are missing from your PC and then you’ll be able to launch the game. To do so, you can access the game properties and then verify files from the local tab.

It will take a minute but after the verification is done you should be able to get your game working again. However, if you’re still unable to launch the game and are on Nvidia GPU then you can fix the error by copying and pasting the game file onto your Nvidia Corporation folder.

You will have to find the PhysXCore.dll folder from the “Life is Strange” game folder and then copy it to the Nvidia Corporation folder. Specifically, you will need to navigate to the “DB8A731FDBD5” and then paste the PhysXCore file in that location.

You can use the search bar on your file explorer to find the folder mentioned above. Alternatively, you can also find the complete file path online. After pasting the file you can try launching Life is Strange again and it should work without further complications.

1. Background Processes

A few users said that they were able to fix this issue by terminating background processes and then launching the game again. So, if you’re using any program that can interfere with your game then it would be best to terminate it using the task manager.

Make sure that your game is the only thing running on your PC and no third-party applications are working in the background. Make sure to disable all the overclocking features on your GPU and reset everything to default settings. Then launch Life is Strange again after rebooting your PC.

Along with the overclocking programs like Riva Tuner, you also need to disable the security programs on your PC. Make sure that the game has administrator permission to access the configuration files and make changes to your computer.

But if you’re still on the same error then it would be best to go ahead and remove the game from your PC entirely. You can do that by uninstalling the game from the Steam client. Then you can install it again after a quick reboot and hopefully, it will work without any errors.

1. Check Drivers

If you’re still unable to launch the game then we suggest that you check your graphics drivers. Make sure that they are up to date and then try launching the game again. If that doesn’t fix your issue then you should use DDU to remove them from your computer and then download graphics drivers again.

However, if you’re in a situation where this issue started happening after updating your windows then you can use the system restore feature to potentially fix the error in your game. This will only work if you had already made a restore point before updating OS.

The majority of Nvidia users were able to fix this problem by moving the PhysXCore file from their game to the Nvidia folder. So, make sure to try that first, and hopefully, you won’t have to go through with all the other methods mentioned here. But if you’re still not able to launch the game then your best bet would be to submit a ticket to the game support.

That way a professional can take a look at your situation and you can follow his instructions to fix your game. You can head over to the Square Enix web page to submit a ticket.

Message fatal error address

When I start Dishonored after a few seconds the following text appears on my screen,
«Rendering thread exception:
Fatal error!

Address = 0x0 (filename not found)

I’ve verified integrity of game cache and it said I have all my files for the game. Any help would be appreciated with this. I don’t have a clue what to do so if anyone could help me with finding a solution that’d be great. Thanks in advance.

Are you using an AMD card — if you’re using NVIDIA make sure you’ve got PhysX installed.
If you’re on the red team (using AMD) — Try this:

Open this file in Notepad:
SteamLibrarysteamappscommonDishonoredEngineConfigBaseEngine.ini
And press CTRL+F and look for «PhysX»

First result should be this:
bDisablePhysXHardwareSupport=True

Change the value «True» to «False», save it and launch the game to see if that fixed it.

Also go to your SteamLibrary and within that:
steamappscommonDishonoredBinariesRedist
and run these in admin mode:

vcredist_x86_2005sp1.exe
vcredist_x86_2008sp1.exe
vcredist_x86.exe
vcredist_x64.exe
There should also be a DirectX folder within the «Redist» folder, open that up and find «DXSETUP.exe» and run that in admin mode too.

After installing all these, restart your computer and try to run the game.

Go back to: SteamLibrarysteamappscommonDishonoredBinariesWin32
and delete the following files:

Make Steam check file integrity again, it will re-download these files.
After it finished downloading, try running it again.

Источник

Message fatal error address

Hi guys, I have updated my computer. Deleted and re downloaded and created a new account. BUT I am still receiving this error message when opening the game. Does anyone have any advice?

Address = 0xb7e543 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x29108e (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x28c605 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x2349b6 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x2349ee (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0xa367ec (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x234721 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x27b46e (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0xa6333e (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0xace605 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]

I never said that it is a faulty memory that causes the issue. CPU is fine. RAM is fine. Program is fine. No game data is corrupt, missing nor damaged.

Out of many wildly bad things you’ve said, you also said the addresses in the dialogue indicates a memory fault so you can trace that. You said it was a fault in memory. You kept throwing up random links to support your statement, and you’re totally not understanding that this is NOT what is happening to the game!

That is just YOUR INTERPRETATION of what I said .

I still claim that your issue with understanding English is responsible for your inability for proper reading and understanding of what I am writing.

I still claim that your bad English understanding is responsible for your inability for proper reading and understanding of what I am writing.

Some player starts the game and the message like in OP appears. What does he do?

1. Opens the terminal and executes: sfc /scannow (checks Windows system files incl. WoW64),

2. Opens the terminal and executes: chkdsk C: /f /r (checks and repairs C: drive),

3. Verifies/repairs the game files over the Steam interface.

The player starts the game and again the message like in OP appears.

There are no missing nor damaged, nor corrupt files nor permissions (sfc & chkdsk!).

CPU is OK. RAM is OK. Software is OK.

However, the memory issue in the message “Address = 0x . (file name not found)” is still there. Why?

However, the OCCURRENCE “Address = 0x . (file name not found)” still appears in the message. Why?

(The correct sentence with “occur” would be: However, “Address = 0x . (file name not found)” still OCCURS.)

On very rare occasions, some drivers or third-party applications (e.g. Antivirus Software, MSI Afterburner/Riva Tuner) can also be responsible for such memory issues showing up in warning messages.

Some player starts the game and the game crashes. The message in the stack of the thread (inside minidump file) appears:

Dump File: UE4Minidump.dmp : C:UsersQianaDownloadsDUMPSAppDataLocalUE4GameSavedLogsUE4CC-Windows-7AF90F234C2D05F05E84BB953D583124_0000UE4Minidump.dmp
Last Write Time: 03.09.2020 18:20:19
Process Name: UE4Game-Win32-Shipping.exe : D:PortablesLife is strange lowWindowsNoEditorEngineBinariesWin32UE4Game-Win32-Shipping.exe
Process Architecture: x86
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Not Present

Nothing happens on launch, no pop up error, no nothing — just this crash dump.

What does he do?

1. Opens the terminal and executes: sfc /scannow (checks Windows system files incl. WoW64),

2. Opens the terminal and executes: chkdsk C: /f /r (checks and repairs C: drive),

3. Verifies/repairs the game files over the Steam interface.

The player starts the game and again the message like above appears.

There are no missing nor damaged, nor corrupt files nor permissions (sfc & chkdsk!).

CPU is OK. RAM is OK. Software is OK.

However, the memory issue in the message “Adress = 0x . ” is still there. Why?

However, the OCCURRENCE “Address = 0x . (file name not found)” still appears in the message. Why?

(The correct sentence with “occur” would be: However, “Address = 0x . (file name not found)” still OCCURS.)

This exception code and the exception information shows us that .NET does not allow one application to even attempt to read/write memory that it is not supposed to.

The first suspect would be a corrupt file, but it is not — the exact same file (a set of files known as “the game”) works without any problem on half a dozen of other machines — the game rejects to start only on that one.

4. The Windows Event Viewer will show us “atidxx32.dll” (a part of AMD driver) as the real culprit .

The issue of our polemic is about properly understanding and interpreting warning messages.

The TOPIC of our polemic is about properly understanding and interpreting warning messages.

I don’t know what’s your issue with the issue, but I clearly see that you have issue with understanding of what I am writing.

I don’t know what’s your PROBLEM with the issue, but I clearly see that you DO NOT UNDERSTAND what I am writing.

The obvious here is that your issue is responsible for your misinterpretations of warning messages and dump files.

The obvious here is that your LACK OF EXPERIENCE is responsible for your misinterpretations of warning messages and dump files.

Atop of it, “an issue” is not exactly the same as “the issue” and that’s why .

. “memory issue” (=== pointer in the stack of minidump file showing the virtual memory address that didn’t return the expected value) does not always necessarily mean “the problem with memory”, “memory fault”, “memory error” etc. and has exactly nothing to do with “the memory IS (or IS NOT) responsible for . ”

If it is not only a language problem responsible, then it’s tragic.

My reply to you is that is NOT what that means. The pointer is simply an address RAM is reading from, and this is no indicator of the system having issues nor anything to do with RAM. An actual memory fault would produce a different dialogue, like the one I demonstrated. They are completely different things. No amount of links you spam is gonna change the fact they are two different things and the problems function differently. Instead, as I explained now countless times, it’s an installation error. They can affect many different files at once. It could be a bad setting in game. It could be bad files. Anything else is not relevant because they are not the main cause of the problem.

If the game had some issue such as it being installed in the wrong version of Windows when you’re trying to run it there, it would have said it couldn’t run/install there. This is not what the «fatal error» here is for. Every type of error has its own dialogue and they are different things. There’s a dialogue for just about every one, so that it is clear to understand what it is about. You’re trying to «interpret» it, and you’re doing so in many bad ways, because everything you’re trying to explain that is causing it is in it’s own dialogue, and this is not even one of those things.

The «Fatal Error» is not thrown in there to say it is pointing to the computer being at fault because you’re running it on that, else there would be something for that. That is not what this one means. Instead, fatal errors are basically what happens to «badly cooked» games, or it responds as if it is one, saying that the system designed in the program just cannot run with the bad components . Real simple.

None of that has anything to do with the machine itself. The hardware doesn’t have to be affected by it. The architecture of the system isn’t the man cause. All of it can run the game. The issue is the game is not compatible with the files it is trying to use , not whatever is being used to run the machine.

So stop saying that stuff. This is NOT what the problem is about. Stop trying to spam links to prove yourself. You’re just simply wrong and refusing to accept understanding you’re describing this very badly and you’re very, very, very wrong.

Struck by the puck, and you don’t see that icepicking on me can’t help?

You could have shortened it: The issue is (in most cases) 32-bit vcredist.

As you say: it’s an installation error.

There are no “bad components” and “the game is not compatible with the files it is trying to use” — the exact same game runs well for the vast majority of players.

The experience shows that installing (or reinstalling if it was already installed) the propper prerequisites — mainly a 32-bit version of vcredist (on a 64-bit Windows) and sometimes reinstalling graphics drivers, solves that kind of problem in the most, if not in all cases.

If you’re interested:

What you see under «Fatal error!» in your screenshots is what’s called a stack trace. The stack trace can get pretty long. Those numbers are memory addresses but they are usually resolved into names but the debug information is missing (why you get «filename not found»). The debug information is usually missing in released games so I wouldn’t worry about «filename not found».

. nor anything else that comes after it.

In computing, a stack trace (also called stack backtrace or stack traceback) is a report of the active stack frames at a certain point in time during the execution of a program. When a program is run, memory is often dynamically allocated in two places; the stack and the heap. Memory is continuously allocated on a stack but not on a heap, thus reflective of their names. Stack also refers to a programming construct, thus to differentiate it, this stack is referred to as the program’s runtime stack. Technically, once a block of memory has been allocated on the stack, it cannot be easily removed as there can be other blocks of memory that were allocated before it. Each time a function is called in a program, a block of memory is allocated on top of the runtime stack called the activation record (or stack pointer.) At a high level, an activation record allocates memory for the function’s parameters and local variables declared in the function.

Programmers commonly use stack tracing during interactive and post-mortem debugging. End-users may see a stack trace displayed as part of an error message, which the user can then report to a programmer.

A stack trace allows tracking the sequence of nested functions called — up to the point where the stack trace is generated. In a post-mortem scenario this extends up to the function where the failure occurred (but was not necessarily caused). Sibling calls do not appear in a stack trace.

The stack trace shows where [NOT WHY!] the error occurs, namely in the Z function. It also shows that the Z function was called by Y, which was called by X, which was in turn called by the code on line # of the program. The activation records for each of these [. ] functions would be arranged in a stack such that the X function would occupy the bottom of the stack and the Z function would occupy the top of the stack.

WHY == 32-bit prerequisites missing on 64-bit OS.

This is my last answer and after that, you’ll get the exact same copy & paste answer again and again .

Источник

Message fatal error address

Hi guys, I have updated my computer. Deleted and re downloaded and created a new account. BUT I am still receiving this error message when opening the game. Does anyone have any advice?

Address = 0xb7e543 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x29108e (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x28c605 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x2349b6 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x2349ee (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0xa367ec (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x234721 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0x27b46e (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0xa6333e (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]
Address = 0xace605 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinariesWin32LifeIsStrange.exe]

Never mind — THIS FIXED IT! The only difference is go into «Life is Strange» instead of Remember Me — but again; THIS. FIXED IT.

Copy the file C:Program Files (x86)SteamSteamAppscommonRemember Me BinariesWin32PhysxCore.dll to the Physx Nvidia driver directory (ie C:Program Files (x86) NVIDIA CorporationPhysXEngineDB8A731FDBD5 ). Then, you can restart the game and it will work without problem

Never mind — THIS FIXED IT! The only difference is go into «Life is Strange» instead of Remember Me — but again; THIS. FIXED IT.

Copy the file C:Program Files (x86)SteamSteamAppscommonRemember Me BinariesWin32PhysxCore.dll to the Physx Nvidia driver directory (ie C:Program Files (x86) NVIDIA CorporationPhysXEngineDB8A731FDBD5 ). Then, you can restart the game and it will work without problem

Hello everybody
I don’t really speak English, I know it has been a while since this but I found the solution, I don’t know how good it is but I found this YouTube video and it worked for me.

It’s in Spanish but you just have to imitate what he does, I hope it helps you

Hi guys, I have updated my computer. Deleted and re downloaded and created a new account. BUT I am still receiving this error message when opening the game. Does anyone have any advice?

Address = 0xb7e543 (filename not found) [in C:Program Files (x86)SteamsteamappscommonLife Is StrangeBinaries[b]Win32[/b]LifeIsStrange.exe]
[. ]

«Fatal error!» because you are trying to play 32-bit game on 64-bit operating system.

Note that Program Files (x86) and Win32.

Install all Versions of vcredist for 32 and 64-bit.
Install all UE4/5 prerequisites for 32 and 64-bit.
Install all Unity prerequisites for 32 and 64-bit.
Install all DirectX Versions (8, 9, 10, 11, 12).

. and you’re good to go for almost every game.

«Fatal error!» because you are trying to play 32-bit game on 64-bit operating system.

That’s not really an issue. 64bit machines are backwards compatible with 32bit programs.

The issue has to do with the drivers needed to run the game. Gravedigging this is unnecessary since it’s been a topic that has come up a bunch since it is a known issue that can be resolved and you can already google for the fix: https://www.reddit.com/r/lifeisstrange/comments/34fcbi/is_anyone_else_getting_a_fatal_error_after_the/cqu3cmy/

«Fatal error!» because you are trying to play 32-bit game on 64-bit operating system.

That’s not really an issue. 64bit machines are backwards compatible with 32bit programs.

That actually is the real issue.

All that stuff after

isn’t what’s causing the crash, but it’s the stuff that is not found because of 32/64-bit “addressing” (the place where the files are stored).

Yes, 64-bit machines have the 32-bit compatibility layer, but during the installation of some games, the necessary 32-bit libraries are not always fully installed.

It results in 32-bit game trying to find the 32-bit dependencies, but it can not find them.

If you are referring to this library copy & paste process described here:

It is best to copy the file C:Program Files (x86)SteamSteamAppscommonRemember Me BinariesWin32PhysxCore.dll to the Physx Nvidia driver directory (ie C:Program Files (x86) NVIDIA CorporationPhysXEngineDB8A731FDBD5 ). Then, you can restart the game and it will work without problem

. it may, or it may not help, but it’s definitely the wrong way of doing it, because if one replaces the 64-bit library with a 32-bit, some other games might stop working — those which are looking for appropriate 64-bit version on that place.

All games made in the recent couple of years are made on 64-bit machines, but many are/were (still) compiled for 32-bit OS. During AMD or Nvidia installs on 64-bit OS, 64 and 32-bit drivers are getting installed — each on its own place.

That actually is the real issue.

but during the installation of some games, the necessary 32-bit libraries are not always fully installed.

That is not a 64bit issue with *running* the game. The installation is the issue causing missing/corrupt components to fail to run it. There are drivers described in some solutions that note that the third party drivers cause the issue because their installation (installed separately from the game) is not entirely compatible for the game, and their software may install the wrong version if you tried to redownload it (which means you may have to delete the entire content before re-installing).

It has nothing to do with the machine. It’s the components that need to be installed properly to run the game.

If the game wasn’t supporting 64bit machines, it wouldn’t be marketed for it. In fact, since the 32bit Macs are obsolete, you have only the supported 64bit install which does exist, so 64 bit machines are supported and it is compatible for them. This is not what the error is about.

. it may, or it may not help, but it’s definitely the wrong way of doing it, because if one replaces the 64-bit library with a 32-bit, some other games might stop working — those which are looking for appropriate 64-bit version on that place.

If you were running a 64bit game on a 32bit machine the way you’re trying to explain this error, they will not run at all. In fact, it wouldn’t be throwing up that error especially since this is not what the error is about.

That’s why this solution was given, and you’re giving the wrong explanation for it. I run 32 bit games/software on 64bit machines, and I don’t actually have this issue, so you are not correct in interpreting this error. Again, it only has to do with incompatible components, not the machine.

That’s why this solution was given, and you’re giving the wrong explanation for it. I run 32 bit games/software on 64bit machines, and I don’t actually have this issue, so you are not correct in interpreting this error. Again, it only has to do with incompatible components, not the machine.

Could it be that you didn’t read all what I wrote or that you somehow misunderstood it — since that’s my impression here.

Not my explanation is wrong, but the RedIt “solution” — it worked for that one case accidentally — because it happened that somebody copied something that functioned and didn’t cause the damage, but some people also run into further issue(s), like:

I can’t find this folder in the NVIDIA Corporation directory DB8A731FDBD5

Where can I pull the ‘PhysxCore.dll’ file because I don’t have Remember Me game?

. and then exactly that happens what I explained above — people copy and paste some random PhysxCore.dll.

So yeah, I’m very much correct in interpreting this error and again, all I am explaining (and you misunderstanding) the whole time “only has to do with incompatible components” — will say it has very much to do with the “type of machine” (64-bit Windows 10 executing 32-bit game) — namely, “machine” in our context means “the running operating system” and the “the running operating system” (Windows 10 64-bit) is causing the problem because of the “incompatible components” (software — 32-bit compatibility layer dependencies/libraries).

More at the very end of this post.

If you run 32-bit games/software on 64-bit machines, and you don’t actually have this issue means that you simply have all dependencies met (== correctly installed) and it proves that I’m correct in interpreting this error, as well as it makes obvious that you misunderstood my explanation.

For easier understanding, simply imagine it as 32-bit software running inside an emulator/virtual machine when running on a 64-bit Windows. See the Wikipedia links at the bottom for further explanation.

That actually is the real issue.

but during the installation of some games, the necessary 32-bit libraries are not always fully installed.

[1] That is not a 64bit issue with *running* the game. The installation is the issue causing missing/corrupt components to fail to run it. There are drivers described in some solutions that note that the third party drivers cause the issue because their installation (installed separately from the game) is not entirely compatible for the game, and their software may install the wrong version if you tried to redownload it (which means you may have to delete the entire content before re-installing).

It has nothing to do with the machine. It’s the components that need to be installed properly to run the game.

If the game wasn’t supporting 64bit machines, it wouldn’t be marketed for it. In fact, since the 32bit Macs are obsolete, you have only the supported 64bit install which does exist, so 64 bit machines are supported and it is compatible for them. This is not what the error is about.

. it may, or it may not help, but it’s definitely the wrong way of doing it, because if one replaces the 64-bit library with a 32-bit, some other games might stop working — those which are looking for appropriate 64-bit version on that place.

[2.] If you were running a 64bit game on a 32bit machine the way you’re trying to explain this error, they will not run at all. In fact, it wouldn’t be throwing up that error especially since this is not what the error is about.

That’s why this solution was given, and you’re giving the wrong explanation for it. I run 32 bit games/software on 64bit machines, and I don’t actually have this issue, so you are not correct in interpreting this error. Again, it only has to do with incompatible components, not the machine.

1. That IS the issue with 32-bit game on 64-bit machines.

The (borked) installation IS the issue, but not because it installs something “corrupt” or “not entirely compatible”, but because (in some cases!) it DOES NOT install Unreal Engine 4 Prerequisites AT ALL.

Namely, what here happens is the following: Every stand alone UE4 game comes bundled with “Unreal Engine 4 Prerequisites Setup” which should be (in case of LIS) under the path:

C:Program Files (x86)SteamsteamappscommonLife Is StrangeEngineExtrasRedisten-usUE4PrereqSetup_x86.exe

However, that “Extras” folder is missing (at least) in many (if not all) of Life Is Strange Steam installations for whatever reason. During the initial Steam game installation, those dependencies usually get triggered by the Steam game installer itself, but not in all cases, and since the prerequisites are not bundled with the game files, it can happen that the game starts, can’t find the prerequisites (because Steam game installer “forgot” to install them) and it can’t trigger the installation of the prerequisites by itself (since the “Extras” folder is missing).

The game crashes with “Fatal Error”.

For comparison purposes only:

In case of “Unreal Engine 4 Prerequisites”, there is no “not entirely compatible” version — the package comes from UE itself, and it brings all what it needs for a game to run properly.

Unreal Engine 4 Prerequisites Setup installs:

Microsoft .NET Framework 4(ver. 4.0.30319.1)
Visual C++ runtime files 2005, 2008, 2012
DirectX End-User Runtimes (June 2010)

There are two versions of “Unreal Engine 4 Prerequisites” (32 and 64-bit) and LIS depends on 32-bit version.

So, of course it has to do with the machine and of course, it’s the components that need to be installed properly to run the game — as explained above.

It has to do with the machine because the machine (== OS) is running 64-bit OS, but it can’t run the game properly because of the missing libraries (== “only components”) and those libraries are part of those vcredist packages — as already explained.

Also, that has nothing to do with “game supporting 64bit machines” or not — every 32-bit Windows game IS supported on every 64-bit Windows installation — if dependencies are satisfied. Only very old games that use 16-bit libraries are not running on 64-bit Windows — they could run on 32-bit version of Windows 10 (== machine) only.

2. This is NOT MY explanation, but quite the opposite .

Somebody in #37 * posted a link to RedIt which is offering that as a (nonsense) solution, and I was claiming that it is the wrong way to do it and that necessary and unnecessary libraries should be installed “all at once” ** on every gaming machine — to solve the existing problem and to prevent future problems — one will need (and install over time) most of those libraries anyway.

As of “I can’t find this folder in the NVIDIA Corporation directory DB8A731FDBD5”: No need to look for it neither in the recent Nvidia driver versions.

If the latest (as of today) Nvidia driver is installed, that folder doesn’t exist anymore.

The real problem however is that copying that “PhysxCore.dll” from one folder to the other manually is tricky because:

. almost each of those folders contains one “PhysxCore.dll”, but each one in another version — which might or might not be the right one for the game. Some games will run with any version, some not.

[. ] there is a version conflict between PhysxCore.dll file provided by the game “Remember Me” and the one installed by Nvidia.

Could it be that you didn’t read all what I wrote or that you somehow misunderstood it — since that’s my impression here.

No I understood it perfectly well what you were saying, but I know you are wrong because what you are saying is NOT how it actually works or what is going on. You’re trying too hard to assert yourself as correct, but you’re actually not.

While you were busy trying to mansplain to me about virtual machines, I happen to have run several over the years, so I already know what I’m talking about. You don’t. The issue is not a dependency on whether you’re running a 64bit machine. The issue is about corrupt/missing components which sometimes also means third party installs are the culprit.

This includes the possibility that you have 64bit files, which the game is trying to run. Because the game is 32bit software, it cannot run 64bit components, even if you have a 64bit machine. That is also a similar issue to mixing installs of 32bit and 64bit MS Office programs (yeah, look it up). The machine is not the problem. The problem is the files. Same kind of issue here, which not necessarily will produce a fatal error, but it is an error of that type: https://steamcommunity.com/app/319630/discussions/1/611696927920681276/

While you also just posted the SAME Reddit post I already did, that post is not only a solution, but it is one of the solutions to this problem. You simply need to replace certain files like that one, even if it means a fresh install. Merely using third party software, even Steam itself, will likely be replacing the same type of file available based on what is installed, not the type you need. Since the game is 32bit, you’re safe with a clean install of the 32bit version of the files, not the 64bit ones.

So, no, the problem is not because you are running a 64bit machine. It’s more that you’re running 32bit software that is trying to run 64bit components or corrupt files. That is it. It has NOTHING to do with the machine.

Could it be that you didn’t read all what I wrote or that you somehow misunderstood it — since that’s my impression here.

No I understood it perfectly well what you were saying, but I know you are wrong because what you are saying is NOT how it actually works or what is going on. You’re trying too hard to assert yourself as correct, but you’re actually not.

So, no, the problem is not because you are running a 64bit machine. It’s more that you’re running 32bit software that is trying to run 64bit components or corrupt files. That is it. It has NOTHING to do with the machine.

That has EVERYTHING to do with the machine.

The issue here is in your contextual thinking.

We are essentially talking about the same thing — we talk about missing 32-bit components (“dependencies”) on an 64-bit machine (== OS).

What you are saying is that 64-bit machine is not a problem, because one can easily install the missing 32-bit components that’ll make the game(s) run; I am saying that 64-bit machine is a problem, because 32-bit components must be additionally installed.

“The machine” is a “PC”, which is a combination of HW and SW. SW consists of OS and all other user SW. OS is running a 64-bit OS with a compatibility layer for 32-bit SW. That 32-bit SW needs additional SW components that need to be installed first, to make 32-bit SW runs on a 64-bit machines, but these components are missing per default and sometimes not installed during automatic installation.

If some 32-bit SW components are per default missing on a 64-bit machine, but they could be installed to get the machine run 32-bit SW properly, than it means that the issue happens because the machine is 64-bit. With other words, the problem in this case is that one is running a 64-bit machine. That’s simple logic.

While you were busy trying to mansplain to me about virtual machines, I happen to have run several over the years, so I already know what I’m talking about. You don’t. The issue is not a dependency on whether you’re running a 64bit machine. The issue is about corrupt/missing components * which sometimes also means third party installs are the culprit.

This includes the possibility that you have 64bit files, which the game is trying to run. Because the game is 32bit software, it cannot run 64bit components, even if you have a 64bit machine. That is also a similar issue to mixing installs of 32bit and 64bit MS Office programs (yeah, look it up). The machine is not the problem. The problem is the files. Same kind of issue here, which not necessarily will produce a fatal error, but it is an error of that type: https://steamcommunity.com/app/319630/discussions/1/611696927920681276/

While you also just posted the SAME Reddit post I already did, that post is not only a solution, but it is one of the solutions to this problem. You simply need to replace certain files like that one, even if it means a fresh install. Merely using third party software, even Steam itself, will likely be replacing the same type of file available based on what is installed, not the type you need. Since the game is 32bit, you’re safe with a clean install of the 32bit version of the files, not the 64bit ones.

“The issue is about corrupt/missing components” is exactly what I said in #36.

“The issue is not a dependency on whether you’re running a 64bit machine” is again “the same but different view” as already explained — when 32-bit components are missing (but could be installed) on a 64-bit machine, then the 64-bit machine is (one of) the problem (

“Because the game is 32-bit software, it cannot run 64-bit components, even if exactly because you have a 64bit machine.” (so the 64-bit machine is a problem in that case)

You are right on, “the problem IS the missing 32-bit files”, but that’s exactly what I already wrote in my #36 (link) .

The main issue with 32-bit SW is the memory limit to max. 4 GB. In normal case, that’s not an issue, but sometimes people have some monstrous Excel file, photos or videos which need more . much, much more.

The secondary issue is the plugin compatibility — old 32-bit plugins will not run in 64-bit software. Again not an issue in most cases — one can simply buy a new plugin, but in some cases (municipal authorities for example), there are still hundreds or thousands of 32-bit plugins in use (for task automatization) which would stop running on 64-bit Office. Most part of it is custom-made and not easily replaceable.

“While you also just posted the SAME Reddit post I already did, that post is not only a solution, but it is one of the solutions to this problem.”

I posted the same Reddit post — as a bad example — what NOT to do!

It is best to copy the file C:Program Files (x86)SteamSteamAppscommonRemember Me BinariesWin32PhysxCore.dll to the Physx Nvidia driver directory (ie C:Program Files (x86) NVIDIA CorporationPhysXEngineDB8A731FDBD5 ). Then, you can restart the game and it will work without problem

. it may, or it may not help, but it’s definitely the wrong way of doing it [. ]

Источник