# Symbol loading and troubleshooting techniques

WinDbg uses symbol files to translate addresses to function names, enable source-level debugging, and provide accurate call stacks. Without symbols, function names, call stacks, and module details may appear as raw addresses, making it difficult to trace issues. Accurate symbol loading is essential for meaningful crash dump analysis and debugging. This section explains how to configure symbol paths, verify symbol loading, and troubleshoot common problems.

## Set up symbol paths

Use the following command to configure symbol paths in WinDbg:

.sympath srv*C:\\Symbols*https://msdl.microsoft.com/download/symbols
    .reload
    Copy to clipboard

- `srv\*` tells WinDbg to use a symbol server.
- `C:\\Symbols` is a local cache directory.
- `https://msdl.microsoft.com/download/symbols` is Microsoft’s public symbol server.
- Use the `.reload` command to apply and reload symbols.

Note

Symbol files are usually .pdb files.

## Verify symbol load status

Use the following command to inspect a specific module:

lmDvm <ModuleName>
    Copy to clipboard

The output for this command shows the following:

- Image path
- Symbol file path
- Timestamp
- Whether symbols are loaded (private/public/deferred)

## Troubleshooting symbol issues

Do the following to troubleshoot symbol issues:

- Verbose logging helps identify why symbols aren’t loading.

> 
> 
> - To enable verbose symbol logging, use the `!sym noisy` command.
>     - Use `!sym quiet` to disable.
- Use `.reload /f /i <ModuleName>` to force the symbol load for a module.
- Check if symbols are missing due to incorrect paths:

    - Ensure .pdb files are present in the symbol path.
    - For private symbols, verify build settings and symbol export.
- Use .exepath and .srcpath if needed to set or display the executable file path and the source file path respectively.

.exepath C:\\Path\\To\\Executable
        
        .srcpath C:\\Path\\To\\Source
        Copy to clipboard

Last Published: Jun 16, 2026

[Previous Topic
Set breakbpoints](https://docs.qualcomm.com/bundle/publicresource/80-62010-1/topics/debug-breakpoints.md) [Next Topic
System-wide app conflicts](https://docs.qualcomm.com/bundle/publicresource/80-62010-1/topics/debug-app-conflicts.md)