Verify that you have BIOS version 7C51c16.zip or newer installed on your motherboard otherwise it won't be recognized and boot up:
| Ryzen 5 |
Cezanne |
5600G |
100 |
3.9GHz |
3MB |
16MB |
A0 |
65 |
AMDRadeonGraphics |
7C51v16.zip |
Next verify that the Ram you have is compatible with the new 5600G either from MSI QVL LIST FOR RAM for the 5000G/GE processor or check the RAM manufacturer's QVL List to see if it is compatible to your motherboard or processor.
I noticed that you are using Mixed RAM part numbers. That is a big NoNo due to incompatibility issues. Remove all the RAM sticks and just try booting up with one RAM stick and see if it boots into Windows.
First thing I would do is update your BIOS to the most current BIOS version for your motherboard which is :
AMI BIOS7C51v182023-05-099.51 MB (Non-BETA)
The BIOS you installed is a BETA BIOS which could be causing your issue.
Here Microsoft Support on your error: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7b--inaccessible-boo...
Cause
The INACCESSIBLE_BOOT_DEVICE bug check often occurs because of a boot device failure. During I/O system initialization, the boot device driver might have failed to initialize the boot device, typically a hard disk.
File system initialization might have failed because it didn't recognize the data on the boot device. Repartitioning the system partition, changing the BIOS configuration, or installing a disk controller can also cause this error.
This error can occur because of incompatible disk hardware. If the error occurred at the initial setup of the system, the system might have been installed on an unsupported disk controller. Some disk controllers require other drivers to be present when Windows starts.
This error can occur, when the storage hardware has failed, and is not able to respond to the request from Windows.
Resolution
This error always occurs while the system is starting. This error frequently occurs before the debugger connection is established, so debugging can be difficult. The OS might not be accessible and the error logs might be empty, as the OS hasn't booted far enough to start those subsystems. The following sections explain resolutions for both situations, if you're unable to boot Windows and if you're able to boot Windows.
If you're unable to boot Windows
If you receive this stop code and Windows doesn't boot forward into the OS, try the following resolutions:
-
Revert any recent hardware changes.
Remove any recently added hardware, especially hard disk drives or controllers, to see if the error is resolved. If the problematic hardware is a hard disk drive, the disk firmware version might be incompatible with your version of the Windows operating system. Contact the manufacturer for updates. If you removed another piece of hardware and the error is resolved, IRQ or I/O port conflicts might exist. Reconfigure the new device according to the manufacturer's instructions.
If you have recently made changes to UEFI (BIOS) settings, such as changing the controller mode from legacy to AHCI in UEFI, revert those changes. For more information, see Advanced host controller interface.
-
Check for storage device compatibility.
Confirm that all hard disk drivers, hard disk controllers, and any other storage adapters are compatible with the installed version of Windows. For example, you can get information about compatibility at Windows 10 specifications.
-
Update UEFI (BIOS) and firmware.
Check the availability of updates for the system UEFI (BIOS) and storage controller firmware.
-
Use the Windows Media Creation Tool to create a bootable USB thumb drive or DVD.
Use the Media Creation Tool on another computer to create a bootable USB thumb drive or DVD. Use this tool to perform a clean install by selecting the setup file or booting from the USB.
For more information, see Get Windows 10.
You might need to disable features, or change your boot sequence priority in the UEFI (BIOS) menu to boot from USB, FDD (FlashDiskDrive) or DVD instead of HDD.
Common boot menu keys
The boot menu keys vary per manufacturer. These keys are commonly used. Check the PC documentation to determine what boot key is used.
Frequently used boot menu keys are:
F12
ESC
F9
F10
F8
Common UEFI (BIOS) setup keys
UEFI (BIOS) setup keys vary per manufacturer. These keys are commonly used. Check the PC documentation to determine what setup key is used.
Frequently used UEFI (BIOS) setup keys are:
ESC
DEL
F2
If you're able to boot Windows
If you receive this stop code and Windows does boot, try the following resolutions:
-
Boot to Safe Mode and then boot normally.
Booting into Safe Mode loads a core set of storage drivers that can allow for the storage system to be accessed once again. Complete the following steps to boot into Safe Mode:
- In Settings, select Update and Security.
- Select Recovery > Advanced startup to boot to maintenance mode.
- At the resulting menu, choose Troubleshoot > Advanced Options > Startup Settings > Restart.
- After Windows restarts to the Startup Settings screen, select option 4, 5, or 6 to boot to Safe Mode.
Once Windows is loaded in Safe Mode, restart your PC to see if the proper storage drivers are loaded and that the storage device is recognized.
Safe Mode might also be available by pressing a function key on boot, for example F8. Refer to information from the system manufacturer for specific startup options.
-
Use the scan disk utility to confirm that there are no file system errors. Select and hold (or right-click) on the drive that you want to scan and select Properties > Tools > Check now.
-
Run a virus detection program. Viruses can infect all types of hard disks formatted for Windows and the resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.
-
For IDE devices, define the onboard IDE port as Primary only. Also check each IDE device for the proper master/subordinate/stand alone setting. Try removing all IDE devices except for hard disks. Finally, check the System Log in Event Viewer for other error messages that might help identify the device or driver that's causing the error.
-
Confirm that there's sufficient free space on the hard drive. The operating system and some applications require sufficient free space to create swap files and perform other functions. Based on the system configuration, the exact requirement varies, but it's a good idea to have 10% to 15% of free space available.
-
Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in the driver properties for a faulting driver. Try updating the related driver.
-
Check the System Log in Event Viewer for other error messages that might help pinpoint the device or driver that's causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time frame as the blue screen.
-
You can try running the hardware diagnostics supplied by the system manufacturer.
-
Use the System File Checker tool to repair missing or corrupted system files. The System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. Use the following command to run the System File Checker tool (SFC.exe).
Here is Tom's Hardware tech article also on how to fix your BSOD error: https://www.tomshardware.com/how-to/fix-inaccessible-boot-device-bsod
