The Hidden World of Hardware Drivers
Your Windows 11 computer is a collection of hardware components built by dozens of different manufacturers. The graphics card might be from NVIDIA, the Wi-Fi chip from Intel, and the audio controller from Realtek. For Windows to actually communicate with these physical components, it requires highly specific translator software called “drivers.”
When a computer suddenly starts suffering from the “Blue Screen of Death” (BSOD) after a system update, the culprit is almost always a corrupted or outdated third-party hardware driver. While you can use the graphical Device Manager to inspect drivers one by one, clicking through fifty different hardware categories to find a specific driver version is incredibly tedious.
To instantly generate a massive, comprehensive list of every single driver actively installed on your Windows 11 machine, you can use the driverquery command.
Step 1: Open the Command Prompt
Because you are querying core system hardware files, you should run this tool as an administrator.
- Press the Windows Key, type
cmd. - Right-click on Command Prompt and select Run as administrator.
Step 2: Running a Basic Query
To see a simple list of all drivers, simply type the command and press Enter:
driverquery
The terminal will output a long table containing three columns:
- Module Name: The internal system name of the driver (e.g.,
nvlddmkm). - Display Name: The human-readable name of the hardware (e.g.,
NVIDIA Windows Kernel Mode Driver). - Driver Type: Indicates whether it is a Kernel driver, a File System driver, etc.
- Link Date: The exact date and time the driver was originally compiled by the manufacturer.
Step 3: Finding Outdated Drivers
The Link Date column is the most important piece of troubleshooting information. If your computer keeps crashing in 2026, and you see a crucial audio driver that has a Link Date of “10/14/2012”, that ancient driver is highly likely to be the cause of your system instability.
However, scrolling through hundreds of lines in the command prompt is difficult. It is much easier to export this entire list to a text file on your desktop so you can search through it using Notepad.
You can do this by using the standard > redirect symbol:
driverquery > "%UserProfile%\Desktop\DriverList.txt"
Step 4: Viewing the Actual File Paths (Verbose Mode)
If you identify a suspicious driver and you want to know exactly where the physical .sys file is located on your hard drive (so you can manually delete it in Safe Mode), the standard query will not tell you.
You must run the command in Verbose mode by adding the /V flag.
driverquery /V
The output will now be massive, including the exact file path (e.g., C:\Windows\System32\drivers\RTKVHD64.sys), the amount of RAM the driver is consuming, and its current running state (Running or Stopped).
Step 5: Exporting to Excel (CSV Format)
If you are an IT administrator auditing the drivers on a remote employee’s laptop, a messy text file is not ideal. You can force driverquery to output the data in a perfect Comma Separated Values (CSV) format using the /FO (Format Output) flag.
driverquery /V /FO CSV > "%UserProfile%\Desktop\DriverAudit.csv"
This generates a pristine CSV file directly on the desktop. When you double-click it, it will open perfectly inside Microsoft Excel, allowing you to instantly sort the columns, filter out Microsoft drivers, and quickly isolate the outdated third-party software causing the crashes.