Open a terminal or command prompt window.
Navigate to the directory where you have the NVIDIA drivers installed. The location can vary depending on your operating system. Here are some common default locations:
Linux: /usr/bin/ or /usr/local/bin/
Windows: C:\Program Files\NVIDIA Corporation\Installer2\Display.DriverVersion\ or C:\Windows\System32\DriverStore\FileRepository\
Run the following command to generate the bug report log:
Linux: nvidia-bug-report.sh
Windows: nvidia-bug-report.exe
Wait for the tool to collect the necessary information. It may take a few moments.
Once the bug report is complete, it will generate a file named something like nvidia-bug-report.log.gz. The file is typically saved in the same directory where you ran the command.
You can then locate the generated nvidia-bug-report.log.gz file and use it for troubleshooting purposes.
You may need to extract the contents of the compressed file using a decompression tool like 7-Zip or WinRAR, to access the log files within.
Related Articles
KB 829939 - Execution of NVIDIA Field Diagnostic (FD) Tool and Collection of Diagnostic Logs, and troubleshooting of GPU(s) not detected
1. Objective To provide a standardized procedure for executing the NVIDIA Field Diagnostic (FD) tool, verifying GPU status, collecting the required diagnostic logs, and documenting the findings for further analysis. 2. Scope This procedure applies to ...
KB 933073 - Using dmesg and Kernel Module Checks to Troubleshoot NVIDIA GPU Issues
Overview This article outlines how to use dmesg logs and kernel module commands to diagnose issues where the operating system fails to detect NVIDIA GPUs—even though they appear in the system's BMC (Baseboard Management Controller). When to Use This ...
KB 787096 - How to Collect NVIDIA Bug Report
Purpose This article provides step-by-step instructions to collect an NVIDIA bug report from servers equipped with NVIDIA GPUs. The NVIDIA bug report is commonly required by NVIDIA Support for troubleshooting GPU driver, CUDA, NVLink, PCIe, and ...
KB 716691 - Powering NVIDIA L40S GPUs in ASUS ESC8000A-E12P Servers
Powering NVIDIA L40S GPUs in ASUS ESC8000A-E12P Servers Overview When deploying NVIDIA L40S GPUs in ASUS ESC8000A-E12P servers, users may encounter a power connector mismatch issue. This KB article explains the root cause and provides the official ...
What is NVIDIA NVLink?
NVLink is a high-speed, low-latency interconnect technology developed by NVIDIA, primarily used in their graphics processing units (GPUs) and other high-performance computing devices. It enables direct communication between multiple GPUs or between a ...
Recent Articles
KB-630208 | How to use Find and Locate to search for files in Linux
Purpose To provide Linux administrators and Field Engineers with guidance on using the find and locate utilities to efficiently search for files and directories within a Linux filesystem based on criteria such as name, type, size, timestamps, ...
KB-630164 | How to use rsync to Synchronize Files
Purpose To provide a clear and practical procedure for using the rsync utility to synchronize files and directories between local systems and remote hosts, including push and pull operations, while preserving file attributes and optimizing data ...
KB-630107 | How to create a Linux swap file
Purpose To provide Field Engineers and Linux administrators with a standardized procedure for creating, configuring, and validating a Linux swap file. This procedure helps ensure sufficient virtual memory is available when physical RAM is exhausted ...
MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims
MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims MSI's standard warranty does not cover physical or accidental damage to an All-in-One (AIO) PC. If the damage is determined to be caused by external factors rather than a ...
KB 134833 - Troubleshooting NVSM Alert NV-CPU-XX – Unrecoverable CPU Internal Error
Purpose This document provides a general troubleshooting procedure for the NVIDIA System Management (NVSM) alert NV-CPU-XX, which indicates that a CPU has reported an internal error. The article outlines how to verify whether the alert represents an ...