Random crashes to desktop - no message

[Sir Danglefrögge]

Pretty much like the title says. Between 30 seconds and 30+ minutes, the game will suddenly crash to my desktop with no error message.

Base Specs:
- Windows 10 (latest build, updates)
- AMD Ryzen 9 5900X
- AMD Radeon RX 6900XT (Sapphire Nitro+ SE)
- ASUS TUF B550M Plus Wifi
- 32 GB 3600 CL16 RAM
- Seasonic Focus 1000W 80+ Gold PSU

Game settings:
- Everything on Ultra
- LOW TAA
- Motion blur, film grain, chromatic ab. all OFF
- No RT, no FSR
- 2560 x 1440p native resolution at 144 HZ
- Vsync ON

I have the latest drivers for my GPU and chipset installed. Motherboard is currently using the latest BIOS revision.

What I've done so far:
- Validated the game files.

- Reduced/removed my overclocks and undervolts.

- Removed the PBO settings for my CPU.

- Applied PCGamingWiki's suggested "r.Streaming.PoolSize=" line, under [SystemSettings], in the engine.ini file. Tried with 6144 and 8192 values (considering my GPU has 16 GB of VRAM). Apparently it's helped some people with similar crashes.

----------------------

Temps are fine, never had an issue with those anyway.

What perplexes me is that the game doesn't hit the RAM or VRAM limits of my components and it still crashes (according to Radeon Software at least). Last time it crashed, it was using about 8-9 GB of my RAM, and 12 GB of my VRAM.

Anybody have any suggestions? I'm loving the game and this is the only gripe I have it with it so far.

[WokoT]

I'm having the same problem so your not alone, i have the same cpu and 6800xt. i have tried rolling back one to Novembers adrenaline update but still the same thing.
Good to know that turning of fsr doesn't work, was going to try that next.
Maybe try all low setting see if it plays longer? Haven't had chance to try that yet.

[Sir Danglefrögge]

Originally posted by WokoT:

I'm having the same problem so your not alone, i have the same cpu and 6800xt. i have tried rolling back one to Novembers adrenaline update but still the same thing.
Good to know that turning of fsr doesn't work, was going to try that next.
Maybe try all low setting see if it plays longer? Haven't had chance to try that yet.

I'll try that later and give an update. I'll also turn off Resizeable BAR in the BIOS (effectively turning off AMD SAM) to see if that does anything.

[Luke]

same problem since day 1

[WokoT]

I installed a new mobo recently and forgot about resizeable bar so it was already disabled.
Save you trying that

[Sir Danglefrögge]

Originally posted by Parry Hotter:

same problem since day 1

Funnily enough, I played it for 2 hours straight during the early access without a single crash. The crashes started happening after the Day 1 Patch (at least, that's what I'm assuming the ~240 MB download was on Feb 10).

Though it could be a random coincidence.

[Sir Danglefrögge]

Originally posted by WokoT:

I installed a new mobo recently and forgot about resizeable bar so it was already disabled.
Save you trying that

Damn. I'll stick to trying lower settings later, then. Thanks.

[Passie1288]

Did you disable your pagefile by any chance? A lot of people only look at the memory that is activily being used, but that's actually not the amount of memory that you need to have available. The total amount of required memory is way higher than that, especially if you use a lot of VRAM.

In the windows task manager you see two different memory amounts. Under "in use" you see how much memory is activily being used by the system. Under "commited" you will see the so called commit charge. This is the total amount of memory that is actually being allocated. VRAM has a huge impact on the commit charge.

I'm playing this game with a 4090 and 32GB of RAM. While the active memory usage usually doesn't get higher than 16GB, the commit charge can reach a whopping 37GB at times. Without a pagefile, the game would crash the moment the commit charge gets over 32GB. Once there is no memory left, the Kernel will block of all memory requests.

[snoopy]

Try out if it is when you see a spider. Every time i see one, then crash to steam homescreen. i cant play anymore because have a quest with many spiders

[Sir Danglefrögge]

Originally posted by Passie1288:

Did you disable your pagefile by any chance? A lot of people only look at the memory that is activily being used, but that's actually not the amount of memory that you need to have available. The total amount of required memory is way higher than that, especially if you use a lot of VRAM.

In the windows task manager you see two different memory amounts. Under "in use" you see how much memory is activily being used by the system. Under "commited" you will see the so called commit charge. This is the total amount of memory that is actually being allocated. VRAM has a huge impact on the commit charge.

I'm playing this game with a 4090 and 32GB of RAM. While the active memory usage usually doesn't get higher than 16GB, the commit charge can reach a whopping 37GB at times. Without a pagefile, the game would crash the moment the commit charge gets over 32GB. Once there is no memory left, the Kernel will block of all memory requests.

Pagefile is actually enabled. Never touched it on my current build, and I checked to make sure it was indeed enabled.

What I'll do later is keep an eye on the "committed" amount of RAM in Task Manager while I play the game. Then I'll lower the settings to see if anything changes. I'll post an update on whether or not anything has changed after this.

[Sir Danglefrögge]

Originally posted by snoopy:

Try out if it is when you see a spider. Every time i see one, then crash to steam homescreen. i cant play anymore because have a quest with many spiders

I don't recall seeing spiders right before my crashes. It legitimately seems random.

[Passie1288]

Originally posted by Sir Dangle:

Pagefile is actually enabled. Never touched it on my current build, and I checked to make sure it was indeed enabled.

What I'll do later is keep an eye on the "committed" amount of RAM in Task Manager while I play the game. Then I'll lower the settings to see if anything changes. I'll post an update on whether or not anything has changed after this.

Have you checked the windows logbooks to see if there is an error message?

[WokoT]

Originally posted by Passie1288:

Originally posted by Sir Dangle:

Pagefile is actually enabled. Never touched it on my current build, and I checked to make sure it was indeed enabled.

What I'll do later is keep an eye on the "committed" amount of RAM in Task Manager while I play the game. Then I'll lower the settings to see if anything changes. I'll post an update on whether or not anything has changed after this.

Have you checked the windows logbooks to see if there is an error message?

Ive checked the eventlog, nothing in application log or system.

[Sir Danglefrögge]

Originally posted by WokoT:

Originally posted by Passie1288:

Have you checked the windows logbooks to see if there is an error message?

Ive checked the eventlog, nothing in application log or system.

Same story here. Nothing stands out in Event Viewer. I remember the approximate times of the last 2 crashes and when trying to look them up, I don't see anything related to Hogwarts Legacy.

[Bassilth]

It might not tell you why it is crashing on the screen but it will log the crash for sure.

Path:
"C:\Users\USERNAME\AppData\Local\Hogwarts Legacy\Saved\Crashes"
The CrashUserData.json file will tell you exactly why the crash happened according to the game.

[Sir Danglefrögge]

Originally posted by Bassilth:

It might not tell you why it is crashing on the screen but it will log the crash for sure.

Path:
"C:\Users\USERNAME\AppData\Local\Hogwarts Legacy\Saved\Crashes"
The CrashUserData.json file will tell you exactly why the crash happened according to the game.

Hmmmm seems all my crashes have the "Unhandled exception" message (it stops there, no strings). Not exactly much to go on. It can refer to quite a few things in UE4.