Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
11,415 questions
Page xxxx too large to be in the dump file when analyzing BSOD using WinDbg
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 71%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBC%3C/text%3E%3C/svg%3E)
Bruce Chung
0
Reputation points
I am facing a error while analyzing dump file by windbg as the following.
The error is "Page 5ac5a80a20 too large to be in the dump file" so that I can't analyze this dump.
Is there any setting to fix this issue by Windbg?
Thanks~
=========
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8074be4a03b, address which referenced memory
Debugging Details:
Page 5ac5a80a20 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Page 850fc73e74 too large to be in the dump file.
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Page 5ac5a80a20 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Page 5ac5a80a20 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Page 850fc73e74 too large to be in the dump file.
Page 850fc73e74 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
Page 5ac5a80a20 too large to be in the dump file.
Unable to read NT module Base Name string at e60edcd7`6a421fb0 - NTSTATUS 0xC0000141
Missing image name, possible paged-out or corrupt data.
Unable to read NonPagedDebugInfo at a169f00c`db239aa5 - NTSTATUS 0xC0000141
Unable to read KLDR_DATA_TABLE_ENTRY at 6c2d5f96`f34feb03 - NTSTATUS 0xC0000141
WARNING: .reload failed, module list may be incomplete
Page 5ac5a80a20 too large to be in the dump file.
{count} votes
-
Gary Nebbett 6,201 Reputation points2025-03-26T11:49:53.7666667+00:00 Hello Bruce,
Apart from the bug check information (DRIVER_IRQL_NOT_LESS_OR_EQUAL and arguments), everything else looks corrupt/incomplete. The problem almost certainly lies with a corrupt/incomplete dump file and there is nothing that windbg can do to compensate for that.
Gary
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 94%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIX%3C/text%3E%3C/svg%3E)
Ian Xue-MSFT 41,711 Reputation points Microsoft External Staff2025-03-27T09:13:00.13+00:00 Hi Bruce,
Thanks for your post. You can also debug a dump file to determine a sub set of information. This article explains how to extract information from a dump file.
For general information on working with dump files, see:
Reference. Extract Information from a Dump File - Windows drivers | Microsoft Learn
Sign in to comment
Sign in to answer