How do I read this dump file?

Question

How do I read this dump file?

Martinel 0

BUGCHECK_CODE:  a

BUGCHECK_P1: ffffc50f606a8f18

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff807ab88bd50

FILE_IN_CAB:  040126-18859-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffcd0f537ea080

READ_ADDRESS: fffff807ac4444c8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffc50f606a8f18 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
nt!ExpScanGeneralLookasideList+40
fffff807`ab88bd50 418b48d8        mov     ecx,dword ptr [r8-28h]

STACK_TEXT:  
ffffbb07`44482138 fffff807`abb3ece9     : 00000000`0000000a ffffc50f`606a8f18 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffbb07`44482140 fffff807`abb39fa8     : 00000000`00000000 fffff807`ab7c11aa fffff807`ac37a6a0 00000000`00040282 : nt!KiBugCheckDispatch+0x69
ffffbb07`44482280 fffff807`ab88bd50     : fffff807`ac37a690 fffff807`3b095180 fffff780`00000004 fffff807`aba445c0 : nt!KiPageFault+0x468
ffffbb07`44482410 fffff807`aba4474c     : 00000000`ffffffff fffff807`aba445c0 00000000`00000005 ffffcd0f`53718dd0 : nt!ExpScanGeneralLookasideList+0x40
ffffbb07`44482440 fffff807`ab9070ba     : ffffcd0f`537ea080 fffff807`aba445c0 00000000`00000080 0d0d0d0d`0d0d0d0d : nt!KeBalanceSetManager+0x18c
ffffbb07`444824b0 fffff807`abb2bdf4     : fffff807`3b095180 ffffcd0f`537ea080 fffff807`ab907060 0d0d0d0d`0d0d0d0d : nt!PspSystemThreadStartup+0x5a
ffffbb07`44482500 00000000`00000000     : ffffbb07`44483000 ffffbb07`4447c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!ExpScanGeneralLookasideList+40

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.8036

STACK_COMMAND: .process /r /p 0xffffcd0f53726040; .thread 0xffffcd0f537ea080 ; kb

BUCKET_ID_FUNC_OFFSET:  40

FAILURE_BUCKET_ID:  AV_nt!ExpScanGeneralLookasideList

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {76f24b7e-30bf-766a-9788-497c3826355f}

My PC crashes every couple of hours and sometimes a browser tab or a game or app .

0 comments

2 answers

Your answer

Answer 1

Thanks.

These minidumps don't appear to have been created by Driver Verifier. They don't mention any third-party drivers. Only generic system files.

In that case, I suggest doing the following:

Go to the Acer website using the link below, download the latest Chipset driver, and install it.

https://www.acer.com/us-en/support/product-support/Nitro_N50-620/downloads?suggest=Nitro_N50-620;0

Driver name: Chipset Driver

Version: 10.1.34.8

(Extract the ZIP file, double-click the file "SetupChipset" to run it, and follow the on-screen instructions to install the driver.)

I noticed that the motherboard BIOS is outdated. I suggest you update it by following Acer's instructions.

Then, see if the system will work stably.

If the crash occurs again after doing this, please share the minidump it created.

Feel free to ask any questions you may have.

Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

Answer 2

David-M 126.5K Independent Advisor

Hi. I'm David, and I'm happy to help you.

The minidump does not mention any driver, only a generic system file (ntkrnlmp.exe).

Was this the only minidump available?

If you have more minidump files, please share them. Sometimes, it may be necessary to analyze multiple minidumps to identify the cause of the problem. You can share the files themselves. You don't need to open them one by one and post the content here.

These files are in C:\Windows\Minidump.

(If you don't have a Minidump folder, check if it is in the plural Minidumps.)

Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

Then, post the link to the ZIP file here so I can have a look.

Looking forward to your reply.

Martinel 0 Reputation points

2026-04-01T00:22:56.78+00:00

https://drive.google.com/file/d/14sg27pNvQ7DJ1A3TOx3dSMTEJA6LMAYt/view?usp=drive_link

i couldnt upload the dump file of that specific one but i "luckly" got another crash and this one i could upload
David-M 126.5K Reputation points Independent Advisor

2026-04-01T12:27:02.0266667+00:00
Sorry for the delay in reply. I've been offline.

Thanks.

This minidump also does not mention any driver, only a generic system file.

I suggest you use the Driver Verifier utility. This utility is used to force the system to show the driver causing the problem.

Before turning on Driver Verifier, I like to create a restore point just in case. I suggest doing the same.

https://support.microsoft.com/windows/system-protection-e9126e6e-fa64-4f5f-874d-9db90e57645a

Turn on Driver Verifier, let the system crash 3 times, then turn off Driver Verifier. Share the minidumps that the crashes created.

Press Win + R, type verifier, and press Enter;

Select Create custom settings (for code developers) and click Next;

Check these options:

Pool Tracking

I/O Verification

Deadlock Detection

DMA Checking

Security Checks

Force pending I/O requests

IRP Logging

Miscellaneous Checks

DDI compliance checking

Select Select driver names from a list;

Sort by Provider and choose all non-Microsoft drivers;

Click Finish and restart your computer. Driver Verifier will now monitor the selected drivers.

(Pay attention to the blue screen that is displayed. Sometimes, it may contain useful information.)

After the system crashes at least 3 times, follow the procedure below to disable the Driver Verifier.

Open Start and type cmd, right-click on Command Prompt and select Run as administrator.

Run the following commands at the Command Prompt one at a time:

verifier /reset verifier /bootmode resetonbootfail

Then, restart the PC.

If the system no longer starts due to BSOD caused by the Driver Verifier, start it in Safe Mode and perform the above procedure to disable Driver Verifier.

https://support.microsoft.com/en-us/windows/windows-startup-settings-1af6ec8c-4d4a-4b23-adb7-e76eef0b847f

Looking forward to your reply.

Feel free to ask any questions you may have.
Martinel 0 Reputation points

2026-04-03T12:25:00.08+00:00

https://drive.google.com/file/d/1wkg1ni0mXgkI4rg6TDV4dkOR4lTbhz6t/view?usp=drive_link

Sorry it took some time but it has been surprisingly stable until today