This issue was mostly fixed in 3DMark v1.5.884, but it seems that it can still occur, if only rarely. If you are experiencing this problem, please submit a support request with your hardware configuration details, including the motherboard model and BIOS version.