Crash On Launch Post-Update SOLVED

[SmallArchangel]

I am aware there have been quite a few threads on this already, I have read them and tried all the suggested solutions to no effect. When I try to launch via Steam, or RedLauncher, or the .exe file the result is the same - the almost immediate appearance of the Witcher 3 crash reporter asking me to send a report. I'm not sure how to view the error-log - anyone advise?

Otherwise I have done everything everyone suggests: deleted mods and updated graphics driver before I even tried launching, removed game saves (difficult when Steam automatically restores them), switched between DX11 and 12, deleted settings files, reinstalled, verified game files. Open to any further suggestions?

[Just Guy 0_0]

Run the steam as administrator and disable steam overlay , also run it with geforce experience , also what is your GPU , CPU , etc?? windows 11 or 10??

[SmallArchangel]

Running Steam as admin wouldn't make any difference considering the game doesn't launch straight from the .exe, which obviously bypasses Steam altogether. Steam overlay already disabled. Are my specs likely to be to blame here? I'm not convinced this is to do with my hardware.

Currently reverting to classic, see if that works. It used to with no issues...

[Orion Invictus]

Originally posted by SmallArchangel:

Are my specs likely to be to blame here? I'm not convinced this is to do with my hardware.

Likely? Not really. But without knowing, we can't be sure. I will say, though, that in my experience, when someone is sure their hardware isn't the problem, it is (most of the time, anyway).

[SmallArchangel]

I don't think it's my hardware, because that would not stop the game from even launching, it would most likely cause problems and ctd's during gameplay. Plus, people with issues launching the new update have very varied specs (as do those who can play with no problems, in fact).

I can also run much newer and more resource-intensive games with no difficulty and high settings (though I am aware that is not always a reliable indicator).

Anyway, as mentioned previously, rolling back to old version so we'll see if that still works. I have read some folks saying classic doesn't run, either...

[Orion Invictus]

Originally posted by SmallArchangel:

I don't think it's my hardware, because that would not stop the game from even launching, it would most likely cause problems and ctd's during gameplay.

It depends. Some CPUs don't have the AVX instruction set, which would prevent games that require it from running (I don't know if that's the case with Witcher 3, just saying that it's not that simple).

Also, the fact you won't even post your specs is typical of people who know their specs are sub-standard but still fully expect every game to run. Posting them just takes a minute, if that, and would let us be sure your hardware is able to run the 4.0 update

Originally posted by SmallArchangel:

Plus, people with issues launching the new update have very varied specs (as do those who can play with no problems, in fact).

That doesn't mean your specific problem can't be caused by your hardware.

Originally posted by SmallArchangel:

I can also run much newer and more resource-intensive games with no difficulty and high settings (though I am aware that is not always a reliable indicator).

The next-gen update is about a month old. Which games would those be, exactly?

[Just Guy 0_0]

Originally posted by SmallArchangel:

I don't think it's my hardware, because that would not stop the game from even launching, it would most likely cause problems and ctd's during gameplay. Plus, people with issues launching the new update have very varied specs (as do those who can play with no problems, in fact).

I can also run much newer and more resource-intensive games with no difficulty and high settings (though I am aware that is not always a reliable indicator).

Anyway, as mentioned previously, rolling back to old version so we'll see if that still works. I have read some folks saying classic doesn't run, either...

What is your GPU and CPU? and what Ram do you have? and what resolution are you trying to play the game?



I have RTX 3080 and the game works on both versions ,


Those are the system requirements to run the game in DX11:

OS: 64-bit Windows 7 or 64-bit Windows 8 (8.1). DirectX 11 is necessary to run the game.
Processor: Intel CPU Core i7 3770 3,4 GHz, AMD CPU AMD FX-8350 4 GHz
Graphics: Nvidia GPU GeForce GTX 770 or AMD GPU Radeon R9 290
RAM: 6GB
Disk space: 40 GB

so basically almost everyone should be able to run the game.

so most likely the issue is something else than hardware.

[SmallArchangel]

I didn't post my specs because I hadn't found them yet (yes, my pc is so old I can't remember last time I upgraded it!) However, it always seems to perform really well on every new game in spite of being 10+ years old... This update may be the exception, weird considering it is essentially not a new game, but hey.

CPU i7 2600l @ 3.40hz
GTX 1070
24GB RAM

I didn't mean games newer than this, I meant 'newer' as in the last year or so. Re-reading that, it wasn't exactly clear, sorry. Besides, I didn't just buy this one, it got auto-updated so when I tried to play it again after a long hiatus, this happened. I wasn't sure exactly how long ago the update landed till now, haven't played for a couple of years.

[SmallArchangel]

Originally posted by HIZ:

Those are the system requirements to run the game in DX11:

OS: 64-bit Windows 7 or 64-bit Windows 8 (8.1). DirectX 11 is necessary to run the game.
Processor: Intel CPU Core i7 3770 3,4 GHz, AMD CPU AMD FX-8350 4 GHz
Graphics: Nvidia GPU GeForce GTX 770 or AMD GPU Radeon R9 290
RAM: 6GB
Disk space: 40 GB

so basically almost everyone should be able to run the game.

so most likely the issue is something else than hardware.

Could be my hardware looking at that, it is pretty low-spec now - who knows. Not easy to find out really. A lot of people reporting low frames, stuttering, glitches and crashes, but I can't even start it, which could be something else.

Originally posted by HIZ:

What is your GPU and CPU? and what Ram do you have? and what resolution are you trying to play the game?

Posted above. Given I haven't been able to launch, I haven't the option to change resolution, but I guess it would default to native, if it even ran that is (1920 x 1080 I think). I don't even recall what the settings were originally - high, I think - though I removed the settings files in case that was an issue.

[SmallArchangel]

Well, Classic version works, but Geralt is completely invisible - so I'm guessing my problem is at least partly to do with mods. Might have to completely delete game file and re-acquire, since I can't find the hidden modded files buried in there...

[Hobgoblin]

Do you have old mods installed from the prior version of the game? That would do it. For those to work, as far as I know? You have to right-click on Witcher in your libarary, go to the Updates tab and select the "aliow Beta updates" options and revert the game back to the original release version.

Otherwise, verify integrity of the files through Steam, or like someone was trying to say; locate the Witcher3.exe (not the RedLauncher.exe), in the binaries folder and right-click and select Properties and click on the Compatibility tab and trying setting it to run as Admin. Also try running it directly from the executable in your game directory to see if that is somehow different. I've had a similar issue with Cyberpunk where the game wouldn't launch with their RedLauncher.exe, so I had to launch it all the time with the Cyberpunk2077.exe, later it was determined to also be an admin issue and once I granted Cyberpunk2077.exe admin rights it fixed the issue. It probably also wouldn't hurt to grant the RedLauncher.exe admin, however. Just in case I've got my story swapped. It's been awhile.

[SmallArchangel]

I had one mod only, but quite script-heavy. I have already reverted to the original version, as I said above, and decided to play without mods and try a fresh run. I've manually deleted the contents of the game folder and verifying all missing files now, which should hopefully eliminate the mod and make Geralt visible again.

I already tried running the game directly from the .exe, as I said in the original post, but it doesn't matter so long as I can get the classic game to run, I'm not bothered about the new version.

[mommajean]

Looks like you haven't performed the files verify. I ran this and during update, it didn't download a file. When I ran this 'file verify', it fixed the problem. I hope, try it.

[Just Guy 0_0]

Where did you get this mod from?

If you got it from nexus , you can go into download history which shows all mods you installed , find the mod , open the download section , file preview, open the folder, copy the name and paste search in steam/steam apps / common / witcher 3


And then simply delete it

[DjOz]

Operating System
Windows 10 Pro 64-bit
CPU
Intel Xeon X5690 @ 3.47GHz 99 °F
Westmere-EP 32nm Technology
RAM
24.0GB Triple-Channel DDR3 @ 668MHz (9-9-9-23)
Motherboard
Alienware 0XDJ4C (CPU 1) 74 °F
Graphics
NV Surround (3840x1080@60Hz)
4095MB NVIDIA GeForce RTX 3080 Ti (EVGA) 105 °F
Storage
1907GB Kingchuxing 2TB (SATA (SSD)) 105 °F
1907GB Kingchuxing 2TB (SATA (SSD)) 105 °F
7452GB Seagate FireCuda Hub SCSI Disk Device (USB (SATA) ) 123 °F
1863GB Kingchuxing 2TB (SATA (SSD)) 105 °F
1863GB Kingchuxing 2TB (SATA (SSD)) 105 °F
1907GB Kingchuxing 2TB (SATA (SSD)) 105 °F
1907GB Kingchuxing 2TB (SATA (SSD)) 105 °F
Optical Drives
PLDS BD-RE DH-8B2SH SCSI CdRom Device
HL-DT-ST BD-RE WH16NS40 SCSI CdRom Device
Audio
Sound BlasterX AE-5 Plus
Power Supply EVGA 1600 Gold
works playing with Ultra+ settings on Directx 11
But wont even start on Directx 12 lowest settings

[SmallArchangel]

Originally posted by mommajean:

Looks like you haven't performed the files verify. I ran this and during update, it didn't download a file. When I ran this 'file verify', it fixed the problem. I hope, try it.

Looks like you didn't read the original post...? I verified files about 6 times by now. It's usually the first 'fix' I try, didn't work for me this time.