awaiting replication 2019 crash carried on into 2020

[steviejay69 1,100]

1 minute ago, Lurtz said:

OK @steviejay69.......I really do appreciate all this help......but you have now started to speak in techno speak which has gone straight over my head   😊

Is the Dymo an issue? I can disconnect it and just plug it in when I need it.

I don't understand what you mean by 'misdirected'? Can I / should I change anything or will the steps re driver fix it?

I'll follow your suggestions re the driver and get back to you.........after I have had dinner (my wife is threatening physical violence if I let it go cold!!!) 

Again - thanks for your help.

I would unplug it just in case it's causing something unusual. Not many gamers have them attached, it appears in the FFB devices....that concerns me.

Misdetected, the crash dump shows no GPU info, so a DDU will 'fix' the driver being not installed correctly or any remnants / settings left by old installers.

SWMBO - yeah don't risk it 😉

 

[Lurtz 86]

Sorry @steviejay69, unplugged the Dymo, ran DDU and downloaded 446.14 but I still get the same result - EGO Dumper page.

[steviejay69 1,100]

F14b BIOS, chipset driver, ME driver. But have to say, things look up to date (apart from UEFI BIOS).

Uninstall any of the Gigabyte utilities you may have installed (RGB Fusion, App Center, Easy Tune, etc.)

Only non-standard thing in there is the ASUS WiFi card that is using a WU / Inbox driver, try the OEM driver (older, 2015). 

Seeing as the monitor is 16:10 (1920x1200) and 60Hz, can you try capping the framerate with the in-game limiter and running Windowed (Fullscreen) instead of Fullscreen?

Edited August 26 by steviejay69
Hail Mary

[Lurtz 86]

What puzzles me is that before, apart from having to click on the quick launch button after the EGO page appeared, 2020 was working fine. It was only after validating the files on Steam that it died.

[steviejay69 1,100]

2 hours ago, Lurtz said:

What puzzles me is that before, apart from having to click on the quick launch button after the EGO page appeared, 2020 was working fine. It was only after validating the files on Steam that it died.

Steam is installed to C:, right? I just noticed your E: is removable. The D drive is spinning rust? (Yes, I checked)

Seatools for Windows.

There doesn't appear to be a tool for SK Hynix SSDs unless they're Enterprise.

Memtest (needs a USB to create bootable stick, test memory sticks singly)

 

[Lurtz 86]

Yes, Steam is installed to C:, but there is also a smaller (40Gb) Steam folder on D:. In the D main folder there is steam.dll and a steamapps folder. I've loaded a screenshot of its contents.

You will see that the 'Common' folder has a 'Date modified' of 13/07/2020. This is the date I installed 2020! Could this be the cause of the problem...that the game is spread over two different drives?

[1512marcel 456]

That could be the cause, but that's just my way of logical thinking. You don't want to seperate game data over different drives.

[LuringPoppy 3]

Its not a hardware issue, I have the exact same problem. Before 1.08 I would still get EGO dumper, but the game would launch, now its just dead completely.

678677-20200824-122835-0.zip

DxDiag.txt

Edited August 26 by LuringPoppy
typo

[Lurtz 86]

You may have a point here @LuringPoppy. When I went to validate my files, I had to wait as 1.08 was installing. After the installation finished, I did the validation and it was after this that the game died after the Dumper screen. I just assumed it was because of the validation but maybe not. Maybe it is 1.08? Any ideas @steviejay69?

[steviejay69 1,100]

4 hours ago, LuringPoppy said:

Its not a hardware issue, I have the exact same problem. Before 1.08 I would still get EGO dumper, but the game would launch, now its just dead completely.

678677-20200824-122835-0.zip

DxDiag.txt

In these dump files there is no resolution detected in the hardware_settings_config.xml

The WER shows a crash in the 446.14 installer.

Also Corsair software - been known to cause issues previously. Would test without.

4 hours ago, Lurtz said:

You may have a point here @LuringPoppy. When I went to validate my files, I had to wait as 1.08 was installing. After the installation finished, I did the validation and it was after this that the game died after the Dumper screen. I just assumed it was because of the validation but maybe not. Maybe it is 1.08? Any ideas @steviejay69?

Well, yes I would have waited to install 1.08 before validating. This would be a Steam function I think (verification). Files will be checked against a manifest with possibly a file hash check for integrity (guesswork).

Nothing to lose now the update has completed by verifying again. Not sure it will solve the issue. Only removal and reinstallation is the next step after verification. Then Steam and or Windows itself. When you reinstall it should load and run dependencies. I always reboot after a reinstall (maybe check video or controller settings then save and exit), just to make sure everything is correctly loaded. Then launch.

Edited August 26 by steviejay69

[Lurtz 86]

Ok. I thought I would try something different. I noticed that in Steam - F1 2020 - Properties - Local Files there was the option to 'Move Install Folder'.

As I showed above, I had 2019 installed on my C drive whilst 2020 was installed on my D and as @1512marcel commented, this doesn't make sense logically so I decided to move 2020 into the C drive Steam folder. Unfortunately my SSD C drive wasn't big enough so, in stead, I moved the Steam folder from C to D. So far, so good. Now I had all my Steam folders in the same place.

Next thing was to try 2019, as this was the version I had moved. The game loaded without any issues. OK - now try 2020. No joy - Dumper screen.

My question now, then, is that if both versions of the game are loading from the same folder on my D drive then the fact that one loads and the other crashes surely points to a software (Steam or Patch 1.08 ) issue with 2020?

[LuringPoppy 3]

8 hours ago, steviejay69 said:

In these dump files there is no resolution detected in the hardware_settings_config.xml

The WER shows a crash in the 446.14 installer.

Also Corsair software - been known to cause issues previously. Would test without.

Well, yes I would have waited to install 1.08 before validating. This would be a Steam function I think (verification). Files will be checked against a manifest with possibly a file hash check for integrity (guesswork).

Nothing to lose now the update has completed by verifying again. Not sure it will solve the issue. Only removal and reinstallation is the next step after verification. Then Steam and or Windows itself. When you reinstall it should load and run dependencies. I always reboot after a reinstall (maybe check video or controller settings then save and exit), just to make sure everything is correctly loaded. Then launch.

Tested without, I just looked at my hardware_settings_config.xml and there is a resolution there. The fact remains, it was working before 1.08 and now it isnt

[steviejay69 1,100]

4 hours ago, LuringPoppy said:

Tested without, I just looked at my hardware_settings_config.xml and there is a resolution there. The fact remains, it was working before 1.08 and now it isnt

OK then I have no further suggestions for you. 

[LuringPoppy 3]

On 8/27/2020 at 10:48 AM, steviejay69 said:

OK then I have no further suggestions for you. 

I did a complete clean install and the game is now working. Probably some bad files on my windows install 

Edited August 30 by LuringPoppy

[Mishal21 0]

On 8/2/2020 at 4:46 PM, Lurtz said:

steviejay69 I am guessing the label printer being designated as a DirectInput device is not normal? It is just a pnp Dymo but it is plugged into a port on a monitor stand that I use. Must be because of that.

I'll look at disabling some of the audio devices but the Arctis is only 6 weeks old so the firmware will be current.

I don't have MBAM.

Thanks for your help with this.

 

If you use steam, than you should use steam to wrap the controller. Don't you use everything at the same time. You should find clean programs. It only gets worth, when you install and deinstall programs after another.