F5F Stay Refreshed Hardware Desktop This model cannot be used with the v2007 UEFi version.

This model cannot be used with the v2007 UEFi version.

This model cannot be used with the v2007 UEFi version.

T
TesGo
Member
85
11-07-2024, 06:39 PM
#1
I’m writing this down ahead of time because it came out angry after facing several problems. It’s now unusable after almost a year of trying to fix things since I upgraded to the v2007 UEFI. I’ve been working with this for nearly 30 years (using an Abit IC7-Max 3 with P4EE). This is the first time I’m completely giving up on it.

Hardware: AMD 7950x, Asus Crosshair Gene BIOS v2007, x64, Corsair 6000MHz CL36 CMK32GX5M2D6000Z36, 1× MP600 Pro XT 2TB, 1× Samsung 980 Pro 2TB – GenZ.2_2 socket, 1× MP510 2TB – GenZ.2_1 socket, Asus 6900XT LC Corsair AX1600i. New issue: BSOD every time I log in or before, showing two different messages—either an uncorrectable error or a machine check exception. It loops through recovery, crashes repeatedly before Windows even loads, then triggers automatic repair, and then repeats the same problems. I’ve entered recovery mode and turned off automatic restarts, but it didn’t help. Now, when I try to enter safe mode, I can’t reach it because I can’t get into Windows.

I’ve rolled back the UEFI to older versions, but each attempt fails—my system still says it’s not valid (rollback is enabled). Possible tests I could try later:
- Use a DDR5 stick from the QVL list and see if it works.
- Try another AM5 CPU; secondary issues:
1. The machine won’t boot or has more BSODs when using EXPO.
2. It won’t start at all if ASUS’s default settings are on.

I must disable all AI overclocking features and disable Asus’s optimization to get it to boot. All previous fixes didn’t work. Things tried before this new problem.

With Asus’s overclocking turned off, I wiped the main SSD, reinstalled Windows 11, bought a wipe-all drive, used Holo ISO, and tested with individual sticks. All passed without crashes after several hours. The graphics card moved to another PC without issues.
T
TesGo
11-07-2024, 06:39 PM #1

I’m writing this down ahead of time because it came out angry after facing several problems. It’s now unusable after almost a year of trying to fix things since I upgraded to the v2007 UEFI. I’ve been working with this for nearly 30 years (using an Abit IC7-Max 3 with P4EE). This is the first time I’m completely giving up on it.

Hardware: AMD 7950x, Asus Crosshair Gene BIOS v2007, x64, Corsair 6000MHz CL36 CMK32GX5M2D6000Z36, 1× MP600 Pro XT 2TB, 1× Samsung 980 Pro 2TB – GenZ.2_2 socket, 1× MP510 2TB – GenZ.2_1 socket, Asus 6900XT LC Corsair AX1600i. New issue: BSOD every time I log in or before, showing two different messages—either an uncorrectable error or a machine check exception. It loops through recovery, crashes repeatedly before Windows even loads, then triggers automatic repair, and then repeats the same problems. I’ve entered recovery mode and turned off automatic restarts, but it didn’t help. Now, when I try to enter safe mode, I can’t reach it because I can’t get into Windows.

I’ve rolled back the UEFI to older versions, but each attempt fails—my system still says it’s not valid (rollback is enabled). Possible tests I could try later:
- Use a DDR5 stick from the QVL list and see if it works.
- Try another AM5 CPU; secondary issues:
1. The machine won’t boot or has more BSODs when using EXPO.
2. It won’t start at all if ASUS’s default settings are on.

I must disable all AI overclocking features and disable Asus’s optimization to get it to boot. All previous fixes didn’t work. Things tried before this new problem.

With Asus’s overclocking turned off, I wiped the main SSD, reinstalled Windows 11, bought a wipe-all drive, used Holo ISO, and tested with individual sticks. All passed without crashes after several hours. The graphics card moved to another PC without issues.

J
Jullinchen
Junior Member
1
11-07-2024, 06:39 PM
#2
It remains effective even when running memory at the base JDEC parameters.
J
Jullinchen
11-07-2024, 06:39 PM #2

It remains effective even when running memory at the base JDEC parameters.

S
strikes2pk
Member
71
11-07-2024, 06:39 PM
#3
Earlier it functioned well at JDEC, but now it's not working properly.
S
strikes2pk
11-07-2024, 06:39 PM #3

Earlier it functioned well at JDEC, but now it's not working properly.

B
ByGlory
Junior Member
11
11-07-2024, 06:39 PM
#4
Avoid dealing with board problems this way—it's usually the board, which is the most error-prone part of a build.
B
ByGlory
11-07-2024, 06:39 PM #4

Avoid dealing with board problems this way—it's usually the board, which is the most error-prone part of a build.

D
dazzlinglogan
Member
67
11-07-2024, 06:39 PM
#5
It seems the system is still experiencing problems even at 4000 with standard settings. Trying to lower the CPU speed or disabling performance features might help. I checked the socket for any damage, but it looks fine. You might want to consider returning it through RMA since Asus support seems unreliable. Regarding BIOS updates, there was an issue in older Haswell models where flashing didn’t work properly—some microcode wasn’t updated correctly. This caused certain CPUs to fail on earlier 4th generation boards. Eventually, I managed to fix it using the Windows update tool, though it required some trial and error and additional hardware purchases. If you're using the in-built BIOS flasher, that could be the reason the downgrade isn’t working. With unstable Windows, this could be a serious concern.
D
dazzlinglogan
11-07-2024, 06:39 PM #5

It seems the system is still experiencing problems even at 4000 with standard settings. Trying to lower the CPU speed or disabling performance features might help. I checked the socket for any damage, but it looks fine. You might want to consider returning it through RMA since Asus support seems unreliable. Regarding BIOS updates, there was an issue in older Haswell models where flashing didn’t work properly—some microcode wasn’t updated correctly. This caused certain CPUs to fail on earlier 4th generation boards. Eventually, I managed to fix it using the Windows update tool, though it required some trial and error and additional hardware purchases. If you're using the in-built BIOS flasher, that could be the reason the downgrade isn’t working. With unstable Windows, this could be a serious concern.