TechFuel HQ

Beelink EQ14 vs GMKtec G3 Plus: Which N150 Mini PC?

LK Wood IV — Sun, 04 Oct 2026 23:45:00 -0500

For a small host with one wired connection, I would start with the G3 Plus. Buy the EQ14 for two Ethernet ports. Both use the same entry-level processor; the choice comes down to which network version you order, the drives you want to fit and what the complete machine costs. Specifications checked October 4, 2026.

Which one should you buy?

Your requirement	Starting choice	Check before ordering
Two physical wired connections	EQ14	Select the intended gigabit or 2.5GbE version
One 2.5GbE connection and a small host	G3 Plus	Confirm the listing names Intel I226-V
Reuse an M.2 2242 SATA drive	G3 Plus	Match SATA protocol as well as the 2242 length
Install two M.2 2280 drives	EQ14	Confirm the exact unit’s supported drive protocols
A workload that definitely requires 32GB	Compare a higher-capacity platform first	Resolve the system-vendor/CPU-vendor support difference before paying
A basic desktop or small service host	Whichever complete configuration fits for less	Include RAM, SSD, network version and delivered cost

The processor does not break the tie. Both systems use the four-core, four-thread N150; Intel specifies a single memory channel and 6W processor base power. Budget electricity from whole-system power instead. That 6W processor rating excludes the rest of the computer. Intel specifications.

Still choosing a processor class? Start with the broader N150 buying guide or our mini-PC shortlist.

The configuration differences that matter

Specification	Beelink EQ14	GMKtec NucBox G3 Plus
Processor	Intel N150	Intel N150
Memory slot	DDR4 SO-DIMM	One DDR4-3200 SO-DIMM
System vendor’s published maximum	16GB	32GB; Intel specifies 16GB for N150
Wired networking	Two gigabit RTL8111H ports or two 2.5GbE I226-V ports	One 2.5GbE I226-V port
Storage listed by manufacturer	Two M.2 2280 PCIe 3.0 slots; supplied drive is SATA III	One M.2 2280 PCIe slot plus one M.2 2242 SATA slot
Power arrangement	Built-in power supply	External 12V/3A adapter

Sources: Beelink EQ14 configuration/specification page, GMKtec G3 Plus specification table.

Ethernet: decide how many physical ports you need

One connection to your switch? The G3 Plus is my pick. If you want separate physical connections for an upstream network and an isolated test network, the EQ14’s second port gives you a reason to choose it instead.

Get the right EQ14 version. The gigabit model uses RTL8111H controllers; the 2.5GbE model uses I226-V. The product name alone leaves that unresolved. For a router build, map the connections with the OPNsense mini-PC setup guide before ordering.

Storage: match the drive to the slot

The G3 Plus makes this choice straightforward: one 2280 PCIe slot and one 2242 SATA slot. Match both length and protocol. A spare 2242 SATA drive gives you a specific reason to choose this box.

The EQ14 needs a closer look. Beelink lists PCIe-capable slots but says the supplied SSD is SATA, and Notebookcheck’s January 2025 review tested a 512GB SATA configuration. That review identifies the installed drive in its sample; it does not settle which upgrade belongs in the unit on sale today. Ask for the supported drive protocols before buying two 2280 drives for it. Notebookcheck’s tested configuration.

Use the NVMe expansion checker to organize the slot and lane requirements for your planned drives. Enter the exact machine’s specifications.

RAM: budget the guests before buying

Start with the guests you intend to keep. Put their allocations and the host reserve into the Proxmox capacity planner. Our Proxmox hardware guide supplies workload starting points.

If that budget already presses against 16GB, I would price a higher-capacity platform. GMKtec advertises 32GB, while Intel publishes 16GB for the N150; buying around the higher figure means getting an exact supported module and support terms from GMKtec first. There is only one RAM slot in the G3 Plus. You cannot add a second module later. For a workload comfortably inside 16GB, choose on ports and total cost.

Published power tests and what they mean for your bill

Tested computer	Reported idle result	Source and context
Beelink EQ14, N150	8.91W average	Notebookcheck, January 27, 2025; one-minute external-monitor test, 16GB RAM, 512GB SATA and dual gigabit Ethernet configuration
GMKtec G3 Plus, N150	9.3W at the wall	Jeff Geerling’s January 2025 test record; Ubuntu 24.04, replacement SSD; the record also describes cooling changes and a High Performance BIOS profile

These measurements belong to Notebookcheck and Jeff Geerling. Their configurations and test conditions differ, so I would use the figures to budget running costs and choose neither machine on that small idle-power difference.

For budgeting, a hypothetical constant 10W system uses 87.6kWh in a 365-day year. At an example rate of $0.20/kWh, that is $17.52 per year. A constant 15W system costs $26.28 at the same rate. The calculation is watts ÷ 1,000 × 8,760 hours × your electricity rate; active work changes the annual average.

Put your tariff into the Power & Cost Calculator, then compare the annual difference with the purchase difference. A tiny power saving is a poor reason to pay much more upfront. The published mini-PC power references keep each measurement with its tested configuration.

Compare the complete basket

Compare complete machines. A barebone offer still needs memory and storage; a cheaper EQ14 offer may be the other network variant. Copy the selected configurations into this worksheet before comparing totals.

Record from the selected offer	EQ14	G3 Plus
Seller and exact configuration	Fill in	Fill in
Installed RAM capacity and module	Fill in	Fill in
Installed SSD model, capacity and protocol	Fill in	Fill in
Ethernet speed and controller	Fill in	Fill in
Required upgrades and their cost	Fill in	Fill in
Delivered total after tax/shipping	Fill in	Fill in
Seller’s return window and warranty contact	Fill in	Fill in

With the needed ports and capacity covered, buy the lower delivered total. Save the final configuration and planned workloads in Hardware Projects for later upgrades.

Find the exact configuration

These are model searches. Select the configuration from your worksheet on the retailer page.

I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.

Beelink EQ14 N150

Search Amazon Search Newegg

GMKtec NucBox G3 Plus N150

Search Amazon Search Newegg

Sources

WD_BLACK SN850X Review: Choose Capacity Before Game Mode

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The WD_BLACK SN850X is a drive I would shortlist when I need more fast local storage, with capacity and physical fit ahead of Game Mode in the decision. It can be a sensible gaming-library purchase without treating every software setting as a reason to spend more. Compare it with a same-capacity alternative, including any cooling you need, before choosing a retailer.

My SN850X ownership lasted between one and two years. It did not disappoint me. The documented 2TB configuration is the reference for this review, while the independent measurements cited below establish the test conditions and results; my ownership account does not identify the capacity or provide a new benchmark session with my former drive.

The exact version matters

The reference drive is the bare 2TB WDS200T2X0E. Sandisk identifies the SN850X family as PCIe Gen4 with up to four lanes, M.2 2280 and TLC flash. Current capacity-specific ratings are below. Manufacturer datasheet.

Capacity	Rated sequential read/write	Endurance
1TB	7,300 / 6,300 MB/s	600 TBW
2TB	7,300 / 6,600 MB/s	1,200 TBW
4TB	7,300 / 6,600 MB/s	2,400 TBW
8TB	7,200 / 6,600 MB/s	4,800 TBW

Source: Sandisk specification table, checked October 4, 2026. These are rated ceilings, not sustained transfer guarantees.

I would not let the small difference between the headline read ratings decide a capacity purchase. If the larger drive solves a space problem and the smaller one does not, that is the more useful distinction. Start by listing what must remain installed. Then leave room in the budget for the rest of the upgrade, including backup storage if you need it.

Sandisk now lists an optional heatsink version at every capacity. Older review statements limiting the heatsink choice to smaller drives describe the lineup at that time. Current product page.

What the 2TB test tells us

Tom’s Hardware’s original 2TB testing found strong storage performance, with the SN850X improving on the preceding SN850 in its gaming-storage workload. Its sustained-write test also found a large fast cache and relatively consistent behavior afterward. Those results support treating it as a capable working drive, while remaining results from that particular sample and test setup. Original 2TB review.

That is enough for me to consider the SN850X alongside the Samsung 990 PRO. It is not enough to promise that changing drives will fix a particular game’s stutter or transform an editing workflow. First identify what is slow. When the existing drive has adequate room and the complaint is elsewhere in the system, I would keep the storage budget available for the part that needs attention. For a new game-library drive, the case is simpler. You are purchasing capacity anyway. Compare the exact SN850X offer against the alternatives in our SSD tier list, with the required space and installation constraints written down before opening the store pages.

Game Mode should earn its place

Sandisk describes Game Mode 2.0 as a feature of its Windows Dashboard software. The same product page describes drive-health monitoring through Dashboard. Manufacturer feature description.

In Tom’s Hardware’s 2TB test, the difference between Game Mode on and off was within the margin of error in 3DMark storage. Its application test did not show an advantage from forcing the setting on. The reviewer also noted that this was not a test of every intended future workload. Game Mode results and test limits.

I would start with the default configuration. A setting is worth keeping when it helps the task you care about.

To evaluate a mode change, keep the game, save point and background work consistent, then repeat the comparison. Its presence on the box should not carry the buying decision, and one older test should not be stretched into a claim that the setting can never help.

The capacity upgrade must physically fit

The bare 1TB and 2TB drives are listed at 2.38mm high; the bare 4TB and 8TB versions are 3.88mm. Sandisk also lists different heatsink dimensions for those capacity groups. Check the complete assembly against your host’s clearance. Dimension table.

This matters most when a buyer moves from a small drive to a much larger one in a confined machine. I would read the laptop or mini PC service documentation before ordering. A familiar M.2 length alone would not satisfy me. For a desktop with a motherboard M.2 cooler, I would check its instructions before buying a separate heatsink version or attempting to combine the two.

Cooling is also part of the sustained-workload decision. Tom’s Hardware reported that the drive’s temperature entered the throttling range during cache writes without a heatsink or additional airflow. That does not predict the temperature in your case. It does give me a reason to plan cooling for extended transfers. Test conditions and thermal observation.

For PS5, Sony requires effective heat dissipation and sets limits for the full assembly. Follow the console’s installation instructions and the SSD cooler’s directions. I would resolve those fit questions before considering appearance or RGB lighting.

Where I would spend the money

My preference is an SN850X sized for the library or projects I expect to keep, bought from a seller with clear terms. Check Amazon and Newegg for the same capacity and cooling configuration. A bare-drive price and a heatsink-drive price are not the same purchase. Neither is a new unit interchangeable with an open-box listing.

For an existing owner, I would first record health information using the manufacturer’s tools and our SSD health-check guide. Sandisk lists a five-year limited warranty, subject to its endurance limit and terms; that does not eliminate the need for a backup. Manufacturer specifications and warranty footnote.

The SN850X earns consideration through the storage it supplies and the evidence behind its performance. I would buy it when those match the machine and workload. I would keep a healthy 980 PRO or another suitable drive when the proposed change offers little beyond a different name in the system information screen.

Where to buy the WD_BLACK SN850X 2TB: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

WD Red Pro Review: When a Heavier NAS Drive Makes Sense

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

I would choose WD Red Pro for a busy NAS that needs its workload allowance or larger capacities. Its case rests on a 550TB/year workload rating, rotation-vibration sensors and a five-year limited warranty. WD positions it for continuous use in demanding NAS systems. Those are practical reasons to consider it; a lightly used home file server deserves a look at Red Plus first. WD Red Pro product information

I have owned Red Pro drives for between one and two years. The exact 16TB and 24TB examples here come from published documentation, with independent test results attributed to their reviewer.

Pick a capacity before picking the badge

Check the suffix.

The WD161KFGX is a useful 16TB reference point; at 24TB, distinguish WD240KFGX from WD241KFGX because WD’s current linked data sheet lists both and gives them different power figures. Every example below is a 3.5-inch SATA CMR drive running at 7,200RPM with 512MB cache. WD Red Pro data sheet

Exact model	Capacity	Rated transfer, up to	Read/write power	Idle power	OptiNAND in data sheet
WD161KFGX	16TB	259MB/s	6.1W	3.6W	No
WD240KFGX	24TB	287MB/s	6.4W	3.9W	Yes
WD241KFGX	24TB	287MB/s	6.0W	3.6W	Yes

These are WD’s specifications. Match any independent test to its exact model.

The 16TB documentation contains a conflict. Its live product page lists OptiNAND and ArmorCache among the technologies, while the capacity-specific PDF marks OptiNAND “No” for WD161KFGX, so I would purchase that model for its storage, workload and warranty characteristics without requiring those flash-related features. If they matter to your design, get the exact revision confirmed first. WD product page, WD model table

Price the whole array. I would compare layouts in the NAS capacity calculator, price the drives needed for my chosen redundancy, and budget a backup destination before committing to any one capacity. Include the backup in that budget.

What the 24TB test shows

TechRadar’s October 2024 review tested WD240KFGX, recording 287MB/s read and 283MB/s write in CrystalDiskMark, plus 270MB/s read and 268MB/s write in AJA, while also describing its operating noise as intrusive for an office. TechRadar’s original WD240KFGX review

It did not test WD241KFGX. Use those figures for WD240KFGX only.

I would take two buying lessons from those results. First, they support treating this model as a bulk-storage drive with credible sequential performance. Second, I would plan enclosure placement before filling a desk-side NAS with it. Neither point requires pretending that one benchmark predicts every file server.

Where will the NAS live? For a machine beside my chair, I would give the reviewer’s noise observation considerable weight; if the array could live elsewhere, capacity and serviceability would move higher on my list. Decide that before ordering several drives.

The six-bay NAS planning guide covers the wider array decision. I would use that before ordering a full set, especially when the new disks also change how you intend to back up and restore the system.

What 550TB/year does and does not mean

An HDD workload rating includes data read as well as data written. WD’s white paper explains that this is a population-level reliability measure, distinct from SSD write endurance. Crossing a figure is not a prediction that one specific disk is about to fail. WD workload white paper

That makes a workload inventory more useful than counting power-on hours alone. Include routine backups and large reads when evaluating your own server. I would choose Red Pro when that work calls for the higher rating, rather than paying for it solely because a NAS stays switched on.

WD’s comparison gives Red Plus a 180TB/year rating and three-year warranty. Red Pro raises those to 550TB/year and five years. Those differences are meaningful purchasing terms, but they do not establish that your particular Pro will survive longer than your particular Plus. WD’s family comparison

For a modest household library, I would start with the Red Plus review. For larger capacity requirements or a consistently busy array, Pro becomes the more natural candidate. Match the drive to the job.

Buy the coverage you expect

A five-year headline is useful only when the actual drive carries the expected coverage. WD’s support documentation distinguishes retail warranty support from OEM drives whose support belongs with the original system maker. Check the serial’s warranty status and retain proof of purchase. WD OEM and retail policy

On Amazon and Newegg, compare the same model and condition, including who is selling it. I would treat a recertified offer as a separate purchase decision. A discount must be large enough to justify whatever warranty and return terms that listing actually supplies.

Check the label on arrival. Match it to the order and consult the enclosure’s compatibility guidance before moving data; Synology’s compatibility list is one example of the manufacturer check to make. Run the supported diagnostics and keep the results. Test the backup before retiring the previous copy.

Where I would spend the money

Red Pro belongs on the shortlist when capacity or workload makes the purchase useful. I would compare the exact offer with the other NAS families in our hard-drive buying guide, keeping the selected model’s condition and warranty consistent.

For a new array, buy enough usable space with a workable backup plan. If an existing array is doing its job, I would keep the drives and spend on a missing backup first. Buy Pro when it solves the storage problem.

Where to buy the WD Red Pro: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

WD Red Plus Review: The Right Model for a Home NAS

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The WD Red Plus is my starting point for a home NAS holding backups, photos and a media library. I would favor the 8TB WD80EFPX when its capacity fits and the competing offers have equivalent warranty coverage. Move to Red Pro when your workload or capacity plan calls for it; being switched on all day is already part of the Plus brief. WD rates the family for continuous operation, with a three-year limited warranty. WD product information

I have owned Red Plus drives for between one and two years. This is a family review: the exact capacities below are researched examples, and the cited benchmarks identify the drive someone else tested.

Buy the model that fits the room

Capacity alone leaves out too much. WD’s September 2025 data sheet lists two 8TB drives and two 12TB drives with meaningful differences. These are manufacturer specifications, including maximum internal transfer rates, rather than measured file-copy speeds from my NAS. WD Red Plus data sheet

Model	Capacity	Cache	Rated transfer, up to	Idle power	Idle / seek acoustics
WD80EFPX	8TB	256MB	215MB/s	3.4W	24 / 28dBA
WD80EFZZ	8TB	128MB	185MB/s	4.1W	25 / 30dBA
WD120EFBX	12TB	256MB	196MB/s	2.9W	20 / 29dBA
WD120EFGX	12TB	512MB	260MB/s	6.1W	34 / 39dBA

At the same total price and coverage, I would choose WD80EFPX over WD80EFZZ because its published specifications give me the better case, though I would set a firm limit on the premium.

Keep a functioning EFZZ. A different suffix alone wouldn’t make me replace it.

The 12TB choice needs more thought. The EFBX is helium-filled; the EFGX uses air. Their acoustic and idle-power figures differ substantially in WD’s table, so moving from one to the other deserves a fresh check if the NAS sits beside your desk. A family name cannot promise a quiet room. WD capacity-specific specifications

Start with usable capacity. The NAS capacity calculator lets you compare layouts and save the drive plan; once that is settled, pick a place for the enclosure before paying for more disks. If it must share a bedroom, I would prioritize the relevant acoustic specification over a higher advertised transfer number.

What the performance evidence tells us

In its June 2026 review, TechRadar tested the 4TB WD40EFPX on a PC, recording AJA results of 187MB/s read and 179MB/s write after an earlier NAS test had produced a cache-influenced result that prompted the change in method. TechRadar’s original test

That is a 4TB result. Use it for that model.

I would buy Red Plus for bulk storage, then evaluate the complete NAS around the actual job. A backup finishing before morning and a library that plays correctly are useful targets. An impressive short copy graph is less useful if your real transfer slows after the first burst.

Before upgrading a working drive, time the task you want to improve. Keep the files and destination the same. Record whether you are reading from the NAS or writing to it, whether another job is running, and what would count as an improvement worth paying for. That is your baseline.

For a new build, our budget NAS guide covers the rest of the machine. I would settle the storage layout before choosing a drive purely for its benchmark position.

Understand the workload rating

WD specifies 180TB/year for Red Plus and lists CMR recording for these models. The rating concerns traffic through the drive. WD’s workload white paper explains that HDD workload includes reads and writes, unlike an SSD’s written-data endurance specification. It is not a countdown to a particular disk failing. WD specifications, WD workload explanation

Count the work you schedule as well as the files you add. I would include full-drive verification jobs when estimating a busy NAS, and leave room for growing backup sets. If the workload is consistently demanding, use the Red Pro review to assess the next tier. Don’t buy a more expensive badge merely because the NAS runs overnight.

Warranty and arrival checks

Compare the actual seller and coverage on Amazon and Newegg. A model name in the listing is only the beginning. WD distinguishes retail drives with its warranty from OEM drives supported through the original system maker, and directs buyers to check warranty status. WD’s OEM and retail support policy

Keep the invoice. I would photograph the label on arrival, match it to the ordered model, check the serial’s coverage, and run the NAS’s supported drive diagnostics before entrusting it with the only copy of anything. Use the enclosure maker’s compatibility list; Synology provides one here.

For power planning, feed the relevant model’s figures into our power-cost calculator as estimates. Add the enclosure separately. Once the system is running, replace estimates with a wall measurement; drive-only figures cannot represent the whole box.

My recommendation

Buy the WD80EFPX if 8TB suits your plan, its listing has the coverage you want, and its delivered price is competitive. Choose a larger model when it solves a real capacity constraint, after checking that model’s power and acoustic figures. I would keep a functioning Red Plus rather than replace it just to move up a tier.

Compare other families in the NAS hard-drive guide if the exact offer is poor. Red Plus earns its place through a suitable specification and a sensible purchase. Buy the version that fits.

Where to buy the WD Red Plus: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Thermalright Phantom Spirit 120 SE Review: Check the Fit

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The Phantom Spirit 120 SE would be on my shortlist for a new desktop that needs substantial air cooling without a large cooler budget. Exact-model tests support that choice. Its main buying complication is physical: confirm the space above your memory before counting on the advertised height.

I would compare the SE’s delivered total with the Peerless Assassin 120 SE on the same day. If they cost about the same and both fit, my preference is the Phantom Spirit SE. That is my buying judgment.

Keep a working Peerless Assassin if it meets your needs. A replacement should solve something.

The configuration this review covers

This is the non-RGB Phantom Spirit 120 SE. Thermalright publishes the following SE specification.

Item	Published specification
Heatsink dimensions	110 × 125 × 154 mm
Heatpipes	Seven, 6 mm diameter
Listed fan	TL-C12B V2, 120 × 120 × 25 mm
Fan control and maximum speed	4-pin PWM; 1,500 RPM, ±10%
AMD mounting support	AM4 and AM5
Intel mounting support	LGA115x, LGA1200, LGA1700 and LGA1851

The Phantom Spirit 120 EVO is a different configuration: Thermalright specifies a 157 mm heatsink and TL-K12 fans rated up to 2,150 RPM. Keep the test variants separate. The taller heatsink alone can change a marginal fit decision.

I would also verify the included mounting parts on older stock. Current socket support on a website does not tell you which revision a third-party seller has boxed. Save the receipt.

Evidence from an actual SE test

Hardware-Helden’s original review tested an i5-13600K at about 181 W in Prime95, reporting 70.9°C with noise matched to 40 dB(A) at 30 cm and temperatures normalized to a 20°C room. Its testing covered LGA1700. That gives the recommendation a defined workload, but I would not transfer the reading to a different processor, different enclosure, or AM5 build merely because the same cooler can mount there.

Compare within that test method. A 40 dB(A) figure from another review can use a different microphone distance, background noise, and enclosure. Mixing those readings would create a precision the evidence does not have.

For a quiet gaming build, I would pay more attention to the sound level that accompanies a sufficient temperature than to the lowest temperature reached with every fan at maximum. For a sustained rendering machine, I would inspect the long-load results and processor power settings first. Those are different priorities.

Why 154 mm may not be your installed height

Hardware-Helden had to raise the front fan slightly over its Corsair Vengeance kit. That observation applies to its particular assembly.

My order of checks would be case allowance, exact memory height, then the fan’s final position. Reject a purchase plan that depends on the fan sitting lower than the RAM allows. Choosing a smaller cooler can be cheaper than discovering after assembly that a side panel will not close. Keep service access in mind, too. Plan how you will reach the memory latches and cooler screws before doing the final cable routing, especially when the build is crowded and removing the cooler again would mean undoing work around components that could have been positioned more conveniently at the start.

The PC Builder can keep the processor and board choice together. It does not validate this cooler’s physical fit. Use the component makers’ dimensions for that decision.

Mounting and noise after installation

The SE test sample included a plastic Intel backplate and fan splitter, but no screwdriver. AMD installation retained the board’s backplate. Follow the supplied instructions. The manufacturer page links the SE manual.

Check the kit before dismantling a working PC. Have the tools ready. Used listings deserve particular attention here; buying an incomplete cooler and then hunting for the right spacers is a poor trade for a small saving.

After assembly, establish a baseline with the stock configuration. Record the workload, room conditions, fan settings, and observed temperature before changing several settings at once. Our CPU temperature guide provides a starting point. If a fan is absent from monitoring or temperatures jump immediately, use the overheating checklist to investigate the installation.

I would tune for the machine’s actual workload. A result that looks impressive in a screenshot can still be an annoying desktop if the fan curve keeps reacting to brief temperature changes. Listen where you sit, then retest the workload that matters.

Alternatives worth comparing

The PA120 SE remains the obvious nearby offer. Its published heatsink specification lists six heatpipes and a 155 mm height. The extra pipe in the Phantom Spirit does not settle every comparison, and neither cooler has a permanently guaranteed value advantage. Include shipping, seller, and returns in the total.

I would consider the NH-D15 G2 for a buyer who specifically values its documented compatibility and support package. For a build that needs a liquid-cooling alternative, inspect the Liquid Freezer III 360 and the space it requires before committing to either layout.

For the SE, write down the case allowance and RAM height before opening the shopping tabs. Those two details decide whether its compact heatsink specification is useful in your machine.

Sources

Where to buy the Thermalright Phantom Spirit 120 SE: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Thermalright Peerless Assassin 120 SE Review: Worth It?

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The Peerless Assassin 120 SE is worth considering when you want a capable tower cooler and would rather spend the rest of the build budget elsewhere. My buying condition is straightforward: the exact version must fit, and its delivered price must make sense beside the Phantom Spirit 120 SE. A famous model name does not excuse a poor offer.

I would keep an existing PA120 SE that meets the machine’s temperature and noise targets. Replacing a working cooler for a neighboring model is a different decision from choosing between them for a new build.

Name the problem before spending. A replacement needs a job.

This assessment draws its performance evidence from the independent tests linked below. Their measurements belong to their test systems; they are not temperatures recorded on a TechFuelHQ rig.

Identify the SE you are buying

Thermalright’s current PA120 SE page specifies the following. Dimensions labeled heatsink exclude the extra space occupied by a front fan.

Item	Published specification
Heatsink	125 × 110 × 155 mm
Heatpipes	Six, 6 mm diameter
Listed fan	TL-C12C, 120 × 120 × 25 mm, 4-pin PWM
Listed maximum fan speed	1,550 RPM, ±10%
AMD sockets	AM4, AM5
Intel sockets	LGA115x, LGA1200, LGA1700, LGA1851

There is a revision wrinkle. PC Gamer explicitly bought an SE V2 carrying TL-C12C-X28 V2 fans, whereas the manufacturer page lists TL-C12C fans; a listing that omits the revision therefore leaves a detail unresolved even when the heatsink name appears to match the recommendation you started with. Keep those configurations separate.

Check the complete kit. For older inventory, ask the seller to confirm the mounting parts. I would save the product description with the receipt, especially if several variants share one retailer page.

What the original tests establish

Tom’s Hardware tested the SE with a Core i9-12900K, MSI Z690-A Pro DDR4 motherboard, and be quiet! Silent Base 802 case. Its results page reports a 61°C rise over room temperature during the 200 W Cinebench run. The cooler also passed that workload at half fan speed, although the reviewer described it as hot. It did not pass the unrestricted Cinebench test, which demanded a little over 230 W in that setup.

That boundary is more useful than a blanket claim that the PA120 SE cools any processor. The result supports considering it for a build with controlled power and suitable airflow, but it does not promise the same temperature on a different CPU or make the cooler a replacement for every large liquid unit. I would keep the workload beside the number when comparing reviews. Match the workload.

Read the unit carefully. A temperature above ambient is not an absolute CPU reading.

RAM can change the case requirement

The headline 155 mm height is only the starting point. Thermalright itself warns buyers to allow for tall memory. The front fan and RAM occupy overlapping space in the normal arrangement; raising that fan to clear a module also raises the installed assembly.

My fit check starts with the case’s documented cooler allowance and the memory kit’s actual module height, then takes in the cooler drawing and motherboard layout so that the planned fan position accounts for the parts already purchased instead of assuming that every nominally compatible component fits together. Leave some room. The side panel must close freely.

For a new build, I would choose unobtrusive memory heatspreaders unless taller modules offer something the build needs. For an upgrade, the RAM is already purchased, so preserving it can outweigh a small difference between cooler prices. Measure first.

Our PC Builder helps compare the rest of the system, but it does not certify cooler mounting or physical clearance. Keep the case and cooler documentation open alongside the parts list.

Installation and everyday ownership

PC Gamer’s V2 installation account describes an Intel backplate, spacers, mounting bars, and spring-loaded cooler screws. It also explicitly declines to judge long-term fan lifespan from its short test. That is the right limit to retain here: an inexpensive fan is not evidence of early failure, and a review sample is not a reliability survey. I would assemble around access. Confirm that the screwdriver can reach the mounting screws before crowding the socket with other parts, and follow the instructions supplied with the exact revision.

Check fan detection after installation. Establish temperature behavior before settling on a quieter curve. If the readings are wrong, work through our CPU overheating checks before ordering another cooler.

Keep the unused mounting pieces with the receipt. A future motherboard change is easier to assess when the complete kit is available, and a missing bracket can erase the savings from a used purchase.

When I would choose another cooler

For a new order, compare the Phantom Spirit SE’s offer and fit directly. Its manufacturer specification lists seven heatpipes and a 154 mm heatsink. That is a reason to examine it, not a mathematical guarantee of better cooling. I would not pay extra for the older name merely because an old review quoted a low launch price.

I would consider the NH-D15 G2 when its documented support and mounting options matter enough to justify the quoted premium. A buyer who needs sustained high-load cooling should also compare a compatible Liquid Freezer III 360. Neither choice removes the need to check the exact case.

For the PA120 SE itself, the last check is the box specification: SE or SE V2, the included fans, and mounting parts for your socket. Match those details before comparing the two retailer totals.

Sources

Where to buy the Thermalright Peerless Assassin 120 SE: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Seagate IronWolf Review: Choose the Right 8TB Model

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The standard Seagate IronWolf is worth considering for a home NAS when its capacity, workload rating, and warranty cover what you need. My recommendation is to choose the exact model before comparing offers. At 8TB, that changes the decision: Seagate lists both a 7,200 RPM ST8000VN004 and a 5,400 RPM ST8000VN002, with different power and acoustic specifications in the same datasheet.

I have owned IronWolf-family drives for between one and two years, with no particular disappointment to report. The ownership note is family-level. The model comparison below comes from Seagate’s documentation, rather than measurements of my drives.

The two 8TB models are different purchases

Both variants use conventional magnetic recording, or CMR. Seagate specifies them for one-to-eight-bay systems with a 180TB/year workload rating and a three-year limited warranty. Those are the shared characteristics; the table shows the differences that matter in a continuously running box.

Seagate specification	ST8000VN004	ST8000VN002
Capacity	8TB	8TB
Interface	SATA 6Gb/s	SATA 6Gb/s
Spindle speed	7,200 RPM	5,400 RPM
Maximum sustained transfer, outer diameter	210MB/s	202MB/s
Average operating power	10.1W	5.3W
Average idle power	7.8W	4.0W
Typical idle/seek acoustics	28/32dBA	25/26dBA

Source: Seagate IronWolf datasheet, page 2. These are manufacturer specifications, not sound measurements from a complete NAS.

For a new home-server build, I would start with the VN002 because, when the server spends much of its time waiting for the next backup or file request, I would give its lower specified power draw more weight than the VN004’s small advantage in maximum sequential transfer rate. Application performance still needs its own assessment.

An existing array deserves a different approach. If you are replacing a failed VN004, establish what your NAS supports before choosing another variant solely to save power. Keep the model number in your notes and on the order. “IronWolf 8TB” leaves too much room for confusion.

What a home NAS asks of it

My preferred role for the standard IronWolf is shared files, backup destinations, and a media library with a defined capacity plan.

Before moving up a tier, write down what the storage has to do: how much space you need now, how you will recover lost files, and whether the same disks also carry busy applications. The NAS capacity calculator makes the space decision easier. Model your intended layout before buying enough drives to fill every slot. A lower price per drive can still be the wrong purchase if you exhaust the enclosure’s bays too early. Leave expansion room where the budget allows it.

Workload needs similar care. Seagate’s annualized workload definition counts both reads and writes, scaled by powered-on hours. The 180TB/year figure is therefore not 180TB of new files you can write annually, and it is not an SSD-style lifetime TBW allowance. Repeatedly reading the same files contributes to host traffic too.

Measure a busy system first.

A household photo archive and a shared production workspace may hold similar amounts of data while moving very different amounts through their disks, so I would check the traffic before assuming that the standard tier covers a system whose capacity requirements happen to look modest. Capacity alone cannot settle that question.

Power matters more when you buy several

Use the manufacturer’s figures as planning inputs, then replace them with measurements from the finished machine. Enter both configurations in our power-cost calculator to compare their estimated running costs.

Here is a narrow example. The specified idle-power difference between the two 8TB models is 3.8W. Four drives would therefore differ by 15.2W at those stated idle values, equivalent to about 133kWh over a continuously powered year. That is calculated as 3.8 × 4 × 8,760 ÷ 1,000. It excludes the enclosure, power-supply losses, active periods, and sleep behavior. Multiply a decision across several bays and the trade-off changes; I would not choose the faster spindle automatically.

TechRadar’s May 2026 review also favors examining the lower-speed variant and larger-capacity alternatives. Its price discussion is a dated snapshot, so it cannot establish today’s best offer. For the power comparison here, I use Seagate’s separately labeled operating and idle rows; those categories should not be mixed.

Health monitoring and the first week

IronWolf Health Management requires a support check. Seagate’s datasheet makes availability dependent on the NAS vendor, so confirm your enclosure and software combination before assigning value to the feature.

My arrival routine would be simple: match the label to the order, retain the invoice, confirm the capacity the system reports, and run the enclosure’s appropriate drive checks before copying the only copy of anything important. Record the results. Repeat checks later against that starting point instead of relying on memory. The VN004 manual includes installation, temperature, and diagnostic guidance for that exact model. Use the matching manual if you buy another variant. A family-level review cannot replace the instructions for the hardware in your tray.

Warranty and alternatives

Compare seller, condition, and warranty provider alongside the model number. Seagate’s channel warranty restricts eligibility by purchasing channel and region; its hardware coverage also excludes lost data. A seller warranty and direct Seagate coverage are different things.

I would choose IronWolf Pro when the documented workload or support package justifies moving up. For a broader comparison with WD Red Plus and enterprise options, use the NAS drive guide, then bring the selected model into the NAS capacity and power plan.

The standard IronWolf’s case is strongest when it satisfies a specific plan without paying for features you will not use. Check both Amazon and Newegg against that same model and condition. The cheaper offer only wins after those details match.

Where to buy the Seagate IronWolf: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Seagate IronWolf Pro Review: The 22TB NAS Decision

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The IronWolf Pro 22TB belongs on the shortlist when a NAS needs more capacity per bay, a heavier workload allowance, and a documented recovery-service package, especially if upgrading its disks would postpone replacing an otherwise suitable enclosure whose bays you have already filled. Its benefits need a job to do. A lightly used home NAS may need less.

This review focuses on ST22000NT001, the 22TB SATA model. I have owned IronWolf Pro-family drives for between one and two years and have no particular disappointment to report. That experience does not identify the capacity of my drives; the model-specific evidence below comes from Seagate and named independent testing.

What the 22TB model provides

Specification	ST22000NT001
Capacity and interface	22TB; SATA 6Gb/s
Recording and enclosure	CMR; helium-filled
Spindle and cache	7,200 RPM; 512MB
Maximum sustained outer-diameter transfer	285MB/s
Workload tier	550TB/year in the datasheet
Drive-bay rating	Unlimited in the datasheet
Limited warranty	Five years, subject to eligibility
Included Rescue service	Three years, subject to terms and country availability

Source: Seagate’s model-specific datasheet table, page 2. “Unlimited” describes the drive’s bay rating; it does not certify every enclosure or configuration.

Keep that model number attached to every comparison. An IronWolf Pro listing at another capacity, or with another suffix, requires its own specifications. The brand name is not enough to match a benchmark or warranty claim.

Transfer tests support bulk storage

Hardwareluxx tested this exact model in June 2023. Its CrystalDiskMark 6.0.2 results report 287MB/s reads and 287.1MB/s writes. That supports Seagate’s maximum sequential-transfer rating under that test; it is not a promise of the same speed across a network or during every part of a large copy.

That is credible bulk-transfer evidence. I would use it to assess large-file storage, while leaving application responsiveness under competing client loads as a separate question.

For a new build, decide where active applications belong before picking the disks. My preference is to separate the capacity decision from the application-storage decision. Use the NAS drives for the jobs that need their space, then assess the rest of the system against its actual workload. The NAS capacity calculator helps establish whether 22TB per bay solves a real constraint. Run your intended redundancy layout and leave room for growth. If the resulting usable space greatly exceeds your foreseeable needs, compare a smaller supported drive before committing to the larger purchase.

The useful acoustic evidence

The most interesting independent finding is sound. In Hardwareluxx’s acoustic test, the 22TB sample was too quiet at idle for the reviewer’s equipment to distinguish a lower result; its chart shows 20dBA. The reviewer also judged that sample quiet under random-access reading.

That is encouraging. It is still one drive, in one setup. Hardwareluxx explicitly changed its measurement method and warned that the results were incompatible with its older acoustic tests. I would not build a cross-review noise ranking from those numbers.

I would consider it for a desk-side NAS.

Preserve the option to return it if the assembled system’s sound is unacceptable, and decide where the enclosure will sit before filling its bays, because moving a completed build into an inaccessible cupboard with poor ventilation would leave you solving a different problem. Choose the location first.

Workload and power need separate budgets

Seagate’s workload definition includes host reads and writes, annualized by powered-on hours. The product manual expresses this model’s maximum rate as less than 550TB/year. I would leave margin below that limit, especially where several jobs share the pool, rather than treating it as a lifetime write-endurance allowance.

The ST22000NT001 manual also specifies a typical peak startup current of 2A on the 12V supply. Startup deserves attention in a DIY enclosure: choose the power supply and drive-power distribution for the whole populated system.

There is an independent check on that concern. Hardwareluxx measured 29.38W during startup on its sample, capturing the drive’s supply rails. That is a startup result, not average running consumption. Do not use it as the constant input for an electricity-cost estimate.

Our NAS capacity and power project keeps the space and power assumptions together. Revisit both when you add disks; the original plan for an almost-empty chassis may no longer describe the finished machine.

Rescue is useful, but keep a recovery plan

The included Rescue service is worth considering alongside the hardware warranty, provided you understand its eligibility requirements and the assessment described in Seagate’s product manual, which determines whether recovery is possible and how the drive should be handled after a claim. Recovery is not guaranteed.

Keep your backup plan.

I would rather budget for a separate recoverable copy than spend the entire storage budget on a more expensive primary array and hope a recovery service will rescue it later. Before adding a replacement disk, work through the enclosure’s supported process and read our six-bay NAS rebuild guide. Save the model, serial number, purchase receipt, and initial health-check results somewhere outside that array.

When I would buy it

I would buy the 22TB IronWolf Pro when its space per bay and workload tier solve a documented need, the enclosure supports it, and the seller can explain the warranty. I would compare standard IronWolf or WD Red Plus first for a modest home NAS. The NAS drive guide covers those alternatives.

At Amazon and Newegg, match ST22000NT001, condition, and seller before comparing the totals. Seagate’s channel policy makes purchasing channel and region relevant to coverage. A five-year claim on a marketplace page deserves a clear answer about who supplies it.

For the right NAS, the Pro’s package is persuasive. Buy that package deliberately, with the capacity and recovery plan already worked out.

Where to buy the Seagate IronWolf Pro: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Seagate Exos X20 Review: 20TB SATA for a Home Server

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The Seagate Exos X20 20TB is worth considering for bulk storage in a home server once you have checked the exact model and seller’s support terms, established that the enclosure supports it, and decided how much usable space your chosen layout will leave. Its published performance is credible. The purchase details matter just as much.

This review covers the standard SATA ST20000NM007D. I have owned Exos-family drives for between one and two years without a particular disappointment. The X20 variant is the documented example researched here, rather than an exact model identified from my ownership history.

Start with the suffix, not the capacity

Seagate’s X20 datasheet lists multiple 20TB products:

Model	Interface	Variant
ST20000NM007D	SATA 6Gb/s	Standard model covered here
ST20000NM000D	SATA 6Gb/s	Self-encrypting model
ST20000NM002D	SAS 12Gb/s	Standard SAS model

The reviewed SATA version is a helium-filled CMR drive with a 7,200 RPM spindle, 256MB cache, and a maximum sustained outer-diameter transfer rating of 285MB/s. The datasheet lists a five-year limited warranty. These specifications describe the product, not automatic warranty eligibility for every resale listing.

For a machine with ordinary SATA ports, order the SATA variant. Seagate’s SAS installation guide explicitly says a SAS drive will not work on a SATA controller. A similar-looking listing at the same capacity is not an interchangeable purchase. I would put the full model number in the build notes and compare both Amazon and Newegg against it. Reject ambiguous listings before spending time deciding whether their price is attractive.

What the independent tests establish

KitGuru tested ST20000NM007D and recorded 293MB/s sequential reads and 289MB/s writes in its default CrystalDiskMark sequential test at QD32 T1. Those are the reviewer’s results from that benchmark. They support the drive’s bulk-transfer capability without predicting an entire server’s performance.

The array results tell a different story. StorageReview tested eight X20 20TB drives in RAID 6 in a QNAP TS-1685, comparing them with eight IronWolf Pro 20TB drives. The X20 trailed that IronWolf Pro set in the published mixed-workload tests. The reviewer reported Seagate’s explanation that the families used different firmware optimizations.

That comparison changes how I would shop.

A strong sequential result from one disk cannot establish whether an Exos array will outperform IronWolf Pro in your NAS, particularly when you are comparing a different enclosure or workload with a published result that used specific 20TB models and their firmware from 2022. Compare the complete offer against the intended job.

For a server storing media, backups, and large project files, I would keep the X20 on the shortlist. For application storage dominated by small competing requests, I would assess the complete storage design before choosing it. The disk is only part of that decision.

Check sector format before adding it to a pool

The SATA product manual documents 512e and 4Kn logical-sector formats, with 512e as the factory shipping default. It also describes FastFormat conversion between them.

Check what a used drive reports. Before creating the pool, confirm its sector format against your controller and storage plan; if the existing format is suitable, leave it alone instead of changing a setting simply because the manual describes how to do so.

Seagate also advises validating full-capacity support with the HBA or RAID-controller manufacturer. That is especially relevant when reusing older server hardware. Work through the exact controller, enclosure, and operating-system combination; a matching cable is only the first check.

Our NAS capacity calculator can then model the usable space in your intended layout. Set aside capacity for redundancy and future growth. Do the layout first.

Workload ratings do not promise a lifespan

The X20 manual specifies an annualized workload below 550TB/year. It describes MTBF as a statistic for a population of drives, which cannot predict an individual unit’s lifespan. I would use those limits to assess suitability and still keep separate copies of important files.

The same manual notes that internal activity can increase sound and power consumption even during periods that appear idle. That makes an absolute promise of quiet operation inappropriate. For a living-room or bedside server, I would prioritize the enclosure’s location and an acceptable return policy before deciding on this model. Read the enterprise-drive noise and recertified-drive guide for the broader home-server trade-off. Plan ventilation and drive mounting as part of the build. Do not assume that the most attractive capacity-per-dollar figure will produce the machine you want to sit beside.

The seller can change the value of the deal

Record the offered condition and warranty provider. I would spend the most attention here because a purchase described as new, a used server pull, and a recertified offer can have very different support arrangements that the product-family specification will not resolve for you. Ask for the exact terms.

Seagate’s OEM guidance says the original equipment manufacturer holds the warranty responsibility for drives sold through that route. Its separate channel warranty restricts coverage by purchasing channel and region. Do not transfer the new-drive five-year specification to an OEM pull or recertified offer without verifying the particular coverage.

On arrival, match the physical label to the order and save the receipt. Check the reported identity and run appropriate diagnostics before committing the drive to your storage plan. Retain the initial results, and keep a recoverable copy of important data elsewhere.

My buying recommendation

The SATA X20 is a reasonable choice for a builder who wants dense bulk storage and is willing to check the details. I would compare the complete offer with IronWolf Pro, including warranty provider and condition, then choose the one that better fits the planned system. The NAS drive guide puts those options together.

Before ordering, save the chosen model in the NAS capacity and power plan. That gives the purchase a purpose: a known amount of usable storage, in a compatible machine, with a recovery path you have already considered.

Where to buy the Seagate Exos X20: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Sapphire Pulse RX 9070 XT Review: Fit and Fan Tradeoffs

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The Sapphire Pulse RX 9070 XT makes sense when you want a straightforward Radeon card and would rather spend your budget elsewhere in the build than on cosmetic extras. I would shortlist it when its delivered price is meaningfully below the premium models. At a similar price, I would compare their cooling behavior and features before choosing the Pulse.

The main reservation is specific: published tests disagree about how reassuring its quiet cooler really is. That deserves more attention than the advertised boost clock. This review evaluates the retail 11348-03-20G using Sapphire’s documentation and the independent tests cited below; it adds no new TechFuelHQ lab measurements.

The version and fit to check

Sapphire’s specification identifies the retail card as follows:

Item	Manufacturer specification	Why I would check it
Memory	16GB GDDR6, 256-bit bus	Compare your games or applications, not memory capacity alone
Dimensions	320 × 120.25 × 61.6mm	Measure the installed case configuration
Form factor	Three slots	Check adjacent expansion cards and intake space
Board power	304W typical	Include the rest of the system in power planning
Power connection	Two eight-pin PCIe connectors	Confirm suitable PSU cables before ordering
PSU recommendation	Minimum 750W	Treat this as guidance for system planning

The manufacturer also lists a support bracket. Plan where it will sit. A nominally compatible case can still become an awkward installation when a front radiator, drive cage, lower expansion card or stiff cable occupies the same space. I would measure those obstructions before treating the case’s advertised maximum GPU length as a complete answer.

Use our PSU wattage calculator to organize the rest of the build, then check the PSU maker’s instructions. Replacing an otherwise suitable power supply merely because a retailer bundles one with the card would not be my default purchase.

Why the cooling reviews need context

PC Perspective’s April 2025 test was encouraging. In its 20-run 3DMark Speed Way stress test, the GPU core stayed at or below 50°C and the hotspot reached 72°C, with the room around 18°C. Its reviewer could not hear the card over the test system’s liquid cooler.

Those are that test’s results. A cool room and another audible fan source matter when interpreting the conclusion. They do not establish how this card will sound beside your desk on a warm evening.

GamersNexus’s dedicated teardown and thermal investigation reached a more qualified verdict. It liked the access to the fans and the assembly approach, but criticized the tested fan-control behavior as memory temperatures rose despite otherwise acceptable core temperatures.

I would read those findings together. The Pulse can be appealing to someone who dislikes fan noise, yet a quiet first impression is not enough reason to stop monitoring the card. Check memory and hotspot behavior as well as the core reading during your own demanding workloads. A fan curve is a choice about competing priorities; the lowest audible speed is not automatically the best choice.

Our RX 9070 XT undervolting guide explains a separate tuning process. Establish a stable baseline before changing it. Do not copy another person’s voltage settings and assume a successful benchmark also proves stability across every game you use.

What a premium model buys

TechSpot’s fourteen-card RX 9070 XT comparison describes the Pulse as a relatively plain model without lighting or dual BIOS. Across the particular games in that comparison, the spread between the fastest and slowest cards was modest: four percent in Black Ops 6 and six percent in the other two reported tests.

I would not pay a large premium for the clock alone. Those margins describe the tested games; the review’s historical prices also need a fresh comparison before buying.

What would the premium fix? A card that fits your case better, offers the physical alternate BIOS you want, or performs better in a comparable noise-normalized test has a clearer upgrade case than an ornate shroud. I would name that benefit before paying for it.

The GPU hierarchy addresses the broader GPU-tier decision. Use it before spending time choosing between two versions of a tier that may not suit your monitor, games or budget.

Quiet fans do not settle coil whine

Fan acoustics and electrical noise should be separate questions. The published tests above cannot promise that every unit will have the same sound in another system. Our coil-whine database collects reader observations; use its sample information and limitations instead of treating a small set of reports as a model-wide defect rate.

Read the return terms. If unusual noise would make this card unsuitable for your room, the seller’s return window and any conditions on opened hardware belong in the comparison alongside the delivered price, even when two listings appear to offer the same Sapphire box.

Check the condition too. New, used, refurbished and OEM packages are different offers. Confirm the model identifier and included accessories instead of relying on a familiar product photograph.

Who should choose the Pulse?

I would keep it on the shortlist for a conventional gaming build with enough physical room, a suitable power supply and a preference for restrained styling. The independent evidence supports considering it seriously, while the fan-control criticism gives you something specific to inspect during the return period.

I would move to another model when the Pulse’s size complicates the installation, dual BIOS matters, or another well-reviewed card costs about the same after shipping. I would also avoid paying an inflated scarcity premium just to obtain this particular cooler.

Compare the two retailers’ actual seller, condition and final delivered cost. The verdict is conditional on that comparison; neither an old launch price nor a favorable review makes every current listing a good purchase.

Sources

Sapphire: Pulse RX 9070 XT specifications — exact retail model, dimensions, power and connections.
PC Perspective: Pulse RX 9070 XT review — original performance and thermal observations in its stated system.
GamersNexus: teardown, fan response and thermals — original examination of assembly and cooler behavior.
TechSpot: fourteen RX 9070 XT cards tested — original board-partner comparison; historical prices are excluded from this verdict.

Where to buy the Sapphire Pulse RX 9070 XT: Check Amazon · Check Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Samsung 990 PRO Review: A Worthwhile SSD Upgrade?

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The Samsung 990 PRO makes most sense when buying it solves a storage problem you can name. More room for a working library is a good reason. Replacing a healthy drive with the same capacity just to improve a sequential benchmark is a weaker one. I would shortlist the 990 PRO for a new performance-focused build, then compare the complete cost of the capacity and cooling it needs.

I owned a 990 PRO for between one and two years. It did not disappoint me. For this review, the configuration comes from Samsung’s documentation and the measured performance comes from the independent review linked below, because my ownership account does not establish which capacity I used or provide a new set of benchmark results for the 2TB drive.

Which 990 PRO this review covers

The reference model is the 2TB bare drive, MZ-V9P2T0B/AM. Samsung specifies M.2 2280, PCIe 4.0 x4, TLC flash and 2GB of LPDDR4 for it. The family shares its advertised sequential ceilings, but capacity and warranty endurance differ. These are manufacturer ratings, not promised transfer speeds in your PC. Samsung datasheet, pages 3–4.

Capacity	Bare US model	Rated read/write ceiling	Warranty write limit
1TB	MZ-V9P1T0B/AM	7,450 / 6,900 MB/s	600 TBW
2TB	MZ-V9P2T0B/AM	7,450 / 6,900 MB/s	1,200 TBW
4TB	MZ-V9P4T0B/AM	7,450 / 6,900 MB/s	2,400 TBW

The table uses Samsung’s specification sheet. Its warranty terms end coverage at the stated write limit or five years, whichever comes first. Those terms do not predict how long an individual drive will survive.

Choose capacity first. I would rather buy enough space for the work I intend to keep than pay for a performance tier while immediately planning the next replacement.

Our SSD endurance calculator translates your own write volume into a planning estimate. It cannot certify a drive’s condition.

What the measured performance supports

Tom’s Hardware’s original 2TB review shows why the workload matters: the 990 PRO finished ahead of the SN850X and Platinum P41 in its 3DMark storage test, but the copy test put it roughly level with the SN850X rather than establishing a lead across the board. During the sustained-write run, it reached about 6.2 GB/s initially, then about 1.4 GB/s after its fast cache was exhausted. These are that publisher’s results. Original performance results and test configuration.

Large projects change the recommendation. A peak write number is a poor substitute for the complete transfer. Before paying extra for the 990 PRO, I would compare the amount of data you move in one sitting with the workload in the cited test, then check whether the source drive or another part of the transfer would prevent you from using the extra speed.

For gaming, use those storage tests to judge storage. They do not establish a frame-rate gain for your GPU, a fixed reduction in every loading screen, or a reason to replace every older NVMe drive. I would keep a working drive until capacity or an observed delay makes the upgrade worthwhile. The 970 EVO Plus ownership review addresses that keep-or-replace decision from the older drive’s side.

Firmware deserves a check before the first big migration

Samsung’s support page listed 8B2QJXD7 when checked on October 4, 2026. Its release note describes improved read-operation stability. The preceding 7B2QJXD7 note addresses intermittent non-recognition and blue screens. Samsung also documents mixed V7/V8 production beginning in September 2023. Current download and release notes. Back up before changing firmware. Record the installed version before moving a working system onto the drive, follow Samsung’s current update instructions, then confirm the version afterward. I would check the drive itself when evaluating old stock or a secondhand unit whose maintenance history I do not know; a seller’s description would not be enough.

The production note also limits what an old review can tell us. Its measurements describe its sample. They should not quietly become a promise that every later capacity, flash revision and firmware behaves identically. I still find the test useful for understanding the product’s strengths; I would not use it to diagnose an individual drive. Our SSD health-check guide provides the next step if you already own one and want to record its condition before changing anything.

Match the cooling to the machine

A bare drive and a drive sold with a heatsink are different installation choices. For a desktop whose motherboard already supplies an appropriate M.2 cooler, I would start by checking the board’s instructions before buying another cooling assembly. For a laptop, verify storage clearance before ordering a tall heatsink version.

Fit comes first. I would not buy an oversized heatsink on the assumption that a more imposing part makes a better upgrade.

For PS5, Sony requires effective heat dissipation and specifies limits for the complete SSD-and-cooler assembly. Its requirements also make clear that passing the advertised sequential-speed threshold does not guarantee identical performance to the console’s internal storage in every game. Follow the Sony installation requirements for your console model.

My buying decision

The 990 PRO belongs on the shortlist if you are building around fast local storage or adding needed capacity. I would compare it with the WD_BLACK SN850X at the same capacity, including the required cooling and the seller’s warranty route. Check the final total at Amazon and Newegg; a launch price from an older review is irrelevant to that decision. If you already own a healthy 980 PRO with sufficient room, I would need a specific workload reason to replace it. If your current storage is causing trouble, diagnose that trouble before assuming a more expensive model is the cure.

My preference is to buy the 990 PRO when the upgrade delivers something concrete: the space you need, the installation you want, or performance in a task you have identified. Keep the older drive when it still does its job. The wider SSD tier list can help compare alternatives once that requirement is clear.

Where to buy the Samsung 990 PRO 2TB: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Samsung 980 PRO Review: Keep It, Update It, Buy Carefully

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

I would keep a healthy Samsung 980 PRO, check its firmware, and replace it only when I need more space or can identify a storage limitation. Buying another one requires a different calculation. Compare its actual capacity, condition and warranty with the alternatives available to you; its old flagship position does not settle today’s purchase.

I owned a 980 PRO for between one and two years. It did not disappoint me. The reference here is the documented 2TB drive, with measured results from independent testing; my ownership account does not supply a capacity, a workload history or a fresh benchmark run that would justify presenting those measurements as results from my former drive.

Read the capacity before the speed claim

Samsung’s bare 2TB MZ-V8P2T0B/AM is an M.2 2280, PCIe 4.0 x4 NVMe drive with 2GB of LPDDR4. The specification sheet describes its flash as three-bit V-NAND. Smaller drives carry different limits. Samsung datasheet, pages 3–4.

Capacity	Rated sequential read/write	Warranty write limit
250GB	6,400 / 2,700 MB/s	150 TBW
500GB	6,900 / 5,000 MB/s	300 TBW
1TB	7,000 / 5,000 MB/s	600 TBW
2TB	7,000 / 5,100 MB/s	1,200 TBW

These ceilings come from Samsung’s capacity-specific table. Samsung’s limited warranty runs for five years or the specified TBW, whichever occurs first. The write limit is not a countdown to failure.

I would avoid a small 980 PRO bought mainly for its badge if the same budget could solve a capacity problem more completely. Work backward from the files you need to keep. Our SSD tier list is a useful comparison map once you know that requirement.

The firmware history matters more than the age of the name

Puget Systems investigated failures involving the 980 PRO in 2023, particularly the 2TB model. Its report identified 3B2QGXA7 and a failure mode in which affected drives became read-only. It recommended 5B2QGXA7 and explicitly said the update would not reverse an already failed drive. That is a documented historical problem in Puget’s machines and reports, not a failure rate for every 980 PRO. Puget’s original investigation. Samsung still listed 5B2QGXA7 on its download page when checked on October 4, 2026. Compare your installed version with the live page rather than relying on the date printed on a review. Samsung firmware downloads.

Back up first. Puget also recommends backing up before applying the update.

If a drive is already reporting errors or has become read-only, I would prioritize preserving accessible files and arranging support rather than trying repeated benchmarks. The SSD health-check guide helps you record what the drive reports.

I would check a used unit more closely. Ask for the actual model and current health information, check the firmware after installation, and keep the purchase record. If the seller cannot establish what is being sold or how a return would work, I would pass; even an attractive asking price would not compensate for uncertainty about the drive’s identity, its condition or the support available if it fails.

Its performance needs context

Tom’s Hardware tested the 2TB 980 PRO in 2021. It did well in that review’s folder-copy workload, while other drives led in some application and read tests. In the sustained-write test, the reviewer changed to 128KB blocks, measured roughly 238GB of fast cache, and recorded an average around 1.7 GB/s after the cache filled. Original 2TB performance results.

The test provides context. It does not establish that every capacity, firmware revision or workload behaves the same. I would use it to ask a more specific question of an upgrade: will it change the task I am waiting for? For a gaming machine with a working 980 PRO, start with available space and actual loading behavior. For a workstation, identify the slow part of the job before buying storage. The review’s transfer result is relevant to copying files; it cannot tell you how much faster your full editing, export or development workflow will become.

A fresh build is different. You have to buy something. Put the 990 PRO and WD_BLACK SN850X alongside the 980 PRO at the capacity you need, then compare the final cost and support terms. I would choose the 980 PRO only when the offer gives me a clear reason to do so.

Cooling and installation choices

Samsung sold a separate 980 PRO with Heatsink in 1TB and 2TB configurations. Its specification sheet gives maximum dimensions of 80.15 × 24.15 × 8.6mm. That is a different physical package from the bare drive. Samsung heatsink datasheet.

For a desktop, I would first check whether the motherboard’s M.2 cooling hardware is intended to cover a bare SSD; for a laptop, I would look up the clearance in the service documentation before choosing the package. Names do not establish fit. PS5 installation also requires suitable cooling, and Sony limits the full assembly’s dimensions. Follow its model-specific instructions rather than choosing from the drive’s name alone. I would settle the mechanical fit before comparing cosmetic differences between heatsinks.

Keep, repurpose, or buy?

Keep it if health and firmware checks are satisfactory and it still has the capacity you need. That is my default. There is no obligation to replace a working part because a newer model exists.

Repurpose it only after deciding what data will live on it and how that data will be backed up. I would record its condition before a move so later changes have a useful baseline. The endurance calculator can help plan write volume, while the drive’s health record tells you about the unit in front of you.

Buy it when the same-capacity comparison is favorable and the seller, firmware path and warranty are clear. Check Amazon and Newegg on those terms. If the offer is no better than a newer alternative, I would choose the alternative; if you already own a suitable 980 PRO, I would spend that money elsewhere.

Where to buy the Samsung 980 PRO 2TB: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Noctua NH-D15 G2 Review: Worth the Premium?

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

I would choose the Noctua NH-D15 G2 for a build where air cooling is a deliberate preference and its mounting system and support package justify the quoted premium without taking money away from parts that would make a more useful difference to the work the PC must do. Budget builds have other options.

Read the variant name. Standard, HBC, and LBC refer to different base shapes. This review uses the standard brown G2 as the buying starting point and identifies other versions whenever their test results appear. The temperatures below belong to the named reviewers.

What you get with the standard G2

These are Noctua’s published standard-model specifications.

Item	Specification
Dimensions with fans	168 mm tall, 150 mm wide, 152 mm deep
Weight with fans	1,525 g
Heatpipes	Eight, 6 mm diameter
Fans	Two NF-A14x25r G2 PWM
Supplied mounting system	SecuFirm2+, with Torx T20 screwdriver
Manufacturer warranty	Six years

The included screwdriver and documented mounting system are tangible parts of the package. Whether they deserve extra money is personal.

Compare the whole purchase. Include the exact mounting parts needed for the present board. The warranty cannot predict a unit’s lifespan.

Standard, HBC, or LBC?

Noctua’s current contact-quality guidance makes the standard version its broadly versatile choice. The specialized versions depend on the CPU heatspreader and mounting conditions.

Version	Where I would begin evaluating it
Standard	AM5 with the supplied offset mounting, LGA1851 with reduced-load ILM, or a build where versatility matters
HBC, high base convexity	LGA1700 under full stock ILM pressure, especially when the CPU has retained deformation from use
LBC, low base convexity	Relatively flat heatspreaders, including AM4 and AM5 without offset mounting

Those are starting points. “AMD gets LBC; Intel gets HBC” discards the mounting conditions that make the recommendation work. Noctua specifically cautions against LBC on LGA1700 under full ILM pressure. I would read its guidance for the existing socket configuration before ordering a specialized version. For an ordinary build, I would avoid making a socket modification a prerequisite for buying a cooler, while recognizing that someone who already has a contact frame installed needs to assess a different configuration from someone putting a new processor into a stock board for the first time. Keep those cases separate.

The thermal advantage has a price

GamersNexus tested the G2 variants with controlled mounting and fan comparisons. In its noise-normalized 250 W Core i9-14900KF test, the HBC recorded a 57.8°C P-core rise over ambient. The Liquid Freezer III achieved 48.1°C in that same comparison. Its 200 W AMD results showed smaller differences between the G2 variants.

The platform matters. A well-executed air cooler can still trail an appropriate large liquid cooler at sustained high heat loads, while the gain from selecting a particular G2 base depends on the platform and cannot become a universal promise that this cooler will transform every gaming PC. Start with your workload.

The reviewers praised the construction and fan clips while questioning value at the review’s historical price. They also found the optional washer modification troublesome to install. Today’s prices need a fresh comparison.

If your current cooler keeps the CPU within its operating limits at a sound level you accept, I would keep it. For a new air-cooled build, compare the Phantom Spirit 120 SE before deciding what the Noctua package is worth to you.

Tall RAM changes the calculation

Noctua’s fit FAQ gives the G2 32 mm of RAM space with its front fan in the default position. Taller modules require a change. Its example uses 35 mm memory: raising the fan by 3 mm raises the height from 168 to 171 mm.

That small difference can decide whether a side panel closes. Check the memory’s exact dimensions. Then compare the final assembly with the case allowance. Removing the front fan leaves 59 mm of RAM clearance under the G2 heatsink, according to Noctua, with a cooling-performance tradeoff. Replacing that fan with a suitable 120 mm model is another documented option. I would price any additional fan before choosing this route. Buying an expensive cooler and immediately paying to change its configuration deserves a second look.

Use Noctua’s compatibility section to check each component. Our PC Builder organizes the wider build but does not certify cooler clearance.

Noise details and the early fin issue

Noctua deliberately runs the paired G2 fans at slightly different speeds to reduce periodic acoustic interaction. Its fan-speed explanation also discusses adjusting the slower fan for individual preference. Listen at the desk. Matching the RPM readings defeats the design’s intent.

Early G2 fin-rattle reports also deserve context. In a September 2024 manufacturer statement reproduced by Hardware Busters, Noctua attributed affected units to fin interlocks loosened by shipping shock. It offered side covers, replacement heatsinks, or refunds and announced reinforced interlocks for later production. That establishes the historical response. It does not establish today’s failure rate. For a used purchase, I would want the receipt, complete mounting kit, and a clear account of any rattle remedy.

Record any new noise before attempting a repair. Describe its conditions to support and get advice before bending fins.

My buying decision

The G2 makes the most sense to me when the buyer has already chosen air cooling and values this particular hardware and support package. A fit compromise or an uncomfortable price premium changes the answer. Compare the PA120 SE for a simpler budget decision, or the Liquid Freezer III 360 if sustained-load performance matters more than retaining a tower cooler.

Before checkout, record the full variant name and final fan height above your RAM. “NH-D15 G2” alone does not settle either detail.

Sources

Where to buy the Noctua NH-D15 G2: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

CyberPower CP1500PFCLCD Review: Check the Revision

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The CP1500PFCLCD is worth considering for a desktop or small homelab that needs enough battery time to shut down cleanly. I would choose it around the equipment it must protect, then check the revision before comparing offers. CyberPower has used this name across different hardware: the documented 1000W version has twelve outlets, while older examples carried a 900W rating and ten outlets. The name alone is insufficient. Current datasheet, historical NUT reports, 2010 inspection.

I owned a CP1500PFCLCD for between one and two years. That ownership is the first-person evidence used here.

I have no recorded revision, runtime measurements, or acoustic measurements to attach to that ownership. The assessment below combines manufacturer documentation with explicitly scoped software reports.

Which CP1500PFCLCD this review covers

The specification reference is the US 120V, 1500VA/1000W version. These are manufacturer specifications, checked against CyberPower’s three-page datasheet.

Detail	Documented configuration
Output limits	1500VA and 1000W
Design	Line-interactive; sine-wave battery output
Outlets	Six battery-backed, six surge-only; NEMA 5-15R
Input	120V; NEMA 5-15P plug
Published runtime	10 minutes at half load; 2.5 minutes at full load
Data connection	USB HID; optional network management accessory
Battery	Replaceable sealed lead-acid cartridge; match serial prefix
Physical size	3.9 inches wide, 11 high, 14 deep

That outlet split matters. Twelve sockets do not provide twelve battery-backed connections.

Before buying, make a short list of what must survive an outage, including the computer, necessary display, NAS, router, and any switch required for shutdown messages, then check that their actual plugs fit the battery side without blocking one another.

Older reviews need equally careful reading. Tom’s Hardware’s November 2010 inspection describes five battery-backed outlets and an earlier “Adaptive Sinewave” implementation. It is useful evidence of the product’s history, but its waveform description and physical layout should not be transferred to the twelve-outlet version. Original inspection.

The runtime number that changes the buying decision

The useful comparison is your required shutdown time against runtime at your actual load. A 1000W output ceiling says how much load the unit is rated to support; it does not promise a long session at that load. CyberPower’s published 10-minute half-load figure corresponds to 500W, while its full-load figure is only 2.5 minutes. Those are manufacturer ratings, not our measurements. Datasheet.

For a worked sizing example, suppose your protected equipment draws 350W while doing the job you need to finish. Dividing 350 by the documented 1000W ceiling gives 35% loading. That arithmetic establishes headroom; it gives no measured runtime. Add the display and network equipment to the input if they will remain connected. I would start with our UPS runtime calculator, treat its result as a planning estimate, and then verify the complete shutdown sequence during a planned maintenance window.

Define success beforehand. A NAS that finishes shutting down with reserve remaining meets a different requirement from a desktop expected to keep rendering through an outage.

If your requirement is sustained high-power work, seek a model with documented runtime at that load and the battery capacity to meet it. Buying this tower simply because “1500” sounds large is the wrong shortcut.

USB shutdown is part of the purchase

The supplied USB A-to-B communication cable connects the UPS to a computer. The front charging ports have a different job. CyberPower’s manual separates them, and it describes PowerPanel software as the route to automatic computer shutdown. Make the data connection during installation. Manufacturer manual, pages 4–6 of the PDF.

For Linux or a NAS, NUT has CP1500PFCLCD reports using usbhid-ups. Look closely at their scope: the displayed examples use NUT 2.7.x and report a 900W nominal limit. One submission reports that changing a low-battery setting appeared to succeed without changing the returned value. Another flags unreliable voltage telemetry. These are specific historical reports, not a failure rate for current units. NUT device reports.

My takeaway is to verify behavior beyond detection. NUT’s upsmon is the component responsible for invoking system shutdown; reading a charge percentage does not establish that this part is configured. For a group of machines, document which host reads the USB device and how the others receive its status. Keep that communication path powered until every dependent system has finished. NUT shutdown-controller documentation.

Our UPS testing guide explains the distinction between charge indication and useful protection. Use the manufacturer’s procedures for your hardware when planning the test.

Battery replacement starts with the serial number

CyberPower lists RB1290X2 for serial numbers beginning CXX, and RB1280X2B for CR9, CXF, or CQC in the cited datasheet. Photograph the label before ordering. A seller listing that says only “fits CP1500PFCLCD” needs more checking. Battery compatibility table.

Budget a maintenance window. The reviewed manual tells owners to turn off and unplug connected equipment, then turn off and unplug the UPS before replacement. Follow its battery instructions; this review does not recommend a live swap. Manufacturer procedure.

Keep the purchase receipt too. CyberPower’s limited warranty describes three years of product coverage, original-purchaser restrictions subject to applicable law, and claim conditions. Its connected-equipment promise is conditional and excludes lost data. I would never count that marketing allowance as a replacement for backups. Warranty document.

When I would choose something else

The APC BR1500MS2 is the comparison to make if APC’s software and replacement-battery route suit your setup. Compare the same protected load and your required runtime, then the current delivered cost from Amazon and Newegg. A higher watt rating alone cannot settle that choice.

I would pass on a CP1500PFCLCD offer whose revision or battery condition cannot be established. For a clearly identified unit protecting a load with a verified shutdown plan, the combination of replaceable batteries and documented communication support gives it a sensible role. The final buying check is straightforward: exact hardware, suitable load, correct cartridge, and a shutdown that has been exercised.

Sources

The evidence ledger links the manufacturer datasheet, manual and warranty, original historical inspection, and NUT documentation. Runtime remains manufacturer-rated; no bench results, current price, or stock availability are asserted here.

Where to buy the CyberPower CP1500PFCLCD: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Beelink Mini S13 Review: Check the Version First

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

I would buy the Beelink Mini S13 for a small, clearly defined job: a basic desktop, a home automation host, or a place to learn a few Linux services. Keep a working N100 box. When shopping for a new machine, pay attention to the SSD, network ports, and exact board inside the case before letting the newer processor name decide the purchase.

I owned the Beelink Mini S13 for between one and two years of use.

This review covers the original 16GB DDR4 configuration documented in the independent tests below; their benchmark figures are attributed to their testers.

The distinction matters. Beelink’s own support response about S13 drivers separates machines with 2.5GbE from those without it. Its 2026 firmware bulletin also identifies different board branches. A product name is not a complete specification.

What the original DDR4 model gives you

Component	Configuration covered here
CPU	Intel N150, four cores/four threads, up to 3.6GHz
RAM	16GB DDR4, one SO-DIMM slot
Storage	Approximately 500/512GB supplied SSD; two M.2 positions in the launch configuration
Network	Original review units have Gigabit Ethernet and Wi-Fi 6
External ports	Four USB-A ports, two HDMI outputs, audio; no USB-C

CPU details are from Intel’s N150 specification. The physical layout is documented in Frandroid’s original review and ITPro’s inspection.

I like accessible storage in a machine intended to stay useful, but treating every S13 listing as the same machine risks discovering that the upgrade instructions or network driver belong to a different board after you have already paid. Ask the listing to answer the practical questions. Is the memory replaceable? Which storage interface is installed? What Ethernet speed is specified? Does the photographed rear panel match the selected option?

Conflicting answers are a reason to buy elsewhere.

Performance is adequate when the job fits

ITPro measured 1,242 single-core and 3,029 multi-core in Geekbench 6, plus 2,984 in PCMark 10. The reviewer also left the unit under load for 12 hours and reported little fan noise without performance falling away. Useful evidence, within its scope. A long test on one sample does not establish years of reliability across the product line.

For gaming, the limits arrive quickly. Frandroid obtained 17fps in Forza Horizon 5 and 13fps in Shadow of the Tomb Raider, both at 720p with the lowest settings. I would take that as a firm reason to shop elsewhere if those games are part of the purchase.

For browsing and a focused server role, I care more about whether the chosen applications fit than about a synthetic leaderboard position. List the simultaneous jobs. Our Proxmox capacity planner helps turn that list into a rough memory budget before it becomes a cart full of hardware, which is a much cheaper moment to discover that your proposed workload needs a larger machine.

The supplied SSD is a buying detail, not a footnote

ITPro’s launch sample delivered 510MB/s reads and 480MB/s writes in AS SSD. Frandroid independently identified a SATA SSD in its review unit, despite the machine offering M.2 expansion. An M.2 shape does not by itself mean a fast NVMe drive. ITPro storage test, Frandroid’s internal inspection. That would not stop me buying an S13 for home automation, but I would be more cautious about a listing charging extra for an unspecified “high-speed SSD,” particularly if the intended job involves moving large files all day.

My first upgrade would be prompted by a real capacity or responsiveness problem. Budget for replacement storage only when the full system still makes sense against a better-equipped alternative; spending to fix several limitations can erase the reason for buying this class of PC.

Keep a drive that does the job.

BIOS revisions explain some conflicting advice

Beelink’s February 2025 bulletin says the S13 N150’s MINISF001 BIOS adjusted GPU frequency from 750MHz to 1GHz. That is a specific firmware change, not a promise that every unit or every game gains the same amount. Later documentation is more important when maintaining a machine today. The Q1 2026 bulletin restricts MINISF006 to the MINISF00X branch and describes MS2V002 for a different DDR4, dual-2.5GbE branch.

Check the existing BIOS and board with support before flashing. Back up first, then follow the matching instructions.

Save those identifiers after setup. Keep a spare USB stick with the installation media and correct network driver alongside the recovery instructions, especially if the machine will live behind a monitor or run without one and you want to avoid reconstructing its configuration during an outage.

S13 versus S12 Pro, and where I would use it

Intel lists the N150 at up to 3.6GHz and the N100 at 3.4GHz. Both have four cores, one memory channel, and an official 16GB memory specification. The N150’s higher clocks do not add another tier of memory capacity. N150, N100.

For a new machine, I would choose the S13 when its complete configuration and seller terms make more sense than the S12 Pro. For an existing S12 owner, keep the working installation unless you can name the problem the replacement solves. Our N150 buying guide explains why the surrounding hardware deserves as much attention as the chip.

For dedicated Home Assistant use, start with the official x86-64 installation instructions. Home Assistant recommends its OS for most users; that guide explains firmware settings and warns that writing the image overwrites the existing system. Choose the Proxmox route if hosting other systems is a deliberate part of the project.

The Mini S13 earns a positive recommendation for that focused role. Buy the configuration you understand, keep a recovery plan, and resist paying for a model-number upgrade that leaves your actual workload unchanged.

Sources

Where to buy the Beelink Mini S13: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Beelink Mini S12 Pro Review: A Small Server Worth Keeping

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The Beelink Mini S12 Pro still makes sense when you can describe its job in one sentence. Run Home Assistant. Keep a small Linux service available. Give a spare monitor a basic desktop. I would keep a working one in those roles, particularly when replacing it means reinstalling software, moving data, and teaching the rest of the household how to recover a service they already depend on.

For a new purchase, the condition is stricter. Buy it for a meaningful saving against an alternative with the ports and storage you need. Its age does not make it a bad computer, but it should not command a premium for an old reputation.

I owned the Beelink Mini S12 Pro for between one and two years.

The measurements here come from the independent tests named below; the configuration under discussion is the original N100 model with 16GB DDR4 and Gigabit Ethernet.

The version matters more than the photograph

Part	Configuration covered here	Buying consequence
Processor	Intel N100, four cores/four threads, up to 3.4GHz	Plan a modest workload
Memory	16GB DDR4-3200 in the original inspected unit	Confirm installed capacity
Main storage	500GB M.2 SSD in RedesZone’s test sample	Check the supplied drive’s interface
Additional storage	Original layout has a 2.5-inch SATA bay	Verify the revision before reusing a drive
Connections	Gigabit Ethernet, four USB-A 10Gbps ports, two HDMI outputs	Choose around your actual peripherals

The CPU specification comes from Intel; the physical configuration comes from RedesZone’s inspected Mini S12 Pro.

That extra drive bay deserves attention. Asked about conflicting listings, Beelink support explained that older Mini S12 versions had one M.2 slot and a 2.5-inch slot, while newer versions had two M.2 slots and no 2.5-inch slot. A familiar blue case therefore does not tell you where your existing SSD will fit. If you already own a useful SATA drive, the original layout can be attractive; if the seller cannot identify the board, judge the purchase on the installed storage alone.

Settle that before buying.

Do not pay for an expansion plan that depends on a photograph of a different revision. I would ask for the actual internal layout, especially when ordering a second drive at the same time as the computer.

What the performance evidence supports

RedesZone recorded 3,099 in PCMark 10 and approximately 850MB/s sequential reads and writes from its supplied SSD. Its separate 30-minute Prime95 stress test reached 96°C, with clock speed decreasing at that temperature. These results belong to that tested unit and workload. Original test results.

Choose the job accordingly. A machine waiting for a home automation event has a different job from one encoding a video all afternoon, and I would accept the S12 Pro for the former while looking for more compute capacity for the latter. Keep the recovery plan simple.

The N100 provides Intel Quick Sync and virtualization support, but its documented memory specification is 16GB across one channel. Those are processor capabilities and limits, not a count of how many streams or virtual machines your particular setup will sustain.

Budget the memory first. Our Proxmox capacity planner provides an estimate for the services you choose.

Home Assistant is the clearest reason to buy it

For a box dedicated to Home Assistant, I favor the direct Home Assistant OS installation because it keeps the machine’s purpose clear and avoids making the household depend on a hypervisor you also use for experiments.

The official generic x86-64 installation guide requires UEFI boot, disabled Secure Boot, and a boot drive with supported logical sectors. Writing the image replaces the existing system, so save anything you need from Windows first. Follow that guide rather than an old screenshot of someone else’s BIOS.

Proxmox remains a reasonable choice when learning virtualization is part of the project. Use our Home Assistant on Proxmox guide for that route. I would keep experiments separate from the automation VM and make its recovery plan understandable to someone else in the house. Add services after checking memory use and backup behavior; a cheap box becomes an expensive inconvenience if nobody remembers which containers need to come back after a failed drive.

Start small.

Maintenance starts with identifying the board

Save the serial number and a photograph of the current BIOS screen before hunting for firmware. Beelink’s Q1 2026 update bulletin lists separate S13/S12 firmware branches with explicit hardware restrictions. Match the documented branch; the family name alone is insufficient.

Keep installation media and the needed network driver with the recovery notes. Establish normal behavior first. Once the machine runs the intended workload and you know how to restore it, change one thing at a time if a specific problem gives you a reason to adjust the configuration.

For an always-on installation, measure consumption at the outlet before using our power cost calculator. A processor power specification does not include every component or the power adapter. Use the number your setup produces.

S12 Pro or something else?

Keep it if it works. Before buying a new S12 Pro, compare the complete configuration with the Mini S13, including storage and network revision, because a second purchase followed by reinstalling services makes little sense when the original machine already handles the work you need.

If you already expect a substantial VM collection or need different networking, widen the search through our homelab mini PC guide. For a dedicated automation machine, the Home Assistant buying guide helps compare the whole installation.

My verdict is positive within that scope. The S12 Pro deserves a defined job, an appropriate price, and a backup plan. Give it those, and there is little reason to buy a replacement purely for a newer model number.

Sources

Where to buy the Beelink Mini S12 Pro: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Beelink EQ14 Review: Check the LAN Version First

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The Beelink EQ14 is a sensible small appliance or light desktop when you want an internal power supply and modest expansion. That is its appeal. I would buy it for the practical advantages while keeping a working N100 computer until its workload gives me a reason to replace it.

Start with the Ethernet specification. Beelink lists both dual-gigabit and dual-2.5GbE versions, and the distinction matters much more to a networked server than the model number suggests. Beelink’s current specifications name different controllers for the two versions.

I owned an EQ14 for between one and two years. This review separates those configurations and credits the published tests used for its performance, power and acoustic figures.

The configuration to compare

Component	Specification	What I would check before ordering
Processor	Intel N150, four cores/four threads, up to 3.6GHz	N150 must appear in the selected offer
Memory	One DDR4 SO-DIMM, 16GB published maximum	Included capacity, not a speculative upgrade
Storage	Two M.2 2280 PCIe 3.0 slots; SATA SSD supplied	Installed drive interface and capacity
Gigabit version	Two Realtek RTL8111H ports	Suitable if gigabit is the intended network
2.5GbE version	Two Intel I226-V ports	Both controller and speed named by the seller
Power and display	Internal power supply; two HDMI outputs	Correct regional power cord and monitor connections

The machine specifications are from Beelink, with the processor checked against Intel’s N150 page.

For a dedicated Home Assistant installation, I would take a satisfactory gigabit offer over paying extra for network capacity I had no plan to use. For a server transferring files to a faster NAS, I would select the 2.5GbE model explicitly. Two identical-looking jacks do not settle the question. That is also how I would compare Amazon and Newegg: select the same network version and included storage first, then compare the complete offer. A cheaper gigabit machine is not a discounted copy of the 2.5GbE version.

A tidy machine with an accessible SSD upgrade

The internal power supply removes the external brick from the desk or shelf. The installation is tidier.

In Clubic’s teardown, removing the bottom exposed the memory slot and two SSD positions; the review also shows the power supply alongside them. I would choose this layout for a tidy fixed installation, while remembering that an internal power supply is less convenient to replace than an external adapter.

Storage is where the product description needs careful reading. NVMe-capable slots do not mean the included drive is NVMe. Clubic measured about 558MB/s sequential reads and 510MB/s writes from its supplied 512GB SATA drive. Those results describe that sample. They explain why comparing the EQ14 against an NVMe-equipped alternative using capacity alone misses a difference. Clubic’s storage test identifies the drive and interface.

Keep a usable boot drive. I would add storage when capacity becomes the problem, choosing a drive for the data it needs to hold and the work it needs to do rather than replacing the original solely to improve a sequential benchmark on an automation box.

Plan monitor connections before buying a dock. Notebookcheck found that its EQ14’s USB-C port supplied data but neither DisplayPort output nor USB Power Delivery. The HDMI connections are the straightforward display route for that unit. Notebookcheck’s port inspection is more useful here than a listing that merely says USB-C.

The N150 and the BIOS caveat

Intel specifies four cores, one memory channel and a 16GB memory maximum for the N150. The graphics specification includes 24 execution units with a maximum dynamic frequency of 1GHz. The processor’s 6W base-power figure is not a measurement of the complete EQ14 at the outlet. Intel’s specifications describe the chip, not every implementation built around it.

Early graphics tests need a date attached. Notebookcheck’s January 2025 unit ran its GPU at 750MHz. On February 28, 2025, Beelink announced EQ14 BIOS TWEQF001 with an adjustment from 750MHz to 1000MHz. Notebookcheck’s original review and Beelink’s update notice document the sequence.

Check the BIOS version first.

An early result cannot settle the performance of an updated machine, and a higher clock in a release note cannot tell us the size of the improvement in a particular application. It does justify checking the installed firmware before troubleshooting unexpectedly weak graphics performance. Use Beelink’s support route to match any update to the exact machine. Its notice tells owners to check upgrade conditions, back up important data and follow the accompanying procedure. TWEQF001 establishes what changed in 2025; it is not a recommendation to install that old release over a newer one.

Quiet operation is the stronger argument

Notebookcheck measured 23.5–23.8dB(A) at idle and up to 24.4dB(A) under load, from 15cm against a 22.5dB(A) background. Idle consumption was 7.9–9.1W in its test. These measurements concern its January 2025 gigabit review unit, so they are a useful reference rather than promised readings for the 2.5GbE configuration. The original acoustic and power results support the EQ14’s role beside a desk.

Measure your normal workload. Put that wall reading into our power-cost calculator. I would judge the machine after its services are running in the intended location before spending time chasing the lowest possible idle screenshot.

Where I would use it

A dedicated automation host is a good fit for this design. For Home Assistant OS, follow the project’s generic x86 guide: it specifies UEFI boot, Secure Boot disabled and a boot drive with 512-byte logical sectors. Writing HAOS replaces the target drive’s existing system. Choose between a dedicated installation and virtualization before following the imaging steps.

Our Home Assistant mini PC guide covers that purchase decision; the N150 platform comparison is for readers still choosing a box. If dual 2.5GbE is the main requirement, compare the exact EQ14 offer with the EQ12 N100. I would retain an EQ12 already doing its job.

For a new EQ14 purchase, my preference is the 16GB configuration with the network version suited to the job. Before checkout, confirm that version in the seller’s specification, then confirm the SSD capacity and return terms. Those details decide whether the offer matches this recommendation.

Sources

Where to buy the Beelink EQ14: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Beelink EQ12 Review: Buy It for the Two Network Ports

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

The Beelink EQ12 earns its place through networking. Buy it for the ports. I would choose the N100 version for a small server that needs two wired connections, especially when one port goes to a faster local network. A growing collection of memory-heavy virtual machines needs a different purchase.

I owned an EQ12 for between one and two years. This review covers the N100 configuration with 16GB DDR5; the benchmark and power figures below come from the named publications that measured them.

Get the EQ12 identity right

EQ12, EQ12 Pro and EQi12 are different buying decisions. This page concerns the four-core N100 machine. Match the processor and memory type before comparing offers; the similar names are not enough.

Part	Configuration covered here	Buying consequence
Processor	Intel N100, four cores/four threads, up to 3.4GHz	Choose it for modest workloads
Memory	One DDR5-4800 SO-DIMM, 16GB manufacturer specification	An upgrade replaces the existing module
Internal SSD	M.2 NVMe over a PCIe x1 connection	An expensive high-bandwidth SSD is wasted here
Additional storage	One 2.5-inch SATA bay	Useful for a separate data drive
Ethernet	Two Intel I225-V 2.5GbE ports in the tested configuration	Check both ports in the offer
Monitor connections	Two HDMI ports and USB-C DisplayPort output in CNX’s test	Useful beyond headless server duty

The CPU limits come from Intel. AZW’s EQ12 specification describes the DDR5 and PCIe x1 configuration. The physical expansion and interfaces were inspected by Igor’sLAB and CNX Software.

I would choose the 16GB version when comparing otherwise equivalent units. Keep the SSD capacity comparison separate: a listing advertised as 500GB and a review sample described as 512GB do not establish identical drives. The manufacturer, seller and included storage can change independently of the EQ12 name.

Why the two Ethernet ports matter

CNX Software measured approximately 2.37Gb/s download and 2.34Gb/s upload using iperf3. That supports the EQ12’s appeal as a small wired node. A local interface test cannot reproduce a router simultaneously encrypting VPN traffic, checking packets against intrusion-detection rules and handling the rest of a busy household’s connections, so I would not turn the result into a promise about those workloads. CNX’s original network test gives the measurement conditions.

Do the network plan first.

My first choice would be to give the ports defined jobs. A dedicated router has an obvious separation between WAN and LAN; a server might use a second network for storage or management. Buying dual Ethernet without such a plan adds little to a Home Assistant appliance sitting on a gigabit switch. Our OPNsense mini PC setup guide covers the practical route from hardware to an installed firewall. If the network depends on this box, keep recovery access available before experimenting with its hypervisor. Combining the router with every homelab experiment makes a routine reboot a household decision.

Memory and storage set the ceiling

Intel specifies one memory channel, a 16GB maximum and no ECC support for the N100. It also lists VT-x, VT-d and Quick Sync. Those features explain the appeal of a compact virtualization or media host, but they do not remove its memory limit. Intel’s N100 specification is the supported baseline for this recommendation.

If the intended guests already need more than Intel’s published maximum, I would choose a platform that specifies the required capacity rather than build a new server around a larger module whose compatibility you hope to establish after delivery. Our homelab mini PC comparison puts the EQ12’s class beside machines intended for more expansion.

The storage decision is simpler. Igor’sLAB found a single-lane NVMe connection and a separate SATA bay. I would spend an SSD upgrade budget on useful capacity and a suitable warranty, not a premium sequential-speed rating the connection cannot deliver. Adding a second drive also creates room to separate operating-system and data storage. Neither drive replaces an external backup. The original teardown shows the arrangement.

Running cost and sound need context

CNX measured 12.1W at idle in Windows with one Ethernet cable connected, rising to 13W with two. Its Windows CPU stress test peaked at 28.9W before settling around 26.5W. Those are readings from that review configuration, not the chip’s 6W specification converted into whole-system consumption. CNX’s measurement conditions matter when estimating an always-on installation.

Use your measured wall consumption in the power-cost calculator.

I would leave the system running its intended services before deciding whether an idle result represents its normal day. Measure with the drives and network cables you plan to keep attached. That is the operating cost worth budgeting.

The EQ12 has fans. Igor’sLAB recorded 33.5dB(A) idle and 36.9dB(A) under load, against a 33.3dB(A) room background, measured from 40cm. That small idle difference supports placing it near a desk; it is not a promise of silence in a bedroom. Igor’sLAB’s acoustic test states the measurement setup.

My buying recommendation

Buy the EQ12 when its connections solve a problem. My strongest case is a modest wired server; a compact desktop that later becomes a homelab node is also a useful role.

Keep a working one. A newer processor name alone is no reason to replace it.

For Home Assistant alone, compare the complete cost against a simpler box in our Home Assistant mini PC guide. Home Assistant’s generic x86 instructions require UEFI boot and a compatible boot drive; writing HAOS also replaces the existing system on that drive. Decide whether you want that dedicated appliance or a VM before installing anything. The Proxmox setup guide serves the latter choice.

Before buying, obtain the exact N100/DDR5 configuration, the seller’s return terms, the supplied power adapter and confirmation of both 2.5GbE ports. That is the EQ12 worth comparing. An EQi12 result in the same search is a different machine.

Sources

Where to buy the Beelink EQ12: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

Arctic Liquid Freezer III 360 Review: Fit Comes First

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

I would shortlist the Arctic Liquid Freezer III 360 for a build that needs substantial sustained cooling and has room for the complete radiator assembly, with its fans in place and the surrounding parts positioned so that installation does not depend on bending a tube around an awkward obstruction. The test evidence is persuasive. Fit still comes first.

This review covers the original black ACFRE00136A, identified in Arctic’s specification sheet. The Pro is a separate purchase. Match the exact name before comparing offers.

The test results below are credited to their original publisher. No temperature, acoustic result, or long-term reliability rate here comes from a new TechFuelHQ test.

The dimensions that matter

Arctic publishes these specifications for the original black 360.

Item	Published specification
Radiator	398 × 120 × 38 mm, aluminum
Radiator fans	Three P12 PWM; 200–1,800 RPM
Tubing	450 mm length
Pump range	800–2,800 RPM, PWM controlled
Supported sockets	AMD AM4/AM5; Intel LGA1700/LGA1851
Manufacturer warranty	Six years

Source: Arctic specification sheet. The 38 mm measurement is the radiator itself. Fans and mounting hardware need additional room.

Start with the case drawing. For a top mount, look at the motherboard’s upper edge and the space needed to route its power cable; for a front mount, account for the graphics card and tube path before assuming that a case advertised to accept a 360 mm radiator accommodates this entire assembly without a compromise. Check the fan thickness too.

Our PC Builder helps organize the wider configuration, but does not validate radiator or pump-block clearance. Record those checks separately.

Why the thermal evidence is convincing

In GamersNexus’s original February 2024 test, the LF III 360 recorded a 46.7°C rise over ambient in its 200 W noise-normalized comparison. That chart included a configuration with the pump at 70%, allowing more of the fixed noise allowance to go to the radiator fans. The nearest competitor was within the test’s margin of error.

The result supports considering this cooler when noise and sustained heat removal matter together. It does not establish a permanent first-place ranking, a universal ideal pump percentage, or the temperature you will see on a different CPU. Compare candidates within the same review method. The tuning lesson is useful. Pump speed is one control among several, and blindly maximizing it may not produce the best result at a chosen sound level. Start with the manufacturer’s setup. Establish a baseline, then make one change at a time.

Keep the workload constant. Otherwise, deciding whether the adjustment helped becomes much harder than it needs to be.

I would not replace an acceptable gaming cooler just to chase this chart position. If the existing machine meets its temperature and noise goals, the money can stay unspent.

Check the board as well as the case

Arctic maintains a motherboard compatibility list because nearby components can matter even when the socket matches. For example, it identifies a pump-body conflict with the preinstalled M.2_1 heatsink on the ASUS ROG Maximus Z690 Apex. Other boards in the same list are marked compatible, while some are incompatible.

Arctic describes a replacement-heatsink support route for specified conflicts. Resolve that before ordering. I would pay particular attention when the motherboard’s appearance or existing SSD cooling arrangement matters to the build. Check the exact board.

An aftermarket SSD heatsink deserves its own check. The manufacturer’s motherboard listing describes a particular board arrangement; it cannot automatically validate every accessory later attached to it, so I would photograph or sketch the socket area with the intended heatsink present and compare that arrangement with the cooler drawings before relying on a compatible-board entry.

Intel installation is a real buying condition

The LF III’s Intel design requires its supplied contact frame in place of the stock loading mechanism. GamersNexus documented that requirement and criticized the restriction. It also found the AMD spring mounting and stiff tubes awkward during installation.

Read the socket-specific manual before buying. If removing the stock Intel mechanism is outside the work you want to do, choose another cooler. That is a reasonable preference.

On AMD, the manual specifies the mounting-module orientation and says to engage both cooler screws gently before tightening them alternately. Follow its illustrated sequence with the board supported and space to work. Resist forcing a difficult screw.

Pick the control cable deliberately

Arctic supplies a combined control option and separate control for the pump, VRM fan, and radiator fans. The latter needs three motherboard PWM headers. Its manual also states that the reported pump RPM is 50% above the physical speed: a 1,500 RPM reading corresponds to 1,000 RPM at the pump.

That detail can save unnecessary troubleshooting. A monitoring number alone is not a failure diagnosis. Note the installed cable arrangement. My preference is separate controls when the board has suitable headers and I intend to tune the sound. For a simpler build, the combined option reduces setup work. Either way, confirm header configuration and watch temperature behavior during the first controlled load. Our CPU temperature guide and overheating checks help separate an alarming number from an installation problem.

When I would buy air instead

I would choose a tower cooler if the case fit remains uncertain, the Intel installation requirement is unwelcome, or the workload does not justify this configuration. The Phantom Spirit 120 SE is worth examining for a budget build. The NH-D15 G2 offers another route when the buyer specifically wants its air-cooling package.

The warranty is a support term, not a promise that every unit will last exactly six years. Keep the receipt and installation details. Before paying for the LF III, confirm the exact SKU, the board’s compatibility entry, and enough space for the radiator with its fans installed.

Sources

Where to buy the Arctic Liquid Freezer III 360: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

APC BR1500MS2 Review: Plan the Shutdown First

LK Wood IV — Sun, 04 Oct 2026 23:42:28 -0500

I would shortlist the APC Back-UPS Pro BR1500MS2 for a Windows workstation or modest NAS setup when its shutdown and battery-maintenance arrangements fit the job. The US model supplies sine-wave battery output with a 900W ceiling and six battery-backed outlets. Its strongest reason to buy is a workable protection plan around those limits. Schneider datasheet.

This is a research-based review of the exact BR1500MS2. I am not claiming personal ownership of this APC model or presenting fresh runtime tests.

Manufacturer manuals establish the hardware details; software documentation and an identifiable owner report expose the setup questions worth resolving before spending money.

The BR1500MS2 you should compare

Use the full suffix when shopping. This review covers BR1500MS2, US 120V, rather than treating every APC unit with “1500” in its name as equivalent. The following values come from Schneider’s model-specific datasheet and user manual.

Item	BR1500MS2 specification
Output limits	1500VA / 900W
Design	Line-interactive; sine-wave battery output
Battery outlets	Six NEMA 5-15R
Additional outlets	Four surge-only NEMA 5-15R
Supply	120V; NEMA 5-15P input plug
USB charging	One Type-A, one Type-C; 15W combined
Replacement battery	APCRBC163
Typical recharge	16 hours

The first buying mistake to avoid is reading 1500VA as 1500W. The second is counting all ten outlets as battery-backed. Both misunderstandings can produce a shopping list that looks plausible until the equipment is connected. I would map the six backed outlets before ordering. Put the devices that must finish work on that list, include the switch or router if another machine depends on it to receive a shutdown message, and decide whether the monitor needs battery power before assigning the remaining sockets.

Map the sockets first. This makes the review useful for your setup even without a universal runtime claim.

Size the protected job

Take a hypothetical workstation, monitor and network load totaling 360W. That is 40% of the BR1500MS2’s documented 900W limit: 360 ÷ 900 × 100. A 720W load is 80%. These are calculated load fractions, not observed runtimes or APC efficiency targets. Use measured draw for the work you expect to be running when power fails. Treat a component list as a starting point. I would want a different margin for a machine that can stop promptly than for a server whose applications take time to close and whose guests must shut down in order.

Our UPS runtime calculator can help compare planning scenarios. Its output remains an estimate. The APC manual directs runtime questions to the product information rather than supplying a single guaranteed duration, so this review does not fill that gap with a retailer’s full-load number or an extrapolation from battery amp-hours. BR1500MS2 manual, specification page.

If you need a stated duration under heavy load, obtain the manufacturer’s curve for this exact unit before purchase. Then confirm that your installation completes its shutdown with reserve remaining. A wattage limit is only the first part of that decision.

Windows support is clearer than the old manual suggests

The supplied communication cable matters. Schneider’s current installation guidance identifies it as AP9827 and describes connecting a computer through it to PowerChute Serial Shutdown. The front charging ports are for charging; do not choose a cable merely because both ends appear to fit. Schneider installation guide.

The older printed manual names PowerChute Personal Edition. Schneider’s compatibility page, updated September 24, 2026, instead directs USB-equipped Back-UPS models to PowerChute Serial Shutdown. It also explicitly says that Back-UPS devices are not supported on Linux by that software. That is a software-support boundary, not proof that a Linux host cannot communicate with the UPS through another system. Current compatibility policy.

This distinction changes my recommendation.

For a Windows desktop, the manufacturer’s documented route is a useful reason to consider the APC, whereas a Proxmox or other Linux installation deserves a closer look at the NUT path and its behavior on the software release you run. A familiar logo does not remove that work.

What the homelab evidence does establish

A June 2022 TrueNAS owner posted BR1500MS2 telemetry using usbhid-ups, then described repeat shutdown tests and behavior when utility power returned. The initial report raised a boot-loop problem; later tests behaved differently, and the discussion did not establish a universal product defect or a universally safe configuration. It is one installation with published observations. Original TrueNAS report.

Make recovery part of the buying checklist.

Plan what happens after the machine shuts down: whether UPS output stops, when power becomes available again, and whether the motherboard automatically boots. Evaluate the whole sequence in a maintenance window. Copying another person’s timer would tell you little about whether your own applications had finished.

NUT assigns shutdown responsibility to upsmon, which can monitor configured UPS sources and invoke the host shutdown command. For several machines, establish who monitors the physical UPS and which systems depend on that monitor. Watching battery percentage in a dashboard does not exercise this chain. NUT documentation.

There is also a current troubleshooting wrinkle worth knowing. Schneider documents Back-UPS self-tests that are not recorded in PowerChute, and some software-triggered tests may return an unknown result. Its July 2026 support note attributes the logging issue to event translation. A missing entry alone therefore should not be your battery diagnosis. Schneider self-test reporting note.

Maintenance and the alternative I would compare

The manual specifies APCRBC163, describes a typical battery life of three to five years with shorter life under heat or frequent outages, and instructs replacement sooner when the unit indicates it. It also calls for connecting the UPS directly to a wall outlet with ventilation unobstructed. Follow the model’s instructions when handling the battery. The manual states a standard three-year warranty; confirm applicable terms for the seller, location and unit you choose. I would price the replacement cartridge alongside the initial purchase and retain the receipt. A used listing needs a battery-age discussion even if the display powers on. Manufacturer manual.

The CyberPower CP1500PFCLCD is the direct alternative to investigate. Check its generation, then compare documented runtime at the same load and the total cost of maintaining each unit. Keep Amazon and Newegg open beside one another so the decision includes both offers.

My verdict is conditional but positive: the BR1500MS2 makes sense when six backed outlets and 900W cover your planned job and you can verify shutdown on your operating system. For extended heavy-load operation, or a purchase based solely on unverified “minutes of backup” claims, keep researching before buying.

Sources

The evidence ledger preserves the exact manufacturer documents and software support pages checked for this review. The TrueNAS thread is a dated individual report. No comparative acoustic test, measured battery runtime, current price, or stock claim is made.

Where to buy the APC Back-UPS Pro BR1500MS2: Search Amazon · Search Newegg. Affiliate links. As an Amazon Associate I earn from qualifying purchases.

VIDEO_MEMORY_MANAGEMENT_INTERNAL: Fix 0x10E in Windows 11

LK Wood IV — Sun, 04 Oct 2026 23:47:21 +0000

By LK Wood IV · 2026-10-04 · ~10 min read · St. Louis County, MO

VIDEO_MEMORY_MANAGEMENT_INTERNAL is bug check 0x0000010E. It means Windows’ video memory manager reached a condition it could not recover from. It does not mean “your graphics card ran out of VRAM,” and it does not condemn the memory chips on the card.

Microsoft’s 0x10E reference says the bug check is usually caused by a video driver behaving improperly. Its explicit resolution is to check Windows Update for an updated video driver. The later settings and hardware tests are TechFuelHQ’s one-variable-at-a-time diagnostic order, not additional Microsoft instructions.

First, make sure this is the right stop code

Windows has several graphics and memory blue screens whose names blur together. The number separates them — and prevents a long detour through the wrong tests.

Stop code	What Windows caught	Start here
`0x10E` VIDEO_MEMORY_MANAGEMENT_INTERNAL	The video memory manager could not recover from an internal condition	This guide: Parameter 1, display driver, stock GPU settings
`0x116` VIDEO_TDR_FAILURE	Windows tried to reset the display driver and the recovery failed	GPU driver crash and TDR guide
`0x1A` MEMORY_MANAGEMENT	Windows found a severe error in its general memory-management structures	MEMORY_MANAGEMENT diagnosis

Write down all four values shown with the bug check if the blue screen or your crash record provides them. For 0x10E, Parameter 1 is the useful router. Microsoft says it describes the type of video-memory error. A value missing from Microsoft’s table needs individual examination rather than a guess.

What 0x10E is reporting

Windows’ video memory manager is called VidMm. Microsoft’s VidMm and GPU scheduling documentation says it sits inside the DirectX graphics kernel, manages GPU memory, and works with the GPU scheduler. The Windows components that implement this work include dxgkrnl.sys, dxgmms1.sys, and dxgmms2.sys.

When a crash report names dxgmms2.sys, it identifies a Windows component in the path where the failure surfaced. The filename is a location — not a verdict. Microsoft says these files are part of the operating-system installation, are not separately downloadable, and are designed to work with the other OS files that accompany them. Do not replace one with a copy from a download site or another PC.

The 0x10E page currently lists 68 Parameter 1 values, from 0x1 through 0x44; nine of those rows explicitly name a driver error or a display-driver-interface call — 0xB, 0xF, 0x10, 0x12, 0x13, 0x16, 0x19, 0x2D, and 0x2E — while the phrases “memory corruption” and “bad hardware” do not appear; those are counts and wording from the published table, not incident data showing how often any cause occurs on Windows PCs.

The table supports starting with the driver, but it neither identifies nor excludes a hardware fault. I would not buy or RMA a card on the stop-code name alone.

Use Parameter 1 to choose the branch

You do not need to translate every table row. The groups below collect rows that are useful for routing this guide.

Microsoft supplies the middle column. The right column is TechFuelHQ’s editorial next test; Microsoft does not prescribe it per parameter.

The table routes investigation; it does not rank causes or prescribe repairs itself.

Parameter 1	What Microsoft’s row says	TechFuelHQ next test (editorial inference)
`0xB`, `0xF`, `0x10`, `0x12`, `0x13`, `0x16`, `0x19`, `0x2D`, `0x2E`	A driver returned an invalid result, overflowed a buffer, broke a contract, or a DDI call failed	Follow Microsoft’s driver update or rollback path first
`0x25`, `0x30`	A GPU aperture write or GPU virtual-address operation failed	After the driver step, remove tuning variables and look for a repeatable result
`0x37`	VidMm failed to lock allocation pages during TDR	Compare the TDR/0x116 fix path after the driver step
`0x3B`, `0x3C`	Memory remained rotated, allocated, or mapped during a D3 power transition	Record whether the same power transition repeatedly precedes the crash
`0x41`, `0x42`	A cross-adapter allocation had an invalid residency or adapter count	Record the adapter configuration; compare supported single- and multi-adapter modes if available
`0x43`	A reserved-frame-buffer save or restore could not map a page	Record whether a power-state transition repeatedly precedes the crash

If your value is not in that short list, read its exact row on Microsoft’s page. Do not turn a table description into a diagnosis it does not make. For example, 0x25 says the GPU attempted to write over an undefined aperture area. That does not tell you whether the initiating fault was firmware, a driver, unstable tuning, or failing hardware.

Fix 1. Update Windows and the approved display driver

Microsoft’s own resolution for persistent 0x10E crashes is to check Windows Update for an updated video driver. Start there. Microsoft’s Windows driver-update instructions also say a manual driver should come from the device manufacturer’s site, and document rollback when trouble begins after an update.

In Settings > Windows Update, install the normal pending Windows updates and restart.
Install the current display package intended for your model. On a laptop or branded desktop, check the PC maker’s support page and choose only a package listed for that exact model and Windows version.
If the crash began immediately after a display-driver update, roll back to the last version that was stable on this machine instead of repeatedly installing the same package.
If ordinary update or rollback does not change the result, use the clean-install procedure in the GPU driver crash guide.

Change one layer at a time.

A simultaneous BIOS update, driver update, Windows repair, and hardware swap may stop the crash, but it leaves you with no idea which change mattered — and no useful evidence if the blue screen returns next week.

Retest the trigger.

Fix 2. Put the GPU and video memory back to stock

Microsoft’s 0x10E page does not name tuning as a cause. This guide still removes core, VRAM, voltage, and power-limit tuning as an isolation step so a repeat test has fewer variables.

Reset GPU core offset, memory offset, voltage curve, and power-limit changes.
Close tuning utilities so they do not reapply a profile at sign-in.
If the card has a physical dual-BIOS switch, shut down before moving it and document the original position. Use the card maker’s instructions.
Retest the workload that normally triggers the crash.

A clean run at stock settings suggests that one of the removed settings correlated with the crash. It does not prove which setting caused it. Repeat the same trigger before drawing that conclusion.

Stop there if it stays stable.

Fix 3. Treat hybrid graphics as one stack

Laptop and multi-GPU systems can involve an integrated GPU, a discrete GPU, and cross-adapter allocations in the same session. Microsoft’s table specifically includes cross-adapter states at 0x41 and 0x42.

Start with the PC maker’s current packages for the exact model. If the firmware or graphics control panel offers a supported integrated-only or discrete-only mode, repeated tests in each mode can compare the two paths. This controlled troubleshooting suggestion goes beyond what Microsoft infers from 0x41 or 0x42. Do not disable the only display adapter on a machine with no safe way back.

For a desktop with two add-in cards, remove the secondary card for a controlled test if doing so is physically safe and the primary card can drive the display. Repeat the comparison. A difference between configurations is evidence about the path. It does not prove that one card is defective.

Fix 4. Repair Windows’ copy of the graphics components

Microsoft does not say 0x10E implies damaged Windows files. If Windows servicing or System File Checker already reports corruption, use Microsoft’s system-file repair instructions, which put DISM before System File Checker. Open Terminal as administrator and run:

Run this branch only when Windows has given you separate file-integrity evidence.

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart after both commands finish. This step is for damaged or mismatched operating-system files. It cannot stabilize an overclock, repair a failing memory chip, or correct a defective power supply.

Avoid sites offering individual DLL or SYS downloads. Microsoft’s VidMm documentation says the relevant kernel graphics files ship only as part of the operating system and that graphics-driver developers must not mix versions of them.

Fix 5. Test hardware only after the software path is clean

In this guide’s editorial workflow, hardware isolation begins when 0x10E repeatedly returns with a current or known-stable driver and GPU and VRAM settings at stock. Microsoft does not give that escalation threshold on its 0x10E page. If the display also shows persistent blocks, colored flashes, or broken geometry, the GPU artifact guide provides a separate diagnosis for that evidence.

Use repeated comparisons that can distinguish paths; one clean run is never conclusive.

Log the trigger. Note the application, display configuration, temperature, and whether the crash followed resume, sign-in, or a monitor change.
Test one display path. Disconnect optional monitors and adapters. A clean run narrows the trigger but does not prove the disconnected monitor is defective.
Test the card in a known-good system, or a known-good card in this PC. A failure that repeatedly follows one card is a stronger isolation signal than the filename in one dump, but it is still not proof by itself.
Test system RAM when the evidence points beyond graphics. Multiple unrelated stop codes, memory-profile instability, or errors outside graphics workloads justify the 0x1A memory test path. A lone 0x10E does not.

Simple VRAM pressure is not a verdict. Microsoft’s GPU-segments page explains how VidMm manages segment types and allocations; it does not say capacity exhaustion causes 0x10E. A VRAM meter alone cannot establish why VidMm reached an unrecoverable condition.

What not to do

Do not buy a GPU from the stop-code name. The official cause section points first to the video driver.
Do not replace dxgmms2.sys or dxgkrnl.sys by hand. If Windows integrity checks report corruption, use the conditional DISM and SFC path above.
Do not edit TDR registry values as a 0x10E fix. Microsoft’s TDR registry documentation says end users should not manipulate those keys; they are for targeted testing and debugging during driver development.
Do not use 0x1A advice for a 0x10E crash. System-memory testing may become relevant later, but the first branch is different.
Do not treat Microsoft’s 68 table rows as cause statistics. They are error types, not a tally of user crashes.

A conservative diagnostic order is therefore: exact code, Parameter 1, current or rolled-back display driver, stock GPU settings, conditional Windows file repair, then controlled hardware isolation. The driver step is Microsoft’s explicit 0x10E resolution; the remaining order is TechFuelHQ’s editorial workflow for changing one variable at a time.

Sources

Microsoft Learn: Bug Check 0x10E: VIDEO_MEMORY_MANAGEMENT_INTERNAL — definition, Parameter 1 table, cause, and resolution; accessed October 2, 2026.
Microsoft Learn: Video memory management and GPU scheduling — VidMm, VidSch, and the Windows graphics-kernel files; accessed October 2, 2026.
Microsoft Learn: GPU segments — memory segments and aperture behavior; accessed October 2, 2026.
Microsoft Support: Update drivers through Device Manager in Windows — Windows Update, manufacturer downloads, reinstall, and rollback paths; accessed October 2, 2026.
Microsoft Support: Use the System File Checker tool to repair missing or corrupted system files — DISM and SFC order and commands; accessed October 2, 2026.
Microsoft Learn: Testing and debugging TDR during driver development — TDR registry keys are for driver-development testing and debugging, not end-user manipulation; accessed October 3, 2026.

Ryzen 5 9600X vs Ryzen 7 9700X: Which Should You Buy?

LK Wood IV — Sun, 04 Oct 2026 00:00:00 -0500

Buy the Ryzen 5 9600X for a gaming build if the 9700X premium would force a worse graphics card. Buy the Ryzen 7 9700X for regular CPU rendering, or when a comparable bundle makes the complete builds cost nearly the same. I would not pay for two extra cores merely to change the badge from Ryzen 5 to Ryzen 7.

What will you run?

Before choosing the eight-core chip, write down the game or application that makes the extra money worthwhile, because the published results below show two processors that sit close together in the cited gaming and Photoshop tests yet separate much more when Blender renders on the CPU. That difference is the reason to buy. Start there, then price the whole machine.

These remain real shopping options. On October 4, 2026, the 9600X appeared at number four on Newegg’s US CPU Best Sellers page. That is a dated retailer ranking, not sales volume or proof of a performance lead.

What changes between the processors

Specification	Ryzen 5 9600X	Ryzen 7 9700X
Architecture	Zen 5	Zen 5
Cores / threads	6 / 12	8 / 16
Base clock	3.9 GHz	3.8 GHz
Maximum boost	Up to 5.4 GHz	Up to 5.5 GHz
L3 cache	32MB	32MB
Default TDP	65W	65W
Socket / memory	AM5 / DDR5 UDIMM	AM5 / DDR5 UDIMM
Cooler in the box	None	None
Boxed product ID	100-100001405WOF	100-100001404WOF

Source: AMD’s 9600X specification and 9700X specification, checked October 4, 2026.

Both pages list the same supported chipsets. There is no reason to assign the 9700X a more expensive motherboard simply because it is a Ryzen 7. Choose the board for the connections, expansion and firmware support you need, then check its exact CPU support list.

Keep the cooler in the budget. AMD recommends a premium air cooler for both. If you already own one, confirm the mounting hardware before treating it as a free part in the new build.

What the published tests say

These historical laboratory results show the workload difference. Use the tested software versions and configurations when interpreting them; they cannot promise a particular frame rate in a 2026 game.

Test and source	9600X	9700X	Calculated 9700X lead
Tom’s Hardware, 1080p gaming geometric mean, RTX 4090, entries without the PBO label	163 FPS	170 FPS	About 4.3%
Puget Systems, Blender 4.0 CPU score	227.76	289.98	About 27.3%
Puget Systems, Photoshop 25.9.1, PugetBench 1.0.1 score	10,950	11,482	About 4.9%

The gaming row comes from the 1080p chart in Tom’s Hardware’s August 2024 review, published August 7 with an August 14 retest note. Its setup used Windows 11 and an RTX 4090. The two application rows come from Puget Systems’ August 7, 2024 review. Puget used an ASUS ProArt X670E-Creator WiFi, 64GB DDR5-5600, an RTX 4080 and disabled PBO. The percentages above are (9700X score ÷ 9600X score − 1) × 100, rounded to one decimal.

For gaming, I would use that small gap to challenge a large CPU premium. Tom’s also explains that the differences shrink with a weaker GPU or higher resolution. Check your games. If a particular simulation or competitive title is the reason for building the PC, find a test of that title with a similar graphics card and settings before using an average from a mixed suite to decide what you should spend. The CPU hierarchy gives broader gaming context; the CPU and GPU benchmark lookup helps you inspect the two parts’ published indexes.

For work, be specific. Blender’s CPU score supports choosing the 9700X for CPU rendering. Photoshop’s result gives a much smaller reason to spend more.

“Content creation” is too broad a shopping requirement; write down the application and operation that makes you wait. If you render on a GPU, don’t apply the CPU-rendering percentage to that job.

Choose by the task you will repeat

Your situation	My buying choice	Check before spending
Gaming build with a fixed total budget	9600X	Whether the saving improves the GPU or avoids another compromise
Regular Blender CPU rendering	9700X	A relevant test for your renderer and a tolerable full-build premium
Photoshop plus occasional games	Usually 9600X	Whether the small application gain matters to your daily work
Similar bundles at nearly the same total	9700X	That the board, RAM capacity and return terms are comparable
Already own a 9600X and mainly game	Keep it	A repeatable CPU limit before replacing a working processor

Choose for the work you do now. I would budget for the 9700X when a CPU-heavy job interrupts the day often enough that I can name the delay, describe how frequently it happens and point to a relevant result showing that the extra cores would help. An occasional export is a weaker reason.

Keep a note of that task beside the parts list. It stops a temporary discount from making the decision for you.

A bundle only earns its place if you want the parts it contains.

The full-build price worksheet

Open both carts at the same time. Use equivalent parts unless a bundle forces a change; record that change explicitly.

Cost to enter	9600X build	9700X build
CPU or CPU/board/RAM bundle	Your checkout figure	Your checkout figure
Motherboard, if outside the bundle	Add once	Add once
Complete RAM kit, if outside the bundle	Add once	Add once
Compatible cooler and required mount	Add if needed	Add if needed
Shipping and tax	Add	Add
Discounts you can actually use	Subtract	Subtract
Total	A	B
Extra cost for the 9700X route	—	B minus A

For a gaming build, place that difference beside the cost of the GPU upgrade you are considering. Decide which route solves your actual limitation.

For regular CPU work, compare the difference with the time a relevant application benchmark suggests you could save, then consider how often you run that task. Don’t turn a benchmark score into hours saved without the runtime of your own job. Keep a simple log of the operation, its duration and how often you wait for it while working; it gives you a useful way to judge the premium even when the benchmark’s project differs from your own.

For an upgrade, keep resale separate. First calculate what you must pay before the old CPU sells. Then make a second total using a realistic net resale figure after fees and shipping. A hoped-for sale should not make an unaffordable upgrade look affordable.

The PC Builder can hold the wider system plan. For RAM, use the DDR5 buying guide and the exact Vengeance versus Flare X5 comparison; record the full kit code when comparing bundles.

Search the exact CPU, then check the offer

These controls open retailer searches. Confirm the model, seller, condition and included items before ordering.

I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.

Ryzen 5 9600X, boxed product 100-100001405WOF:

Search Amazon Search Newegg

Ryzen 7 9700X, boxed product 100-100001404WOF:

Search Amazon Search Newegg

Check your final cart against the worksheet before paying. If the 9700X route has acquired a board you don’t need, less RAM or a GPU downgrade, revisit the comparison. My default remains the 9600X for a gaming budget and the 9700X for work that earns its extra cores.

Sources

AMD Ryzen 5 9600X and Ryzen 7 9700X: current product specifications.
Tom’s Hardware gaming tests: August 2024, source of the historical gaming row.
Puget Systems content-creation tests: August 7, 2024, source of the Blender and Photoshop rows.
Newegg US CPU Best Sellers: category ranking read October 4, 2026.

Sources re-read October 4, 2026. Retailer prices and stock are deliberately left to the current offer and your worksheet.

GPU or PSU Coil Whine? Find the Noise Before Swapping

LK Wood IV — Sun, 04 Oct 2026 00:00:00 -0500

By LK Wood IV · Published 2026-10-04 · ~8 min read · St. Louis County, MO

A new graphics card starts buzzing, and the power supply sits just below it. Which one do you replace?

Before ordering either part, repeat the scene that bothers you, change the frame cap and listen again while watching the fans, because changing the GPU’s workload also changes what the power supply has to deliver. A cap alone cannot identify the culprit.

My ASUS ROG Astral RTX 5080 OC produced a faint whine only in uncapped game menus, audible with my ear at the case panel. Any frame cap removed it. That is one report from my card, running with an EVGA SuperNOVA 1000 GT, and the reusable observation records that same unit. It gives you a test to repeat; it cannot promise the same result from another Astral or another PSU.

My Astral RTX 5080 OC, the card behind report #1 in the community census. Photo: TechFuelHQ.

Decide whether this is a noise test at all

Do not continue a listening test if there is smoke, a burning smell, visible connector damage or repeated shutdowns. Power down and get the fault assessed. A phone recording cannot establish that a crackling electrical sound is harmless.

For a stable system, ordinary coil whine is a plausible explanation. Corsair describes vibrating inductors, and ASUS describes load-related resonance in graphics cards. Neither description means every buzz from a PC is coil whine.

Keep the PSU enclosure closed.

Do not insert a tube, screwdriver or microphone through its grille. Corsair warns that PSU capacitors can retain charge after unplugging. Have the manufacturer handle a faulty PSU fan, or replace the supply.

Use one scene and change one setting

Download the GPU and PSU noise test log (CSV). It contains suggested test rows with blank results. Fill it in for your machine.

Start with the game or application where you hear the noise. Keep the same save point, camera position, graphics settings and case-panel state, and record the exact card and PSU models, including the revision if known, so that a later comparison does not accidentally mix two board designs or two versions of a supply. Mute the speakers.

Check	What to record	What the result tells you
Desktop before the game	Fan state, noise location and whether the sound is present	A baseline for this session
Repeatable noisy scene	Actual FPS, GPU fan RPM if available, and noise at your seat	The symptom under the workload you care about
Same scene capped at 60 FPS	Whether the cap takes effect and whether pitch or loudness changes	Whether this lower frame-rate condition changes the noise; 60 is a test setting, not a required gaming target
Same scene at your preferred cap	The same observations	Whether a usable everyday setting solves your complaint
Restore the original setting	Whether the original sound returns	Whether the change repeats rather than coinciding with a different scene

Use the game’s own limiter when available. Verify the resulting FPS on screen. A setting called “60” is no help if the menu ignores it. AMD documents that frame-rate limits can reduce GPU power demand, including in menus. Changing GPU demand also changes the load supplied by the PSU. If the noise changes, either remains a candidate. You have found a useful condition to repeat.

Do not combine the first comparison with other changes. Save the undervolt or new fan curve for a separate run; otherwise, even if the sound disappears, you will have no way to tell which change helped or which setting you should restore if a game becomes unstable later. If a cap solves the problem, stop there. For further tuning, use the GPU undervolt settings database and validate your own card’s stability separately.

Separate the fans from the electrical noise

Watch the fans as well as the FPS counter. A buzz that changes immediately with a scene or cap while reported fan RPM stays steady is a reason to investigate electrical noise. A rattle that begins with a fan starting is a reason to investigate that fan. Record the timing.

If a fan is visibly motionless while the noise continues, its rotation cannot be producing that sound. Do not extend that observation to every fan in the case. Some PSUs deliberately stop their fans: Corsair’s zero-RPM reference lists specific models and part numbers. A silent fan does not mean the PSU is electrically inactive.

For a GPU or case fan with a manufacturer-supported control, you can compare two permitted fan speeds at idle and then restore automatic control. Leave the pump alone. Do not force a fan to stop, put a finger into moving blades or disable cooling under load. If a card’s fans fail to operate when its own documentation says they should, follow the fan troubleshooting branch before continuing a gaming test.

Listen from outside the case near the graphics-card area, then near the PSU exhaust. Keep your hands and recording device clear of vents and fans. Note the apparent location, including “unclear.” If panels obscure the source, let a shop isolate it instead of reaching into a powered PC.

Leave the case closed for these comparisons.

Read reports for your exact product

The coil-whine census has a different job from this test log: it stores one accepted owner report per physical unit. The September 26 dataset still contained 47 reports across 44 models when checked on October 4. No individual model had reached the five-report publication floor.

These examples help choose the next check:

Product in the census	Available context	Useful next step
ASUS ROG Astral RTX 5080 OC	One report, my menu-only observation with an EVGA SuperNOVA 1000 GT	Try the menu-cap comparison before buying a different PSU
XFX RX 6950 XT Speedster MERC 319	Three reports; exact SKU is present in two	Match the model and available SKU, then read each workload; three units cannot establish a model-wide rate
Sapphire NITRO+ RX 9070 XT	Two reports	Do not substitute the wider RX 9070 XT group for this particular board
Corsair SF450 and Seasonic FOCUS PX-650	One PSU report each	One owner’s result cannot choose a quiet replacement PSU for your GPU

The source is the public submissions CSV, with issue numbers linking back to the owners. The GPU-family table mixes board designs. It cannot establish that an ASUS PRIME, Sapphire NITRO+ and PowerColor Red Devil will sound alike simply because all three use an RX 9070 XT.

The missing detail often matters more than the model name. “Capping FPS changes it” leaves out whether the owner tested a menu at 60 FPS with the case on the floor or gameplay at 144 FPS with the case beside their head, which makes it a poor substitute for repeating the test where you actually sit. Keep that context in your log.

Keep it, exchange it or test another supply

My first choice is to keep a stable system when a reasonable cap removes the annoyance.

If the card remains distracting at your normal seat during normal gameplay, contact the seller while its return or exchange window is open. Explain the exact symptom and ask which remedy applies. You do not need to call the card electrically defective to explain that its noise is unacceptable to you.

If the sound clearly comes from the PSU, start with that supplier’s support. If the source remains unclear and you have no suitable spare, pay for diagnosis before buying replacements by guesswork. For a loaned or shop-supplied comparison PSU, check the build’s power and connector requirements using the PSU wattage calculator and the component manufacturers’ instructions.

Change only the supply and its cables, then repeat the same scene and cap. Use the comparison PSU’s own supplied or explicitly approved cables throughout. Seasonic warns that modular cables can differ even between models from the same brand. Matching plugs are insufficient. A quieter second setup gives you a practical choice. It does not establish that the original PSU was defective, that the GPU alone caused the noise, or that a higher wattage rating guarantees silence. Record which configuration you kept.

What the manufacturer guidance says about service

The US ASUS graphics-card FAQ describes slight high-frequency noise as a component characteristic. Corsair’s US PSU support article describes the mechanism and directs concerned owners to support. Those pages do not decide an individual warranty claim, and they are not a blanket statement about every region or seller.

Send the exact model, purchase date, country, workload, FPS cap and a recording from your usual seat. Include any crashes or other faults separately. Ask for a written decision under the terms that apply to your purchase. Do not consume the return window running a promised “burn-in cure.”

Once you have identified the component, submit your unit to the census. A quiet result is useful too. If the source is still unclear, keep that uncertainty in the log rather than assigning the noise to a GPU or PSU in the public data.

Sources

Checked October 4, 2026. Manufacturer guidance below is separate from the subjective owner reports.

Corsair Vengeance vs G.Skill Flare X5: Which DDR5 Kit?

LK Wood IV — Sun, 04 Oct 2026 00:00:00 -0500

Buy the cheaper kit that your motherboard supports. For this comparison, that means Corsair Vengeance CMK32GX5M2B6000Z30 against G.Skill Flare X5 F5-6000J3038F16GX2-FX5. Both are 32GB kits with two modules, rated for DDR5-6000 CL30. I would pay extra for a documented fit or compatibility advantage; a different logo is no reason to spend more. The exact specifications come from Corsair and G.Skill.

Check the label first.

“Vengeance” and “Flare X5” name families. Before you put either in the cart, compare the complete kit label with the seller’s selected variant, especially if the product page lets you switch between RGB and non-RGB heat spreaders, different capacities or different timings while retaining a similar title and photograph. This guide compares the two part numbers above. For choosing capacity or finding other kits, start with the broader DDR5 buying guide.

The exact-kit comparison

Specifications below were read on October 4, 2026. Rated speed requires the relevant memory profile and compatible hardware; it is not an automatic setting for every PC.

Purchase detail	Corsair Vengeance	G.Skill Flare X5
Exact part number	CMK32GX5M2B6000Z30	F5-6000J3038F16GX2-FX5
Capacity and package	32GB, 2 × 16GB	32GB, 2 × 16GB
Rated transfer rate	6000 MT/s	6000 MT/s
Rated CAS latency	CL30	CL30
Tested voltage	1.40V	1.35V
Current profile listing	AMD EXPO and Intel XMP	AMD EXPO and Intel XMP 3.0
Default SPD transfer rate	4800 MT/s	4800 MT/s
Module height	35mm	33mm

Sources: the manufacturers’ Corsair kit specifications and G.Skill kit specifications, plus Corsair’s series dimensions and G.Skill’s exact-product overview for height.

The voltage row describes each manufacturer’s tested profile. Leave it at that. Neither a lower listed voltage nor a matching CL number establishes a frame-rate winner, so I would use those specifications to identify the correct product and BIOS profile, then make the purchase on fit, documented support and the cost of the offer in front of me.

The Corsair C30 versus Z30 trap

There is a third kit worth recognizing before checkout: CMK32GX5M2B6000C30. Corsair’s C30 product page lists Intel XMP, while the Z30 kit above lists EXPO and XMP. The capacity, transfer rate and CAS number can match while the profile field differs.

Copy the whole model code into your shopping notes before you compare retailer listings.

Then match it against the retailer’s selected variant, the cart and the motherboard support entry. The picture is secondary. If a bundle picker replaces the kit you chose with another Vengeance or Flare X5, keep the original code beside the replacement and work through the specifications again before accepting the substitution; the shared family name is too little information to approve the change.

For an AM5 system, I would shortlist the EXPO-listed Z30 or the exact Flare X5 first. If a C30 bundle looks cheaper, check its specific motherboard support before accepting it. Avoid a blanket “Corsair is for Intel, G.Skill is for AMD” rule: the two primary kits here both list both profiles.

When the shorter Flare X5 is worth buying

The height difference is small but concrete. Flare X5 is listed at 33mm; Corsair lists non-RGB Vengeance DDR5 at 35mm. The same Corsair table puts Vengeance RGB at 45mm, so exchanging the non-RGB kit for an RGB variant also changes the fit calculation. Corsair dimensions, G.Skill overview.

Read your cooler’s memory-clearance instructions with the fan in the position you intend to use.

Check the case limit if those instructions call for raising the fan. Don’t buy on the phrase “low profile” alone.

Both kits clear? Move on. If only the Flare fits as planned, its shorter heat spreader solves a real build problem. I would choose it before redesigning a build just to keep a preferred memory brand. G.Skill itself tells buyers to check the cooler’s actual clearance; its series description does not promise a universal fit.

Fill in this worksheet before ordering

Use one row per kit. Resolve a blank compatibility field before you start comparing prices.

Check	What to record	How it changes the choice
Motherboard	Full model and hardware revision	Open that board’s memory support page
Processor	Exact CPU and the support-list CPU family	Use the matching support list
Memory	Complete kit code and number of modules	Reject a mismatched listing
Profile	EXPO/XMP entry and intended speed	Confirm the board’s setup instructions
Firmware	Installed BIOS and relevant support notes	Resolve an update requirement first
Physical fit	Cooler clearance and RAM height	Remove the kit that does not fit
Purchase	Seller, condition, delivered total, return window	Compare equivalent offers

The PC Builder helps organize the rest of the parts list. Its compatibility checks do not replace a motherboard memory QVL or validate a particular kit at its advertised speed. Keep those checks separate. G.Skill provides its own QVL and RAM Configurator links on the exact kit page. Record the support-page URL beside the part number so you can return to the same entry if a retailer changes the bundle, the order arrives with a different label or you later need help with the BIOS configuration.

Once both rows pass, buy the cheaper equivalent offer and save a copy of the order.

Don’t count a rebate you will not claim or a bundled part you would immediately replace as a saving. A return window that lets you finish and test the build is useful; paying for a brand preference is optional.

Search for the selected part number

The controls below open retailer searches. Match the exact part number, seller and condition before buying.

I may earn a commission if you buy through these affiliate links. As an Amazon Associate I earn from qualifying purchases.

Corsair Vengeance CMK32GX5M2B6000Z30:

Search Amazon Search Newegg

G.Skill Flare X5 F5-6000J3038F16GX2-FX5:

Search Amazon Search Newegg

Keep the purchase useful after installation

Before enabling a performance profile, confirm that the system recognizes the installed capacity and follow the motherboard’s setup procedure. Both kits publish a default SPD speed below their rated profile. Start with the BIOS configuration if the kit runs at its default after installation. Corsair specification, G.Skill specification.

Test the selected configuration while the return window is open. If you encounter instability, return to the board’s default memory settings and work through the manufacturer’s support instructions before buying more RAM. Corsair’s RAM FAQ includes guidance for profile-related instability.

Buy one matched kit. Corsair’s FAQ recommends against combining DDR5 kits, and G.Skill’s specification carries the same warning. If you already own enough stable RAM, I would keep it instead of swapping brands for matching headline specifications. If you need more capacity, use the AM5 add-versus-replace decision in the DDR5 guide.

For a new build, settle the 9600X versus 9700X CPU budget before spending the remainder on memory cosmetics. The RAM price index is historical listing context; use its dated observations as context, then compare actual checkout totals for the two exact kits.

Sources

Manufacturer pages checked October 4, 2026. This comparison uses published specifications; it does not report a head-to-head benchmark.

Safe GPU Temperature: Read Your Card's Exact Limit

LK Wood IV — Sun, 04 Oct 2026 02:47:23 +0000

By LK Wood IV · Published 2026-10-04 · St. Louis County, MO

TL;DR · Safe GPU temperature

Use the limit for your exact card. A GPU is inside its operating range while its core temperature remains below that maximum and it is not reporting thermal slowdown. On a supported NVIDIA card, add the current core temperature to the current T.Limit margin. That sum is the card's maximum operating temperature.

There is no universal safe GPU temperature.

NVIDIA currently lists 85 C for the desktop RTX 5070 and 90 C for the RTX 5090.

The same 85 C reading is the limit on one card — and leaves 5 C on the other.

Those numbers are not interchangeable. The useful question is how much room remains before this card reaches its limit.

Read the exact limit with nvidia-smi

Open Terminal or PowerShell on a PC with an NVIDIA driver and run:

nvidia-smi --query-gpu=name,driver_version,temperature.gpu,temperature.gpu.tlimit --format=csv

The two temperature fields have different jobs:

temperature.gpu is the current core temperature.
temperature.gpu.tlimit is the number of degrees remaining before the maximum operating temperature.

Add them.

current core temperature + current T.Limit = maximum operating temperature

That is the whole calculation.

NVIDIA’s current nvidia-smi documentation defines T.Limit as a signed, relative reading rather than an absolute temperature and warns that the sensor is unavailable on some products; if the command returns N/A, skip to the specification-page method below.

The RTX 5080 result on this site

On September 14, 2026, my RTX 5080 on driver 616.56 returned 42 C for the core and 46 C for current T.Limit:

42 C + 46 C = 88 C

A later reading returned 41 C plus 47 C, again 88 C, matching the Maximum GPU Temperature on NVIDIA’s RTX 5080 specification page.

The method matters more than the idle reading. Although the current temperature moves with the workload, the sum identifies the ceiling built into the card’s current temperature-limit reporting, which is the number a generic range cannot supply.

What zero and negative T.Limit values mean

For the same RTX 5080, nvidia-smi -q -d TEMPERATURE reported this ladder:

nvidia-smi field	Reported value	Temperature on this 88 C card	What NVIDIA says can happen
Current T.Limit	46 C	Core was 42 C	46 C of operating headroom remained
Max Operating T.Limit	0 C	88 C	Software may optimize clocks for thermal conditions
Slowdown T.Limit	-2 C	90 C	Hardware may optimize clocks to cool the GPU
Shutdown T.Limit	-5 C specification	Above 93 C	Below this margin, the GPU may shut down for protection

Stop at zero. On this card, 88 C is the maximum operating point. The negative slowdown and shutdown values describe protection beyond that point; 93 C belongs to the protection ladder rather than the usable operating range.

NVIDIA’s manual says a current T.Limit of 0 C or lower means the GPU may optimize its clock based on thermal conditions. That makes the reading easy to use:

Positive T.Limit: operating headroom remains.
Zero T.Limit: the core has reached maximum operating temperature.
Negative T.Limit: the core has passed that maximum and is in the protection ladder.

NVIDIA RTX 50 maximum GPU temperatures

These are NVIDIA’s desktop reference or Founders Edition figures, verified on October 2, 2026. NVIDIA says add-in-card specifications can vary, so use the board maker’s page for a custom model when it publishes a different limit.

GPU	NVIDIA maximum GPU temperature
GeForce RTX 5090	90 C
GeForce RTX 5080	88 C
GeForce RTX 5070 Ti	88 C
GeForce RTX 5070	85 C
GeForce RTX 5060 Ti	87 C
GeForce RTX 5060	89 C
GeForce RTX 5050	87 C

The five-degree spread is why copied temperature charts fail: an RTX 5070 at 85 C is already at NVIDIA’s maximum, while an RTX 5090 at the same temperature still has 5 C left.

The sequence is not monotonic. NVIDIA lists 89 C for the RTX 5060 and 85 C for the RTX 5070.

How much headroom should a healthy card have?

The NVIDIA sources reviewed here do not prescribe one fixed margin for daily use.

Start with the card. Then look at the workload and its behavior.

My hand-tuned ROG Astral RTX 5080 produced a useful real load check: in a 25-minute gaming log, the core averaged 56 C and peaked at 60 C across 308 samples, with zero throttle events and 28 C left below its published maximum. The full log and method are in the ROG Astral RTX 5080 review and its open telemetry dataset.

That is one card, one cooler and one case. Treat it as a worked example.

Look at three things under the workload that matters:

Headroom: a positive T.Limit means the core remains below its maximum.
Clock behavior: a temperature at the limit with falling clocks means cooling is controlling performance.
Stability: crashes, shutdowns or a temperature that suddenly rose from the card’s own baseline need diagnosis even when a generic chart calls the number normal.

If the card reaches its limit during ordinary gaming, use the GPU overheating guide to separate airflow, dust and cooler-contact problems. That page owns the fault diagnosis; this one owns the limit.

If T.Limit is unavailable

Run the temperature query anyway. temperature.gpu works on NVIDIA discrete GPUs covered by the manual even when the relative limit sensor does not.

Do not guess. Find the exact model on the GPU maker’s specification page and look for Maximum GPU Temperature, Maximum Operating Temperature or a model-specific thermal limit. NVIDIA’s own RTX 50 table shows that adjacent models can differ.

For an add-in card, check its board maker; for a laptop, check the laptop maker, because NVIDIA’s desktop specification pages describe reference or Founders Edition designs and explicitly say board-partner specifications may vary rather than defining every card sold under the same GPU name.

If you only need the current number, the GPU section in the temperature-check guide covers Task Manager and the shorter nvidia-smi command.

Core, hotspot and memory are different readings

Keep the readings separate. The equation on this page uses the GPU core temperature; it does not turn a hotspot or memory-junction reading into a core reading or give either reading the core’s limit.

If the core stays below its maximum but hotspot or memory is much warmer, compare like with like. The GPU overheating guide explains the core-to-hotspot gap and what a widening gap changes about the diagnosis.

Sources

NVIDIA nvidia-smi documentation, Temperature fields, accessed October 2, 2026.
NVIDIA desktop specifications for the RTX 5090, RTX 5080, RTX 5070 family, RTX 5060 family and RTX 5050, accessed October 2, 2026.

Glance Dashboard Setup on Windows 11 Without Docker

LK Wood IV — Sat, 03 Oct 2026 11:47:22 +0000

By LK Wood IV · 2026-10-03 · ~8 min read · St. Louis County, MO

Glance is a self-hosted start page: one screen for links, feeds, service checks, calendars, server statistics, and other widgets. You do not need Docker to run it on Windows. The project publishes a portable Windows executable, and the official README’s Windows path is simply the executable plus a glance.yml file in the same folder.

The name is easy to mix up with Glances, the Python system monitor. They are different projects. If you wanted the monitoring tool, use the Beszel vs Netdata vs Glances comparison. This guide covers glanceapp/glance, the dashboard.

I tested Glance v0.8.6 natively on Windows 11 Home build 26200. I verified the downloaded archive against the SHA-256 published by GitHub before running it, bound it only to loopback, exercised good and bad config reloads, and sampled the process after ten minutes. The setup below is a reduced version of that tested configuration.

No installer was involved.

What the native Windows run measured

These numbers describe one capture on one PC. They are useful for sizing this small dashboard, but they are not a cross-machine benchmark.

Treat them as a reference point.

The browser run used an isolated Playwright Chromium context that allowed only 127.0.0.1 and localhost, was configured to abort every other destination before request dispatch, and recorded zero external requests, failed requests, console errors, or page errors while the complete dashboard fit a 1440-pixel viewport without horizontal overflow.

Check	Glance v0.8.6 result
Official archive	`glance-windows-amd64.zip`, 6,518,780 bytes
SHA-256	`e92ca602a1b807f00310b1b70c8271fe779001a5648bb4a13e0f50e81355076c`, matched GitHub’s release API
Process start to first HTTP 200	565.4 ms
Working set at 35.8 seconds	19.07 MiB
Private memory at 35.8 seconds	53.24 MiB
Working set at 603.2 seconds	25.64 MiB
Private memory at 603.2 seconds	58.52 MiB
CPU time at 603.2 seconds	2.234 seconds
Browser check	HTTP 200, no console or page errors, no external requests

The dashboard rendered CPU, RAM, and disk use from the Windows host. It did not render a CPU temperature. The Docker widget failed because the native machine had no Docker socket. Both outcomes are covered below rather than hidden behind a perfect-looking screenshot.

1. Download the official Windows build

Open the Glance v0.8.6 release and download the Windows archive that matches your CPU. For a typical 64-bit Intel or AMD Windows PC, that is glance-windows-amd64.zip.

Start with the hash.

Create a folder that you own, such as C:\Tools\Glance, and extract the archive there. Keep the downloaded ZIP until you verify it.

In PowerShell, move to the folder containing the ZIP and calculate its hash:

Get-FileHash .\glance-windows-amd64.zip -Algorithm SHA256

For v0.8.6, my downloaded archive and GitHub’s API both returned:

e92ca602a1b807f00310b1b70c8271fe779001a5648bb4a13e0f50e81355076c

Match the whole value. When a newer release replaces v0.8.6, use the digest attached to that release rather than reusing this one.

Do not shorten the comparison.

After extraction, confirm the executable before configuring anything:

Set-Location C:\Tools\Glance
.\glance.exe --version

The tested binary printed v0.8.6.

2. Create a local-only glance.yml

Create glance.yml beside glance.exe and paste this configuration:

server:
 host: 127.0.0.1
 port: 8080

branding:
 app-name: Windows Glance

pages:
 - name: Home
 width: wide
 columns:
 - size: small
 widgets:
 - type: clock
 hour-format: 12h
 - type: calendar
 first-day-of-week: monday

 - size: full
 widgets:
 - type: monitor
 title: Local services
 cache: 1m
 sites:
 - title: Glance
 url: http://127.0.0.1:8080/

 - type: server-stats
 servers:
 - type: local
 name: Windows PC

This is intentionally smaller than the project’s example dashboard. It gives you a clock, calendar, loopback health check, and Windows server statistics without credentials, outside feeds, or Docker.

That is deliberate.

The host: 127.0.0.1 line is the safety boundary. Glance’s server configuration says the host controls which address the server listens on and that its default is all interfaces. Loopback keeps this first run on your PC. Do not remove that line just to make another device connect; exposing a dashboard to the LAN is a separate access and firewall decision.

If you later decide that phones, tablets, or another workstation should reach this page, choose the listening address and Windows Firewall scope together, test from the intended client, and confirm that the dashboard is still unreachable from networks that were never meant to see it.

Validate the file before starting the server:

.\glance.exe --config .\glance.yml config:validate

A valid file returns to the prompt without an error. To inspect the fully resolved config, use:

.\glance.exe --config .\glance.yml config:print

3. Start Glance and open the dashboard

Run the executable from the same folder:

.\glance.exe

The console should report that the server is starting on 127.0.0.1:8080. Leave that window open, then visit:

http://127.0.0.1:8080/

Leave the console visible; Glance reports bad edits there.

The official Windows instructions use the same executable-and-config arrangement and point the browser at port 8080. This guide keeps that arrangement but supplies a smaller config and explicitly binds the server to loopback.

If you prefer to keep the config elsewhere, pass its path every time you start Glance:

.\glance.exe --config D:\Dashboard\glance.yml

This guide stops at a portable manual launch. I did not install Glance as a Windows service, create a scheduled task, or add an autostart entry during the capture, so I am not presenting any of those as tested steps.

4. Edit the dashboard while it is running

Glance watches the configuration file. Save a valid change and refresh the browser if the visible page has not already updated.

Save once, then watch the console.

The official auto-reload documentation says a valid save takes effect without restarting the process. It also says a bad live edit logs an error and leaves the old configuration running.

That is what happened in the Windows capture:

Save operation	New page visible after
In-place file write	606.6 ms
Atomic file replacement	638.8 ms
Invalid live config	Error logged after 632.5 ms; old page stayed HTTP 200
Valid config restored	Recovered after 657.9 ms

The capture exercised an in-place write and an atomic file replacement. I did not drive Notepad or VS Code during the test, so the evidence supports Glance’s file reload behavior, not an editor-specific promise.

Reloading also clears Glance’s cached widget data. The official configuration reference warns that frequent reloads can cause APIs to rate-limit repeated requests. Finish a group of edits before saving when a page pulls several outside feeds.

5. Add service checks without mistaking them for alerts

The monitor widget sends a GET request and treats HTTP 200 as healthy. Add another entry under sites when a local service is ready:

 - title: Jellyfin
 url: http://127.0.0.1:8096/

Use an address reachable from the Glance process. A green result means that one request succeeded from this Windows PC. It does not prove that the service is reachable from outside your network, and Glance cannot report a whole-PC or whole-network outage while the machine running Glance is down.

That is the same placement limit covered in the Uptime Kuma setup guide. Treat the Glance monitor as a convenient status panel. Use a separately placed monitor when you need alerts or an outside view.

Server stats has no temperature

The server-stats widget rendered CPU, RAM, and disk percentages in the native test. Temperature was absent. Running the sensor command produced:

.\glance.exe sensors:print

Failed to retrieve sensor information: Exception occurred. (Not supported )

That is expected on the tested host.

Glance’s server-stats documentation says temperature is omitted when the widget cannot find a suitable sensor. The missing number did not stop the other Windows statistics from rendering.

Docker Containers shows a socket error

Do not add this widget to a no-Docker setup:

- type: docker-containers

The Docker Containers reference says the widget requires access to docker.sock and defaults to /var/run/docker.sock. On the native Windows machine, it tried that Unix path and returned a socket error. Removing the widget is the correct fix when you do not run Docker.

Remove it.

If your goal is managing Compose stacks rather than displaying a home page, Glance is the wrong layer. Dockge manages Compose files; Glance links to services and summarizes them.

Fix three captured startup failures

Glance says glance.yml is missing

Running v0.8.6 from an empty folder returned exit code 1 and this exact message:

parsing config: reading glance.yml: open glance.yml: The system cannot find the file specified.

Put glance.yml beside the executable or pass the full path with --config.

Check the folder first.

Glance logs a config error but the exit code is zero

In this Windows capture, a file containing only pages: [] logged:

Config has errors: no pages configured

That specific invalid run returned exit code 0. Do not use the process exit code alone as proof that a config is valid. Read the console and run config:validate before starting the dashboard.

Read the error, not only the code.

The browser cannot connect

First check that the Glance console is still open and that its start line names the same host and port you entered in the browser. Then inspect the listener:

Get-NetTCPConnection -LocalPort 8080 -State Listen

With the config above, the local address should be 127.0.0.1. If another process already owns 8080, select another unused port in both server.port and the Glance self-check URL.

The setup I would keep

Keep the native dashboard small at first: clock, calendar, local server stats, and a handful of service links. Leave it on loopback until you have a deliberate remote-access design. Remove widgets whose dependencies do not exist on the Windows host rather than accepting a permanent red error card.

Glance v0.8.6 was quick to start and stayed modest in this capture, but the more useful result was failure behavior: a bad live edit preserved the last valid page, missing temperature did not break CPU/RAM/disk, and the Docker widget failed loudly instead of pretending the socket existed. Those are the boundaries that make the dashboard predictable.

Sources

Three ways to keep a hardware plan moving

LK Wood IV — Sat, 03 Oct 2026 05:00:00 -0500

This first public issue connects three decisions that are easy to lose between browser tabs: a PC parts list, a NAS capacity plan, and a GPU shortlist. It is published on the site as part of the public archive.

Save and resume a PC build

The PC Builder now keeps up to eight named builds on the device you are using. A saved build restores the exact CPU, motherboard, RAM, GPU, storage, power supply, and case selections. The share URL carries the same selections when you need the plan on another device or want to send it to someone else.

The saved list stays in browser storage. It is not an account. Save and restore action events omit the build name and parts list. Measurement of displayed retailer choices and clicks can identify selected products, as described in the privacy policy. The builder still shows compatibility warnings, its calculated power estimate, and separate Amazon and Newegg choices for selected parts.

Carry a NAS plan into its operating cost

Start with the NAS and RAID Capacity Calculator. After it produces a valid capacity result, Continue to power cost carries the drive count, drive capacity, unit, and RAID level into the Power Cost Calculator.

Capacity does not determine power draw, so the destination starts with a clearly labeled four-bay NAS estimate. Replace its idle watts, load watts, and load hours with measurements from your hardware. The power page keeps the NAS context in its share link and provides a return link to the exact capacity plan.

Cut the GPU list to the cards that fit

The 2026 GPU hierarchy ranks 43 desktop cards on its stated 1440p raster basis. Its model search, tier filter, and VRAM filter narrow the existing table without changing the benchmark rows or tier cutoffs.

Use the hierarchy to choose a performance band, then open the GPU comparison tool when you need a smaller side-by-side decision. The hierarchy keeps its source basis and dates beside the ranking, so the filters do not turn a dated benchmark set into a live price or availability claim.

Keep the route

Bookmark this issue if these three paths belong to the same project. For future tests, tool changes, build guides, and meaningful corrections, use the newsletter form below or the site-wide RSS feed.

WHEA_UNCORRECTABLE_ERROR 0x124: Read the Record

LK Wood IV — Sat, 03 Oct 2026 00:00:00 -0500

WHEA_UNCORRECTABLE_ERROR is Windows reporting that hardware raised a fatal error it could not contain. The stop code is 0x00000124, usually shortened to 0x124.

That definition tells you what the blue screen does not say. It does not say “replace the CPU.” It does not make AuthenticAMD.sys or a processor name a diagnosis. Windows Hardware Error Architecture (WHEA) collects a record from the component or platform that reported the condition. Your next job is to read that record.

Microsoft’s 0x124 reference gives you the two fields that route the investigation:

Parameter 1 identifies the kind of error source that reported the problem.
Parameter 2 points to the WHEA_ERROR_RECORD that describes it.

Preserve those before changing firmware settings, reinstalling Windows or ordering a part.

The Hardware Diagnostic Workbench can keep the stop time, bug-check parameters, error record, tuning state, and controlled tests in one device-local project. It records evidence; it does not turn a WHEA source into a replacement-part verdict.

First, make sure 0x124 was the crash

If the blue screen stayed up, photograph the stop code. If the PC restarted too quickly to read it, start with the random-restart guide. Its Event 41 command converts the saved decimal bug-check value to hexadecimal. Decimal 292 is 0x124.

If a bug-check value of zero is the only evidence you have, stay with the restart guide until a matching photo or dump confirms 0x124. The zero does not establish a stop code for that shutdown; it does not overrule separate evidence from the same crash.

Also keep corrected WHEA events separate from this blue screen. Microsoft’s WHEA error-processing documentation says Windows can log corrected hardware-error information without stopping. A fatal uncorrected condition is saved and followed by a bug check. Both deserve attention, but a corrected event alone is not proof that the machine had a 0x124 crash.

Preserve the dump before changing settings

Check C:\Windows\Minidump for a .dmp file whose timestamp matches the crash. A kernel or automatic dump can instead be at C:\Windows\MEMORY.DMP. Copy the matching file to a working folder so a later crash or cleanup cannot replace the only copy.

If no dump exists, configure the next one through System Properties > Advanced > Startup and Recovery > Settings. Microsoft’s small-dump guide documents the Small memory dump option and %SystemRoot%\Minidump location. A small dump can omit context that a larger kernel dump retains, but it preserves the stop code, parameters and kernel stack.

Write down what changed before the first crash:

CPU, GPU or memory clock and voltage changes
XMP or EXPO being enabled
a BIOS update or settings reset
newly installed memory or a PCIe device
a cooler, fan or pump change
the load that reliably triggers the crash

That list does not convict anything. It gives you reversible comparisons after the record picks a branch.

Read Parameter 1 and the error record in WinDbg

Open the matching dump in WinDbg. Microsoft’s dump-opening guide documents the File > Open crash dump flow. Its documented first-pass command is:

!analyze -v

Find the WHEA_UNCORRECTABLE_ERROR (124) section and its arguments. Keep the full values for Arg1 and Arg2. Then pass the second value to Microsoft’s WHEA record extension:

!errrec <Arg2 value>

For example, if Arg2 is ffffa10b12345028, the command is !errrec ffffa10b12345028. Do not copy that example address into your own analysis; use the address printed by your dump.

The !errrec reference says the command displays the contents of the WHEA error record. Save the output with the dump. Start with the notification or source type, severity and record-section headings.

If !errrec cannot read the record from a small dump, keep that dump rather than treating the failed command as a diagnosis. For a future crash, use System Properties > Advanced > Startup and Recovery > Settings to choose Automatic memory dump or Kernel memory dump. Microsoft’s system-failure and recovery reference documents both options and their paging-file requirements. A later, larger dump may retain the needed record; it is not guaranteed to make every record readable.

Parameter 1 picks the branch, not the replacement part

Microsoft’s table defines these useful routes:

Parameter 1	Error source	What the branch establishes
`0x0`	Machine check exception	A processor machine-check source reported the condition. Read the record sections before choosing CPU, cache, memory or bus tests.
`0x3`	Nonmaskable interrupt	The platform reported an NMI condition. Use the record and the system or board maker’s diagnostics.
`0x4`	Uncorrectable PCI Express error	Start with the PCIe record and the exact device or port evidence it contains. Do not default to the CPU branch.
`0x5`	Generic hardware error	The source type alone is broad. The record section and platform documentation carry the useful detail.
another value	Another WHEA source	Use Microsoft’s 0x124 table and the section printed by `!errrec`; do not force it into one of the rows above.

The restraint in the machine-check row is deliberate. Microsoft’s hardware-error source documentation says one processor machine-check source can report processor, cache, memory and system-bus errors. “Processor” in the source line therefore does not, by itself, prove a failed processor.

The record can contain processor, platform-memory, PCIe, bus, device, NMI or generic sections. Microsoft’s error-record documentation defines those section families. Treat a section as a routing clue. A single filename, vendor string or bus label is not a purchase order.

Put deliberate tuning back to default

Microsoft lists heat, defective hardware, memory and a processor beginning to fail among 0x124 possibilities. It specifically says to disable overclocking, confirm cooling works and run memory diagnostics.

If you changed a clock, voltage, power limit or memory profile, record the current value and restore only those deliberate changes to their documented defaults. Test the same workload again before making a second change. One change at a time is what tells you whether stability returned.

Entering UEFI settings is also the point to make sure you can retrieve the device’s BitLocker recovery key. Microsoft says a security or hardware change can cause a recovery prompt, and it cannot recreate a lost key. Use its recovery-key instructions before the firmware-settings step. Do not change TPM or Secure Boot settings as part of this diagnosis.

This step tests configuration stability. It does not prove a component is healthy or defective. If the crash continues at defaults, keep the defaults while you isolate the branch.

Follow the record’s branch

Machine-check or processor section

Start with cooling and settings because they are reversible. Confirm that the fans or pump operate and compare CPU temperature under the triggering load with the processor maker’s limit. The CPU overheating guide covers the temperature and cooler checks without turning a hot reading into an automatic replacement.

If the record points toward memory or the crash began with a memory-profile change, use the MEMORY_MANAGEMENT test sequence: default memory speed first, then a real memory test, then one-stick isolation if the test reports errors. A machine check can include memory and bus faults, so this is evidence-led isolation rather than a claim that 0x124 means bad RAM.

If cooling, defaults and memory isolation are clean, keep the dump and exact record output for the system or motherboard maker. A CPU swap is a late isolation test, not the interpretation of a vendor name in WinDbg.

PCIe section or Parameter 1 `0x4`

Record the exact PCIe section fields and compare them with what changed: a new GPU, storage adapter, add-in card, riser, slot or firmware revision. Power down before touching hardware and use the board and device maker’s service instructions for reseating or moving a device. Change one device or slot at a time, then repeat the same workload.

Do not assume every PCIe error is the graphics card. The bus also carries NVMe drives, network adapters and other devices. The record and the board’s slot map should narrow the path before isolation.

Generic, NMI or platform-specific section

Preserve the full record and use the exact computer or motherboard maker’s hardware diagnostics and firmware notes. These branches are where a generic “replace the CPU” answer is least defensible. The platform can add information that Windows’ generic source label does not explain.

What not to do first

Do not reinstall Windows before reading the dump. It does not identify the hardware source and can discard the evidence window.
Do not raise voltages to make the crash disappear. That changes the electrical conditions and creates a second variable.
Do not replace the CPU because WinDbg prints a processor vendor string. A machine-check source can cover cache, memory and system bus errors too.
Do not treat every WHEA-Logger warning as a fatal crash. Preserve the corrected event and compare timestamps, but keep its severity distinct.
Do not buy several parts at once. A pile of simultaneous swaps can hide which comparison mattered.

Microsoft Support’s consumer WHEA fix page also recommends Windows and driver updates, recovery options after a recent change, and general blue-screen troubleshooting. Apply an update or rollback when the timing and record point at that device or change. The WHEA record is what keeps that step targeted.

The stopping rule

Escalate with the dump, !analyze -v output, !errrec output, settings history and isolation result together. Replace a component when the error follows that component or a manufacturer diagnostic condemns it, not because the stop code’s name sounded like a CPU failure.

If the dump is missing or unreadable, keep the system at documented defaults and configure the next dump. The next reproducible crash with a preserved record is more useful than a guess made from the blue screen alone.

Sources

NVMe Expansion Compatibility Checker

LK Wood IV — Sat, 03 Oct 2026 00:00:00 -0500

What this checker answers

An NVMe expansion card can place one or more M.2 drives behind a motherboard PCIe slot. The difficult part is the lane path: a slot may look like x16 while operating with fewer electrical lanes, and a passive multi-drive card needs the host to expose the specific lane split documented for that slot.

This first catalog covers four ASUS motherboard models. Pick the board model and CPU group first, then the slot, adapter topology, and drive count. The result shows the documented electrical lanes, explicit lane mapping, conditional conflicts, and the source document beside the conclusion. Where ASUS does not state a board revision, the result says so.

How each topology is handled

Single-drive adapter: the checker looks for a documented lane path of at least four electrical lanes. It does not decide physical clearance, boot support, firmware behavior, or operating-system support.
Passive dual-drive card: the selected slot needs explicit evidence for two drives, such as a documented x4/x4 mapping or an exact manufacturer-stated maximum for the named adapter.
Passive quad-drive card: the selected slot needs explicit evidence for four drives, such as x4/x4/x4/x4 or an exact manufacturer-stated maximum for the named adapter.
Switched card: a genuine onboard PCIe switch handles downstream division without host bifurcation. The board record alone cannot confirm that exact card’s fit, firmware, boot support, or drive enumeration.

The requested drive count is also checked against the chosen adapter topology. A passive dual card cannot hold three drives, even if the host slot documents more lane groups.

The motherboard tables in this first catalog name ASUS Hyper M.2 adapter models. Their socket-to-lane mapping is evidence for those named cards. A third-party passive carrier needs the same mapping to the active x4 groups; the reported lane count by itself does not establish that its sockets line up.

Read the conflicts before installing

PCIe slots can share lanes or change behavior with a particular CPU group, another populated slot, or an onboard connector. The result repeats the source record’s conditional text. Treat those conditions as part of the result, not as optional notes.

“Not documented” is a deliberate outcome. It does not claim the configuration is impossible. It says the available manufacturer evidence does not establish the requested layout, so the next step is the exact motherboard model’s manual, any manufacturer-stated revision, and the exact adapter documentation.

Hardware Projects

LK Wood IV — Sat, 03 Oct 2026 00:00:00 -0500

Plan without losing the thread

A hardware decision often crosses several calculators. A gaming build may start in the PC Builder, move through GPU comparison and PSU sizing, then return days later. A NAS plan may pair capacity with power cost. Hardware Projects keeps the goal, constraints, supported tool inputs, and dated references under one local project ID.

The workspace does not merge those tools into a new compatibility engine. Each connected tool keeps its own evidence boundary and result language. A product appearing in the project means it was referenced by a tool or template; it does not mean every other saved part works with it.

That boundary matters. I do not treat a saved product list as a compatibility verdict. Suppose an upgrade starts with a graphics-card shortlist, reaches a power estimate, and later needs a motherboard lane check after another drive enters the plan. The project keeps those supported inputs under one title, while each tool still explains what its result establishes, which source or assumption it used, and what the exact manuals and physical inspection must answer before buying or installing a part.

Choose the right way to move a project

Use a limited snapshot link when another person needs the calculator state and product references. The link excludes the use case, private constraints, diagnostic text, and evidence. Opening it creates an unsaved preview with a new ID, so it cannot silently replace a project already stored on that device.

Use the full JSON download for backup or transfer between your own devices. That file includes the private fields omitted from a snapshot. Import also opens a preview and requires an explicit save.

Keep that file private, especially when the constraints or diagnostic notes identify your equipment. Treat it as personal.

Projects are stored in this browser. Clearing browser storage can remove them, and another browser or device cannot see them without a JSON transfer. If browser storage is unavailable, full, or corrupt, the workspace reports the failure instead of replacing the stored record.

Back it up.

Start with a focused route

Start with one decision.

For a new gaming PC or upgrade, start with PC Builder, compare the exact GPUs you are considering, then run the saved load through the PSU calculator.
For a storage server, start with the usable-capacity and fault-tolerance tradeoff in the NAS calculator, then carry its state into the power-cost calculator.
For intermittent faults, open the Diagnostic Workbench from a diagnostic project. Record the symptom, display or hardware path, recent change, tests, and outcome without placing those notes in a shared snapshot.
For ECC or expansion decisions, attach the dated result from the AM5 ECC checker or NVMe expansion checker. Keep the manufacturer evidence and its stated scope beside the project.

Hardware Diagnostic Workbench

LK Wood IV — Sat, 03 Oct 2026 00:00:00 -0500

Capture before changing the machine

The most useful incident record starts with what the machine did, not what you think failed. Write the exact message, indicator, sound, or loss of function. Add the local date and time, workload, and what stayed operational. A monitor that displays No Signal, a screen that goes black and returns, and a PC that loses power are three different observations even when they happen during the same game.

Save volatile evidence before a restart when it is safe to do so. That can include an on-screen error, an event timestamp, a container state, a temperature with its unit, or the name and version of a driver. The workbench does not run commands, change settings, restart services, erase logs, or decide that a part is bad.

Map the full path

Record the path between the thing producing data and the place the symptom appears. For a display that might be GPU → GPU port → cable or adapter → monitor input → monitor. For a drive it can be SSD → M.2 slot or cable → controller → firmware → operating-system driver. For a container it includes the container limit, parent cgroup, host memory, and time window.

Exact hardware and software identity keeps later tests comparable. Include model numbers, firmware, operating system, driver, application, and workload when they matter. A linked product from Hardware Projects stays attached when you edit the diagnostic record here.

Change one variable per controlled test

For each test, write four things:

The one variable changed.
The conditions held constant.
The duration or number of repetitions.
The observed result, including a unit where one applies.

If you changed a cable, driver, power limit, and graphics setting together, record that as an uncontrolled test. It may restore service, but it cannot show which change mattered. Keep destructive actions, firmware changes, and storage writes outside an improvised experiment; use the exact device documentation and a current backup before a step can put data or recoverability at risk.

Blank worksheet for JavaScript-off use

Copy this block into a local text file when browser scripting is unavailable:

Hardware incident title:
Record created (local date and time):
Last updated (local date and time):

Exact symptom:

Hardware and software:

Display, signal, storage, network, or container path:

Trigger, timing, frequency, and workload:

Recent change before the first event:

Observations and evidence:

Tests already run:
- Variable changed:
- Conditions held constant:
- Duration or repetitions:
- Observed result:

Outcome or next evidence checkpoint:

Read each export as a different privacy boundary

Save on this device keeps the Hardware Project in the current browser profile. The project URL contains a local ID, not the notes themselves, and it works only where that local record exists.

Download full JSON creates a complete portable record. It includes the title, linked product references, tool state, every diagnostic field, evidence records, and project dates. Treat that file as private if your notes contain serial numbers, hostnames, addresses, account names, file paths, or log excerpts.

Copy private summary produces readable plain text from the full diagnostic record. Review it before pasting because it can carry the same private details as the form.

Copy share URL without notes creates the limited Hardware Projects snapshot. The shared snapshot omits diagnostic text, evidence, free-form constraints, and the private use-case field. It can retain non-sensitive project structure such as the project type, title, linked product references, and supported tool state.

No browser-local save is a backup. Export the JSON before clearing site data, moving browser profiles, reinstalling the browser, or doing repair work that may affect the operating-system drive.

Docker Exit Code 137: Prove OOMKilled Before Raising Memory

LK Wood IV — Sat, 03 Oct 2026 00:00:00 -0500

By LK Wood IV · 2026-10-03 · ~8 min read · St. Louis County, MO

Docker exit code 137 is a clue, not an OOM verdict. Under GNU Bash’s exit-status rules, a command terminated by fatal signal number N is reported as 128 + N. Linux lists SIGKILL as signal 9, which is why a shell-observed SIGKILL commonly appears as 137. That convention is not proof of the sender or cause: Docker returns the container command’s exit status, so a command can also return 137 itself. Docker documents at least two non-memory ways to send SIGKILL: docker kill uses it by default, and docker stop escalates to it when the process does not exit before its timeout.

Do not restart, recreate, or raise the memory limit yet. Those changes can erase the state and timing that separate a container limit from host pressure, a stop-timeout escalation, an operator kill, or an application-selected exit code.

The job is to bind every observation to the same container ID and time window. Capture first. Change one thing only after the evidence names a cause.

Use the Hardware Diagnostic Workbench to retain that container ID, bounded time window, configured limits, event sequence, kernel or daemon evidence, cgroup counters, and each later test. The record does not interpret exit 137 as an OOM verdict.

The four records to save first

Set the container name or ID, plus a bounded window that covers a few minutes before and after the failure. Use timestamps with an explicit timezone offset or Z; Docker says an unqualified timestamp uses the client machine’s local timezone.

CONTAINER='replace-with-name-or-id'
SINCE='2026-10-03T18:20:00-05:00'
UNTIL='2026-10-03T18:30:00-05:00'

First, save the stopped container’s identity, state and configured memory controls. docker inspect is read-only and works on stopped containers.

docker inspect --type=container \
 --format 'id={{.Id}} name={{.Name}} image={{.Config.Image}} exit={{.State.ExitCode}} oom_killed={{.State.OOMKilled}} started={{.State.StartedAt}} finished={{.State.FinishedAt}} error={{json .State.Error}} memory={{.HostConfig.Memory}} reservation={{.HostConfig.MemoryReservation}} memory_swap={{.HostConfig.MemorySwap}} oom_kill_disable={{json .HostConfig.OomKillDisable}} restart_count={{.RestartCount}}' \
 "$CONTAINER"

Second, capture Docker’s event history for that exact container and interval. Docker exposes separate oom, kill, die, stop and restart events. Its retained event history is limited to the last 256 events, which is another reason to collect it before doing more work on a busy host.

docker events \
 --since "$SINCE" \
 --until "$UNTIL" \
 --filter type=container \
 --filter container="$CONTAINER" \
 --format '{{json .}}'

Third, save application output from the same interval. This can show an orderly shutdown request, an application-level allocation failure, or the last completed operation. Absence of a useful final line is not proof of a kernel kill.

docker logs --timestamps --since "$SINCE" --until "$UNTIL" "$CONTAINER"

Fourth, check the host kernel and Docker daemon around those timestamps. journalctl accepts space-separated date and time values for --since and --until; the separate UTC values below describe the same interval as the Docker variables above and work on systemd releases that do not accept that RFC 3339 form. These read-only queries explicitly select the current boot:

JOURNAL_SINCE='2026-10-03 23:20:00 UTC'
JOURNAL_UNTIL='2026-10-03 23:30:00 UTC'

journalctl -k --boot=0 --since "$JOURNAL_SINCE" --until "$JOURNAL_UNTIL" --no-pager \
 | grep -Ei 'out of memory|oom-kill|killed process|memory cgroup'

journalctl -u docker.service --boot=0 --since "$JOURNAL_SINCE" --until "$JOURNAL_UNTIL" --no-pager

If the incident occurred before the current boot, run journalctl --list-boots, choose the boot ID whose recorded interval contains the incident, and replace --boot=0 in both commands with --boot=THE_32_CHARACTER_BOOT_ID. If the host does not use systemd, use its actual kernel and daemon log mechanism. Do not substitute an unbounded dmesg | tail and then assume the last message belongs to this incident.

Read the evidence as a set

What you captured	What it establishes	What it does not establish
Exit code `137` only	The container command reported 137	Who or what chose that value
`State.OOMKilled=true`	Docker recorded an OOM-killed state	Which memory boundary caused it, or how much memory is safe
Docker `oom` event in the same window	Docker emitted an OOM event for that container	Whether the configured limit is simply too small, the host is overcommitted, or the workload is leaking
`kill` followed by `die`, with the signal and matching time	A signal was sent in Docker’s event sequence	Who initiated it unless the surrounding daemon/orchestrator record says so
Kernel OOM record naming the victim/cgroup	The kernel selected a process under memory pressure	That blindly raising this container’s limit protects the host
The exact cgroup’s local `oom` counter increased	An allocation in that cgroup was about to fail because of that cgroup’s memory limit	Which process was selected, or how much memory is safe
cgroup `oom_kill` counter increase	An OOM killer killed a process in that cgroup	Which cgroup supplied the limiting boundary, or that the killed process was the container’s PID 1
`State.OOMKilled=false` and no memory evidence	No OOM cause has been demonstrated	That memory pressure is impossible

That last row prevents a reasoning error. A false flag is not permission to declare “not memory,” just as a 137 is not permission to declare “memory.” Keep the cause unknown until another record closes the gap.

Separate a container boundary from host pressure

The memory value in the inspect record is the hard memory limit in bytes. A zero means Docker did not configure a per-container hard limit. It does not mean the host, VM, systemd unit, parent cgroup, or orchestrator is unlimited.

Docker’s resource documentation distinguishes a hard --memory limit from a softer --memory-reservation. It also warns that without constraints a container can use as much memory as the host kernel scheduler allows, and that host OOM can select processes when the machine cannot perform essential work.

Use this split:

A nonzero container limit and matching Docker oom event do not identify the limiting boundary by themselves. A kernel OOM record naming that cgroup as the limiting boundary, or a same-window increase in oom from that exact cgroup’s memory.events.local, corroborates the container boundary. An oom_kill increase alone only says a process in the cgroup was killed by an OOM killer. Once the boundary is identified, measure the workload and decide whether the limit, the application’s own memory configuration, or a leak is wrong.
No container hard limit plus a host kernel OOM record points to host or parent-boundary pressure. Giving one container more memory is not a fix; it has no private boundary to raise.
A kill or stop-timeout sequence with no correlated memory evidence points away from an OOM diagnosis. Docker documents that docker stop sends the configured stop signal first and forcibly sends SIGKILL after the timeout.
No correlated record stays unresolved. Preserve the worksheet, increase observability, and wait for a second incident rather than editing limits by guesswork.

Read cgroup counters only where the host exposes them

Do not paste a path from someone else’s machine. Docker’s cgroup driver, systemd integration, parent cgroup and cgroup version determine the location. Locate the container’s cgroup through that host’s runtime configuration, replace the placeholder assignment below with the path you verified, then read the files that actually exist there. These commands only read those files.

For cgroup v2, read the following Linux kernel memory-interface files with the read-only commands below:

CGROUP_PATH='/replace/with/verified/container-cgroup-path'
cat "$CGROUP_PATH/memory.max"
cat "$CGROUP_PATH/memory.high"
cat "$CGROUP_PATH/memory.events"
cat "$CGROUP_PATH/memory.events.local"

memory.max is the hard limit. memory.high applies reclaim pressure but does not itself invoke the OOM killer. In memory.events, oom counts occasions when allocation was about to fail at the limit, while oom_kill counts processes in the cgroup killed by an OOM killer. The regular file is hierarchical; memory.events.local is local to that cgroup.

For a host still using cgroup v1, the kernel documents the older files below. The same documentation marks the v1 soft-limit and OOM-control interfaces deprecated, so read them as legacy evidence rather than advice for new configuration.

CGROUP_PATH='/replace/with/verified/container-cgroup-path'
cat "$CGROUP_PATH/memory.limit_in_bytes"
cat "$CGROUP_PATH/memory.usage_in_bytes"
cat "$CGROUP_PATH/memory.failcnt"
cat "$CGROUP_PATH/memory.oom_control"

If the container was removed or its cgroup disappeared, say that the counters were unavailable. Do not replace missing evidence with a guessed path or a counter from a new container.

Copy this incident worksheet before changing anything

Docker exit-137 incident

Observed at (timestamp + timezone):
Host name / VM:
Docker Engine version:
Container name:
Full container ID:
Image + immutable digest if available:
Compose project / service or launcher:

State
 ExitCode:
 OOMKilled:
 StartedAt:
 FinishedAt:
 RestartCount:
 State.Error:

Configured boundary (bytes as reported by inspect)
 Memory:
 MemoryReservation:
 MemorySwap:
 OomKillDisable:
 Parent/orchestrator limit, if separately proven:

Same-window evidence
 Docker oom event: yes / no / unavailable
 Docker kill event + signal:
 Docker die event + exitCode:
 Stop/restart event immediately before death:
 Kernel OOM record naming process/cgroup: yes / no / unavailable
 cgroup version and exact path:
 memory.events(.local) before change, if retained:
 Application's last timestamped log line:

Classification
 [ ] container/parent OOM is correlated
 [ ] host OOM is correlated
 [ ] stop timeout or external signal is correlated
 [ ] application returned 137 without proven SIGKILL
 [ ] unknown — preserve evidence and observe again

One change to test next:
Result and timestamp:

The empty boxes matter. “Unavailable” is evidence quality; it is not a “no.”

Choose the next action from the proven branch

Container or parent memory boundary proven: compare the configured boundary with the application’s measured peak and memory model. A Java heap, Node heap, database cache, shared memory, native allocation and filesystem cache do not all appear under one application setting. Fix the thing consuming memory or set a tested boundary with headroom. The Docker RAM planner estimates future host capacity for a known stack; it does not diagnose this incident and should not replace the capture above.

Host pressure proven: inventory every workload and host reserve before changing one container. Docker warns that the Linux kernel can kill processes, including Docker or other important applications, when the host cannot satisfy essential memory work. Moving the failure from one container to the whole host is regression, not remediation.

Stop-timeout escalation proven: find why PID 1 did not handle the configured stop signal or finish within the timeout. Docker notes that shell-form ENTRYPOINT and CMD run below /bin/sh -c, which does not pass signals to the executable. Fix signal handling or set a justified grace period; do not change memory because the final number happened to be 137.

Manual/orchestrator kill proven: trace the actor from the daemon, service, scheduler or automation log. The container behaved as instructed.

Cause still unknown: keep the worksheet and improve capture for the next occurrence. A restart may restore service, but it does not turn an unknown cause into an OOM diagnosis.

What I verified and what I did not

I verified the command syntax and field semantics against Docker’s current documentation and the cgroup file meanings against current Linux kernel documentation on 2026-10-03. I did not run an OOM experiment on a Docker host for this article, so none of the worksheet values or branches is presented as a TechFuelHQ measurement.

The article also does not assume Kubernetes. Pod eviction, Kubernetes OOMKilled status, pod limits and node-pressure decisions add another control plane and need their own evidence path.

Sources

Docker Engine: container exit status — Docker returns the command’s exit status when the command runs and exits.
GNU Bash: Exit Status — Bash reports a command terminated by fatal signal N as 128 + N; read 2026-10-03.
Linux signal(7) — standard signal behavior and the signal-number table identifying SIGKILL as 9; read 2026-10-03.
Docker inspect — low-level object data, JSON output and Go-template field selection; read 2026-10-03.
Docker system events — event types, time filters, container filters, JSON Lines output and 256-event retention; read 2026-10-03.
Docker container kill — default SIGKILL behavior; read 2026-10-03.
Docker container stop — initial stop signal and forced SIGKILL after timeout; read 2026-10-03.
Docker resource constraints — no-limit default, hard and soft controls, host OOM risk, swap behavior and OOM-killer warning; read 2026-10-03.
Docker Compose service attributes — current mem_limit, mem_reservation, memswap_limit and OOM-related keys; read 2026-10-03.
systemd journalctl — accepted time forms, current/selected boot filtering and boot inventory; read 2026-10-03.
systemd time syntax — calendar and UTC time syntax referenced by journalctl; read 2026-10-03.
Linux kernel cgroup v2 memory controller — memory.max, memory.high, memory.events and memory.events.local; read 2026-10-03.
Linux kernel cgroup v1 memory controller — legacy limit, usage, failure and OOM-control files plus deprecation status; read 2026-10-03.

If the incident is actually disk pressure rather than memory pressure, the Docker cleanup guide separates disposable cache and images from volumes that can contain the only copy of data.