## Prelude: “It’s Not Software Until It’s Hardware”
It started, as these things usually do, with a crash.
My desktop — a perfectly respectable Ryzen 7 5700X rig with an RTX 4070 Ti Super — had been running a perfectly respectable gaming setup. Water-cooled CPU, decent board, 32GB of DDR4, and a Lian Li case that probably cost more than it should. Everything was fine.
Then the blue screens started.
Not just any blue screens. *Kernel-mode* blue screens. The kind that mean something in the silicon decided to have a disagreement with Windows. I did what any of us would do: I restarted, crossed my fingers, and hoped it was a driver issue.
It was not a driver issue.
—
## The Investigation Begins
Two distinct crashes emerged from the wreckage of memory dumps:
**Crash #1:** `KMODE_EXCEPTION_NOT_HANDLED` (0x1E) — The GPU was screaming about a power exception. Not a software crash. A *hardware* crash. Something was wrong at the electron level.
**Crash #2:** `CRITICAL_PROCESS_DIED` (0xEF) — Windows’ kernel decided a critical process had shuffled off this mortal coil. Same symptom, slightly different flavour.
Both happened under GPU load. Both happened during gaming. That is a clue.
When your computer only dies when the graphics card is working hard, you don’t blame Windows. You start looking at the card, the power, and the thermal paste — in that order.
—
## The Hardware Autopsy
Here’s what I was working with:
| Component | Model |
|———–|——-|
| CPU | Ryzen 7 5700X (water-cooled, because I’m not an animal) |
| GPU | RTX 4070 Ti Super — less than a year old |
| PSU | Antec 850W High Current Gamer — older than my patience |
| Motherboard | ASUS B450-F Gaming |
| RAM | 32GB DDR4 |
| Case | Lian Li O11 Dynamic |
A reasonable machine. Nothing exotic. Nothing that *should* blue screen during a gaming session unless something is genuinely wrong.
—
## The Smoking Gun: 12VHPWR Overdraw
HWiNFO64 was deployed. Data was captured. And there it was — ugly as a Windows Aero theme:
| Metric | Reading | Rating |
|——–|———|——–|
| 12VHPWR Current | 16.66A | ~8.3A rated |
| 12VHPWR Power | ~200W | ~110W rated |
| Power Deviation | 10-15% | <5% healthy |
| GPU Hot Spot | 84°C | Thermal limit |
The RTX 4070 Ti Super draws power through a 12VHPWR connector rated for roughly 110 watts. My Antec PSU was pushing nearly *double* that through a single connector. That’s not a surge. That’s a sustained electrical overload.
But how? The PSU is 850W. The rig doesn’t draw that much total power. Where was the extra wattage coming from?
Then I found it.
**The Antec’s GPU power cables were wired incorrectly.** Both 8-pin PCIe connectors on the GPU adapter were running off the *same* PSU cable and rail. The GPU was pulling 200W through a connector rated for 110W. Every gaming session was a controlled burn — until it wasn’t.
Additionally, the GPU Hot Spot was pinned at its thermal limit and the Power Reporting Deviance was sitting at 10-15% — when healthy is under 5%. The card was thermally throttling and electrically strangled simultaneously.
—
## The Fix: Reroute and Pray
The solution was embarrassingly simple.
I rerouted the GPU power adapters to use **two separate PSU cables on two separate rails**, instead of both connectors sharing one cable. The 12VHPWR connector was no longer being asked to carry double its rated load.
Was the PSU at fault? Technically no — it’s an 850W unit, and the system wasn’t exceeding total wattage. The issue was *distribution*, not capacity. The cables were the problem. I found the problem before I had to buy a new PSU.
Shin-Etsu Micro-Si thermal paste was also applied to the CPU during the process — the 5700X was running warm, and the best paste in my arsenal deserved to be used. Not directly related to the crashes, but a worthwhile upgrade nonetheless.
—
## Post-Fix Data: A Clean Bill of Health
After the cable fix, a fresh HWiNFO64 log showed the difference:
| Metric | Before Fix | After Fix |
|——–|———–|———-|
| 12VHPWR Power | ~200W (over spec) | 35-46W (normal) |
| 12VHPWR Voltage | Fluctuating | 12.27-12.31V (stable) |
| Power Deviation | 10-15% | 0.9-8% |
| GPU Hot Spot | Pinned at 84°C | 84-89°C under load |
The overdraw pattern was gone. The connector was no longer being tortured. The system was finally operating within spec.
—
## The Verdict
**This was a user defect, not a PSU failure.** When I upgraded, my old card was a 3070 and it had no issues with the single cable/rail, I just didn’t also correct the cabling. Live and learn and be very happy neither the GPU or PSU ended it’s run in a blaze of glory.
The fix was free. The diagnosis took longer than the repair.
—
## Will It Stay Fixed?
Probably. The dual-cable fix properly distributes load across two cables, each rated for the task.
If the crashes return, the obvious next step is a new PSU — something like the **Corsair RM850x** or **Seasonic Focus GX-850 V4**. Both are 850W Gold units with native 12VHPWR, full modular cabling, and a 10-year warranty. They’re the reliable, well-reviewed options that won’t cause problems.
But for now? The rig is stable. The 12VHPWR is within spec. The BSODs have stopped.
Sometimes the answer isn’t a new GPU or a new CPU. It’s just… better cable management.
—
*Special thanks to Ada — who spent far too long staring at HWiNFO64 logs so I didn’t have to.*
Leave a Reply