Realbench LuxMark-x64.exe stopped working

[madmeatballs]

When luxmark-x64.exe stops working can it be possible that my ram isn't stable? or this has something to do with GPU overclocks?
Although, I highly doubt it is GPU instability though since I passed Realbench 8hr stress with 1.4v DRAM Voltage. It is just that I am testing my ram because I believe it is faulty I keep on getting page fault/system PTE misuse BSOD when I power up my computer from a cold boot. G.Skill asked me to test at Bios optimized settings with XMP enabled and disabled. Well in this one I have XMP enabled. I just want to know if this LuxMark-x64 crash can also be caused by unstable ram.

[jab383]

Yes, it can. I have had that error when tweaking RAM a little too far.

Luxmark exercises CPU, DRAM, GPU and video RAM. All those have to be stable. GPU instability shows only in Luxmark. CPU overclock instability will show up in Luxmark, but shows up sooner in H264 or Multitasking stages. RAM instability shows up where ever the RAM makes errors.

[Eric_F]

Yes, if Luxmark freezes, but everything else in RealBench works, you're still on the edge of instability somewhere.

Luxmark especially pushes I/O transfers from the GPU though CPU and RAM. It will work the memory controller hard.

If you set your RAM to stock voltage and speed and it still locks up, then look closely at your CPU voltages. SA voltage comes into play here, as does the Vdroop effect of CPU load-line calibration.

I have two near-identical i7-6700K builds. (Only difference is the video cards.) The one that's "mine" (the one in my sig) seems to be a particularly good i7; it overclocked easily to 4.9GHZ at temperatures I liked. (5 was possible, but too hot for my taste) Luxmark never failed on it -- Instability showed up more on Handbrake tests that used AVX and pushed CPU loads to the max. The other build, which I put together for my wife, was an uphill battle all the way. The memory controller showed a distinct preference for one pair of memory slots over another. Luxmark would throw it constantly until the SA and VCCIO voltages were tweaked slightly beyond just what was necessary for good CPU clock stability. My impression is that one's memory controller is "weak" and needed additional tweaking to make it run well with the OC'd RAM. The end result was that the best stability came from a slightly lower CPU overclock (4.7 max instead of 4.9) which gave a better range of voltages to keep the memory controller happy. The silicon lottery is like that sometimes.

[Jollydet]

I was chasing my tail for days trying to setup a 6800k overclock, getting black screens and luxmark crashing just like in your screenshot, turns out it is indeed a gpu issue there is an open issue with luxmark crashing on pascal gpus as listed in the release notes for even the newest nvidia driver, to verify it is a gpu issue you can select benchmark instead of stress test and only select h264 video encoding, or you can run the x264 stress test people have been using on haswell chips for years or run realbench stress test with a non pascal gpu. Until nvidia fix this issue do not use realbench stress test as it is not reliable on pascal gpu based systems and you will go crazy.. Hope that helps!

[MMikhail]

Jollydet wrote:
I was chasing my tail for days trying to setup a 6800k overclock, getting black screens and luxmark crashing just like in your screenshot, turns out it is indeed a gpu issue there is an open issue with luxmark crashing on pascal gpus as listed in the release notes for even the newest nvidia driver, to verify it is a gpu issue you can select benchmark instead of stress test and only select h264 video encoding, or you can run the x264 stress test people have been using on haswell chips for years or run realbench stress test with a non pascal gpu. Until nvidia fix this issue do not use realbench stress test as it is not reliable on pascal gpu based systems and you will go crazy.. Hope that helps!

So, RB instability is really a GPU problem?
Going crazy with this for month now...
https://rog.asus.com/forum/showthread.php?87057-Blender-BLF_lang_init-locale-data-path-for-translati...

[Arne_Saknussemm]

Very often a clean (use DDU) reinstall of graphics driver solves this issue.

Been posted up here many times if you have a quick search.

There are some issues with Pascal and latest drivers though.

[Jollydet]

Arne Saknussemm wrote:
Very often a clean (use DDU) reinstall of graphics driver solves this issue.

Been posted up here many times if you have a quick search.

There are some issues with Pascal and latest drivers though.

Hi Arne
For me the issue remained even after a clean install of w10, before a clean install i used ddu wipe and then installed a bunch of the older drivers to no avail

[Arne_Saknussemm]

Hope Nvidia get their act together RE drivers ASAP...:(

[madmeatballs]

Oh, well nvidia has to fix their sh*t lol.

[Chino]

Running the latest NVIDIA drivers and benchmarking in RB without a problem.