************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToChakraJsProvider : false

-- Configuring repositories

  ----> Repository : LocalInstalled, Enabled: true

  ----> Repository : UserExtensions, Enabled: true

Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 46

Microsoft (R) Windows Debugger Version 10.0.29457.1000 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\111425-16343-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 26100 MP (12 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0xfffff804dc800000 PsLoadedModuleList = 0xfffff804dd6f4f10

Debug session time: Fri Nov 14 00:07:12.401 2025 (UTC + 3:00)

System Uptime: 0 days 4:36:52.179

Loading Kernel Symbols

..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

.............................................................

................................................................

................................................................

.........................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 000000cc`fb23c018). Type ".hh dbgerr001" for details

Loading unloaded module list

.................

For analysis of this file, run !analyze -v

nt!KiPageFault+0x10:

fffff804dceacc50 c645ab01 mov byte ptr [rbp-55h],1 ss:ffffba0a85bd8fcb=??

3: kd> !analyze -v

Loading Kernel Symbols

..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.

Run !sym noisy before .reload to track down problems loading symbols.

.............................................................

................................................................

................................................................

.........................................

Loading User Symbols

PEB is paged out (Peb.Ldr = 000000cc`fb23c018). Type ".hh dbgerr001" for details

Loading unloaded module list

.................

---

•                                                                         *
  

•                    Bugcheck Analysis                                    *
  

•                                                                         *
  

---

UNEXPECTED_KERNEL_MODE_TRAP (7f)

This means a trap occurred in kernel mode, and it's a trap of a kind

that the kernel isn't allowed to have/catch (bound trap) or that

is always instant death (double fault). The first number in the

BugCheck params is the number of the trap (8 = double fault, etc)

Consult an Intel x86 family manual to learn more about what these

traps are. Here is a portion of those codes:

If kv shows a taskGate

    use .tss on the part before the colon, then kv.

Else if kv shows a trapframe

    use .trap on that value

Else

    .trap on the appropriate frame will show where the trap was taken

    (on x86, this will be the ebp that goes with the procedure KiTrap)

Endif

kb will then show the corrected stack.

Arguments:

Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT

Arg2: ffffcf0105aaee70

Arg3: ffffba0a85bd8fa0

Arg4: fffff804dceacc50

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec

Value: 1703

Key  : Analysis.Elapsed.mSec

Value: 23003

Key  : Analysis.IO.Other.Mb

Value: 0

Key  : Analysis.IO.Read.Mb

Value: 1

Key  : Analysis.IO.Write.Mb

Value: 24

Key  : Analysis.Init.CPU.mSec

Value: 1187

Key  : Analysis.Init.Elapsed.mSec

Value: 63970

Key  : Analysis.Memory.CommitPeak.Mb

Value: 109

Key  : Analysis.Version.DbgEng

Value: 10.0.29457.1000

Key  : Analysis.Version.Description

Value: 10.2506.23.01 amd64fre

Key  : Analysis.Version.Ext

Value: 1.2506.23.1

Key  : Bugcheck.Code.LegacyAPI

Value: 0x1000007f

Key  : Bugcheck.Code.TargetModel

Value: 0x1000007f

Key  : Dump.Attributes.AsUlong

Value: 0x1808

Key  : Dump.Attributes.DiagDataWrittenToHeader

Value: 1

Key  : Dump.Attributes.ErrorCode

Value: 0x0

Key  : Dump.Attributes.KernelGeneratedTriageDump

Value: 1

Key  : Dump.Attributes.LastLine

Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage

Value: 0

Key  : Failure.Bucket

Value: 0x7f_8_nt!KiPageFault

Key  : Failure.Hash

Value: {2f8e6272-1536-8847-15b3-d73bdf95dfe4}

Key  : Hypervisor.Enlightenments.ValueHex

Value: 0x7417df84

Key  : Hypervisor.Flags.AnyHypervisorPresent

Value: 1

Key  : Hypervisor.Flags.ApicEnlightened

Value: 0

Key  : Hypervisor.Flags.ApicVirtualizationAvailable

Value: 1

Key  : Hypervisor.Flags.AsyncMemoryHint

Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested

Value: 0

Key  : Hypervisor.Flags.CpuManager

Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi

Value: 1

Key  : Hypervisor.Flags.DynamicCpuDisabled

Value: 1

Key  : Hypervisor.Flags.Epf

Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks

Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable

Value: 1

Key  : Hypervisor.Flags.MaxBankNumber

Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl

Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush

Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing

Value: 1

Key  : Hypervisor.Flags.Phase0InitDone

Value: 1

Key  : Hypervisor.Flags.PowerSchedulerQos

Value: 0

Key  : Hypervisor.Flags.RootScheduler

Value: 0

Key  : Hypervisor.Flags.SynicAvailable

Value: 1

Key  : Hypervisor.Flags.UseQpcBias

Value: 0

Key  : Hypervisor.Flags.Value

Value: 55185662

Key  : Hypervisor.Flags.ValueHex

Value: 0x34a10fe

Key  : Hypervisor.Flags.VpAssistPage

Value: 1

Key  : Hypervisor.Flags.VsmAvailable

Value: 1

Key  : Hypervisor.RootFlags.AccessStats

Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened

Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor

Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading

Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync

Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled

Value: 0

Key  : Hypervisor.RootFlags.IsHyperV

Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened

Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt

Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened

Value: 1

Key  : Hypervisor.RootFlags.Nested

Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor

Value: 1

Key  : Hypervisor.RootFlags.Value

Value: 1015

Key  : Hypervisor.RootFlags.ValueHex

Value: 0x3f7

Key  : WER.System.BIOSRevision

Value: 5.19.0.0

BUGCHECK_CODE: 7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffcf0105aaee70

BUGCHECK_P3: ffffba0a85bd8fa0

BUGCHECK_P4: fffff804dceacc50

FILE_IN_CAB: 111425-16343-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808

Kernel Generated Triage Dump

FAULTING_THREAD: ffff808bd96fc080

STACK_OVERFLOW: Stack Limit: ffffba0a85bd9000. Use (kF) and (!stackusage) to investigate stack usage.

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1 (!blackboxwinlogon)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: cs2.exe

STACK_TEXT:

ffffba0a85bd8fa0 fffff804dceacc97 : 736f7263694d1513 70726f432074666f 316e6f697461726f 0304550306243026 : nt!KiPageFault+0x10

ffffba0a85bd9130 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x57

SYMBOL_NAME: nt!KiPageFault+10

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.6899

STACK_COMMAND: .process /r /p 0xffff808bc268e080; .thread 0xffff808bd96fc080 ; kb

BUCKET_ID_FUNC_OFFSET: 10

FAILURE_BUCKET_ID: 0x7f_8_nt!KiPageFault

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {2f8e6272-1536-8847-15b3-d73bdf95dfe4}

Followup: MachineOwner

---

3: kd> .process /r /p 0xffff808bc268e080; .thread 0xffff808bd96fc080 ; kb

Implicit process is now ffff808b`c268e080

Loading User Symbols

PEB is paged out (Peb.Ldr = 000000cc`fb23c018). Type ".hh dbgerr001" for details

Implicit thread is now ffff808b`d96fc080

*** Stack trace for last set context - .thread/.cxr resets it

RetAddr : Args to Child : Call Site

00 fffff804dceacc97 : 736f7263694d1513 70726f432074666f 316e6f697461726f 03045503`06243026 : nt!KiPageFault+0x10

01 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 00000000`00000000 : nt!KiPageFault

Hi, thank you for replying. As per checking and analyzing the event logs, there are multiple nvlddmkm errors on the PC. This is your Nvidia graphics card driver. For us to fix the issue, kindly follow the steps below:

 

Let us run a clean installation of the Nvidia driver. This is different from doing DDU or updating the driver, as this will remove all entries and replace them with compatible ones. Kindly follow the steps from the link below:

 

https://nvidia.custhelp.com/app/answers/detail/a_id/10/~/geforce-experience-driver-installation-failed.-how-do-i-manually-clean-install#:~:text=%20How%20do%20I%20manually%20clean%20install%20the,installation%20process%2C%20close%20any%20programs%20which...%20More%20

 

Note: This is 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.

 

Additional note: If the issue persists, I suggest removing the GPU and placing it into another PCIe port available (This is applicable if you are using a Desktop PC or an External GPU). However, if all fails, I suggest contacting a local technician to physically check the device for any hardware-related issues.

I figured out what the problem was, it was the RAM. And it was showing a graphics card error because of the undervolt

Thank you for helping

Hi, can you further check if you have more Minidump files on the PC? As per checking the Minidump files, it is only displaying general errors. In addition, can you please check the System logs on the PC so I can further examine the root cause of the issue?

To share the System logs, please follow the steps in the link below:

 

Press the Windows key + X, then select "Event Viewer"

Click the drop-down of "Windows logs"

Right-click System > click Filter Current logs > Check: Critical, Warning, and Error > Hit OK

On the right pane, click "Save Filtered Log File As..."

Save the System logs file to your desktop and share it by following the steps from the link:

https://support.microsoft.com/en-us/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

 

Note: You can also use your preferred cloud storage to upload and share the logs.

https://1drv.ms/f/c/bca8a87c1914bcc3/EsheJowB9cZIpTqHaA3Eo0IBoUVLm8RBL6d2tT-8JNwPug?e=KeAsFg

Hi, I'm Bernard, a fellow Windows user. I'm happy to help!

As per checking the logs you have, it is only displaying a general error on the PC. In this case, can you please upload and share all the Minidump files on the affected device so I can further examine the root cause of the issue?

 

Press Windows key + E (To open File Explorer)

 

Click "This PC" > then follow the file path:

 

C:\Windows\Minidump

 

Copy the Minidump files and save them to another location, like the Desktop or Documents.

 

Then please upload it to Cloud storage like OneDrive or any cloud storage you are using, and please share the shareable link here.

To upload and share the link using OneDrive:

Go to this link: https://onedrive.live.com/, then upload the file.

Then, provide the shareable link by following the steps from this link: https://support.microsoft.com/en-us/office/share-onedrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

https://1drv.ms/f/c/bca8a87c1914bcc3/EsheJowB9cZIpTqHaA3Eo0IBoUVLm8RBL6d2tT-8JNwPug?e=KeAsFg

To troubleshoot the BSOD (Blue Screen of Death) related to ntkrnlmp.exe, which indicates an unexpected kernel mode trap, you can follow these general steps:

1. Check for Hardware Issues: Ensure that all hardware components are functioning properly. Faulty hardware can often lead to BSOD errors. Run hardware diagnostics provided by your system manufacturer.
2. Update Drivers: Outdated or incompatible drivers can cause system crashes. Update all device drivers, especially those related to graphics, network, and storage.
3. Remove Recently Installed Hardware: If you have added new hardware recently, try removing it to see if the issue persists.
4. Run Windows Memory Diagnostics: Memory issues can lead to BSODs. Use the Windows Memory Diagnostics tool to check for memory problems. You can find it in the Control Panel under Memory.
5. Check for System Corruption: Run the System File Checker (SFC) tool to repair corrupted system files. Open Command Prompt as an administrator and run the command sfc /scannow.
6. Analyze Crash Dumps: If you are familiar with debugging, you can analyze the crash dump files using tools like WinDbg. Use the command !analyze -v to get detailed information about the crash.
7. Check Event Viewer: Look for critical errors in the Event Viewer that occurred around the same time as the BSOD. This can provide clues about what caused the crash.
8. Disable Overclocking: If your system is overclocked, revert to default settings as overclocking can lead to instability.
9. Run a Virus Scan: Malware can cause system instability. Run a full system scan using a reputable antivirus program.

By following these steps, you should be able to identify and potentially resolve the issues causing the BSOD related to ntkrnlmp.exe.

---

References:

• Bug checks (stop code errors)
• Advanced troubleshooting for stop code errors