Thanks for the latest version FurMark 1.19.0.I have a question for you.My laptop graphics is GeForce GTX 1060 and it will be hotter while running stress test with FurMark 1.19.0.But it didn't be hot with FurMark 1.18.2.Why do you know? Any suggestions would be appreciated.

I have no particular idea. FurMark 1.19.0 has exactly the same stress test module than FurMark 1.18.2. The background image has been updated but I don't think it's the source of the additional stress test.

Thanks for your reply.Is it possible that the FurMark 1.18.2. cannot recognize the Nvidia GTX1060 of my laptop but FurMark 1.19.0 can.What's the difference between FurMark can support my hardware and it cann't.

Sorry to bother you. I have a question about Furmark. Could you please give me some suggestions if you are free.

The FPS and GPU's usage in Furmark will drop down to 104 and 65%(from 140 fps and 99% usage) if I run another CPU stress test together.(CPU burner,AIDA64 or Prime95) That weird thing is it will come back to normal if I uncheck and check again the item how many CPUs to be allowed to run Furmark.in the device manager.(settings in detail, please refer to the steps below)It is weird because I didn't change anything and just checked and unchecked the item(CPU) in the affinity of device manager.

Here's the problem in detail.

I have a laptop with i7-8700K CPU, Nvidia GTX 1070 graphics card and windows 10.The Furmark v1.19.1.0 will show me a 140 FPS and a 99% of GPU usage after running stress test.After I ran a CPU stress test together as the GPU burner bulid-in Furmark app.(or Prime95)The FPS and GPU usage will immediately drop down to 108 FPS and 65% of GPU usage.In the meantime, No any limit reasons were found in Furmak.But it will come back to normal as running Furmark alone if I reset the affinity(CPU) in the device manager.

Why the FPS and Usage in Furmark will come back to normal when I just did the following steps?

1.Right-click on the Windows taskbar and launch Task Manager.2.Then switch over to the details tab.3.Find the "Furmark app" in the list, right-click on it and choose Set affinity from the context menu.4.Just uncheck the "all processors" item(how many CPUs to be allowed to run Furmark)5.Check the "all processors" item againg6.Press "OK" button to apply.7.Then, you can see the FPS and Usage come back to normal as before.

I know if I end the CPU stress test, the FurMark will come back to normal, too.But I am wondering why it will also work when I just reset the affinity(CPU) in the device manager.Is it a bug in Furmark? What do you think about that.That problem will let system not get the maximum loadings when I run a combined test(CPU and GPU)and forget to set the affinity(CPU) for Furmark.

In my system Furmark's 1.19.1 does not work properly.Please check whether it operates normally on the next system.An error occurs in about three minutes from the execution of the program and the program is dropped.Thanking you in advance.

Why is there no database on Furmark 1.19.1 for 4k resolution. I have a very decent score on my RX Vega 56 of 7555 and would like to know how that stands comparitively to other 4k resolution scores.

There is a link at the bottom of the FurMark scores page. But most of scores seem fake. I just re-benchmarked my GeForce GTX 1080 and I get a score of 2790 points (47 FPS) for preset P2160 (3840x2160). I haven't tested the RX Vega 56 but 7555 seems a very high score for a single Radeon. Maybe it's a crossfire score? For the preset P1080, I get 7295 points (122 FPS) with the GTX 1080.

I have a laptop with i7-8700K CPU, Nvidia GTX 1070 graphics card and windows 10.The Furmark v1.19.1.0 will show me a 140 FPS and a 99% of GPU usage after running stress test.After I ran a CPU stress test together as the GPU burner bulid-in Furmark app.(or Prime95)The FPS and GPU usage will immediately drop down to 108 FPS and 65% of GPU usage.In the meantime, No any limit reasons were found in Furmak.But it will come back to normal as running Furmark alone if I reset the affinity(CPU) in the device manager.

Yes there a minor thread affinity issue in the current FurMark but it will be fixed in the next release.