What does KMODE_EXCEPTION_NOT_HANDLED mean and why does it happen randomly when i play Ashes of the Singularity. I get a blue screen of death and then an instant restart.
~football13tb
Here's what Microsoft has to say about it: https://msdn.microsoft.com/en-us/library/windows/hardware/ff557408(v=vs.85).aspx
Something's getting corrupt in memory.
Were it me, the first thing I'd do is check with my motherboard/PC mfr to make sure I have the latest chipset, LAN, audio, etc. drivers installed. After that I'd take a hard look at my memory components. You can search for MEMTEST86, download the latest version in a bootable form and run the memory test.
Good luck!
I assure you if anything is the cause it is Ashes of the Singularity. My system has handled every memory/GPU/CPU benchmark just fine over the last three years. I also know my all of my drivers are up to date and my BIOS is up to date. I just want the developers at Ashes of the Singularity to know their game caused my only 2 BSoD's on my computer since i built it three years ago.
Windows 10
Ashes Dx11 (Dx12 is horribly unstable)
GTX 660ti EVGA SC edition 2GB VRAM
i5 4670k
8gb 1600mhz RAM
~football13tb
I would still recommend rerunning memtest. Components wear out, even though your computer may have been fine over the last three years, it could have developed an issue over time. AotS can use large amounts of system memory, which might be using muscles in your PC that hasn't flexed in so long that it forgot that it had them.
After you have confirmed that your system does not have any hardware or driver related issues I recommend saving your games regularly, until you get the crash again. Reload, and see if you can reproduce it. This would help diagnose the issue so that the developers can resolve it if there is an issue in the game.
If your problem persists, you should consider submitting a support ticket.
if you have updated to 361.43 driver reupdate to 361.75
"Changes and Fixed Issues in Version 361.75
...
[361.43] Users get SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M(1000007e) BSOD when using driver in games. [1715822]"
good luck
Just so you know memtest did not come up with any issues, and i was running 361.75 driver during both of the BSoD's
Also, i have started a support ticket with Stardock to help track this error down.
~football13tb
Welcome Guest! Please take the time to register with us.
AshesoftheSingularity Forums