Share via

BSOD on startup

Anonymous
2024-05-30T20:08:34+00:00

I have been getting occasional BSOD on startups and shutdowns. I've looked at the event manager and it says: The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000006000, 0xffffa28d41d24480, 0xffffffffc0000225, 0x0000000000000000). 

It usually happens after I spend more than 3-4 hours on the PC.

Here are the minidumps https://www.dropbox.com/scl/fi/dqmdvfz0lrg7ulfb7avkp/Minidump.zip?rlkey=84rify9jsclz6wpxj331z9ruq&st=vrofeafr&dl=0

Windows for home | Windows 10 | Performance and system failures

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 No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-06-01T03:05:46+00:00

    Thank you for your reply.

    1. search for CMD, find the command prompt and select Run as administrator.
    2. Enter the following commands one at a time, making sure to only execute the next command after the previous one completes:

    DISM /Online /Cleanup-Image /ScanHealth

    DISM /Online /Cleanup-Image /CheckHealth

    DISM /Online /Cleanup-Image /RestoreHealth

    SFC /Scannow

    1. After the scanning is completed, you can check the scanning information, have you tried it?

    You try to use it for a while, and then a new blue screen log you uploaded to us!

    Also if it's not the battery it could be the power supply

    Of course this can be observed in the new blue screen logs.

    But it could be that the power supply is not a fatal error.

    but the blue screen logs will also show it

    Kirito|Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-05-31T07:45:36+00:00

    Thank you for your reply,

    I want to ask what is the downsides of not using compressed memory because I ran both the memory check tool and memtest and they both turned out ok.

    Secondly this is a desktop it does not have any battery-related settings in the device manager, What should I do for the second error since it is a desktop?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-05-31T07:24:56+00:00

    Hello yiğitharun and welcome to the Microsoft Community!

    According to your feedback, you are experiencing a blue screen of death problem with your computer at startup

    From the blue screen logs you uploaded, I found three issues

    I will use this to explain them to you

    1. The first error is ntkrnlmp.exe error caused by MemCompression

    This is a memory error

    If you get a memcompression blue screen, you can fix it by disabling memory compression.

    Right click on the start menu and select “windows powershell (administrator)” and enter the following command: Disable-MMAgent -mc, then reboot your computer to take effect.

    If you want to restore it, you can type Enable-MMAgent -mc. To check the current status you can enter Get-mmagent command.

    Meanwhile, you can try the following methods to see if there is any problem with your memory stick hardware

    Check the RAM:

    Tap Windows+R, type MdSched and tap Enter to open the memory diagnostic tool

    Tap Reboot Now and check for problems

    Follow the prompts to check, wait for it to complete, and check the report to see if any problems are detected.

    You can upload the information to us.

    1. The error reported is The power policy manager experienced a fatal error.

    It is about stornvme.sys.

    stornvme.sys is the storage miniport driver.

    The reason for the blue screen is “The power policy manager experienced a fatal error”, which may be caused by an abnormality in the power related driver.

    You can try the following steps to resolve this issue:

    Launch the Device Manager by pressing “Windows Logo Key + X”.

    Under the “Battery” category, right-click on all drivers and select Uninstall. Once the uninstallation is complete, reboot the device.

    Open Device Manager again, select the Power category, click Actions > Scan for hardware changes, and wait for Windows to automatically reinstall the drivers.

    Reboot the device again after the installation is complete.

    Download the BIOS and power-related driver installation package for your device model from the official website of the device brand, and overlay and install it into the device.

    Reboot the device again after installation and see if the blue screen still appears.

    1. nsiproxy.sys error caused by svchost.exe

    Svchost.exe is a system process responsible for shared services

    nsiproxy.sys is the network storage interface proxy service driver

    We suggest you to use the following methods: i. Update or reinstall the drivers of all major hardware of your computer (including discrete and core graphics cards, wired and wireless network cards, sound cards, etc.) and bios through official channels. ii. Please completely uninstall the previous drivers before installation. iii. Do not install drivers from third-party websites. If the computer is overclocked, it is recommended to cancel the overclocking and use it at the default frequency. Use the sfc / scannow command to detect and repair damaged system files. Right-click the Start menu → click (win10/Windows PowerShell (Administrator) (A)) (win11/Windows Terminal (Administrator)) → type: sfc /SCANNOW (press Enter) Dism /Online /Cleanup-Image /ScanHealth (press Enter) Dism /Online /Cleanup-Image /CheckHealth (press Enter) DISM /Online /Cleanup-image /RestoreHealth (press Enter) When finished, restart the computer and again type: sfc /SCANNOW (press the (Press Enter)

    Next, uninstall the optimization software that came with your system.

    After the above attempts, if the blue screen occurs again

    Please upload the new blue screen log to us.

    Thank you for your understanding and support!

    We hope you find the above information helpful.

    Kirito|Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments No comments