Diablo 4 Beta - Temporary Fix for Fenris Error game crashing while in the main campaign instance
ฝัง
- เผยแพร่เมื่อ 18 มี.ค. 2023
- Edit with temporary "solution" : the issue is related to wide screen- This time I've unplugged every screen apart from the standard 60hz 21 inch 1080p 16:9 screen and I could do a couple of dungeons with no fenris crash. Next I only plugged in the wide screen with bigger aspect ration and 144hz refresh rate and the game crashed within minutes on the first dungeon, lastly I've changed the hertz ratio on my wide screen to 60hz to match the rest of the screens and it seems to work too.
The problem history and troubleshooting:
The issue starts occurring randomly in the instanced dungeon for the main quest (it often happens in regular dungeons however the first time it's being loaded I have a few minutes before it starts crashing therefore rushing is the only option).
The last campaign quest took me 10 crashes to try. Whenever the game crashes the first time the subsequent attempts aren't possible because the crash is almost immediate.
To go further I had to do something else in the world in the video i've choosen a dungeon. Next I went back to the main story quest and finished it by rushing as quickly as I could just as I've completed the entire storyline to be fair.
My first character crashed on the first mission and there was no option to expore therefore I made the second char and rushed out of there asap.
Not sure why this happens as I'm the only one from my group that struggles with this issue. Tried comparing the machines and the only difference is that I have sound interface, multiple screen setup of which one of them is super wide (wider than the game supports and I get the black bars at the side) as per the software comparison it's really hard to tell what are the differences - there could be loads. However in my opinion it boils down to hardware that causes the issue.
The fenir crash report shows that one of the threads is crashing out and the access is denied.
Seeing that I've tried adding the game to firewall rules, disabled fire wall, antivirus etc.
There's multitude of shader / rendering issues just before the crash it might be just a standard system massage as the game is still in the development state there might be missing bits here and there but just in case I tried lowering the details of the game, changing the resolution, changed screeens on which I play ( i usually play on the ultrawide).
Next I Updated the gpu and windows version to the latest.
Also changed the chroma settings that every forum mentions still no use.
System specs:
CPU Details: Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz
GPU details : ROG ASUS GTX 1080ti
RAM : 32gig 3600Mghz BasiliskX
Mainboard: Z370 Carbon
Monitor 1 : Samsung Odyssey g9 ultrawide
Monitor 2 and 3 : Dell u2414H
Mouse : Corsair Scimtar Elite
Keyboard : Asus ROG HORUS GK2000
Audio interface : Focusrite Scarlet 2i2
Drivers:
Nvidia driver version : 531.29
Direct X Runtime version : 12.0
Operating sys: Win 10 latest as of today. - เกม
Yeah got the same Isssue, also tried everything like you did. The crashes occure mostly in Dungeons.
Also using widescreen Monitor . My Specs :
RTX3080 10gb GDDR5
i9-9900KF @ 5ghz
16gb DDR4 3200
Z370 Carbon Mainboard
maybe the wide screen is somehow the cause of it. I'll make sure to attach that video to a bug report along with all the crash reports that been generated by fenris system.
@@patryk199530 I tried to play with my 16:9 monitor and didn't work, crashed again while I was in a dungeon.
@@justinhess4535 I've got standard 1080p monitor and it didn't work so yeah.
Seems like in dungeons something goes wrong for us. I've noticed that my whole pc freezes when that happens and there are awful memory leaks.
The game resource usage climbs up to 22gb of ram and my whole gpu power I don't think it's that demanding...
just checked, it seems like wide screen is the issue. Unplugged every screen apart from standard 21 inch 1080p monitor and I could do couple of dungeons without a crash - plugged in the wide screen only and it crashed within minute.
My FPS randomly drop when I play and sometimes crashes into this fenris message. It mostly happens outdoors when I enter a city or TP, or there are a lot of mobs and I press abilities. Dungeons it runs perfectly. Idk why it happens because I have 16gb ram and I can play games like New World perfectly so why wouldn't my PC be able to handle diablo 4? I hope it's a blizz mistake cause I don't know what to do. Hope it doesn't happen on launch.
I've noticed that they have huge memory leaks - i have 32 gigs of ram and a good gpu
this game takes it all ...
I have this bug also. But I do not have the patience that you do. Or the technical knowhow. Ill just wait for them to fix it. At least I was able to get to lvl 20 so I get ma wolf hound pup.
haha that was my plan too but I noticed that it's doable to do the quests this way or at least it shows that you can get out of the crash zone if you find yourself stuck in the crashing loop of death :D.
do you have wide screen or multiple screens ? if yes are they this same resolution ?
To save everyone time - the fix for this is simple:
Delete the Diablo 4 Folder in your Documents Folder...you don't have to bother doing anything else.
I'll try that
Thank you, this worked. Shame the queue is 145mins now :)
it worked, but when messing with the graphics putting full screen, I pressed alt+tab and the game crashed
niceeeeee
@@leonardoinhoqui Yeah it happened to me one more time after that, but that was it. They were stress testing as well, so that may have contributed to the situation. It was pretty stable after Friday
Now in the open beta it's worse for me if I give alt+tab it crashes...
Mine crashed as well but after an hour, they certainly did something but it han't fix the issue :D
same here
@@lukejuke2385 delete the Diablo 4 folder in documents as @Troy Muni said it solves it, but don't put the game full screen because the problem via return leaves full screen (windowed mode)
I have the exact same issue every time i cross that bridge on that quest my game crash a couple time after
seems like D4 still crashes with no overclock and the visual ++ redist - the next thing I've tried is to cap my wide monitor to 60hz to match the other monitors I use so that all of them are at 60hz seems to work - also got the latest nvidia drivers which support D4
@@patryk199530 was about to try this but after the hotfix from 2day i didn’t crash anymore and manage to complete that main quest
@@joblotrep even after the hotfix I still crash sometimes but it isn't nearly as bad as it was :)
i get this problem just hitting play. i cant even start the game. and there is nothing in documents
try running the game in full screen.
in Your documents create Diablo IV folder and in that folder create LocalPrefs.txt file
This is maxed out graphics. if you pc can't run it well maybe at least you'll be able to get past play button and adjust the graphic settings accordingly.
In that file paste
LocalPreferencesVersion "2"
SkipIntroMovie "1"
FirstTimeFlowCompleted "1"
DisplayModeFlags "0"
DisplayModeWindowMode "0"
DisplayModeWinLeft "0"
DisplayModeWinTop "0"
DisplayModeUIOptWidth "1920"
DisplayModeUIOptHeight "1080"
DisplayModeWidth "1920"
DisplayModeHeight "1080"
DisplayModeRefreshRate "60"
DisplayModeColorSpace "0"
DisplayModeMSAALevel "1"
Monitor "0"
HDRBlackPoint "0.001000"
HDRWhitePoint "1000.000000"
HDRBrightness "250.000000"
SDRBrightness "1.000000"
SDRLinearThreshold "0.500000"
SDRHuePreserveRatio "0.660000"
SDRExposureFactor "1.000000"
Vsync "1"
GpuCrashReportingMode "0"
Adapter "0"
DisableChromaEffects "0"
LockCursorInFullscreenWindowed "0"
LimitForegroundFPS "1"
MaxForegroundFPS "150"
LimitBackgroundFPS "1"
MaxBackgroundFPS "8"
Sharpen "0.300000"
HardwareClass "5"
PCIVendor "4318"
PCIDevice "6918"
flSafeZoneLeft "0.000000"
flSafeZoneTop "0.000000"
FontScale "1"
ColorBlindFilter "0"
ColorBlindIntensity "1.000000"
CursorScale "0"
QualityPreset "2"
TextureQuality "2"
TextureFilterQuality "4"
ShadowQuality "3"
FogQuality "2"
PhysicsQuality "1"
ParticlesQuality "1.000000"
ClutterQuality "4"
FurQuality "2"
SSAOQuality "2"
AntialiasingQuality "1"
WaterSimQuality "1"
ShaderQuality "2"
ReflectionQuality "1"
GeoComplexity "2"
HeightFieldGeometryDetail "1"
LowFX "0"
Reflections "1"
DynamicShadows "1"
SoftShadows "1"
Raytracing "0"
RaytracedShadowsQuality "0"
RaytracedReflectionsQuality "0"
Distortion "1"
DLSS "0"
FSR "0"
FSR2 "0"
XeSS "0"
RenderResolutionScale "1.000000"
RenderCheckerboarded "0"
MipBias "-0.000000"
DisableTrilinearFiltering "0"
MasterVolume "0.200000"
EffectVolume "1.000000"
MusicVolume "1.000000"
NarrationVolume "1.000000"
AmbientVolume "1.000000"
SoundDriver "0"
AudioDevice "0"
SpeakerMode "0"
QuestSubtitlesEnabled "1"
CinematicsSubtitlesMode "1"
PlayInBackground "0"
MuteSound "0"
MuteEffects "0"
MuteAmbient "0"
MuteVoice "0"
MuteMusic "0"
ItemDropSoundMaster "1"
ItemDropSoundWeapons "1"
ItemDropSoundArmor "1"
ItemDropSoundJewelry "1"
ItemDropSoundSocketable "1"
ItemDropSoundOther "1"
ItemDropSoundMinQuality "0"
ItemAmbientSoundMaster "0"
ItemAmbientSoundWeapons "0"
ItemAmbientSoundArmor "0"
ItemAmbientSoundJewelry "0"
ItemAmbientSoundSocketable "0"
ItemAmbientSoundOther "0"
ItemAmbientSoundMinQuality "0"
ItemDropHoverSound "0"
ChatAudioDucking "1"
ChatAudioDuckingEnergy "0.000000"
TextLocale "2"
SoundLocale "2"
PushToTalk1 "1"
PushToTalk2 "1"
VoiceAutoJoin1 "0"
VoiceAutoJoin2 "0"
VoiceOutputVolume1 "1.000000"
VoiceOutputVolume2 "1.000000"
MicVolume1 "1.000000"
MicVolume2 "1.000000"
VoiceOutputDevice1 "0"
VoiceOutputDevice2 "0"
MicDevice1 "0"
MicDevice2 "0"
PlayerErrorAudioMode "0"
UseScreenReader "0"
TranscribeVoiceChat "0"
ScreenReaderPlaybackSpeed "0.000000"
ScreenReaderVolume "1.000000"
ScreenReaderVoice "0"
UseThirdPartyReader "0"
SubtitleSize "0.000000"
SubtitleColorIndex "0"
BackgroundOpacity "0.000000"
UseTextToSpeech "0"
TTSVoiceId "0"
TTSPlaybackSpeed "1"
EnableTTSChannelLocal "1"
EnableTTSChannelParty "1"
EnableTTSChannelTrade "1"
EnableTTSChannelClan "1"
EnableTTSChannelWhisper "1"
EnableTTSLineBreaks "1"
EnableTTSCharacterName "1"
EnableTTSChannelName "1"
EnableTTSItemName "1"
FilterFlags "-1"
@@patryk199530 thanks man! i super appreciate this. it still didnt work but oh wells. im not getting angry about it
@@snakehachi R.I.P :/
Replying here so people may find this information useful if they Google that crash.
It happened a lot during the server slam too, I had random crashes at one point in the act 1. Sometimes once every hour or 10min.
For me the problem was solved by reducing the frequency of my RAM in the bios. The RAM is the Ripjaws V 32 Gb DDR4, it supports 3600 MHz but you have to OC for that, it can make some games unstable.
It decreased it to 3400 MHz, I kept XMP in the bios and it worked perfectly fine for the remaining >20h I played the game without crash. I quickly tried to go back to 3533 or 3600 MHz at some point and the game crashed under 10min so I am confident it was the issue.
Hope it helps!
after installing d4 i noticed same issues started occuring in other games such as warzone 2.0.
however there the error was more specific - it was to do with overclock of my gpu and also visual ++ redist update done that and problem solved too so it should technically work for d4
- no overclock
- all in one visual ++ redist 2023 installed
@@patryk199530 Yes, fully agree, MW2 crashes the same way that's why I knew I had to try that. It returns a DirectX error. Could really be an unstability of the RAM/MOBO combination since most of the RAM sticks are sold for 3600MHz with OC (!).
seems like D4 still crashes with no overclock and the visual ++ redist - the next thing I've tried is to cap my wide monitor to 60hz to match the other monitors I use so that all of them are at 60hz seems to work - also got the latest nvidia drivers
I have no idea what you're even doing here to fix it?
Read the description. The video presents the problem and the "solution" is in the description, although I just crashed again after a longer while so it doesn't get rid of the problem....