Is this from bad overclock or hdd

Rowan88 · 15 Jul 2017 at 07:53

Hi,

I was testing my CPU/GPU overclocks. Passes 1 hour of RealBench and passes Valley/Superposition/3DMark.

But during Batman Arkham Knight this has happened twice at random moments:

Does anyone know if these are errors related to the overclocking or if this is to do with my hard drive? I only ask because I had a problem the other day where I had to end up re-installing windows that was only 3 days old because of corrupted files.

Thanks

Danny75 · 15 Jul 2017 at 08:17

I think MSVCR100.dll points to some missing or corrupted Microsoft Visual C++.

When you first install the game, it also installs the appropriate Visual C++ stuff (or it should).

Since you did a fresh Windows install on your C: drive, that stuff is now gone, even though the game itself remained on your Z: drive.

Solution might be to completely remove Arkham Knight, and try installing it again. Unless you know the exact Visual C++ versions you need and can find and download them. If the latter doesn't succeed, they probably weren't the exact set and you'll have to try re-installing the game, methinks.

Rowan88 · 15 Jul 2017 at 08:22

I installed all the DirectX/Visual C++ stuff that usually installs at the time of the game, but what I did notice was someone on the steam forums relating to a file called "PhysXDevice64.dll". Apparently if I renamed it to "PhysXDevice64.dll_old" that would sort the problem so I am testing this as we speak.

But I will make sure all my Visual C++ etc are all up to date with newest versions.

benjii · 15 Jul 2017 at 10:24

Do a repair of all your C++ stuff, you should find the installers in the game folder. If not, easily find them on the Microsoft site. As an aside, an hour isn't nearly long enough to determine stability, I suggest leaving it over night.

Pocah · 19 Jul 2017 at 07:23

TBH this sort of thing is the very reason I won't overclock! The problem is that while you can be 99.99% sure a system is stable you can never be 100% sure, especially when something like this happens. The answer would be to turn overclocking off and run the system for a few weeks. If there isn't a problem, then try overclocking again. If the problem happens again, then it's the overclocking. I know, I know, it's a pain because there isn't an instant answer, but when computers go wrong it's often very difficult to tie down just exactly what's is failing. Most of the time you can make an educated guess, and prove it one way or the other pretty quickly, but, sometimes, I am afraid, you just have to throw time and money at the situation. It's horrible, but it's the only way.

Rowan88 · 19 Jul 2017 at 08:34

Pocah said:
TBH this sort of thing is the very reason I won't overclock! The problem is that while you can be 99.99% sure a system is stable you can never be 100% sure, especially when something like this happens. The answer would be to turn overclocking off and run the system for a few weeks. If there isn't a problem, then try overclocking again. If the problem happens again, then it's the overclocking. I know, I know, it's a pain because there isn't an instant answer, but when computers go wrong it's often very difficult to tie down just exactly what's is failing. Most of the time you can make an educated guess, and prove it one way or the other pretty quickly, but, sometimes, I am afraid, you just have to throw time and money at the situation. It's horrible, but it's the only way.

This had nothing to do with overclocking!
If you read my above post I told you after a bit of research it was a known issue that was easily fixed by editing a filename

Pocah · 19 Jul 2017 at 09:01

Se

Rowan88 said:
This had nothing to do with overclocking!
If you read my above post I told you after a bit of research it was a known issue that was easily fixed by editing a filename

Serves me right for not reading all the posts then, but the point still stands.

Rowan88 · 19 Jul 2017 at 13:48

Lol,

Agree about overclocks not going to be 100% stable, but if you are getting extra speed and its not crashing a lot then seem's worth it to me.

But each to their own

VKleita · 19 Jul 2017 at 16:09

Pocah said:
TBH this sort of thing is the very reason I won't overclock! The problem is that while you can be 99.99%

You can never be sure a system is 100% stable even at stock due to driver issues, firmware revisions, conflicts etc.

All we can do is try to test as much as possible to run out issues.