Download BlueScreenView for Windows

Yes, BlueScreenView is completely safe. It is developed by Nir Sofer under the NirSoft brand, one of the most respected independent Windows utility developers since 2001. The tool has been recommended by Microsoft MVPs, BleepingComputer editors, and IT professionals worldwide for over a decade.

The official BlueScreenView download is a small ZIP file (approximately 83 KB for 32-bit, 146 KB for 64-bit) that contains only the executable and a readme file. It does not install any background services, browser toolbars, or bundled software. Because it is a portable application, it writes nothing to your Windows registry and makes zero changes to your system files. The tool only reads existing crash dump files from C:\Windows\Minidump — it never modifies or deletes them.

• No installation required — extract and run directly
• No internet connection needed during operation
• Does not require elevated privileges for basic usage (admin needed only for accessing system dump folders)
• Source behavior is fully documented on the official NirSoft page

Pro tip: Some antivirus programs flag NirSoft utilities as potentially unwanted programs (PUPs) because of the command-line export features. These are false positives. You can verify the download hash against the values posted on the NirSoft website.

Download BlueScreenView from our verified link on the download section to ensure you get the authentic file.

BlueScreenView is 100% free from malware, spyware, and adware. NirSoft utilities have been scanned and verified by major security vendors for years, and the official distribution has never contained any malicious code.

The entire application is a single executable file (BlueScreenView.exe) under 150 KB. There are no hidden DLLs, no phone-home connections, and no data collection of any kind. BlueScreenView operates entirely offline — it reads local minidump files on your hard drive and displays the crash information in a simple table view. It never transmits crash data, system information, or personal files over the internet.

• No telemetry or analytics built into the application
• No auto-update mechanism that contacts external servers
• No advertising, pop-ups, or upsell prompts
• Regularly scanned by VirusTotal with consistent clean results from 60+ engines

Pro tip: Always download from the official NirSoft website or a trusted mirror. Third-party download sites sometimes repackage NirSoft tools with bundled installers that do contain adware. If your download is larger than 200 KB, it is probably a repackaged version.

See our features overview for details on how BlueScreenView processes crash data locally.

The official download for BlueScreenView is hosted on Nir Sofer’s NirSoft website at nirsoft.net. Our download section links directly to the authentic BlueScreenView v1.55 files from the official source.

NirSoft distributes BlueScreenView in two variants: a 32-bit version (bluescreenview.zip, approximately 83 KB) and a 64-bit version (bluescreenview-x64.zip, approximately 146 KB). Both are standard ZIP archives containing the executable, a help file, and a readme. There is no separate installer — you simply extract the ZIP and run BlueScreenView.exe directly.

• Use the 64-bit version if you run Windows 10 or 11 on modern hardware (most users)
• Use the 32-bit version only on older Windows XP/Vista/7 machines with 32-bit processors
• Both versions read both 32-bit and 64-bit crash dump files regardless of which version you run

Pro tip: Avoid sites like Softonic, CNET Download, or FileHorse for NirSoft tools. While the software itself may be legitimate, those sites often wrap it in custom installers that bundle unwanted programs. Stick to the direct ZIP download.

Head to our download page for direct links to both the 32-bit and 64-bit versions.

Yes, BlueScreenView v1.55 works on Windows 11 without any issues. The tool supports every Windows version from XP through Windows 11, including both 32-bit and 64-bit editions. Thousands of users on Reddit’s r/techsupport community regularly use BlueScreenView on Windows 11 to diagnose BSOD crashes.

Windows 11 stores minidump files in the same location as previous versions: C:\Windows\Minidump. BlueScreenView automatically scans this folder on launch and displays all available crash dumps. The crash dump format has remained consistent across Windows versions, so BlueScreenView reads Windows 11 dumps just as accurately as Windows 7 or 10 dumps. The bug check codes, driver information, and stack trace data are all parsed correctly.

• Compatible with Windows 11 versions 21H2, 22H2, 23H2, and 24H2
• Works on both Intel and AMD systems running Windows 11
• Supports ARM64 crash dump analysis when run on x64 systems
• No known compatibility issues with Windows 11 security features like HVCI or Secure Boot

Pro tip: If BlueScreenView shows no crash dumps on Windows 11, the most likely reason is that Windows is not configured to save minidump files. Go to Settings > System > About > Advanced system settings > Startup and Recovery > Settings, then set “Write debugging information” to “Small memory dump (256 KB)” and confirm the dump file folder is %SystemRoot%\Minidump.

Check the system requirements section for the full list of supported operating systems.

BlueScreenView has extremely low system requirements. It runs on any Windows PC from Windows XP onward, needs less than 5 MB of RAM during operation, and the application itself is under 150 KB in size.

Because BlueScreenView is a lightweight diagnostic utility that reads small minidump files (typically 256 KB to 1 MB each), it places almost no load on your CPU, RAM, or disk. Even a 15-year-old laptop running Windows XP with 512 MB of RAM can run BlueScreenView without slowdown. The tool loads crash dump data into memory as you select each dump, so memory usage stays flat regardless of how many dumps are listed. On a modern Windows 11 machine, you will barely notice it running.

• OS: Windows XP, Vista, 7, 8, 8.1, 10, or 11 (32-bit or 64-bit)
• RAM: Under 5 MB working set (any system with 256 MB+ total RAM is fine)
• Disk: Under 200 KB for the application files
• CPU: Any x86 or x64 processor from the last 20 years
• Permissions: Standard user for analyzing pre-copied dumps; Administrator for reading C:\Windows\Minidump directly

Pro tip: Because BlueScreenView is so lightweight, keep a copy on a USB flash drive. When a friend or coworker has BSOD problems, plug in the USB, run BlueScreenView.exe directly from it, and diagnose the crash on the spot — no installation needed.

See the system requirements table for detailed specifications.

No, BlueScreenView is a Windows-only application. It runs natively on Windows XP through Windows 11 and does not have macOS or Linux versions. This is by design — BlueScreenView reads Windows minidump files (.dmp), which are produced exclusively by the Windows kernel during BSOD crashes.

macOS and Linux have their own crash reporting systems (crash logs on macOS, kernel oops/panic logs on Linux) that use completely different formats. BlueScreenView cannot read these formats, and there would be no practical reason to run it on a non-Windows system since BSODs are a Windows-specific phenomenon. However, if you need to analyze Windows crash dumps on a non-Windows machine, there are workarounds available.

• Run BlueScreenView inside a Windows virtual machine (VirtualBox, VMware, or Parallels on macOS)
• Use Wine on Linux to run BlueScreenView — multiple users report it works under Wine 5.0+
• Copy the minidump files from the Windows machine to a USB drive and analyze them on any other Windows PC

Pro tip: If you manage mixed-OS environments, use the command-line export feature (BlueScreenView.exe /shtml report.html /MiniDumpFolder "path") on a Windows machine, then view the generated HTML report on any OS with a web browser.

For more on BlueScreenView’s platform support, visit the features section.

Yes, BlueScreenView is completely free. There is no paid version, no premium tier, no trial period, and no feature restrictions. Every function — including crash analysis, export, command-line automation, and remote dump viewing — is available at no cost.

Nir Sofer has been releasing free Windows utilities under the NirSoft brand since 2001, and BlueScreenView follows the same freeware model as his other 200+ tools. The software is free for both personal and commercial use. System administrators can deploy it across enterprise networks without purchasing licenses. IT service providers can use it on client machines without any legal restrictions. There has never been a paid or “Pro” version of BlueScreenView.

• Free for personal, commercial, and educational use
• No registration, activation key, or account required
• No ads, donations requests, or upgrade prompts in the application
• All features unlocked from the first run, permanently

Pro tip: While BlueScreenView itself is free, be cautious of third-party websites that offer “BlueScreenView Pro” or charge money for the download. These are scam sites redistributing the free tool with bundled adware. The authentic version is always free.

Download the full-featured free version from our download section.

There is no difference because there is no paid version. BlueScreenView exists only as a single, free release. Any website claiming to sell a “premium” or “pro” edition of BlueScreenView is misleading you.

NirSoft operates on a straightforward freeware model. Nir Sofer develops all utilities independently and distributes them free of charge. The revenue model is based on advertising on the NirSoft website, not software sales. BlueScreenView v1.55, the latest version released, includes every feature the tool has ever offered: multi-dump scanning, four lower-pane display modes, CSV/HTML/XML/text export, command-line batch processing, remote network dump analysis, and Google search integration for bug check codes.

• v1.55 is the complete and final feature set — nothing is held back
• Command-line export works identically to GUI export
• No “unlock code” or license key system exists
• The tool has been stable since its last update with no ongoing development costs

Pro tip: If you want more advanced dump analysis beyond what BlueScreenView offers (such as full kernel debugging), Microsoft’s WinDbg is also free. BlueScreenView is the faster, simpler option for identifying faulty drivers, while WinDbg provides deeper stack trace analysis for complex crashes.

See the features section for a full breakdown of what BlueScreenView includes.

BlueScreenView does not require installation. You download a ZIP file, extract it, and run the executable directly. The entire process takes under 30 seconds.

Because BlueScreenView is a portable application, there is no installer wizard, no setup.exe, and no “Next-Next-Finish” process. You get a clean ZIP archive containing BlueScreenView.exe (the main program), BlueScreenView.chm (the help file), and a readme text file. This portable design means you can run BlueScreenView from any folder, including a USB drive, without leaving traces on the host system.

1. Visit the download section and click the download link for your system (64-bit for modern PCs, 32-bit for legacy systems)
2. Save the ZIP file (bluescreenview-x64.zip, approximately 146 KB) to your Desktop or Downloads folder
3. Right-click the ZIP file and select “Extract All” (or use 7-Zip/WinRAR)
4. Open the extracted folder and double-click BlueScreenView.exe
5. If Windows SmartScreen shows a warning, click “More info” then “Run anyway” — this is normal for unsigned portable tools
6. BlueScreenView opens and automatically scans C:\Windows\Minidump for crash dumps

Pro tip: Create a dedicated folder like C:\Tools\BlueScreenView for your NirSoft utilities. This keeps them organized and makes it easy to add the folder to your PATH environment variable for command-line access.

For a more detailed walkthrough, check the Getting Started guide.

BlueScreenView only comes as a portable application. There is no traditional installer version. Every download from NirSoft is a portable ZIP file that you extract and run without installation.

This portable-only approach is one of BlueScreenView’s strengths. IT professionals and system administrators prefer portable tools because they can be carried on a USB drive and run on any Windows machine without modifying the system. The 32-bit ZIP is about 83 KB and the 64-bit ZIP is about 146 KB, so the entire application fits on virtually any storage medium. BlueScreenView saves its configuration in a .cfg file in the same directory as the executable, not in the Windows registry.

• No registry entries created or modified
• No files placed in Program Files, AppData, or System32
• Configuration stored in BlueScreenView.cfg alongside the .exe
• To “uninstall,” simply delete the folder — nothing else to clean up
• Can run from USB drives, network shares, or cloud-synced folders

Pro tip: Some third-party sites offer an “installer” version of BlueScreenView. These are unofficial wrappers that add the tool to your Start Menu and sometimes bundle additional software. Always use the official portable ZIP from NirSoft for the cleanest experience.

Download the portable ZIP directly from our download section.

The most common reason BlueScreenView shows an empty list after a BSOD is that Windows is not configured to save minidump files. By default, some Windows installations — especially clean installs of Windows 10 and 11 — do not enable small memory dump creation.

When a BSOD occurs, Windows writes crash data to a dump file only if the “Write debugging information” setting is configured in Startup and Recovery. If this is set to “(none)” or if the Minidump folder does not exist, no .dmp files are created and BlueScreenView has nothing to read. Another common cause is insufficient disk space on the C: drive, which prevents Windows from writing the dump file. On rare occasions, the BSOD may occur so early in the boot process that the dump infrastructure is not yet initialized.

1. Right-click “This PC” on the Desktop and select “Properties”
2. Click “Advanced system settings” on the left panel
3. Under “Startup and Recovery,” click “Settings”
4. Set “Write debugging information” to “Small memory dump (256 KB)”
5. Confirm the dump file folder is %SystemRoot%\Minidump
6. Click OK and restart your PC — the next BSOD will generate a dump file

Pro tip: You can also check if minidumps exist manually by navigating to C:\Windows\Minidump in File Explorer. If the folder is empty or missing, that confirms the configuration issue. If dump files exist but BlueScreenView still shows nothing, open Advanced Options (Ctrl+O) and verify the folder path is correct.

See the Getting Started guide for detailed configuration steps.

BlueScreenView failing to open is rare but usually caused by antivirus interference, corrupted downloads, or running the wrong architecture version. The fix is straightforward in each case.

Some antivirus products (particularly Avast, AVG, and Kaspersky) quarantine NirSoft tools because they flag the command-line data export capabilities as “potentially unwanted.” When this happens, the .exe is silently blocked or deleted before it can launch. Another cause is downloading the 32-bit version on a 64-bit system where the Minidump folder has restricted access permissions. Corrupted ZIP downloads can also result in a broken executable that crashes immediately.

1. Check your antivirus quarantine or exclusion list — add BlueScreenView.exe as an exception if it was flagged
2. Re-download the ZIP file from our download section and verify the file size matches (83 KB for 32-bit, 146 KB for 64-bit)
3. Right-click BlueScreenView.exe, select Properties, and check “Unblock” at the bottom of the General tab if present
4. Try running as Administrator: right-click the .exe and select “Run as administrator”
5. If on a 64-bit system, make sure you downloaded the 64-bit version (bluescreenview-x64.zip)

Pro tip: If BlueScreenView opens but immediately closes, it may be trying to scan a Minidump folder it cannot access. Launch it from the command line with BlueScreenView.exe /MiniDumpFolder "C:\Users\YourName\Desktop" pointing to an accessible folder to confirm the application runs. Then fix permissions on C:\Windows\Minidump.

Check our system requirements to verify you have the right version for your OS.

When BlueScreenView lists ntoskrnl.exe as the “Caused By Driver,” it usually does not mean the Windows kernel itself is faulty. ntoskrnl.exe is the NT kernel, and it appears because the crash occurred while the kernel was executing code on behalf of another driver. The real culprit is typically a third-party driver that triggered an exception the kernel could not handle.

This is the single most common source of confusion among BlueScreenView users. Reddit’s r/techsupport forum sees this question daily. The key to finding the actual faulty driver is to look at the lower pane of BlueScreenView, specifically in “Only Drivers Found In Stack” mode. Drivers highlighted in pink are the ones that were in the call stack at the time of the crash. A third-party driver (like nvlddmkm.sys for NVIDIA GPUs or atikmdag.sys for AMD GPUs) highlighted in pink is almost always the real cause.

1. Click on the crash dump entry in the upper pane
2. In the lower pane, switch to View > “Only Drivers Found In Stack” (or press F7)
3. Look for pink-highlighted rows — these are the drivers in the crash stack
4. Identify any non-Microsoft driver in the pink list (check the “Company” column)
5. Update or reinstall that driver using DDU (Display Driver Uninstaller) for GPU drivers, or download the latest version from the hardware manufacturer

Pro tip: If multiple crashes all show different ntoskrnl.exe bug check codes (like PAGE_FAULT_IN_NONPAGED_AREA, IRQL_NOT_LESS_OR_EQUAL) with no consistent third-party driver, this often points to failing RAM. Run Windows Memory Diagnostic or MemTest86 to test your memory modules.

Learn more about interpreting crash data in our Getting Started guide.

BlueScreenView v1.55 is the latest and final version. Nir Sofer released this version and has not issued further updates because the tool is feature-complete and stable. There is no auto-update mechanism built into the application.

Since BlueScreenView is a portable tool, “updating” simply means downloading the new ZIP and replacing the old executable with the new one. However, as v1.55 has been the current version for several years and remains fully functional on Windows 11, there is no update to apply. The minidump file format used by Windows has not changed in ways that would break BlueScreenView’s parsing logic, so the tool continues to work correctly on the newest Windows releases.

• Current version: v1.55 (latest available)
• No auto-updater or update check feature exists in the app
• To check for future releases, visit the official NirSoft BlueScreenView page periodically
• If you have an older version (v1.50 or below), download v1.55 from our download section and replace the old .exe

Pro tip: You can verify your current version by opening BlueScreenView and clicking Help > About. If it shows version 1.55, you are running the latest release. Your configuration file (BlueScreenView.cfg) is preserved when you replace the executable, so your settings carry over.

Get the latest version from our download page.

BlueScreenView and WhoCrashed serve similar purposes but target different users. BlueScreenView is better for technically proficient users who want raw data fast, while WhoCrashed provides plain-English explanations better suited for beginners.

BlueScreenView displays crash data in a sortable table format, showing bug check codes, parameters, driver names, and memory addresses directly. It highlights suspect drivers in pink and lets you switch between four different lower-pane views. WhoCrashed, developed by Resplendence Software, generates automated crash reports with descriptions like “This was probably caused by the following module: nvlddmkm.sys (NVIDIA driver)” and sometimes suggests remediation steps. WhoCrashed has a free Home edition and a paid Professional edition ($29.95) with additional features like kernel dump analysis.

• Speed: BlueScreenView loads instantly (portable, under 150 KB); WhoCrashed requires installation (~15 MB) and takes longer to generate reports
• Detail: BlueScreenView shows more raw data (all loaded drivers, addresses, parameters); WhoCrashed summarizes and interprets
• Export: BlueScreenView exports to CSV/HTML/XML/text with command-line support; WhoCrashed generates formatted reports
• Price: BlueScreenView is fully free; WhoCrashed Home is free but Pro costs $29.95
• Remote analysis: BlueScreenView supports network paths (\\\\computer\\share); WhoCrashed Pro has remote analysis

Pro tip: Many IT professionals use both tools together. Run BlueScreenView first for quick identification of the faulty driver, then use WhoCrashed if you need a plain-language explanation to share with a non-technical client or manager.

See the full feature comparison to understand BlueScreenView’s technical capabilities.

Use BlueScreenView for quick driver identification from BSOD crashes. Use WinDbg when you need deep kernel-level debugging with full stack traces, symbol resolution, and source-level analysis. BlueScreenView is a 30-second tool; WinDbg is a full debugging environment.

BlueScreenView reads the minidump header and driver list, then presents it in a simple table. You can identify the faulty driver in under a minute with no configuration. WinDbg (Windows Debugger), Microsoft’s official debugging tool, requires downloading debug symbols, setting up symbol paths, and running commands like !analyze -v to get detailed analysis. WinDbg reveals much more: exact faulting instruction addresses, full call stacks with function names, thread states, and memory pool data. This depth is necessary for driver developers or when BlueScreenView’s quick analysis is not specific enough.

• Learning curve: BlueScreenView requires zero training; WinDbg requires significant command-line debugging knowledge
• Setup time: BlueScreenView runs in seconds; WinDbg needs symbol server configuration (10-15 minutes first time)
• Analysis depth: BlueScreenView shows driver-level data; WinDbg shows instruction-level data
• Best for: BlueScreenView for home users and first-pass analysis; WinDbg for developers and kernel debugging

Pro tip: A practical workflow is to start with BlueScreenView to identify the suspect driver, then open the same dump in WinDbg only if you need deeper analysis. Run !analyze -v in WinDbg to get the verbose automated analysis that often identifies the exact function call that triggered the crash.

Learn how to get started with BlueScreenView in our Getting Started section.

BlueScreenView supports a full set of command-line parameters for automated crash dump analysis and batch export. These options let you scan specific folders, generate reports in multiple formats, and integrate BlueScreenView into scripts or monitoring systems without opening the GUI.

The command-line interface was added in version 1.10 and is particularly useful for system administrators who manage multiple machines. You can point BlueScreenView at any folder containing .dmp files, export the crash list to CSV, HTML, XML, or plain text, and control sorting and display modes — all from a batch file or PowerShell script. The output files are clean and parseable, making them suitable for log aggregation tools.

• /MiniDumpFolder "C:\path" — scan a custom folder instead of the default Minidump location
• /shtml "report.html" — export crash list as an HTML table
• /scomma "report.csv" — export as CSV for spreadsheet analysis
• /sxml "report.xml" — export as XML for automated processing
• /stab "report.txt" — export as tab-delimited text
• /sort "~Crash Time" — sort by column (~ prefix for descending order)
• /LoadFrom 3 /SingleDumpFile "file.dmp" — analyze a single dump file
• /LowerPaneMode 2 — set lower pane to show only stack drivers

Pro tip: Combine command-line options for automated reporting: BlueScreenView.exe /MiniDumpFolder "\\\\server\\c$\\Windows\\Minidump" /shtml "\\\\reports\\server-crashes.html" /sort "~Crash Time". Schedule this as a Windows Task Scheduler job to generate daily crash reports from remote machines.

See the features section for more on BlueScreenView’s automation capabilities.

Yes, BlueScreenView can analyze crash dumps from any computer on your network. You can point it at a remote machine’s Minidump folder using a UNC network path, or copy dump files to a local folder and scan them there.

To analyze a remote computer’s crashes, you need network access to the target machine’s administrative share or a shared folder containing the dump files. BlueScreenView reads the remote .dmp files over the network just as it would read local files. This feature is invaluable for IT administrators managing multiple workstations or servers. You can also create a text file listing multiple computer names or IP addresses, and BlueScreenView will scan all of them in sequence using the /ComputersFile parameter.

1. Open BlueScreenView and press Ctrl+O (or go to Options > Advanced Options)
2. Select “Load MiniDump files from the following MiniDump folder”
3. Enter the network path: \\ComputerName\c$\Windows\Minidump
4. Click OK — BlueScreenView scans the remote folder and displays all crash dumps
5. Alternatively, use /ComputersFile "machines.txt" on the command line with a text file listing one hostname per line

Pro tip: For large networks, create a batch script that iterates through machine names and exports a separate HTML report for each: for /f %m in (machines.txt) do BlueScreenView.exe /MiniDumpFolder "\\%m\c$\Windows\Minidump" /shtml "reports\%m.html". This gives you a crash report dashboard for your entire fleet.

Explore all analysis options in our features overview.

To uninstall BlueScreenView, simply delete the folder containing BlueScreenView.exe. Because it is a portable application, there is nothing else to remove — no registry entries, no Start Menu shortcuts, no AppData files, no Windows services.

BlueScreenView stores all its settings in a single file called BlueScreenView.cfg in the same directory as the executable. When you delete the folder, this configuration file goes with it. There are no leftover files anywhere else on your system. This is one of the major advantages of portable applications over traditional installed software. Unlike programs installed through a setup wizard, BlueScreenView does not scatter files across Program Files, ProgramData, AppData, or the Windows registry.

1. Close BlueScreenView if it is currently running
2. Navigate to the folder where you extracted BlueScreenView (for example, C:\Tools\BlueScreenView)
3. Delete the entire folder (contains BlueScreenView.exe, BlueScreenView.chm, BlueScreenView.cfg, and the readme)
4. Empty the Recycle Bin if you want to free the disk space (under 200 KB total)

Pro tip: If you ran BlueScreenView from a USB drive, simply unplug the drive. If you pinned BlueScreenView to the taskbar or created a desktop shortcut manually, delete those shortcuts as well. BlueScreenView never creates these automatically.

If you want to reinstall later, just download a fresh copy from our download section.

Yes, BlueScreenView works completely offline. It does not require an internet connection for any of its functions. The tool reads crash dump files stored locally on your hard drive and processes everything on your machine without contacting any external server.

This offline capability makes BlueScreenView ideal for diagnosing crashes on air-gapped systems, machines in secure environments, or computers where the BSOD has disrupted network connectivity. The only optional feature that uses the internet is the “Google Search” function in the right-click context menu, which opens your browser to search for a bug check code. Even this feature is just a convenience shortcut — it does not send data to any server, it simply constructs a Google search URL and opens it in your default browser.

• All crash analysis performed locally — no cloud processing
• No license validation or phone-home check on startup
• Export features (CSV, HTML, XML) work entirely offline
• Can be carried on a USB drive and used on machines with no internet
• The Google Search shortcut is the only feature that opens a browser, and it is completely optional

Pro tip: For truly isolated environments, pre-download the NirSoft help page for common BSOD error codes and keep it on the same USB drive as BlueScreenView. This way you can look up bug check codes without needing internet access on the target machine.

Check our Getting Started guide for offline setup instructions.