TechClassy

TechClassy diagnostic route

Error Checker

Recognize a code, exact message, driver filename, Stop Code, or command result and route it to the right diagnostic family.

Use the exact code, final message, Stop Code, driver filename, or final SFC/DISM line — not a description from memory.

Runs in this browser — no upload, no account, nothing stored

Ctrl/⌘ + Enter

Real cases
Resume a saved session — paste a Resume Capsule

The capsule is validated and restored only in this browser. An invalid capsule changes nothing.

Complete, source-reviewed pages

Browse the supported diagnostic records

0x80070005 Access deniedWindows received an access-denied response while an update-related operation tried to read, write, or register a protected resource. 0x800f081f Source files not foundWindows servicing could not locate repair source files that match the installed image and requested operation. 0x80073712 Component manifest is damaged or missingWindows servicing found required component data in an inconsistent, damaged, or missing state. 0x800f0831 Required package dependency is missingWindows servicing could not resolve a package or manifest dependency needed by the update. 0x80070070 Insufficient disk spaceThe operation could not continue because the target volume did not have enough usable free space. 0x800705b4 Operation timed outAn update-related operation exceeded its allowed time before returning a completed result. 0x80070002 File not foundWindows could not find a file required by the current update, Store, or servicing operation. 0x80248007 Update data was not foundThe Windows Update data store could not supply information required for the requested update operation. 0x80d02002 Delivery or download timeoutThe update delivery path did not complete within the expected time window. 0xc1900101 Driver-related upgrade rollback familyWindows Setup rolled back an upgrade after a driver or low-level device interaction failed during setup. 0x80070426 Service is not activeA required Windows service was not active when the operation requested it. 0x8007001f A device attached to the system is not functioningAn update or setup operation received a device-level failure while interacting with attached hardware or its driver stack. Code 10 Device cannot startWindows could not start the device using its current driver and configuration. Code 22 Device is disabledThe device is disabled in Device Manager. Code 28 Drivers are not installedWindows does not currently have a usable driver installed for the device. Code 31 Windows cannot load the required driversWindows found the device but could not load the drivers required for it. Code 32 Driver service is disabledA driver service required for the device is disabled or not configured to start. Code 43 Device reported a problemWindows stopped the device because the device or its driver reported a failure. Code 45 Device is not connectedWindows currently treats the device as physically or logically disconnected. Code 48 Driver is blockedWindows blocked the driver from starting because it is known to have a problem with Windows. MEMORY_MANAGEMENT Severe memory-management errorWindows stopped because the kernel detected a severe inconsistency in memory management. IRQL_NOT_LESS_OR_EQUAL Invalid kernel memory access at a raised IRQLKernel-mode code attempted an invalid or pageable memory access while running at an interrupt level where that access was not allowed. DRIVER_POWER_STATE_FAILURE Driver did not complete a power-state transitionWindows stopped after a driver failed to complete a required power-management request in time. DPC_WATCHDOG_VIOLATION A high-priority kernel task exceeded its time limitWindows detected that a deferred procedure call or interrupt routine ran too long or the system spent too long at an elevated interrupt level. CRITICAL_PROCESS_DIED A critical Windows process terminatedA process required for Windows to continue safely terminated or became corrupted. PAGE_FAULT_IN_NONPAGED_AREA Invalid reference to nonpaged memoryKernel-mode code referenced invalid memory that should have remained resident and valid. INACCESSIBLE_BOOT_DEVICE Windows lost access to the boot volumeWindows could not access the system partition during startup. KERNEL_SECURITY_CHECK_FAILURE Critical kernel data structure corruptionThe kernel detected corruption of a critical internal data structure and stopped to protect system integrity. SFC: no integrity violations No protected system-file integrity violation detectedSFC completed and did not find an integrity violation in the protected system files it checked. SFC: repaired corrupt files Protected system-file corruption was found and repairedSFC found corrupt protected system files and reported that it repaired them successfully. SFC: unable to repair some files Protected system-file repair is incompleteSFC detected protected system files that it could not repair. SFC: could not perform the requested operation SFC did not complete its scan or repair operationWindows Resource Protection could not perform the requested SFC operation, so the output does not establish whether protected files are healthy. DISM: restore completed The Windows image repair completed successfullyDISM reported that the restore operation completed successfully for the targeted image. DISM: source files not found DISM could not obtain matching repair source filesDISM could not locate or use source files that match the Windows image being repaired. bddci.sys Bitdefender-related driver filenamebddci.sys is commonly associated with a Bitdefender driver component, but its appearance in crash evidence does not prove the security product originated the failure. ntoskrnl.exe Windows kernel imagentoskrnl.exe is the Windows kernel image. It commonly appears in crash stacks because the kernel handles the stop, not because the file itself is necessarily the root cause. ntfs.sys Windows NTFS file-system driverntfs.sys is a Microsoft file-system driver. Its appearance can involve storage, file-system, filter-driver, memory, or device paths and is not a root-cause verdict. netio.sys Windows network I/O system drivernetio.sys participates in the Windows networking stack. A crash reference can involve network filters, VPNs, security software, drivers, or memory corruption without proving which component initiated it. kbdclass.sys Windows keyboard class driverkbdclass.sys is a Microsoft keyboard class driver. Its presence in a crash stack can reflect input filters, device drivers, or broader memory corruption and needs the Stop Code and stack context. ERR_PROXY_CONNECTION_FAILED Browser could not connect through the configured proxy pathChromium reported that the connection attempt through the configured proxy did not succeed. ERR_QUIC_PROTOCOL_ERROR The browser's QUIC connection failedChromium reported a failure while using the QUIC transport path. The message does not establish whether the browser, network, VPN, proxy, firewall, or server ended the path. 0x80370106 Windows Sandbox or virtualization stack could not start the virtual environmentThe Sandbox launch path did not establish the virtualization environment it needed. 0x80370102 Required virtualization support is unavailableThe requested virtualization environment could not start because required hypervisor or virtualization support was not available to Windows. Windows memory dump Check whether useful crash evidence already existsA small memory dump can preserve bug-check parameters and a limited view of the crash state. It can support diagnosis but does not automatically prove a root cause. Windows Hello unavailable Biometric sign-in option is unavailable or not recognizedWindows Hello availability depends on supported hardware, device enumeration, drivers, sign-in configuration, policy, and the current Windows state. Internal disk shown as removable Windows or firmware reports an internal storage port as hot-pluggableA disk can appear in the removable-device interface when the storage controller, firmware, port metadata, or driver reports that connection as hot-pluggable. bad_module_info Windows recorded an application crash without a unique root-cause codebad_module_info is an application-crash label seen in some Windows error records. It is not a uniquely identifying Windows component or a root-cause verdict.

After the first check

Read the evidence this route produces

Paste a bounded msinfo32 or DxDiag text report and extract the Windows build, system model, firmware mode, memory, DirectX, display-driver, and explicitly reported problem-device facts without uploading the report.

Windows System Information Snapshot ReaderNo upload · bounded excerpt · source-governed interpretation

Local-first utility

Privacy

The diagnostic parser, evidence readers, verification loop, and Evidence Pack run in your browser. TechClassy does not intentionally store the raw text you paste, Event Viewer or update-log excerpts, full command output, usernames, local file paths, dump files, device serial numbers, observations, parsed summaries, or generated Evidence Packs.

No advertising, analytics, session replay, account system, upload surface, or third-party diagnostic script is loaded in this release. Standard hosting security logs may contain request metadata such as time, requested path, and network information; diagnostic and evidence text is not sent as a URL parameter or API body by the tool.

Use boundary

TechClassy organizes evidence and reviewed next checks. It is not a substitute for Microsoft, an OEM, an employer's IT team, or a qualified repair professional. Results distinguish confirmed facts from possible causes and do not guarantee a repair.

Back up important data before making system changes. Stop when an action requires credentials, firmware changes, disk work, account recovery, or a command whose prerequisites you cannot verify.

Independent operation

This is a newly researched, independently operated diagnostic product. It does not claim to be the prior TechClassy editorial team or a continuation of prior authorship.

Open the permanent page