Error map
Automatic Repair couldn't repair your PC Automatic Repair couldn't repair your PC — Log file: C:\Windows\System32\Logfiles\Srt\SrtTrail.txt
Windows · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (8)
EC2 status check failed: Instance reachability check failed (1/2 checks passed)
AWS can reach the host, but the operating system inside the instance isn’t responding — kernel panic, full disk, broken network c…
The User Profile Service failed the sign-in. User profile cannot be loaded.
Windows can’t load your profile — the profile registry entry or NTUSER.DAT is corrupt, or the Default profile is damaged.
Blue Screen: CRITICAL_PROCESS_DIED (Stop code 0x000000EF)
A process Windows can’t run without (csrss, wininit, smss…) stopped unexpectedly, so the system halted.
Your PC needs to be repaired: The Boot Configuration Data file is missing some required information (0xc000000f)
Windows Boot Manager can’t find a valid BCD entry or boot files — after disk changes, failed updates, cloning or dual-boot change…
Windows Error 0x80004005 (E_FAIL): Unspecified error
A generic failure code — the operation failed for a reason the component didn’t report precisely. Context decides the fix.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
The kernel booted but couldn’t mount the root filesystem — usually a missing or broken initramfs after a kernel update.
error: unknown filesystem. Entering rescue mode... grub rescue>
GRUB can’t find or read the partition holding its files — common after resizing/deleting partitions or installing Windows alongsi…
Blue screen: INACCESSIBLE_BOOT_DEVICE (0x0000007B)
Windows lost access to the system drive during boot — storage driver/controller mode change, failed update, or disk/BCD problems.
Two steps away (21)
An error occurred (UnauthorizedOperation): You are not authorized to perform this operation. Encoded authorization failure message: ...
The IAM identity is missing an EC2 (or related) permission. The encoded message tells you exactly which action and resource were…
InsufficientInstanceCapacity: We currently do not have sufficient capacity in the Availability Zone you requested
AWS has no free capacity for that instance type in that Availability Zone right now.
VcpuLimitExceeded: You have requested more vCPU capacity than your current vCPU limit
Your account’s On-Demand (or Spot) vCPU quota for that instance family and region is used up.
Windows Error 0x80070005 (E_ACCESSDENIED): Access is denied
Windows refused an operation because the account or process lacks permission — seen in Windows Update, installers, Task Scheduler…
Windows Error 0x80070002: The system cannot find the file specified
A file or registry entry Windows expected is missing — common in Windows Update, backups and app installs.
Windows error 0x8007000D (The data is invalid)
Windows read update, installer or setup data that is corrupted or incomplete.
Blue Screen: IRQL_NOT_LESS_OR_EQUAL (Stop code 0x0000000A)
A driver accessed memory at an interrupt level where that’s not allowed — almost always a faulty or incompatible driver, sometime…
Blue Screen: MEMORY_MANAGEMENT (Stop code 0x0000001A)
Windows detected a severe memory-management error — commonly faulty RAM, unstable memory settings or a bad driver.
Blue screen: DPC_WATCHDOG_VIOLATION (0x00000133)
A driver spent too long at high priority (DPC level) — typically SSD/NVMe firmware, storage controller drivers (iaStorA.sys) or g…
Windows Error 0x800F081F: The source files could not be found
DISM or “Turn Windows features on or off” (often .NET Framework 3.5) couldn’t find the files needed to install the feature.
Windows error 0x80070057 (The parameter is incorrect)
A Windows component received an invalid value — common in Windows Update, Backup, DISM (Error: 87) and disk formatting.
The trust relationship between this workstation and the primary domain failed
The computer’s machine account password no longer matches Active Directory, so domain logins fail.
Killed / Out of memory: Killed process (Linux OOM killer)
The kernel ran out of memory and killed a process to recover — the program just prints “Killed” (exit code 137).
bash: /bin/rm: Argument list too long
A glob like * expanded to more file names than the kernel allows in one command (ARG_MAX), so the command never ran.
cannot execute binary file: Exec format error
The program was built for a different CPU architecture or OS — e.g. an x86_64 binary on an ARM machine (Raspberry Pi, Graviton, A…
bash: command not found
The shell can’t find an executable with that name in any directory on your PATH.
E: Could not get lock /var/lib/dpkg/lock-frontend — is another process using it?
apt can’t run because another package operation (often automatic updates) holds the dpkg lock.
fork: Cannot allocate memory / ENOMEM
The kernel refused a memory allocation — RAM and swap are exhausted, or overcommit/cgroup limits block it.
Blue screen: WHEA_UNCORRECTABLE_ERROR (0x00000124)
The hardware reported an error Windows couldn’t recover from — CPU, RAM, overclock/undervolt, overheating or power delivery.
Blue screen: UNEXPECTED_STORE_EXCEPTION (0x00000154)
The memory/store manager hit an exception — commonly a failing SSD/HDD, outdated storage drivers, or antivirus.
Blue screen: CLOCK_WATCHDOG_TIMEOUT (0x00000101)
A CPU core stopped responding to clock interrupts — usually overclocking/undervolting, BIOS/microcode bugs, or CPU/power hardware…
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException