Sudden crashes and BSOD in Win10
Hello! I have an Asus Vivobook 15, that came with Keep-OS and I installed Windows 11 using the official website and step by step. Last week it started crashing and having BSOD's, getting stuck on boot and sometimes not even recognizing the OS (win11). It started after a Win Update. Since I haven't found a solution and Asus does not care for the consumer, had no alternative and downgraded to Win 10. I'm still facing some crashes and BSOD. I checked the SDD, manually and with Crystal Disk Info (98% health), checked the fan... I really don't know what else to do. https://1drv.ms/u/c/7f13816d644baeb5/IQCrQrt8VfRkRZAOG5BT6By0ASV3wLkzdMiLZ-ctbrSsW84?e=PTUVlN Here is the System Events Log.
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_link
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.
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
