- Joined
- Oct 2, 2004
- Messages
- 14,025 (1.84/day)
System Name | Dark Monolith |
---|---|
Processor | AMD Ryzen 7 5800X3D |
Motherboard | ASUS Strix X570-E |
Cooling | Arctic Cooling Freezer II 240mm + 2x SilentWings 3 120mm |
Memory | 64 GB G.Skill Ripjaws V Black 3600 MHz |
Video Card(s) | XFX Radeon RX 9070 XT Mercury OC Magnetic Air |
Storage | Seagate Firecuda 530 4 TB SSD + Samsung 850 Pro 2 TB SSD + Seagate Barracuda 8 TB HDD |
Display(s) | ASUS ROG Swift PG27AQDM 240Hz OLED |
Case | Silverstone Kublai KL-07 |
Audio Device(s) | Sound Blaster AE-9 MUSES Edition + Altec Lansing MX5021 2.1 Nichicon Gold |
Power Supply | BeQuiet DarkPower 11 Pro 750W |
Mouse | Logitech G502 Proteus Spectrum |
Keyboard | UVI Pride MechaOptical |
Software | Windows 11 Pro |
I wanted to report this to 3DMark, but the system refuses to accept my bug report, so I'm hoping someone from Futuremark is floating around these parts...
Now, I know my overclocks can go to very limits, but something isn't right with the stress test in latest 3DMark.
I tweak the graphic card, stress it with Extreme stress test, I sit there watch it go through all 20 loops and the end result is 0% frame consistency and 1 completed loop. Now, wait a minute, it just finished all 20 of them and it looked perfectly smooth. And yet framerate was apparently so bad it scored 0% and only 1 completed loop even though it completed 20 of them? That can't be right?
I've seen it do this when driver restarts and I understand why it might confuse the app, but this wasn't the case now. The driver didn't reset. I double checked with the Event Viewer.
What is going on here?
Now, I know my overclocks can go to very limits, but something isn't right with the stress test in latest 3DMark.
I tweak the graphic card, stress it with Extreme stress test, I sit there watch it go through all 20 loops and the end result is 0% frame consistency and 1 completed loop. Now, wait a minute, it just finished all 20 of them and it looked perfectly smooth. And yet framerate was apparently so bad it scored 0% and only 1 completed loop even though it completed 20 of them? That can't be right?
I've seen it do this when driver restarts and I understand why it might confuse the app, but this wasn't the case now. The driver didn't reset. I double checked with the Event Viewer.
What is going on here?