- Joined
- Feb 20, 2019
- Messages
- 8,339 (3.91/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. |
The 6500 and 6400 aren't awful cards, just bad examples of a typical AMD driver/HDMI/DP feature experience.I didn't pick a bad example. AMD just relies on Windows native controls to toggle stuff on like Variable Refresh Rate, which the 6400 / 6500 both support. NVIDIA however likes to unnecessarily duplicate functionality into their outdated-looking control panel.
- PCIe x4 instead of x16 causes problems on older machines, and the silicon was designed specifically for PCIe 4.0 in laptops.
- Lacking encoder means parts of the Adrenaline suite are just missing entirely. That could be relevent IMO, as with things like Freesync that causes issues as I've found AMD drivers expose some Freesync options in one tab whilst being greyed out in another tab when using a non-freesync display. I've managed to "enable" Freesync in the driver via game profiles on a non-freesync display which breaks things and causes odd behaviour until a reboot.
- Display engine limitations that are different to all previous-gen cards, and the rest of the entire 60-series line-up. If anything was going to trip up the driver dev team or slip through the QC net, that's a prime candidate.
I mean, all that I've just said sounds like big problems with Radeon drivers but I've had equally stupid issues with Nvidia connecting to TVs in the past. For years, their control panel screwed up refresh rates and colour range, frequently resetting to limited-HDMI (16-235 instead of 0-255) for both a home TV and an TV in the lobby at work.
Last edited: