So. This is a bit of a journey so strap in.
GPU: ASUS RX 6600
CPU: Ryzen 5 9600X
Mobo: ASRock 620M-HDV/M.2+
Will include other beeps and boops if you guys think they're relevant.
I upgraded my setup a week ago. Had issues right from the get-go:
- Windows wouldn't detect the inbuilt monitor speakers
- Couldn't get my screen tablet working
Updated the chipset drivers. Flashed a BIOS update which is when I no longer got display when booting up the computer (no signal), but the display came back after the system booted to windows
Eventually deduced the problem must be in AMD Radeon (TM) graphics driver that showed error 12 in device manager and requested further installation from some Device PCI-VEN_1002&. A similar further installation PCI-VEN demand was in the... security11? You can probably figure it out since I forgot the name of the device, but it shared a location with the graphics driver.
Also took a closer look at the chipset driver installation, which showed one error message regarding an oem11.inf driver
I wanted to uninstall all the AMD drivers and tried using their own software, which requested the computer to be booted in safe mode. Complied, and suddenly I no longer get display
No BIOS, no windows, nothing - just no signal
Made myself a USB stick from where I can boot Ubuntu - no dice, won't boot, stuck to a flashing screen with an underscore. But the catch is, there is a display
Removed the GPU, plugged the dvi cable from my monitor to the MOBO. No signal. Nothing.
Decided to take out the mobo battery. Let it chill for 10-15 minutes before putting it back in. That apparently did not reset the BIOS.
Made a Windows Boot Repair USB. I get display and access to the installation menus. Repair doesn't find anything to fix and apparently I forgot to set a save point. Oops. Oh well.
After that I managed to boot the live version of Ubuntu from the USB. So clearly the internal graphics work, but it absolutely does not explain why I don't get any display for BIOS or Win10
Did I brick my mobo and how the heck do I fix this? Should I try resetting the BIOS again until I actually manage to reset it? I don't have a jumper
Solved! Go to Solution.
UPDATE:
Unfortunately couldn't get the exact response from their tech guy as they weren't at the shop when I picked it up
They took the setup apart. Motherboard and processor were fine physically, no issues there. They reupdated the BIOS to the newest version again and I'm suspecting they reset it before doing so.
Windows had become corrupted. It was missing the boot files and that's why it wouldn't boot at all (but was fine booting from a stick. No clue why win10 boot repair did nothing though)
They could offer no idea why it wouldn't get display for BIOS. They spent 7 whole hours fighting with it, apparently, before getting any display at all.
After I got the machine back, it still had issues finding the inbuilt speakers. There was no longer an error 12 for Amd Radeon Graphics however.
Did a clean install of Win10 and that fixed the speaker issue.
There is a clear cmos pins on that motherboard it's on the lower right corner next to m2_2 slot. ( A620M-HDVM.2.pdf page 9). You can carefully short it with a screwdriver or something if you don't have a jumper but before you should take all power cords off the wall so there is no power anywhere.
Did you do a clean Windows install when you upgraded? Is the Windows fully updated? Here is a solution for very similar error: Solved: Ryzen 3 2200G Vega 8 driver problem - AMD Community
Try to get to bios by pressing the enter bios key (del key usually) many times after you start the pc. There might be delay before the monitor displays the image when you start the pc so don't wait for display before start pressing del.
There is a bios flashback feature on that motherboard which allows to update bios without going to bios and you could try that if needed.
I didn't do a clean install of windows when upgrading, which is hindsight 20/20 as clearly I should have (never thought entering safe boot would cause problems, given it still booted to windows...)
I just plugged in my previous ssds and booted it from there, with no other apparent issues other than the conflict in devices and driver installation problems. Windows was fully updated though.
I've tried getting to BIOS but the problem is that I get no display regardless. Just nothing, despite sitting there and tapping away for 5+ minutes.
I've also tried shorting the cmos with a screwdriver several times, but that didn't work at all
So as a last resort, I *did* try BIOS flashback.
Now it no longer boots, but the DRAM and CPU lights are continuously lit up red. Reseating the RAM did nothing for it and the CPU fans don't spin, so I suspect the CPU might have to be reseated to try and solve this new issue
I had that problem with my 4K Monitor also when I upgraded from Windows 10 to Windows 11 UEFI BIOS mode.
Under Windows 10 CSM BIOS Mode (Legacy Mode) I had video output during POST when the PC is first powered up. But after installing Windows 11 and using UEFI BIOS mode I lost Video output during POST but as soon as Windows 11 started to run I got video output to my 4k Monitor. The only way I got video output with Windows 11 during POST was when I had my Samsung 2k Smart TV connected. That was the only way to configure BIOS with Windows 11 at that time.
But after upgrading my RX 1070 to a RTX 4060 I now get video output to my monitor and TV set during POST with UEFI BIOS Mode enabled.
If you update or install your BIOS again it should automatically be at its factory default settings. It is possible that your BIOS has UEFI mode set as default.
The strangest thing is after trying to boot in safe mode there was no longer display for BIOS or Windows, but I was able to boot Ubuntu from a stick no problem
Edit: Still no BIOS though
Sounds pretty bad...I don't think you could have broken it using software there must be something wrong with the hardware. Maybe try to
-check manual for installation instructions on everything especially what slots to use for ram
-maybe take out motherboard and see the mounting points on the case are all attached in right places and align with the holes of the motherboard
-reattach all psu cables
-reseat the cpu and reattach cooler and check cpu pins for damage
-using only 1 stick of ram (try both sticks) to get it to post with nothing else attached except keyboard and monitor
-wait at least 5min on the first boot before doing anything because it might take long time to train memory
This video might help: AMD AM5 Solid CPU and Ram Light, No Post, Possible Solution - YouTube
I ended up bringing it to a computer repair shop today that specializes in motherboard damage, so if there's something physical wrong with the mobo I'm sure they'd pick up on it
On the downside, they were just as baffled as me about it, since it worked fine (minus the driver and device error code 12 for the graphics and no access to BIOS screen after I updated it to 3.20) before the safe mode boot
If they can't find out anything, might have to fight for the warranty. Went out and bought a new ssd so I can do a clean install of Windows regardless if they can troubleshoot what's wrong with it at the repair shop. Thankfully their problem diagnosis just costs 50 euros no matter how long it takes and it's good to have a second opinion imo
UPDATE:
Unfortunately couldn't get the exact response from their tech guy as they weren't at the shop when I picked it up
They took the setup apart. Motherboard and processor were fine physically, no issues there. They reupdated the BIOS to the newest version again and I'm suspecting they reset it before doing so.
Windows had become corrupted. It was missing the boot files and that's why it wouldn't boot at all (but was fine booting from a stick. No clue why win10 boot repair did nothing though)
They could offer no idea why it wouldn't get display for BIOS. They spent 7 whole hours fighting with it, apparently, before getting any display at all.
After I got the machine back, it still had issues finding the inbuilt speakers. There was no longer an error 12 for Amd Radeon Graphics however.
Did a clean install of Win10 and that fixed the speaker issue.
If Windows Boot Manager/Bootloader was corrupted the only way I found out to fix that issue is using DiskPART in BIOS Command Prompt.
Using your USB Windows installer you could have entered Command Prompt and try using Diskpart to fix your Windows Boot Manager/Boot Loader.
You can can instructions by going to DiskPart website or googling " How to fix Windows Boot Manager using Diskpart".
I had a similar issue in the past but was unable to fix my Windows Boot Manager/Boot loader using Diskpart in Windows Command Prompt. I was forced to do a clean Windows Install and that fixed the issue.