• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

GravityMark v1.89 GPU Benchmark

When trying to run Direct X (instead of Vulkan) I get this error every time, nut vulkan runs fine.

Error.jpg
 
When trying to run Direct X (instead of Vulkan) I get this error every time, nut vulkan runs fine.
It could be a driver issue, since previous Nvidia generations work fine. We will either try to fix it on our end or report it.
 
AMD R7 7800X3D + RX7800XT @2650~2750MHz (min/max)
DirectX12+RT
2025-07-01 15.10.23 gravitymark.tellusim.com 91cf9acc53bd.jpg


Vulcan+RT
2025-07-01 15.24.44 gravitymark.tellusim.com 6998a8339c45.jpg


Seems Vulcan offers quite the jump over DX12 when RT is used and all other setting are the same
 
Last edited:
It could be a driver issue, since previous Nvidia generations work fine. We will either try to fix it on our end or report it.
I tried the prior 9 drivers compatible with the 5090s, as well as the prior 3 versions of gravity mark. For me, dual 5090s in DX results in the error I reported.

However Vulkan runs fine across all those drivers and and the versions of the Gravitymark, but DX.... error
 
Last edited:
#212
DateJune 22 2025
User:D:D
APIDirect3D12
Version1.88 (Sep 16 2024)
PlatformMicrosoft Windows 10 Home 10.0.19045
ProcessorIntel(R) Xeon(R) CPU E5-2696 v3 @ 2.30GHz
MotherboardX99 Taichi ASRock
Memory31.92 GB
Graphics CardNVIDIA GeForce RTX 5070
Graphics Driver576.52
Video Memory11.94 GB
Resolution2560x1440
Asteroids200,000
Score55,156
Time167.0 s
FPS330.3
Min / Max141.3 / 554.4
Efficiency1,680 (Frames / W⋅ms)
Consumption9.12 W⋅h (196.63 Watt)

 
It could be a driver issue, since previous Nvidia generations work fine. We will either try to fix it on our end or report it.
Tried all combinations, the prior 9 drivers compatible with the 5090s, as well as the prior 3 versions of gravity mark. For me, dual 5090s in DX results in the error I reported.

However Vulkan runs fine across all those drivers and and the versions of the Gravitymark, but DX.... error, again, and again

Error.jpg
 
Tried all combinations, the prior 9 drivers compatible with the 5090s, as well as the prior 3 versions of gravity mark. For me, dual 5090s in DX results in the error I reported.

However Vulkan runs fine across all those drivers and and the versions of the Gravitymark, but DX.... error, again, and again

View attachment 406247
Thank you for the details. We are waiting for delivery of the 50xx for testing.
 
I tried the prior 9 drivers compatible with the 5090s, as well as the prior 3 versions of gravity mark. For me, dual 5090s in DX results in the error I reported.

However Vulkan runs fine across all those drivers and and the versions of the Gravitymark, but DX.... error

It seems like the driver issue (576.88):

D3D12 WARNING: ID3D12Device::RemoveDevice: Device removal has been triggered for the following reason (DXGI_ERROR_DRIVER_INTERNAL_ERROR: There is strong evidence that the driver has perf
ormed an undefined operation; but it may be because the application performed an illegal or undefined operation to begin with.). [ EXECUTION WARNING #233: DEVICE_REMOVAL_PROCESS_POSSIBLY_AT_FAULT]
 
Some rather strange scores on here, unless people are using 1000 watt BIOSes, I can't see how the top scores are even remotely possible.

GravityMark_001.png


GravityMark_002.png



Screenshot_20250708_030537.png
Screenshot_20250708_031117.png
 
First runs
 

Attachments

  • gravity mark top 9 .png
    gravity mark top 9 .png
    911.8 KB · Views: 11
  • gravity mark top 9 2 .png
    gravity mark top 9 2 .png
    259.3 KB · Views: 14
Normal default raster.

Wonder if it is because I have SAM turned off?

GravityMark_003.png


So SAM does affect score by 6K points on a Radeon 7900 XTX.

GravityMark_004.png




Efficiency1,168 (Frames / W⋅ms)
Consumption18.24 W⋅h (393.11 Watt)
 
Last edited:
It seems like the driver issue (576.88):

D3D12 WARNING: ID3D12Device::RemoveDevice: Device removal has been triggered for the following reason (DXGI_ERROR_DRIVER_INTERNAL_ERROR: There is strong evidence that the driver has perf
ormed an undefined operation; but it may be because the application performed an illegal or undefined operation to begin with.). [ EXECUTION WARNING #233: DEVICE_REMOVAL_PROCESS_POSSIBLY_AT_FAULT]
tried it with 590 driver, no issues in Vulkan, but got this in DX12 :
d12error.jpg
 
I wonder if it could be anything to do with the removal of 32bit PhysX from it's drivers for 50xx GPU's
 
Back
Top