How to analyze minidump file?
I using Windows 10 and my PC got blue screen, and then I have 1 minidump file in Folder /windows/minidump/. but I can't analyze what is wrong with my Computer. can anyone help me to analyze it? I will upload the minidump in Gdrive, the link down below. thanks in advance! https://drive.google.com/file/d/15kM6memcnABF6qym6OLnNtdkEd4JxS22/view?usp=drive_linkSurface Book 3 - BSOD when using external monitor (Windows 10 20H2)
Dear community, I am facing an issue where my Surface Book 3 device goes into a BSOD when it is idle for some minutes, while connected to an external Samsung S24R650 monitor. From Event Viewer, I get this error: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000019c (0x0000000000000050, 0xffffa10b079af080, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b0e12159-a128-4fa6-9dcc-d5a842b5e62a. And from the WinDbg analysis, the result is the following: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WIN32K_POWER_WATCHDOG_TIMEOUT (19c) Win32k did not turn the monitor on in a timely manner. Arguments: Arg1: 0000000000000050, Calling monitor driver to power on. Arg2: ffffa10b079af080, Pointer to the power request worker thread. Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3218 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 13751 Key : Analysis.Init.CPU.mSec Value: 999 Key : Analysis.Init.Elapsed.mSec Value: 7335 Key : Analysis.Memory.CommitPeak.Mb Value: 97 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 FILE_IN_CAB: MEMORY.DMP BUGCHECK_CODE: 19c BUGCHECK_P1: 50 BUGCHECK_P2: ffffa10b079af080 BUGCHECK_P3: 0 BUGCHECK_P4: 0 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: csrss.exe FAULTING_THREAD: ffffa10b079af080 STACK_TEXT: fffffa0f`cf845040 fffff806`6559481a : 00000000`00000012 00000000`00000000 fffffa0f`cf845400 00001f80`00000000 : igdkmdn64+0x374f87 fffffa0f`cf845050 fffff806`6558d855 : 00000000`00045454 ffffa10b`00a82000 fffffa0f`cf845348 ffffa10b`062ee7d0 : igdkmdn64+0x37481a fffffa0f`cf845130 fffff806`6558509c : 00000000`00000000 ffffa10b`06247be0 00000000`00000064 fffff806`65594f2a : igdkmdn64+0x36d855 fffffa0f`cf8451a0 fffff806`6526d29f : 00000000`00045404 00000000`00000003 00000000`00000000 00000000`00000000 : igdkmdn64+0x36509c fffffa0f`cf8451d0 fffff806`652717df : 00000000`00000001 00000000`00045404 ffffa10b`00a82000 fffff806`6558509c : igdkmdn64+0x4d29f fffffa0f`cf845260 fffff806`6529f5ff : 00000000`ffffffd0 fffff806`6526d3a4 00000000`01000000 00000000`00000000 : igdkmdn64+0x517df fffffa0f`cf8452d0 fffff806`6529fdf3 : fffff806`0000000f 00000000`00000028 ffffa10b`06247be0 00000000`00000000 : igdkmdn64+0x7f5ff fffffa0f`cf845370 fffff806`652a0516 : 00000000`00000010 00000000`00000000 ffffa10b`06731400 ffffa10a`fdb59bf0 : igdkmdn64+0x7fdf3 fffffa0f`cf8453f0 fffff806`6529e114 : 00000000`00000107 ffffa10b`06731400 ffffa10b`06731410 00000000`00000000 : igdkmdn64+0x80516 fffffa0f`cf8454e0 fffff806`65280dc3 : ffffa10b`00000101 00000000`00000022 fffffa0f`00000107 00000000`00000001 : igdkmdn64+0x7e114 fffffa0f`cf845550 fffff806`65273e90 : 00000001`00000004 ffffa10b`06244560 fffffa0f`cf845630 ffffa10a`f7c02000 : igdkmdn64+0x60dc3 fffffa0f`cf845590 fffff806`6527e604 : 00000000`00000010 00000000`00000001 fffffa0f`cf845600 fffff806`5b01f500 : igdkmdn64+0x53e90 fffffa0f`cf8455e0 fffff806`6546e206 : ffffa10b`00a82000 fffff806`5b084ea4 00000000`00000001 00000000`00000000 : igdkmdn64+0x5e604 fffffa0f`cf845610 fffff806`6546c27f : 00000000`00000000 ffffa10b`06244560 00000000`00000001 fffffa0f`cf845759 : igdkmdn64+0x24e206 fffffa0f`cf845670 fffff806`65452cf7 : ffffa10b`0601c2b6 00000000`0002625a ffffa10b`0601c230 ffffa10a`fda24501 : igdkmdn64+0x24c27f fffffa0f`cf8456f0 fffff806`65451c0e : 00000000`000c323a fffffa0f`cf840000 00000000`00000000 00000000`000c31c3 : igdkmdn64+0x232cf7 fffffa0f`cf8457c0 fffff806`6544ec87 : 00000000`00000080 ffffa10b`06247be0 00000000`00000000 ffffa10a`fda24510 : igdkmdn64+0x231c0e fffffa0f`cf8458f0 fffff806`65430760 : 00000000`00000000 ffffa10a`fda24510 fffffa0f`cf845af8 ffffa10b`0688e4e0 : igdkmdn64+0x22ec87 fffffa0f`cf845950 fffff806`654251a7 : ffffa10b`20fb0cb8 00000000`00000005 fffffa0f`cf845b20 fffff806`6526c2d5 : igdkmdn64+0x210760 fffffa0f`cf8459b0 fffff806`65422740 : 00000000`00000000 fffffa0f`cf845b20 00000000`00000005 ffffa10b`20fb0cb8 : igdkmdn64+0x2051a7 fffffa0f`cf845a20 fffff806`65436310 : da6c18ee`8bf0cebc 00000000`00000003 00000000`00004032 ffffa10b`162187c8 : igdkmdn64+0x202740 fffffa0f`cf845bc0 fffff806`6543ef0d : ffffa10b`06244560 ffffa10b`162187b0 ffffa10b`06244560 00000000`00000000 : igdkmdn64+0x216310 fffffa0f`cf845c30 fffff806`6543eac7 : ffffa10b`06244560 00000000`00000000 ffffa10b`1e8a65d0 00000000`00000000 : igdkmdn64+0x21ef0d fffffa0f`cf845d90 fffff806`6542de02 : ffffa10b`06244560 fffffa0f`cf846007 ffffa10b`06244560 ffffa10b`06247be0 : igdkmdn64+0x21eac7 fffffa0f`cf845f00 fffff806`654268bb : 00000001`00000004 ffffa10b`1e8a65d0 ffffa10b`06244560 fffff806`6526e400 : igdkmdn64+0x20de02 fffffa0f`cf846050 fffff806`6541f262 : ffffa10b`1e8a65d0 fffffa0f`cf846540 fffffa0f`cf846540 00000000`00000000 : igdkmdn64+0x2068bb fffffa0f`cf846130 fffff806`653fa41d : 00000000`00000001 ffffa10b`06919dc0 00000000`00000040 fffffa0f`cf8465c0 : igdkmdn64+0x1ff262 fffffa0f`cf8464c0 fffff806`653ef308 : 00000000`00000000 fffff806`5b0f405f ffffa10b`06247be0 00000000`00000000 : igdkmdn64+0x1da41d fffffa0f`cf8467b0 fffff806`653b6351 : ffffa10a`ff730000 fffffa0f`cf846999 fffffa0f`cf846999 00000000`00989680 : igdkmdn64+0x1cf308 fffffa0f`cf846810 fffff806`65257026 : ffffa10b`00a82000 ffffa10a`fdf49180 ffffa10b`00a82000 00000000`00000000 : igdkmdn64+0x196351 fffffa0f`cf846860 fffff806`603337ad : 00000000`00000000 ffffa10a`fdf49ec8 fffffa0f`cf846940 00000000`00000000 : igdkmdn64+0x37026 fffffa0f`cf8468c0 fffff806`602b4aeb : 0000001d`0e01fb64 fffffa0f`cf846999 fffffa0f`cf847130 fffff780`00000320 : dxgkrnl!DpiDxgkDdiDisplayDetectControl+0x7eb95 fffffa0f`cf846920 fffff806`60332d33 : ffffa10a`fdf49180 ffffa10a`fdf49180 ffffa10a`fdf49180 00000000`00000001 : dxgkrnl!DpiFdoInvalidateChildRelations+0x10b fffffa0f`cf846a00 fffff806`6025ede6 : 00000000`00000021 fffffa0f`cf846be8 00000000`ffffffff fffff806`5b460c20 : dxgkrnl!DxgkPowerOnOffMonitor+0x7f76f fffffa0f`cf846b20 fffff806`60266270 : ffffa10b`ffffffff ffffa10a`fe3b2e20 ffffa10b`06bbae90 00000048`0000001e : dxgkrnl!DpiGdoDispatchInternalIoctl+0x586 fffffa0f`cf846bd0 fffff806`5b08f825 : 00000000`00000000 ffffa10a`00000000 00000000`c0000002 00000000`00000010 : dxgkrnl!DpiDispatchInternalIoctl+0x100 fffffa0f`cf846d00 fffff4e3`be863a39 : fffffa0f`cf846dd0 00000000`00000000 fffff4a7`82ca8490 fffff4e3`be8caa3a : nt!IofCallDriver+0x55 fffffa0f`cf846d40 fffff4e3`be8ca672 : fffff4a7`82ca8490 fffffa0f`cf846ee0 00000000`00000000 ffffa10b`00000000 : win32kbase!GreDeviceIoControlImpl+0xed fffffa0f`cf846de0 fffff4e3`be8ca43f : fffffa0f`cf847130 00000000`00000000 00000000`00000001 00000000`00000050 : win32kbase!DrvSetWddmDeviceMonitorPowerState+0x212 fffffa0f`cf846f50 fffff4e3`be88d5af : 00000000`00000050 00000000`c00000bb 00000000`c00000bb 00000000`00000001 : win32kbase!DrvSetMonitorPowerState+0x2f fffffa0f`cf846f80 fffff4e3`be88cb7b : 00000000`00000000 fffffa0f`cf847100 00000000`00000000 00000000`00000001 : win32kbase!PowerOnMonitor+0x1cf fffffa0f`cf847000 fffff4e3`be88c7e2 : ffffa10b`25a02720 ffffa10b`25a02720 00000000`00000001 00000000`00000000 : win32kbase!xxxUserPowerEventCalloutWorker+0x20b fffffa0f`cf847370 fffff4e3`beb80ce1 : ffffa10b`079af080 00000000`00000000 00000000`00000025 00000000`00000025 : win32kbase!xxxUserPowerCalloutWorker+0xe2 fffffa0f`cf8473e0 fffff4e3`bf0e474e : ffffa10b`079af080 00000000`00000000 00000000`00000000 00000000`00000000 : win32kfull!NtUserCallNoParam+0x71 fffffa0f`cf847410 fffff806`5b208cb5 : ffffa10b`00000005 00000000`00000025 00000000`00000000 00000000`00000000 : win32k!NtUserCallNoParam+0x16 fffffa0f`cf847440 00007ff8`de1110e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25 0000003d`c78bfe58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`de1110e4 STACK_COMMAND: .thread 0xffffa10b079af080 ; kb SYMBOL_NAME: igdkmdn64+374f87 MODULE_NAME: igdkmdn64 IMAGE_NAME: igdkmdn64.sys IMAGE_VERSION: 30.0.101.1340 BUCKET_ID_FUNC_OFFSET: 374f87 FAILURE_BUCKET_ID: 0x19C_DRVSETMONITORPOWERSTATE_HANG_igdkmdn64!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {cfff9c4c-cbec-2dd9-38ae-0ef8cae456c9} Followup: MachineOwner Device is fully patched (January 2022) and even after updating to the latest Intel driver, it still crashes. I am now applying February patches, but I am not sure it will be fixed. Any ideas? Kind regards, Bruno MartinsSurface Pro 8 BSOD, help to identify why?
HI, Since a couple of month a rather stable Windows 11 (microsoft re-imaged) on a Surface Pro 8 has become extremely unstable. I experience BSODs daily. I'm rather "walked" in troubleshooting but this one doesn't pop out for me what's going down. Trying to figure if this is a software or hardware problem. I haven't found any correlation when it crashes, what I've got started and running. This machine got some installs. Edge Dev, Hyper-V and more. Machine is up to date with the support/driver files from Microsoft. WU is also up to date, nothing missing. I'm not sure but I think I experience the crashes when I've got either Edge or a Remote Desktop session running (using RDCman from Sysinternals). But they're user space application and should bring the system down. Anyone here with the skills to find out why if I provide a minidump?
Missing C:\Windows\System32\ntkrnlmp.exe causing frequent BSOD on Windows 11 Insider
Hi, I got a problem with my Windows 11 Insider as it got frequent BSOD (1-3 times a day) and it is really frustating. The BSOD code varies but the most common is IRQL_NOT_LESS_OR_EQUAL. When I see the log on WinDBG, I found out that the cause was not because of RAM or drivers or something else. It caused by missing ntkrnlmp.exe in C:\Windows\System32. I already contacted Microsoft support chat, but none of their solution are working. The solution I got from them are: - Running command such as SFC or DISM: but none of them worked. They can't detect anything. - Creating a new profile: I dont think profile will mess up/restore file inside System32 - Repair using ISO: I can't do that since I have to wipe out the data, so it is already out of question. - Reinstall: I don't want to wipe out my data. My solution to (hopefuly) fix this is I need the copy of the file so I can place it inside my C:\Windows\System32. I know it is risky but I dont have any choice. If I don't know the risk, I would already download it from random website on the internet. Log using !sym noisy: https://drive.google.com/file/d/1XY4UNt51EupxcxydrINHVdFswUcceCCz/view?usp=share_link Thanks in advance.MEMORY_MANAGEMENT BSOD on VMware! (25099)
[UPDATE 4/21] Setting the VM to use a single core in VMware allows this build to boot without any issues. This is more of a heads up for people trying to install this build in VMware. Most attempts to boot this build in the latest version of VMware will result in a MEMORY_MANAGEMENT BSOD. After several restarts, you will eventually get into Setup/Windows. Here's a feedback hub link for those who have also experienced this. https://aka.ms/AAgq409 Does anyone have a physical machine that has 2 or more CPUs installed? If so, can you please try to boot 25099 and see if you get the MEMORY_MANAGEMENT BSOD? I would love to know if this occurs on real hardware From what I've observed: 25099 with 6 processor cores in VMware: Fine 25099 with 4 physical CPUs: BSODs
Windows 10 22H2 can be rendered unbootable if ''Windows Fax and Scan'' is removed
There is a serious bug in the 32-bit kernel releases (x86) of Windows 10 22H2 (though older versions, such as 21H2 or 21H1 may also be affected; I have not tested). I was doing some test-installs of the latest 22H2 release, using install-media built from the Media Creation Tool. (The version that this tool creates is currently Build 19045.2006). To reproduce this bug, do the following: 1 Install the x86 version of Windows 10 Version 22H2 onto a PC, or inside a VM (e.g. Home or Pro) 2 After the Desktop appears, go to Start > Settings > Apps > Optional Features 3 Click "Windows Fax & Scan" in the list, then the "Uninstall" button 4 After the uninstall is finished, and "Reboot required" appears, restart the PC or VM session 5 During the next boot-up, it will first go to this screen briefly: "Updating your system 0%" But will then go to a blue-screen with this error: Stop code: KMODE_EXCEPTION_NOT_HANDLED What failed: NTFS.SYS 6 After a reboot, the blue-screen will appear again, then after the next reboot Windows will go to the "Preparing Automatic Repair" screen 7 The only way to repair the Windows install is to use a System Restore point, should one exist I have been able to replicate this issue on ALL x86 kernel installs of Windows 10 22H2 I have tested, but the 64-bit (x64, AMD64) kernel versions are unaffected. I have no ARM devices to test. Needless to say, this should be treated as critical as this is easily reproduceable, and uses only built-in options supplied with Windows, but leaves systems completely unbootable afterwards. Thanks
