Keep in mind that
@x BlueRobot found the actual part of software that crashed the computer so his advices are lot better than mine. Usually, this happen when you update your drivers by overwriting an old version. Try to clean desinstal your videodriver first, reboot in safe mode, then use a video driver cleaner tool that AMD recommends (i don't know AMD cards), reboot in safe mode, then reinstall the last videodriver from AMD.
Those are recent games, AMD did not evacuate each bug in these.
I suppose this happened when you changed from a zone in the game, then make a U turn and go back, no ?
If C, D and E are different physical drives, I, as a random computer-joe advice, would still recommend to put the virtual memory on your D drive, and set it to a fixed size of 1.5x your total RAM. Making it fixed would hang and release the system instead of making it crash (in my opinion). Making it variable or automatic would increase the hang time. If set to low, then here are your overflow.
Setting it on the a different physical disk than C or the game is an oldschool optimisation than proven good result with windows systems (nerd reason : C get a full SATA bandwidth for OS, then D get a full SATA bandwidth for swap, then E get a full SATA bandwidth for game files. This is oldschool but still work well).