Think Like a Computer
No ads, no affiliate links, no software recommendations you did not ask for.

Understand the failure, then fix it

Understand the failure. Then fix it.

Most troubleshooting pages hand you five commands and hope one works. These explain what the machine is actually complaining about first, because a fix you understand is one you can adapt when the next machine fails differently.

Boot errors and stop codesHow networking works

There is a particular kind of technical article that gives you a numbered list, tells you to run each command, and never says what any of them do. Sometimes it works. When it does not, you are exactly where you started, with no idea which step was the wrong assumption.

What this site does differently

Every page starts with what the error means. A boot error naming the BCD is telling you something specific about where the firmware looked and what it found; a blue screen after moving a disk to new hardware is a driver problem with a predictable cause. Once that is clear, the repair steps stop being a ritual and become a decision you can make.

Why the networking section exists

Half of what looks like a broken application is a network doing exactly what it was configured to do. One-way audio on a call, a game that reports strict NAT, a port-forward rule that works from outside and not from inside — these are all the same handful of mechanisms seen from different angles. Learn the mechanism once and the symptoms stop being separate problems.

The old site

This domain ran a Windows and networking blog from 2011 onwards, and some of its pages were widely linked. Where a page here covers the same problem as one of those, the old address redirects to it. The material is rewritten rather than restored — much of it described versions of Windows that no longer exist — but the reader arriving from a decade-old forum link should still land on the answer they were promised.

Boot failures and stop codes

The screens that stop a machine before it starts. What each code is actually reporting, and the repair order that does least damage first.

See all →

How networks actually work

Routing, NAT, DNS and the rest — the mechanics rather than the analogies, so the next problem is one you can reason about instead of search for.

See all →

When the connection is the problem

One-way audio, strict NAT, port forwarding that does nothing, VPNs that will not pass. Different symptoms, mostly the same cause.

See all →

Permissions and the file system

Access denied on a folder you own, permissions that changed themselves, drives that will not map. Where the permission actually lives.

See all →

The questions that bring people here

My PC says "File: \Boot\BCD" with error 0xc000000f. Is the drive dead?

Usually not. That message means the firmware found a boot device but could not read a usable boot configuration on it, which is far more often a damaged BCD store, a changed boot order or a disk that lost its active flag than a failed drive. Confirm the disk is visible from a recovery environment before assuming hardware.

Why does Windows blue-screen after I move the disk to another PC?

Because the copy of Windows on that disk only loads the storage controller driver it needed on the old machine. On different hardware that driver is wrong, Windows cannot read the disk it is booting from, and it stops with 0x0000007B. Switching the new machine's SATA mode to match the old one is often enough to get it booting so the driver can be fixed properly.

I am an administrator, so why does Windows say access denied?

Being in the Administrators group is not the same as running with administrative rights. User Account Control gives you a filtered token for ordinary work, and the folder's permission list may not grant your account anything directly. The fix is usually to look at the actual ACL rather than to take ownership, which causes its own problems.

My game says my NAT is strict. What does that actually mean?

It means your router's translation table will not accept an inbound packet from a peer it has not already been talking to on that exact port, so direct peer-to-peer connections fail and traffic is relayed instead. UPnP resolves it for most people; where it does not, the cause is usually two layers of NAT or a carrier-grade NAT you do not control.