F5F Stay Refreshed Hardware Desktop System fails to start after Razor Synapse setup, no access to recovery mode.

System fails to start after Razor Synapse setup, no access to recovery mode.

System fails to start after Razor Synapse setup, no access to recovery mode.

I
iiFruity
Junior Member
1
04-16-2023, 05:22 AM
#1
Hello! Here are the stats summarized: Windows 10 64-bit, AMD Ryzen 9 7950X, Nvidia Founders Edition 4080, Aorus Master X670E motherboard, G.Skill 32GB RAM, 6000MHz, WD Black SN850X 2TB M.2 drive, Gigabyte ATX3.0 1000W power supply, Gigabyte Aorus Waterforce 360 AIO. BIOS version F6 (original). Previously switched to F8 due to boot loops; took time to enter recovery mode. Issue occurred while using Remote Desktop to connect to a work PC. Connection dropped after reinstalling Razor Synapse, which required a restart. Restarted the PC but it failed to proceed past postcode 46. Attempted recovery via on/off sequence, but OS didn’t boot. Checked CMOS and reset settings; motherboard manual indicated 46 is reserved. Reset CMOS caused boot code to lock at 3F or C5—hard to interpret. Plugged in monitor via iGPU but no display. Disconnected all peripherals, still no start. Seeking advice from others. Also mentioned trying to bypass wall hacks in Tarkov this evening. Updated March 1, 2023 by walshe25
I
iiFruity
04-16-2023, 05:22 AM #1

Hello! Here are the stats summarized: Windows 10 64-bit, AMD Ryzen 9 7950X, Nvidia Founders Edition 4080, Aorus Master X670E motherboard, G.Skill 32GB RAM, 6000MHz, WD Black SN850X 2TB M.2 drive, Gigabyte ATX3.0 1000W power supply, Gigabyte Aorus Waterforce 360 AIO. BIOS version F6 (original). Previously switched to F8 due to boot loops; took time to enter recovery mode. Issue occurred while using Remote Desktop to connect to a work PC. Connection dropped after reinstalling Razor Synapse, which required a restart. Restarted the PC but it failed to proceed past postcode 46. Attempted recovery via on/off sequence, but OS didn’t boot. Checked CMOS and reset settings; motherboard manual indicated 46 is reserved. Reset CMOS caused boot code to lock at 3F or C5—hard to interpret. Plugged in monitor via iGPU but no display. Disconnected all peripherals, still no start. Seeking advice from others. Also mentioned trying to bypass wall hacks in Tarkov this evening. Updated March 1, 2023 by walshe25

_
_XplodingPig_
Member
179
04-16-2023, 05:22 AM
#2
It's understandable to feel frustrated. Based on information about your motherboard, I recommend updating to the latest BIOS version released in February this year. If it boots up, check if it can read your drives. You can flash the BIOS using Q Flash without needing a boot process. If that doesn't work, remove one RAM stick and both memory modules, then test the situation. Let me know what you find!
_
_XplodingPig_
04-16-2023, 05:22 AM #2

It's understandable to feel frustrated. Based on information about your motherboard, I recommend updating to the latest BIOS version released in February this year. If it boots up, check if it can read your drives. You can flash the BIOS using Q Flash without needing a boot process. If that doesn't work, remove one RAM stick and both memory modules, then test the situation. Let me know what you find!

G
gustavofx
Junior Member
14
04-16-2023, 05:22 AM
#3
I checked online for guidance on clearing code 46. The suggested method involves completely powering off the PC, disconnecting it from the source, reconnecting it, restoring power, and attempting a boot. It’s uncertain if this will resolve the problem, but worth trying. I’ve never experienced issues with Razer Synapse, so it seems unlikely to be the cause. Correlation doesn’t always mean causation.
G
gustavofx
04-16-2023, 05:22 AM #3

I checked online for guidance on clearing code 46. The suggested method involves completely powering off the PC, disconnecting it from the source, reconnecting it, restoring power, and attempting a boot. It’s uncertain if this will resolve the problem, but worth trying. I’ve never experienced issues with Razer Synapse, so it seems unlikely to be the cause. Correlation doesn’t always mean causation.

H
hotcone33
Member
204
04-16-2023, 05:22 AM
#4
I verified the BIOS page to confirm my naming and noticed they released a new version from last week. Likely preparing for the 3D CPUs. I’m hoping this will reduce problems. I plan to download it tomorrow at work and see if it helps. I’ll test one RAM stick first—will it boot without any RAM? One stick worked, so I’ll run a memory checker on that and then try both sticks. A BIOS update might improve stability? Updated March 1, 2023 by walshe25 Problem solved!
H
hotcone33
04-16-2023, 05:22 AM #4

I verified the BIOS page to confirm my naming and noticed they released a new version from last week. Likely preparing for the 3D CPUs. I’m hoping this will reduce problems. I plan to download it tomorrow at work and see if it helps. I’ll test one RAM stick first—will it boot without any RAM? One stick worked, so I’ll run a memory checker on that and then try both sticks. A BIOS update might improve stability? Updated March 1, 2023 by walshe25 Problem solved!

J
Jolias055
Junior Member
31
04-16-2023, 05:22 AM
#5
I previously tried turning it off and on again. When it stopped this morning, I went to work for the day. After leaving, I disabled the PSU switch in an effort to truly shut it down, and left that setting for about 11 hours. Still, it didn’t boot tonight. I’m planning to unplug it completely or try a short break to see if it works. Also, just to note, I linked the no-start issue to the Razor Synapse installation because my previous crash was due to an NVIDIA driver update (somehow), and the recovery mode fixed everything. I expected it to be similar here, but I couldn’t get it to start!
J
Jolias055
04-16-2023, 05:22 AM #5

I previously tried turning it off and on again. When it stopped this morning, I went to work for the day. After leaving, I disabled the PSU switch in an effort to truly shut it down, and left that setting for about 11 hours. Still, it didn’t boot tonight. I’m planning to unplug it completely or try a short break to see if it works. Also, just to note, I linked the no-start issue to the Razor Synapse installation because my previous crash was due to an NVIDIA driver update (somehow), and the recovery mode fixed everything. I expected it to be similar here, but I couldn’t get it to start!

P
Pekaaa
Member
206
04-16-2023, 05:22 AM
#6
Confirming the request. No RAM will be used.
P
Pekaaa
04-16-2023, 05:22 AM #6

Confirming the request. No RAM will be used.

I
iFrIIwi_YT
Junior Member
9
04-16-2023, 05:22 AM
#7
They shared a single stick, and I'm composing this on my PC now. I plan to run a memory check to look for any issues. After that, I'll try again using two sticks. I also intend to apply a BIOS update tomorrow, which should help with stability.
I
iFrIIwi_YT
04-16-2023, 05:22 AM #7

They shared a single stick, and I'm composing this on my PC now. I plan to run a memory check to look for any issues. After that, I'll try again using two sticks. I also intend to apply a BIOS update tomorrow, which should help with stability.