Benchmark causes Blue Screen (while stress testing via V-Ray NEXT works fine)

[JezUK]

My two machines, 7980xe, are both overclocked via the auto settings in BIOS (to 'Extreme'), and both are running at a clock speed of 4.2Ghz.

My slave PC runs the Benchmark for around 6-7 seconds and then the benchmark UI disappears (i.e. crashes).

My main PC does the same, only at around 6-7, seconds, instead of the benchmark software crashing, it this PC Blue Screens and crashes Windows.

I'm running Windows 10 Pro and the latest version of the Benchmark, 1.0.8.

Any ideas

Thanks.

[vlado]

Is that the CPU or the GPU portion of the benchmark?

Normally a blue screen means either a hardware problem (overheating, faulty memory etc) or a driver issue (when rendering on the GPU).

Best regards,
Vlado

[JezUK]

CPU testing only.

When I then try an actual render (Distributed) - both machines complete that 15 minute render fine.

(VRay benchmark testing before OC'ing were running fine and reporting times etc).

It's just strange the an actual render of over 15 minutes works fine (which is quite a severe stress test in itself), but the benchmark fails / bombs out / blue screens.

[savage309]

V-Ray Bench can not cause a BSOD by itself. It is overclock/hardware/OS problem (the fact that it works when it is not OC confirms that).

Best,
Blago.

[JezUK]

Yes I think the OC was too severe, so I’ve tturned it down. Seems the benchmark test is more extreme than an actual render.

[savage309]

The benchmark uses the render after all, so it is the same. There is difference on the things the CPU does for the different scenes, so mostly this is causing it.

Best,
Blago

[varosi]

On the Blue screen usually you may find some information about what driver is the cause of the BSOD.