Windows 11 ,23H2 version, issue BSOD _ stopcode _bad config and Reboot issue

Question

Windows11 23H2 version BSOD , stopcode, bad config, ......Reboot issue using command prompt , after run SFC /scannow message shown widows resourse protection found corrupt files , e.g C:\windows \logs\CBS\CBS.log

to be successfully repaired if reboot the system

but I'm facing issue with reboot, my hp laptop is unable to reboot because whenever I'm going to reboot, again BSOD screen is coming after 5 min process .....I have tried all possible troubleshooting under Advanced option like startup repair ,not working then system restore also not working for me , system image recovery not working for me , uninstall update not working for me then finally i opted to go Comnand prompt option and use SFC /scannow

I also highlighted here when using UEFI firmware test , I have done all test successfully except SSD test showed ,software error ..........I have only one option command prompt to resolve my issue but we don't know the correct command I have to write to reboot my system subject to BSOD error

could you please resolve it my issue?

Answer 1

Dear S K Sharma1,

Welcome to the Microsoft Community

Thank you for reaching out to the Microsoft Community for assistance. I understand that you're experiencing these persistent Blue Screen of Death (BSOD) issues on your Windows 11 23H2 system. I'll do my best to guide you through the next steps to resolve this problem.

From your description, it seems like your system is encountering frequent BSOD errors, and even after running the SFC /scannow command, the issues persist. Additionally, the UEFI firmware test results indicate a potential software error related to your SSD, which might be contributing to the problem.

Steps to Resolve the Issue

1. Analyze Blue Screen Logs: To help us analyze the cause of these blue screens, I'd like you to set up your system to create a small memory dump file when the error occurs. Here are the steps to configure your system for small memory dump (minidump) files:
   • Right-click on ‘This PC’ or ‘Computer’ on your desktop or in File Explorer, and select ‘Properties’.
   • Click on ‘Advanced system settings’ on the left-hand side.
   • In the System Properties window, go to the ‘Advanced’ tab and click on ‘Settings…’ under the ‘Startup and Recovery’ section.
   • In the Startup and Recovery window, under the ‘System failure’ section, make sure the following settings are configured:
   • Check ‘Write an event to the system log’.
   • Uncheck ‘Automatically restart’.
   • Ensure the ‘Write debugging information’ option is set to ‘Small memory dump (256 KB)’.
   • Confirm the dump file location is set to %SystemRoot%\Minidump.
   • Click ‘OK’ to apply these settings and then restart your computer to ensure the changes take effect.
   Once your system is configured to create small memory dump files, please wait for the next blue screen event to occur. After that, follow these steps to locate and share the dump file:
   1. Navigate to the folder C:\Windows\Minidump.
   2. Locate the most recent .dmp file.
   3. Upload the .dmp file to a network drive or a cloud storage service like OneDrive, Google Drive, or Dropbox.
   4. Share the link to the uploaded file with me here.
   By analyzing the minidump file, I will be able to gain more insights into what might be causing these blue screen errors and provide you with a more accurate solution.
2. SSD Health Check: Given that the SSD test failed during the UEFI firmware tests, the issue might be related to your SSD's health. Use the chkdsk command to check the SSD for errors:

    chkdsk C: /f /r
   

   This will scan the drive for errors and attempt to repair them. Note that this process might take some time, depending on the size and condition of your SSD. Disclaimer:  Microsoft provides no assurances and/or warranties, implied or otherwise, and  is not responsible for the information you receive from the third-party  linked sites or any support related to technology.    If you are going to modify BIOS Settings, please  back up all your personal files first to ensure you do not lose data.
3. Boot in Safe Mode: If you're able to boot into Safe Mode without encountering a BSOD, this may indicate that a third-party driver or software is causing the issue. In Safe Mode, try uninstalling any recently installed drivers or software that could be contributing to the problem. Windows startup settings - Microsoft Support

Please proceed with the steps above and share the blue screen and Event Viewer logs so we can analyze them further. Once we have those logs, we can provide more targeted advice.

If you need help with any of the steps or have further questions, please don't hesitate to reach out. I’m here to help you through this process.

Best Regards,

Martin | Microsoft Community Support Specialist