recently BSOD after formatting my pc

Question

recently BSOD after formatting my pc

Anonymous

my pc always crash, and it happens when i left my pc for so long.
i have always turn on my pc for 24 hours for the past 2 years but it have no problem before i began to format and reinstall my windows.

https://drive.google.com/drive/folders/1slAQ1zt1-qE-4RY6vei95B1BEjML_YwV?usp=drive_link
this is the link to the minidump that i have zip and i my pc specification from cpu-z

************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true

-- 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.032 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Loading Dump File [C:\Windows\Minidump\101123-12218-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Kernel base = 0xfffff8002ca00000 PsLoadedModuleList = 0xfffff8002d62a2e0 Debug session time: Wed Oct 11 02:30:45.162 2023 (UTC + 7:00) System Uptime: 0 days 7:17:27.798 Loading Kernel Symbols ............................................................... ................................................................ ................................................................

Loading User Symbols

Loading unloaded module list ...................... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff8002cdfcd70 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa0f3d2ad500=000000000000001e 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common BugCheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: ffffac8a3fa7a8a0, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:

************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: ExceptionRecord *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: ContextRecord *** *** *** *************************************************************************

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 4202

Key  : Analysis.Elapsed.mSec
Value: 7632

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 359

Key  : Analysis.Init.Elapsed.mSec
Value: 2198

Key  : Analysis.Memory.CommitPeak.Mb
Value: 98

Key  : Bugcheck.Code.LegacyAPI
Value: 0x1e

Key  : Failure.Bucket
Value: AV\_R\_nt!KiDispatchException

Key  : Failure.Hash
Value: {36796e09-312c-3519-a508-ce00ff2df497}

Key  : WER.OS.Branch
Value: vb\_release

Key  : WER.OS.Version
Value: 10.0.19041.1

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: ffffac8a3fa7a8a0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB: 101123-12218-01.dmp

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

READ_ADDRESS: fffff8002d6fb390: 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 0000000000000000

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000) Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
fffffa0f3d2ad4f8 fffff8002ce5435b : 000000000000001e ffffffffc0000005 ffffac8a3fa7a8a0 0000000000000000 : nt!KeBugCheckEx fffffa0f3d2ad500 fffff8002ce10f6c : 0000000000001000 fffffa0f3d2adda0 ffff800000000000 0000000000000000 : nt!KiDispatchException+0x18affb fffffa0f3d2adbc0 fffff8002ce0c9bd : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExceptionDispatch+0x12c fffffa0f3d2adda0 ffffac8a3fa7a8a0 : 0000000000000220 ffffac8a3fa936ea 0000000000000030 ffffac8a3b630620 : nt!KiPageFault+0x43d fffffa0f3d2adf38 0000000000000220 : ffffac8a3fa936ea 0000000000000030 ffffac8a3b630620 ffffac8a2cc310a0 : 0xffffac8a3fa7a8a0 fffffa0f3d2adf40 ffffac8a3fa936ea : 0000000000000030 ffffac8a3b630620 ffffac8a2cc310a0 ffffac8a32f35050 : 0x220 fffffa0f3d2adf48 0000000000000030 : ffffac8a3b630620 ffffac8a2cc310a0 ffffac8a32f35050 ffffac8a3e4d6d50 : 0xffffac8a3fa936ea fffffa0f3d2adf50 ffffac8a3b630620 : ffffac8a2cc310a0 ffffac8a32f35050 ffffac8a3e4d6d50 0000000000000000 : 0x30 fffffa0f3d2adf58 ffffac8a2cc310a0 : ffffac8a32f35050 ffffac8a3e4d6d50 0000000000000000 fffffa0f3d2ae090 : 0xffffac8a3b630620 fffffa0f3d2adf60 ffffac8a32f35050 : ffffac8a3e4d6d50 0000000000000000 fffffa0f3d2ae090 fffffa0f3d2ae019 : 0xffffac8a2cc310a0 fffffa0f3d2adf68 ffffac8a3e4d6d50 : 0000000000000000 fffffa0f3d2ae090 fffffa0f3d2ae019 0000000000000000 : 0xffffac8a32f35050 fffffa0f3d2adf70 0000000000000000 : fffffa0f3d2ae090 fffffa0f3d2ae019 0000000000000000 0000000000040293 : 0xffffac8a3e4d6d50

SYMBOL_NAME: nt!KiDispatchException+18affb

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.3516

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 18affb

FAILURE_BUCKET_ID: AV_R_nt!KiDispatchException

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {36796e09-312c-3519-a508-ce00ff2df497}

Followup: MachineOwner

this is the sample of the latest crash.
please help me in identifying if there is a hardware issue so that i can just replace the correct hardware.

regards,
Albert

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

7 answers

Answer 1

Hi, Albert Theodorus 施升濠

I am pleased to receive your reply. Based on your description of the test operation, it seems that your memory stick has a compatibility issue. Of course, this doesn't mean that your hardware is faulty or damaged, but this also can't be set up to allow the memory diagnostics to pass without any problems, so we recommend that you contact the memory stick or branded machine manufacturer for after-sales support and try to test or replace the memory stick.

We look forward to hearing from you.

Best Regards,

Martin | Microsoft Community Support Specialist

Answer 2

ok, after a few days of doing test number 2. i found a memory error while doing memory diagnostic with 4 pcs of ram initially.
so i try to test with just a pair, and try to switch the slot before the next pair. after reseating slot. i get a prompt after windows boot to download MSI center and the test went good with no error found on either pair of ram and slot.
so i am trying to put all 4 pcs of ram again, and do retest on memory diagnostic.

i can do 2 times without having error now. so i want test more times,
the next i try is 4 times. the memory diagnostic always freeeze when it reach 3 of 4, nearly around finish. i have waited all night and at the morning it still stay the same. do i need to just pass 2 times ? or i should have pass 4 also if i set to 4 times ?

Answer 3

Hi, Albert Theodorus 施升濠

I am very glad to receive your reply. The prompt you mentioned after entering a command can be ignored, because the command has already been executed. Have you tried solution number 2 and 5 so far since your reply? I would like to know if there is any new progress in your question.

I am looking forward to your reply again.

Best Regards,

Martin | Microsoft Community Support Specialist

Answer 4

Reinstall all hardware drivers

i have already format my pc, but i did not save the driver from the first time i bought the pc. so i download everything i need again from the manufacture site.

i have already turn off all the auto clock and disable any clocking from the bios.
for %i in (%windir%\system32\*.dll) do regsvr32.exe /s %i

this command let me install directplay which maybe i still dont have yet.
other than that command. other dont have a noticeable error

this pc have never change any parts before.

the only change is in the monitor.
previously i am using LG 22 Inch Monitor but changing it to :
i am currently using Ultra Wide Curved Gaming Monitor 30 Inch 1080P 200Hz

i'll check solution number 2 and 5.

Answer 5

Hi, Albert Theodorus 施升濠

Welcome to the Microsoft community.

Did you do anything special before the blue screen happened? For example, install the Windows update and replace the hardware. If so, please describe it in detail or take a screenshot in your next reply.

According to the blue screen log analysis result, The error code is KMODE\_EXCEPTION\_NOT\_HANDLED (1e). This is a very common BugCheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address.it is because the driver of one of your devices is incompatible with the current system. The process that generates the blue screen is ntkrnlmp.exe, which is the Windows kernel file .You can try the following steps.

1.  Reinstall all hardware drivers

You can download the appropriate drivers (including BIOS, standalone and core graphics cards, wired and wireless network cards, sound cards, SATA, etc.) from your computer manufacturer's website, and then manually reinstall them, especially graphics drivers.

2.  Diagnose the memory

Win + Q Open the search box, type "MdSched", press Enter to open the memory diagnostic screen, select "Restart now and check for problems (recommended)." Then restart the system and start memory diagnostics.

3.  If the CPU/GPU is manually overclocked, restore the frequency and all related values to the default values.

4.  Repair the damaged system kernel file

Run the command prompt as administrator (Win + Q opens the search box, type "cmd", select "Run as administrator") and type the following command.

    sfc /scannow

    DISM /Online /Cleanup-Image /RestoreHealth

    for %i in (%windir%\\system32\\*.dll) do regsvr32.exe /s %i

5.  If the above steps do not solve your problem, you can try a clean boot, you can refer to the following article:

How to perform a clean boot in Windows - Microsoft Support

If there is anything not clear or I can't understand your problem, please do not hesitate to let me know.

Best Regards,

Martin | Microsoft Community Support Specialist

Share via

recently BSOD after formatting my pc

Debugging Details:

Followup: MachineOwner

7 answers