- Joined
- Feb 20, 2019
- Messages
- 8,706 (3.99/day)
| System Name | Bragging Rights |
|---|---|
| Processor | Atom Z3735F 1.33GHz |
| Motherboard | It has no markings but it's green |
| Cooling | No, it's a 2.2W processor |
| Memory | 2GB DDR3L-1333 |
| Video Card(s) | Gen7 Intel HD (4EU @ 311MHz) |
| Storage | 32GB eMMC and 128GB Sandisk Extreme U3 |
| Display(s) | 10" IPS 1280x800 60Hz |
| Case | Veddha T2 |
| Audio Device(s) | Apparently, yes |
| Power Supply | Samsung 18W 5V fast-charger |
| Mouse | MX Anywhere 2 |
| Keyboard | Logitech MX Keys (not Cherry MX at all) |
| VR HMD | Samsung Oddyssey, not that I'd plug it into this though.... |
| Software | W10 21H1, barely |
| Benchmark Scores | I once clocked a Celeron-300A to 564MHz on an Abit BE6 and it scored over 9000. |
Most of the GPU instabilities I've seen in the last decade or so have been crashes caused by sudden clock and voltage changes. I guess where a GPU is stable at higher clocks and loads, something about the silicon degradation or VRM degradation over time seems to hate the sudden ramps from low load to high load and vice-versa. In other words, a failing GPU can be 100% stable for an hour of Furmark/OCCT/Superposition but will crash in real games, or 3DMark where the scene gets unloaded and reloaded and the GPU cycles from idle to full regularly.
Nah, not useless. It's a very quick and successful way to test if the GPU's cooler can handle full TDP. Variants like OCCT or Kombustor also integrate output checking so you can quickly tell if there is faulty VRAM or if the GPU is spitting out errors because it's fallen the wrong side of the stable clock/voltage curve.
For real-world stability, it's not very useful any more, but as a rapid diagnostic to check for cooler/paste issues and faulty silicon it's still an excellent litmus test.