I just got a new Thinkpad P53 with a Quadro RTX 3000 graphics card (roughly equivalent to the GeForce RTX 2060 consumer card), and am getting sporadic benchmark results for the graphics card. 3D Mark "Time Spy" score is sometimes 2900, sometimes 5500 (specifically, graphics test 2 gives consistent fps results from run to run, but graphics test 1 sometimes gives fps ~30, and sometimes ~10).
I'm getting similarly extreme osculation in Passmark 3d graphics benchmark (sometimes get a score ~5000, sometimes ~10000).
Laptop is plugged in and set to high performance throughout. No programs running in background, etc.
I've benchmarked a lot of computers (both desktops and laptops), and have never seen this kind of oscillation when the computer remains in a constant state (power supply, performance mode, etc.)
It's obviously normal to see small variations, but with this computer I run the test once I get one result, then run it again and the number halves... then run it several more times, and sometimes I get the first number, sometimes the second number.
I'm wondering if anyone else has seen this kind of benchmark variation, and whether it is indicative of a hardware issue, or whether it could be caused by Lenovo's power management software or something.
The weird thing is that Furmark seems to run at constant fps for hours, and 3D Mark 11 also seems to give consistent results from run to run...
Any help is much appreciated!
I have updated my BIOS and all my device drivers and nVidia drivers to latest available versions, run all Windows updates, Lenovo updates, etc.
I have made sure my laptop power settings are always on Maximum Performance, and that all relevant advanced settings are set to prefer performance over energy savings:
I have tried setting global nvidia control panel settings to always use the nVidia processor, and always "prefer maximum performance":
I have tried disabling my laptop's integrated graphics entirely via the relevant BIOS setting.
None of these adjustments have solved the problem.
I have purchased and run the full version of 3D Mark Fire Strike stress test, which has revealed the the problem does seem to be related to the GPU sometimes failing to reach the appropriate clock levels under load. During the stress test, clock rate would sometimes boost appropriately, and sometimes fail to boost until part way through the test (sometimes tens of minutes):