A Fatal DirectX has occurred (1100002)

[Dynratygus]

Thank you for the reply.

Have you tried changing the window size at all? Check whether the game is running in fullscreen mode, windowed or borderless fullscreen. Fullscreen is generally more efficient when using GPU resources. Also, does this crash happen when you are logged on in game? Or does it occur when trying access a certain location in game?

Hope to see you online!

[jkengland]

I am not getting an error but my system completely crashes. The solution posted above to limit frame rate to 30 seems to resolve the issue, however I do not consider this FIXED.

[Valkeyreion]

Hey Dynratygus, thanks for the reply.

I tried it in full-screen, no crashes occurred. This issue is really strange, for the life of me I can't figure out what could be causing it; so far the game doesn't crash in:

-DirectX9
-DirectX11 at 30FPS in Borderless Windowed
-DirectX11 at 60FPS in Fullscreen

But the game will crash in DX11 at 60FPS in Borderless Windowed, so this is a very strange issue. As for where the crashes occur, it's not bound to any location, it's just a crash in general.

If you've got any ideas on how to fix it then I'd be greatly appreciative but considering other people have had similar issues and the crash only occurs in certain system configurations, I would recommend passing it along to the bug fix team as it seems like it's most likely an issue with the game in my opinion.

Thanks again for the help so far, and for any further help you can give me

[Valkeyreion]

Hi Dynratygus, I replied previously but the issue is still persisting so I'm sending out a second reply in the hopes you can aid me further with this issue.

Thanks again for your time.

[Xaeom]

Hey guys, I have the same thing here. Started recently. Current build:

Ryzen 7 1700
Corsair Vengeance Pro RGB - 16GB 3600mhz
MSI RTX 2080 TI

You other folks, I wonder whether you also have the Corsair Vengeance RGB RAM? I've got a weird suspicion that it might be this, as changing the clock rates on the RAM seemed to change the frequency of this crash.

I've now swapped to my older DDR and haven't received a crash since. Only one nights worth of test, though, will keep this updated.

PS I'm running the game at 200fps due to beefy card and a 200hz monitor with GSync.

I haven't tried DX9, didn't know it was possible. If I get a crash on this RAM, I'll try it next.

X

[Evan748]

Hey guys, I have the same thing here. Started recently. Current build:

Ryzen 7 1700
Corsair Vengeance Pro RGB - 16GB 3600mhz
MSI RTX 2080 TI

You other folks, I wonder whether you also have the Corsair Vengeance RGB RAM? I've got a weird suspicion that it might be this, as changing the clock rates on the RAM seemed to change the frequency of this crash.

I've now swapped to my older DDR and haven't received a crash since. Only one nights worth of test, though, will keep this updated.

PS I'm running the game at 200fps due to beefy card and a 200hz monitor with GSync.

I haven't tried DX9, didn't know it was possible. If I get a crash on this RAM, I'll try it next.

X

I use Corsair Vengeance Ram but not RGB. A couple weeks back my PC totally broke playing FFXIV but I didnt mention it here as I thought it was unrelated... Cleaning and re-seating the RAM fixed it.

On a different note...

Valkeyreion mentions that it works for her @60FPS in fullscreen with DirectX 11 but thats not the case with me, mine will crash.

It works in DirectX 9 @60FPS or DirectX 11 @30FPS... I will try Borderless Windowed with DirectX 11 @unlimited FPS/60FPS and see what happens.

EDIT: Yeah Borderless Windowed DirectX 11 @60FPS crashed within 5min =(

[Astorrin]

I had to use Display Driver Uninstaller and install the newest Nvidia driver to fix my directx crash.

If that don't work i know that ryzen don't like RAM XMP profile, maybe try to turn that off in bios.

[KageTokage]

After the most recent windows update, I had two back to back crashes of this nature within maybe 30 seconds of logging in.

The severity was bad enough that the GPU basically turned off then wouldn't turn back on, forcing me to forcibly shut down the PC. The second shutdown actually ended up causing some severe file corruption that forced me to reinstall Windows entirely, and while the game seems to now be running better then ever, they seriously need to work out whatever hiccups in the DX11 client that are causing this, since I really shouldn't be having to worry every single time I see the "Update and shut down" option show up.

[Voidkissed]

After the most recent windows update, I had two back to back crashes of this nature within maybe 30 seconds of logging in.

The severity was bad enough that the GPU basically turned off then wouldn't turn back on, forcing me to forcibly shut down the PC. The second shutdown actually ended up causing some severe file corruption that forced me to reinstall Windows entirely, and while the game seems to now be running better then ever, they seriously need to work out whatever hiccups in the DX11 client that are causing this, since I really shouldn't be having to worry every single time I see the "Update and shut down" option show up.

I had something very similar happen, though afterwards the game is running, arguably, worse! So this is just getting to be ridiculous and is currently unplayable for me.

[KageTokage]

The game was still running in my case, as well. I could still hear the music playing, but there was no display on the screens and the keyboard was unresponsive.

It's rather frustrating because I had managed to avoid that particular crash for multiple weeks.

So far, reinstalling the OS seems to have alleviated the issues, but I imagine it's only a matter of time before it breaks again...