cancel
Showing results for 
Search instead for 
Did you mean: 

Asus rog strix x299-e gaming problem (4f error)

TheDexter
Level 7
Hello,

my system:
Asus Rog Strix X299-E gaming
Gskill Tridenz RGB F4-4133C19D-16GTZR
Asus Gtx 1080ti
Intel i7 7800x
2x m.2 samsung 960 pro
2x850 pro ssd
be quiet silent loop 280mm
750W power supply be quiet plantinum +.


today i got my new pc parts.
I build it and launched in the bios.
I set my 2x m.2 samsung 960 pro into raid 0 pcie and insert my usb stick with windows 10 (used the official windows media creating software).
After that it started to install.
It said reboot to finish xy.
Since this point i cant enter my bios or get any picture of my pc.

What i tried:

cmos reset: unplugged the battery and waited 10 min.
cmos reset from the mainboard.
testing ram slots.

im getting the error 4f everytime if ram is plugged in.

Asus support told me to refund the mainboard but i want to fix it.

Got new motherboard from asus -> same problem now but i got a bit further.

windows restart after installing -> getting ready with asus bios logo -> black screen and no chance to do anything

Greetings Mark
18,807 Views
24 REPLIES 24

Hopper64
Level 15
Are you overclocking anything?

Seems like I saw something about these boards not supporting anything besides intel drives in RAID. Try one 960 and test.*
MZ790A Bios 2002, GSkill F5-8000J3848H16GX2-TZRK, 13900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.0, Asus Strix 4090 w/ Optimus block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Samsung 990, Windows 11 Pro

Hopper64 wrote:
Are you overclocking anything?

Seems like I saw something about these boards not supporting anything besides intel drives in RAID. Try one 960 and test.*


already tried to put one out but it doesnt help me.

i cant use the board now 😞

but i saw someone that made a video on youtube and he managed to install the system

Hopper64
Level 15
Are you trying to run your memory at 4133?
MZ790A Bios 2002, GSkill F5-8000J3848H16GX2-TZRK, 13900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.0, Asus Strix 4090 w/ Optimus block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Samsung 990, Windows 11 Pro

Hopper64 wrote:
Are you trying to run your memory at 4133?


no but i cant change anything atm because i get no picture

Hopper64
Level 15
Try a different video card?*
MZ790A Bios 2002, GSkill F5-8000J3848H16GX2-TZRK, 13900KS, EKWB D5 TBE 300, Seasonic Prime TX-1600 ATX 3.0, Asus Strix 4090 w/ Optimus block, Phanteks Enthoo Elite, Asus Claymore 2, Asus Gladius 3, Asus XG349C, Samsung 990, Windows 11 Pro

Raja
Level 13
Update to the latest UEFI build by using USB BIOS Flashback: https://rog.asus.com/forum/showthread.php?94815-X299-UEFI-updates

That kit isn't rated for X299, so might be causing some issues. Try one module only.

Chino
Level 15

I have the exact same issue.

The board posted just fine, several times as I loaded optimum defaults, loaded xmp timings, etc. Booted from USB and installed windows, it said restart to continue, and post fail 4f.

I've tried clearing the cmos and a battery pull, different sticks of memory, just one stick in slot C1, different video card, nothing works, just 4f no post.

My system:

Strix x299 E.
7820x
GTX 1080
32Gb gskill trident z rgb 3600 C17 4x8 (listed as x299 certified)
Evo pro 960 m.2
6Gb HDD
Optane stick.

What is occurring between windows installing and that reboot, that kills the board so even blanking the cmos doesn't help? I know what the manual says, but what exactly does 4f mean?

I can get another board, that's not the problem, I'm just worried that this might happen again, because I don't know what caused it.

Thanks, and nice to meet you guys.
Marry.

Raja
Level 13
Yep, even the OP stated his board was working fine til the install.

Sounds strange. 4F can occur on these boards when memory is overclocked, but can also be something else. Out of interest, can you list all the USB peripherals that are plugged into the board? Wondering if any of the components/peripherals have some kind of compatibility issue with fast boot.

And are you using the 0503 UEFI build?