TechClassy diagnostic route
Driver files
Identify what a named .sys file can establish—and what it cannot establish—before changing drivers or security software.
Try a scenario
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
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.
After the first check
Read the evidence this route produces
Paste bounded driverquery or PnPUtil enumeration text and extract driver, package, provider, class, version, signer, state, path, and device-relation facts without recommending a download or naming a culprit.