The problem with getting the blue screen every ten to minutes is getting bothersome. I’m almost ready to hang it up. In order to test something, I recently reformatted my SSD and started fresh. Just windows, drivers, and the game. The problem still persists.
I am wondering, do console players have a similar issue, or is it just PC players? Anyway, here’s my specs.
I run FFXIV, WoW, D2, D3, SWTOR, and many other games with zero issue. D4 -used- to run fine also. But ever since the expansion, it’s been majorly busted. I refuse to believe it’s my system. It’s too new and exhibits no issues with other games. Please, at this point, I don’t care about balance or grinds or whatever because if I can’t play, they don’t matter. Please, fix this one thing!
Look in the Windows\Minidump(s) folder for the crash file, should be named by date.
Copy that to your desktop then open in Windows Debugger, I have this by default but you may need to get it from the MS store, it is free.
Inside the debugger there will be an option to analyze! run that and see what is causing the reboot.
Make no mistake d4 is triggering it, but it will actually tell you a bit more.
You should look here after every BSOD to see what it says happened.
Essentially there is a memory leak so you want to change your game settings to lower the memory footprint as low as possible without losing the reasons to play.
Turn RT and resolution scaling off, unless you absolutely need DLSS to get playable frames. These seeem to be problematic and may be causing more issue than good currently.
Start there and see if it goes longer.
Alternatively you can look in the game folder if you see the Fenris error popup. There are text files there for FenrisErrors.
It may not tell you much, but it should show you the state when the error occurred. Sometimes it can tell you what call cuased the unhandled exception. It could be useful for them to fix, though I would think they grab this automatically when the Fenris Error box pops up.
The folder it is in is protected generally that is why you need to copy it somewhere else like desktop.
Then delete it from desktop, not the original, once you are done.
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
I play on both Xbox and PC and I’ve literally never had a crash on either outside of PTR client. To be fair I do play on Xbox more often which gives less chance for my PC to experience anything negative. But I play on it often enough that I should have seen a crash by now.
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common BugCheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8074c498553, The address that the exception occurred at
Arg3: ffff93030a75a6c8, Exception Record Address
Arg4: ffff93030a759ee0, Context Record Address
It basically will tell you what caused the error, what we are doing is making sure it is not Hardware failure related.
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff8017504539d, memory referenced.
Arg2: 0000000000000010, X64: bit 0 set if the fault was due to a not-present PTE.
bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the processor decided the fault was due to a corrupted PTE.
bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8017504539d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Now just google what is in the value next to IMAGE_NAME: with the word BSOD if you want and it should hopefully help you better understand what is going on with the BSODs
For example, from my example goolge returns
So yeah I had not updated my graphics drivers when that happened.
What you are doing is narrowing down what is causing the BSOD to get it to stop. MS actually gives you a lot of tools, it is just information overflow for people at times.
Like I said make no mistake you cannot fix what is wrong with the game, but you can make sure you take steps to make sure it is not something else on your end.
This is just the process I follow when I get BSODs as they can be troubling if it is Hardware that needs to be replaced.
That’s a memory issue right there. Which could either be faulty RAM, faulty ram on the GPU, driver issue, D4 trying to access inaccessible/non-existent RAM, etc. I’m more inclined to believe it’s D4 being dumb.
D4 is basically telling you there should be something here to write on, but where I would write this data there’s nothing there, so instead of correcting myself, I’m going to shutdown. Think of trying to fill a bucket with water, but there’s no bucket.
Only thing you can do on your part is to try and update your drivers. Possibly lower some settings in game. Make sure anything taxing on your GPU is turned off if at all possible.
Also send in your crash data to Blizzard support. Make a ticket. More reports helps them possibly find a solution on their end.
Pagefile/Memory issue. It all circles back to the game having a memory leak.
Things you can do.
Set a static/larger pagefile manually. This will extend the amount of time before crashing can occur.
Lower framerate cap. May keep the memory leak in check.
Increase in game graphic settings. Wait what? Why would you do that? Ideally to force the game to utilize more GPU and VRAM instead of CPU/System Ram.
Remember to update your BIOS. Sometimes there are changes related to CPU Microcode and/or Voltage values to increase stability. On the off chance this is related, anything that causes instability in the CPU also affects the RAM.
It kinda reads to me like they allocated something to a memory address and then tried to access it later after freeing it up which doesn’t mean the memory is bad but the code accessing it is.
I think this is probably accurate. And I’ll bet all these mini updates are them chipping away at each individual instance they find where the game application is trying to do this.
FWIW this reminds me of a CPU upgrade 15 years ago. System was rock stable and the only component I upgraded was the CPU.
The new CPU was also rock stable except it couldn’t run WoW, and WoW only, for more than a few minutes before it would crash.
