Heaven crashing on directx 11.

MurphyBrix · 27 Mar 2016 at 17:30

Hi Guys

Wanted to see if i could overclock my card abit, so opened bench marking up on heaven to use it, and Ive discovered when directx 11 is selected instead of directx 9, which runs fine by the way, heaven crashes really soon after the test starts and im getting this message -

Display driver stopped working and has recovered. Display driver Nvidia windows kernal mode driver version 364.51 stopped responding and has successfully recovered.

It starts and stops about 3 times and then says application heaven.exe has been stopped from using graphics hardware.

Im running a gigabyte 980ti at 2560x1440 at 144hz on my gsync screen with no vsync on.

Everything works perfectly fine on directx 9, is there any reason its doing this or im i being a complete noob.

Cheers guys

MurphyBrix · 27 Mar 2016 at 17:30

Also my nvidia drives are all up too date.

theMilitant · 27 Mar 2016 at 17:52

Your GPU overclock may just be unstable. Tried running at stock settings, with any CPU overclock removed as well? Open up some monitoring software like MSI Afterburner while you're running the benchmark to check your CPU and GPU temps.

MurphyBrix · 27 Mar 2016 at 17:56

I'm currently running at stock, nothing has even been adjusted and thats the way its been going. my cpu isnt an overclockable version just a standard i7-3770.

Danny75 · 27 Mar 2016 at 18:08

Try using the 362.00 Nvidia driver.

Could also be some missing Microsoft Visual C++ thing needed, who knows. I had a similar problem with Valley or Heaven in the past, but don't remember what the fix was exactly.

Try 3DMark too, see what happens. https://www.futuremark.com/benchmarks/3dmark

MurphyBrix · 27 Mar 2016 at 18:13

I did try the 3dmark tests what I did try worked. Although I did notice they weren't working at a brilliant rate. I shall try that driver when I get on my machine later. I take it directx 11 should work just as fine as directx 9??

Adam123 · 27 Mar 2016 at 23:24

I'd DDU your current gpu drivers, reinstall 362.00, manually update direct X and C++ x64 & x86 and double check settings in BIOS and try again. I've had Valley throw a wobbly in the past.

That's a lot of ands