Share via

BSOD Occurs When Shutting Down Computer

Anonymous
2025-05-19T16:51:35+00:00

Hello! I have prepared a report to tell you about some serious problems I have experienced and to ask what is really the reason behind them. And this report is not in depth. It is just a summary. Also, this report is definitely not a joke and is a real event:

On May 10, since the KB update could not be installed on the computer (error code 0x8000FFFF, and all solutions have been tried.) I installed an update from the microsoft update catalog. Since the update could not be installed, the error was:

This update is not suitable for your computer.

I tried other KB updates besides this error, the result was the same. Therefore, I started to shut down the computer with alt+f4. However, while shutting down, the system suddenly crashed and a BSOD screen appeared like this:

This BSOD screen was not ordinary and it was quite strange that it was dark blue. However, after the BSOD, the computer was able to boot normally. (That is, I was able to access the desktop without any problems.) 8 days passed. And yesterday at 2025/05/18 13:30:34, I had another BSOD. Here's how it happened:

I opened a game from Steam on the computer and played it. Then I closed Steam but did not close it completely. I pressed Alt+F4 to shut down the computer and the following screen appeared while shutting down:

There is an application that prevents you from shutting down your computer,

Steam is preventing you from shutting down your computer.

Close it anyway - Cancel

The selected sentence here was cancel and my hand slipped and I pressed enter and canceled. I was greeted by a completely gray screen. (Either the graphics driver crashed or Explorer crashed.) Then 2-3 seconds passed and I got a BSOD. The BSOD screen was the same again:

Here is the Event Viewer as an evaluation:

Event Viewer deatils:

This computer has rebooted in a bugcheck. The bugcheck performed was: 0xc000a003 (0x00000000000000000, 0x0000000000000000, 0x0000000000000000, 0x00000000000000000). The dump was saved to: C:\WINDOWS\Minidump\051825-5671-01.dmp. Report ID: bbd7bd95-ef51-42b0-80a1-6513d16132ae.

Apart from these, the computer is trying KB updates in the background and it keeps failing. The following were tried as a solution:

Watched all videos to solve update errors on Youtube.

All solutions for the update error from artificial intelligence.

All cache related to the update has been cleared.

But all of them were in vain. Also the following happens:

-Dism and sfc are not working.

-I think WinSxS is corrupted.

Except for KB updates, other updates are installed by Windows Update.

-I can't delete windows update copies with disk cleanup. (No more)

-Sometimes when shutting down or restarting, "Updates are in progress. Please keep your computer on." And this happens twice when restarting. However, it is completed in a short time. When shutting down, this screen appears first when shutting down and then when turning on.

-When the computer gives an error, the most specific and extreme errors occur.

Apart from these, I checked all the hardware at the BIOS level and everything was normal. In other words, everything is physically intact and the firmwares is not corrupted. However, it will not work the following:

-In-place upgrade. (It will drag my system into even more absurd errors)

-A clean installation. (Disk cleaning run as administrator "i.e. cleanmgr" or something else, more absurd and specific unique errors.

-There is no point in doing sfc or dism from WinRe. Because the problem is in the malfunctioning of WinSxS or Windows.

-A bug that does not exist in any forum, so there is no point in looking for a solution.

-A bug that is so specific that it cannot be solved even with regedit.

In short, the system has disabled itself but without showing it to me. Also, I always use the same license key and this license key is retail, that is, a physical key, also original. These events are really causing chaos, and they are trying to make my patience and solution almost impossible. So I'm thinking about a new operating system, (for example, POP!_OS, and similar Linux distributions or stable OS .etc) Also, there is no virus on the computer. Even if there was, it would not create such specific errors. Please tell me what could be the real reason behind these errors. Maybe I tried all the solutions, I tried specific codes, but it did not work. Since in-place upgrade will continue with the same results, there is no point. Either give me a specific solution that solves all these windows errors or suggest me the most stable operating system. (ESPECIALLY non-Windows!!!)

Regards, MovelessMove.

[NOTE: I want to remind you again, I tried all the solutions but couldn't find a solution to the impasse. If I need to remind you, I can guarantee and swear that everything I wrote is 100% real and not a troll.]

[[ALSO, please do not have independent consultants respond here, as the errors are very specific.]]

Windows for home | Windows 11 | 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

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-06-17T02:29:38+00:00

    I found the reason myself and it is necessary to update the dbx at the firmware level. I even formatted it because of the same problem but the same problem persists. However, I do not know how to update the dbx at the firmware level. Also, this is only related to secure boot in Windows, it is not normally available in operating systems other than Windows. Also, do you have this error at a certain interval? I mean, when you shut down or restart your computer?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-06-17T02:12:30+00:00

    Did you ever figure this out? I also just got this bsod code and can not find it anywere

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-05-20T06:13:11+00:00

    And here is DumpStack analysis:

    DLOGFILE00010000DUMP

    Dump stack initialized at UTC: 2025/05/18 10:30:34, local time: 2025/05/18 13:30:34.

    #BugCheckCode 0x00000000C000A003

    #BugCheckP1 0x0000000000000000

    #BugCheckP2 0x0000000000000000

    #BugCheckP3 0x0000000000000000

    #BugCheckP4 0x0000000000000000

    Progress 0x00000042

    Elapsed BugCheck duration 00001952ms

    Starting get secondary dump callbacks size.

    Progress 0x00000052

    Finish get secondary dump callbacks size.

    Dump Type: 4, Total Dump Size: 2567538, Secondary Dump Size: 2363762.

    Starting write of dump header.

    Finish write of dump header.

    Starting write of minidump data.

    Finish writing of minidump data.

    Progress 0x00000044

    Elapsed BugCheck duration 00003861ms

    Starting invoking secondary dump callbacks.

    Calling nvlddmkm.sys secondary callback.

    Return from nvlddmkm.sys secondary callback.

    Writing nvlddmkm.sys secondary callback data.

    Writing nvlddmkm.sys secondary callback data done.

    Calling USBXHCI secondary callback.

    Return from USBXHCI secondary callback.

    Writing USBXHCI secondary callback data.

    Writing USBXHCI secondary callback data done.

    Calling PortDriverStandard secondary callback.

    Return from PortDriverStandard secondary callback.

    Writing PortDriverStandard secondary callback data.

    Writing PortDriverStandard secondary callback data done.

    Calling \Device\DxgKrnl secondary callback.

    Return from \Device\DxgKrnl secondary callback.

    Writing \Device\DxgKrnl secondary callback data.

    Writing \Device\DxgKrnl secondary callback data done.

    Calling Wdf01000 secondary callback.

    Return from Wdf01000 secondary callback.

    Writing Wdf01000 secondary callback data.

    Writing Wdf01000 secondary callback data done.

    Calling blackbox - CI secondary callback.

    Return from blackbox - CI secondary callback.

    Writing blackbox - CI secondary callback data.

    Writing blackbox - CI secondary callback data done.

    Calling blackbox - Winlogon secondary callback.

    Return from blackbox - Winlogon secondary callback.

    Writing blackbox - Winlogon secondary callback data.

    Writing blackbox - Winlogon secondary callback data done.

    Calling blackbox - NTFS secondary callback.

    Return from blackbox - NTFS secondary callback.

    Writing blackbox - NTFS secondary callback data.

    Writing blackbox - NTFS secondary callback data done.

    Calling blackbox - PNP secondary callback.

    Return from blackbox - PNP secondary callback.

    Writing blackbox - PNP secondary callback data.

    Writing blackbox - PNP secondary callback data done.

    Calling blackbox - BSD secondary callback.

    Return from blackbox - BSD secondary callback.

    Writing blackbox - BSD secondary callback data.

    Writing blackbox - BSD secondary callback data done.

    Calling secondary multi-part dump callbacks.

    Starting TRIAGEDUMPDATA multi-part secondary callback.

    Finish TRIAGEDUMPDATA multi-part secondary callback.

    Starting SMBiosData multi-part secondary callback.

    Finish SMBiosData multi-part secondary callback.

    Starting SMBiosRegistry multi-part secondary callback.

    Finish SMBiosRegistry multi-part secondary callback.

    Starting SMBiosRegisters multi-part secondary callback.

    Finish SMBiosRegisters multi-part secondary callback.

    Starting SMBiosDataACPI multi-part secondary callback.

    Finish SMBiosDataACPI multi-part secondary callback.

    Starting PCI multi-part secondary callback.

    Finish PCI multi-part secondary callback.

    Starting Etw multi-part secondary callback.

    Finish Etw multi-part secondary callback.

    Finish calling secondary multi-part dump callbacks.

    Progress 0x00000045

    Finish invoking secondary dump callbacks.

    Starting invoking dump complete callbacks; Type: 0x04.

    Finished invoking dump complete callbacks; Type: 0x04.

    Progress 0x00000046

    Dump ended at UTC: 2025/05/18 10:30:34, local time: 2025/05/18 13:30:34.

    Elapsed BugCheck duration 00003896ms

    Progress 0x00000053

    Dump completed successfully.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-05-20T06:10:50+00:00

    Hello,

    Thank you for posting the issue in the community forum.

    Thank you for posting your questions in the community forum.

    As far I can understand that your computer has a BSOD problem. So, you can follow these steps to fix the blue screen of death issue:

    Step 1 – Open the Windows Recovery Environment as follows:

    • Go to Settings > System > Recovery (Windows 11), Settings > Update & Security >Recovery (Windows 10), and tap Advanced Restart at Startup.
    • Press the Shift key on your keyboard and restart your system from the Start menu.
    • Press and hold the CPU power button for 10 seconds to shut down the system, restart the system, and then press the power button again for 10 seconds when the Windows logo appears until it shuts down again. Repeat this step 3 times to enter the Windows Recovery Environment.

    Step 2 - Click on "Advanced Options" > troubleshoot the issue.

    Step 3 - Click on Uninstall the update in case there is a problem after the update.

    Step 4 – If there are any issues after installing the new app, click on "Startup Settings" and restart. Then press F4 or F5 to enter Safe Mode and uninstall the app using the command, appwiz.cpl command will take you to the programs and features that will be able to find all the installed apps. Choose the right app and uninstall it. Then restart the system.

    Step 5: If the issue persists, click on Start Repair and check if the issue is resolved.

    Step 6 – If the issue is still not resolved after starting the repair, repeat steps 1 and 2 and click on the Command Prompt and run the following command one after another:

    1. bootrec /fixmbr
    2. bootrec /fixboot (if it says access denied, no problem, go straight to the next command)
    3. Bootsect/NT60 System
    4. bootrec /fixboot
    5. bootrec /rebuilt
    6. SFC /SCANNOW
    7. chkdsk C:

    Then click Continue to restart the system.

    For more details and to resolve this issue, follow the following link: Resolving Blue Screen errors in Windows - Microsoft Support

    Hopefully, after following these steps correctly, you will be able to fix the blue screen issue.

    Sincerely,

    Sam | Microsoft Community Moderator.

    I think you are underestimating the problem I am experiencing. The problem I am experiencing is one of the most unprecedented errors in the world. And while cleaning unnecessary files from winsxs (with a dism command), it accidentally deleted the repair locations of winsxs. That is why the system is working ridiculously. There are no KB updates, how do you expect me to delete them? Also, commands like sfc, dism, chkdsk C: will not work at all because winsxs is corrupted! The reason I want to don't an in-place upgrade is because I am afraid that the system may exhibit strange behaviors again. Also, the BSOD error stop code: " 0x000a0003 " This error code is neither documented nor official anywhere. If you think it is a virus, you are wrong. Because even a virus cannot do any of these strange things that Windows does. If it were a virus, the system would either give a BSOD at every startup or more serious files would be deleted. Also, the suggestions you give are 4/10 level suggestions. In other words, mid-level solution suggestions. Even if I reset the registry to fix it completely, it won't fix unless WinSxS is reset. Also, no one is telling me why I'm getting these ridiculous BSOD and unusual errors. What really causes these?

    Also, the following are not broken:

    All physical hardware, drivers, firmware, cables.

    I must say, I'm not mad, I'm just trying to understand why these weird things are happening. Best regards, MovelessMove.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-05-19T22:29:59+00:00

    Hello,

    Thank you for posting the issue in the community forum.

    Thank you for posting your questions in the community forum.

    As far I can understand that your computer has a BSOD problem. So, you can follow these steps to fix the blue screen of death issue:

    Step 1 – Open the Windows Recovery Environment as follows:

    • Go to Settings > System > Recovery (Windows 11), Settings > Update & Security >Recovery (Windows 10), and tap Advanced Restart at Startup.
    • Press the Shift key on your keyboard and restart your system from the Start menu.
    • Press and hold the CPU power button for 10 seconds to shut down the system, restart the system, and then press the power button again for 10 seconds when the Windows logo appears until it shuts down again. Repeat this step 3 times to enter the Windows Recovery Environment.

    Step 2 - Click on "Advanced Options" > troubleshoot the issue.

    Step 3 - Click on Uninstall the update in case there is a problem after the update.

    Step 4 – If there are any issues after installing the new app, click on "Startup Settings" and restart. Then press F4 or F5 to enter Safe Mode and uninstall the app using the command, appwiz.cpl command will take you to the programs and features that will be able to find all the installed apps. Choose the right app and uninstall it. Then restart the system.

    Step 5: If the issue persists, click on Start Repair and check if the issue is resolved.

    Step 6 – If the issue is still not resolved after starting the repair, repeat steps 1 and 2 and click on the Command Prompt and run the following command one after another:

    1. bootrec /fixmbr
    2. bootrec /fixboot (if it says access denied, no problem, go straight to the next command)
    3. Bootsect/NT60 System
    4. bootrec /fixboot
    5. bootrec /rebuilt
    6. SFC /SCANNOW
    7. chkdsk C:

    Then click Continue to restart the system.

    For more details and to resolve this issue, follow the following link: Resolving Blue Screen errors in Windows - Microsoft Support

    Hopefully, after following these steps correctly, you will be able to fix the blue screen issue.

    Sincerely,

    Sam | Microsoft Community Moderator.

    Was this answer helpful?

    0 comments