PC Tips (dot) click
Hardware and Software Tutorials, Benchmarks and Reviews
GeForce Now Supported Controller List
The DDR Memory Apocalypse
![]() |
| RAM price trends. Ignore the sudden drop. |
The above screenshot is from an online sale of DDR4 2400MHz kits produced two months ago.
I just checked and G.Skill seems to have these and 3000MHz RAM with plenty of supply. That is certainly also new stock.
Prices start at around 54€ per 8GB DIMM, which is somewhat higher than the 40€ I'd expect it to be based on spot prices.
HP Omnibook 3 14" (AMD) Quick Review
![]() |
| The best picture I could find on HP materials |
I recently quickly tested a mainstream HP Omnibook 3 14" laptop based on the terribly bad Ryzen 5 40 chip.
This is a new laptop with excellent build quality. This model in particular has an IPS screen and a very good one at that:
- Anti-glare type but slightly gloss
- No dirty-grit like surface w/ excellent definition.
- Excellent color range, seems like a full 100% sRGB panel with great calibration.
- Response time seemed ok
The bad
- Speedometer 2.0 run at ~205.00, boost tops at 3.50GHz (should be 4.30)
- ~240 on i5 8265U
- ~250 on i3-N305
Xbox on PC is a Joke
- Downloads do not stop computer from suspending. Downloading a 100GB game may mean manually waking it up if you have short of a Gigabit connection (or are using WiFi).
- Cannot move installed games between drives.
- Need to have the main install folder on C drive.
Xbox pad works on login screen, does not let you unlock(Working with Xbox One gamepad or later)- Cannot use controllers other than Xbox compatible ones (360, One, Series).
The Intellification of AMD
Through multiple rebrands, AMD is slowing becoming the Intel we used to know and hate. This post will hopefully keep you away from these products or at least caution you to pay a fair price.
The first step in this journey was given with the 5000 series, but it became much worse with 7000: it had Zen 4, Zen 3 and Zen 2 chips in the lineup. The distinguishing feature? It ended in 20, 30 or 40.
Now we have a "40" chip with Zen 2 cores. This was entirely predictable.
Going back to 7000, there were 7520U chips that were some low cost 4 core chips with small iGPUs called Mendocino. 7735U was Zen 3(+), but this one could be passable, even if I think it should have never been "Ryzen 7" or 7700 to begin with.
It is hard to understand the Mendocino chips because they are mostly available in more expensive laptops than this 5000 chips, despite lower core counts and significantly worse iGPUs (40%+ deficit). You could since last year, and still can, buy 5700U (Zen 2 6C), 5625U and 5825U laptops for less. Even the 5625U is a perfectly fine chip for office work and will be for some years.
The (not so) new chips
- Ryzen 5 30, 4C/8T 2.8GHz Zen 2, Radeon 610M 2CU
- Ryzen 5 40, 4C/8T 2.4GHz Zen 2, Radeon 610M 2CU
- Ryzen 3 110, 4C/8T 3.0GHz Zen 3, Radeon 660M 4CU (!!!)
- Ryzen 5 130, 6C/12T 2.9GHz Zen 3, Radeon 660M 6CU
- Ryzen 5 150, 6C/12T 3.3GHz Zen 3, Radeon 660M 6CU (higher TDP)
- Ryzen 7 160, 8C/16T 2.7GHz Zen 3, RAdeon 680M 12CU
- Ryzen 7 170, 8C/16T 3.2GHz Zen 3, RAdeon 680M 12CU (higher TDP)
AM3 and AM4 Motherboards for Home Servers - MCE, ECC and RAS Features
![]() |
| ASRock AM4 Pro4 Motherboard |
Update, 2026: Zen 3 chips require at least Kernel 6.12 for proper decoding and (I think) handling of MCE and ECC errors. Without it, only a single message of error is logged, no CE/UE are logged or actions taken.
A while back I have built ECC platforms based on consumer hardware and found the information on the web is not really accurate.
Specifically, while ASUS AM3 boards support ECC mode and I have been using this for some years now. I have never witnessed any error being reported during this time, but I am located near the sea level which has influence on the number of cosmic rays.
There is also Machine Check Exceptions support on these platforms but the motherboard itself is hit and miss. These are useful to track errors in CPU caches and other parts, that help prevent data corruption and make you aware of damaged hardware (mostly PSU or board VRMs).
Some TLDR for CPUs:
- AMD Phenom I/II and Athlon 64 X2 chips support error reporting through module "edac_mce_amd". This module works without ECC and reports cache or other errors related to the CPU.
- Athlon II also works.
- For AM4 Ryzen, APUs only support ECC if they are from "Pro" line.
- ASUS AM3 M4A8xx motherboards officially support ECC but you should not rely on it.
- ASUS AM4 and Ryzen support ECC through RASDaemon but only on up to date BIOS.
- Older ASUS AM4 BIOS report through kernel methods but only uncorrectable errors(UE) are logged in '/sys' nodes.
- All ASRock AM4 boards seem to support ECC mode, with corrected error reporting.
- Gigabyte AM4 B550 boards mention ECC mode support.
- Only ECC Unbuffered RAM is supported. (PC3/4-xxxxxE JEDEC specs)
On the kernel side:
- RAM ECC is supported through "amd64_edac" module.
- CPU error reporting is handled by "edac_mce_amd".
- ASUS M4A87TD/USB3
- ASUS M4A88TD-V EVO/USB3
- ASUS A320M-K
- ASUS EX320M Gaming
- ASUS ROG Strix B450-F
- ASRock A520M Pro4
Testing Methods
ASUS AM3 Motherboards
![]() |
| ASUS M4A88T |
The kernel itself only shows messages with no detail, no matter what kernel parameters are passed to 'mce' boot parameter:
[Hardware error] Machine Check Exception
From testing, these will be corrected errors but I don't know how it will handle uncorrectable errors, as those are harder to reproduce. There is some level of functionality here but it seems the kernel will not be aware of corruption of memory from uncorrectable errors.
The first problem is there is no additional information on what exactly the error is, so the OS will not know if it needs to kill some process to prevent data corruption. There should be additional lines after the [Hardware error] entry but the motherboards is not handling the error further.
Also, the '/sys' nodes for 'mc*' entries in edac module are not be populated with error counts. So you can't really track them over time without custom scripts that monitor the kernel log.
I don't consider ECC to be fully functional on these boards because of this, though some posts seemed to imply ECC was correctly supported.
These boards also don't report any kind of error related to CPU errors. I was first aware of this functionality when a damaged ASRock board started locking up but due to errors reported to the OS. On compatible boards, these show up on the kernel messages in the following format:
[Hardware error] Machine Check Excpetion loggedThese do not get recorded on MCE Log but are specifically handled by the kernel. ('edac_mce_amd' module) This is useful because uncorrected errors can then discard buffers or kill the process with corrupted data.
[Hardware error] ERROR DETAILS
Because of ASUS not enabling this functionality, you may get some data corruption if the PSU or motherboard VRM are damaged. I would not rely on this hardware without regularly testing CPU stability with something like Prime95.
ASRock AM4
I have personally had good success with the A520M Pro 4 motherboard. When using a Zen 3, Ryzen based 5600 CPU, everything seems to work as expected. For instance, corrected errors (CE) are reported correctly:
[ 988.187253] mce: [Hardware Error]: Machine check events logged[ 988.187257] [Hardware Error]: Corrected error, no action required.[ 988.187266] [Hardware Error]: CPU:0 (19:21:2) MC17_STATUS[-|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0x9c2040000000011b[ 988.187282] [Hardware Error]: Error Addr: 0x000000008df651c0[ 988.187287] [Hardware Error]: IPID: 0x0000009600050f00, Syndrome: 0xd29d00080a800c02[ 988.187295] [Hardware Error]: Unified Memory Controller Ext. Error Code: 0[ 988.187307] EDAC MC0: 1 CE on mc#0csrow#2channel#0 (csrow:2 channel:0 page:0x15beca offset:0x2c0 grain:64 syndrome:0x8)[ 988.187315] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD[ 1315.867282] mce: [Hardware Error]: Machine check events logged[ 1315.867287] [Hardware Error]: Corrected error, no action required.[ 1315.867296] [Hardware Error]: CPU:0 (19:21:2) MC17_STATUS[-|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0x9c2040000000011b[ 1315.867311] [Hardware Error]: Error Addr: 0x00000000acee4840[ 1315.867316] [Hardware Error]: IPID: 0x0000009600050f00, Syndrome: 0xd29d00080a800c02[ 1315.867324] [Hardware Error]: Unified Memory Controller Ext. Error Code: 0[ 1315.867335] EDAC MC0: 1 CE on mc#0csrow#2channel#0 (csrow:2 channel:0 page:0x199dc9 offset:0x40 grain:64 syndrome:0x8)[ 1315.867343] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD[ 1643.548321] mce: [Hardware Error]: Machine check events logged[ 1643.548326] [Hardware Error]: Corrected error, no action required.[ 1643.548335] [Hardware Error]: CPU:0 (19:21:2) MC17_STATUS[-|CE|MiscV|AddrV|-|-|SyndV|CECC|-|-|-]: 0x9c2040000000011b[ 1643.548351] [Hardware Error]: Error Addr: 0x00000000e9115f80[ 1643.548356] [Hardware Error]: IPID: 0x0000009600050f00, Syndrome: 0xd29d00080a800c02[ 1643.548364] [Hardware Error]: Unified Memory Controller Ext. Error Code: 0[ 1643.548376] EDAC MC0: 1 CE on mc#0csrow#2channel#0 (csrow:2 channel:0 page:0x21222b offset:0xe80 grain:64 syndrome:0x8)[ 1643.548384] [Hardware Error]: cache level: L3/GEN, tx: GEN, mem-tx: RD
As you can see, both EDAC interface and MCE report the memory errors that were detected during memory scrub.
This is rather important feature that allows you to detect configuration or other RAM problems that may eventually cause uncorrectable errors (UEs).
Looking at the '/sys/devices/system/edac/mc/mc0/*e_count' nodes, will give you a summary of the number of each type of error since system boot.
The motherboard also works fine with both RASDaemon and mcelog software:
- When an hardware reboot is forced by MCE, the kernel logs the error when the system reboots. It is visible with dmesg command (dmesg | grep mce).
- It is also acessible by running mcelog on the terminal, upon which it will be consumed from the error stack.
- Further mcelog executions without runtime errors will return empty.
ASUS AM4
![]() |
| ASUS EX320M Gaming |
CPU related MCE/RAS may require some register tweaking, according to AMD's documentation for these CPUs. I have managed to reproduce CPU crashes by undervolting, with no errors reported in the kernel or RAS Daemon.
Other AM4 Brands
Lexar microSD 633x 128GB Review
- A1 app performance class,
- U3 UHS performance class (30MB/s),
- V30 video performance class.
- Lexar specs for 128GB model is 100MB/s read and 30MB/s writes.
- 32 and 64GB models don't list write speeds above the already rated by V30/U3 class.










.png)

