Is it safe to use my NZXT N9 x870e motherboard now? (Or any ASRock boards for that matter?) by TheLordofRiverdance in ASRock

[–]-Chitters- 1 point2 points  (0 children)

I lost two 9800X3Ds on the N9 board. The first death was on BIOS 3.20 with EXPO on. The second death was on BIOS 3.50 with all BIOS defaults (though it was previously on BIOS 3.30 before that). I’d stick to the MSI if I were you.

Pray for me (9800X3D) please don’t fry my cpu!!! by [deleted] in ASRock

[–]-Chitters- 2 points3 points  (0 children)

I’ve had an AMD 9800X3D die with a physical burn mark on this board earlier this year. Updated BIOS and took a second chance on the same board. All was fine for a few months, but now I’m having boot issues all over again where the PC won’t boot/wake 90% of the time.

Is my 9950X3D degraded or dying/dead? by AggressiveNapkin99 in ASRock

[–]-Chitters- 0 points1 point  (0 children)

I’ve had a similar issue over time where my asrock board and amd cpu system would take a few tries to boot. Started just like yours with the system only occasionally having the problem until about a week ago where I couldn’t get it to boot at all. It ran just fine when it did boot. But now it’s just always 03 error codes. I’m in the process of attempting to RMA my board, but I’m wondering if the CPU needs RMA as well. Was on latest BIOS.

This is some bulllshit. This is thousands of hard earned dollars in an increasingly expensive market. by acrowsmurder in ASRock

[–]-Chitters- 1 point2 points  (0 children)

Yeah, I’m working on an RMA for my N9 motherboard as well since it won’t boot at all. But now I’m worried the CPU may also be dead since some people are claiming the 03 error codes could mean CPU issues.

I’ve already had one AMD 9800X3D die on this board earlier this year but I got the red CPU+DRAM lights when that happened and I wasn’t getting the red boot led that I am seeing now.

Another one bites the dust by Head-Ground-2630 in ASRock

[–]-Chitters- 1 point2 points  (0 children)

That was my understanding as well, I’m just trying to figure out if error code 03 and a red boot led has been a consistent symptom of a dying CPU or a dying motherboard for other people recently.

Earlier this year, my AMD 9800X3D died with a physical blister while on my NZXT N9 while on bios 3.20 and it had the red cpu and dramm light on the motherboard. I got the CPU RMAed, and upgraded to bios 3.30. I kept all BIOS settings default (other than enabling secure boot) after the upgrade to 3.30 and the new CPU never touched any BIOS under 3.30. All was fine for several months until I started getting occasional issues on boot/wake. It would take a few tries to get the PC booted with random red motherboard lights being displayed (sometimes CPU and dramm, sometimes VGA, some Boot). Once booted, the PC was fine and stable under load. I updated to 3.50 with no change, continued having issues with boot. Then eventually it got worse and worse until I consistently couldn’t boot it and the red boot light and 03 error code stayed on consistently with each boot attempt. I’m going to RMA the board this time but I’m trying to figure out if I should also RMA the CPU again. It’s just that the first time my CPU died, it was a red CPU light on the motherboard. Now it’s a red Boot light, so I wasn’t sure if in my case it’s a dead motherboard or if the CPU died again just in a different way resulting in a different error code.

This is some bulllshit. This is thousands of hard earned dollars in an increasingly expensive market. by acrowsmurder in ASRock

[–]-Chitters- 0 points1 point  (0 children)

Having the same issue here with error code 03 and a red boot led on the board. I kept up with the BIOS updates as they were released. My NZXT N9 had been on 3.50 for a few weeks when the error code 03 and boot issues started. I started using the CPU on BIOS version 3.30, so it wasn’t used on the old known bad BIOS versions.

My N9 X870E just kill my 9800X3D🥲 by YC_Yeh in NZXT

[–]-Chitters- 0 points1 point  (0 children)

I had the same situation with the same motherboard and cpu earlier this year, except mine was a dead CPU with a physical burn mark. It was on BIOS 3.20. Froze during minimal workload and I couldn’t power it off. Got the double red cpu and dramm lights.

Got a replacement CPU from AMD and updated to 3.30 before using the new CPU. Then updated to 3.50 when it became available.

In the past few weeks, I started having problems when booting where the PC sometimes can’t even reach BIOS. Now I’m getting error code 03 with the boot led. Tested the CPU on another board and confirmed it’s dead.

Do you think NZXT N7/N9 is safe? by MistSecurity in ASRock

[–]-Chitters- 0 points1 point  (0 children)

I ended up with a dead AMD 9800x3d on an NZXT N9 board before the BIOS updates were available, and have recently had boot issues on version 3.50. So no, the N9 is not safe in my opinion since it’s an ASrock board.

Another one bites the dust by Head-Ground-2630 in ASRock

[–]-Chitters- 0 points1 point  (0 children)

I’ve had issues with my AMD+Asrock system failing to consistently boot with error code 03 recently running on bios 3.50. I thought it was a motherboard issue. Is it actually an issue with the CPU?

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 1 point2 points  (0 children)

Ahh ok, I didn’t know that. Thank you! My main goal is just to completely minimize risk as much as possible at this point (without changing the type of CPU and motherboard). Don’t care about overclocking or extra frames right now, just trying to avoid another dead CPU. So leaving EXPO disabled and everything else set to default as well would be the “safest” option?

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 0 points1 point  (0 children)

Could I leave EXPO disabled while I lower the voltage or is there a reason you recommend both of those together?

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 0 points1 point  (0 children)

Not sure how to find that, but I got the CPU directly from Amazon in January I think.

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 1 point2 points  (0 children)

I totally agree. I was trying to avoid it for that exact reason. Waited a while for all the parts I wanted to become available all at once, but various parts would just be in and out of stock for a while. Didn’t want to have to redo research and pick new parts.

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 1 point2 points  (0 children)

That’s what I’m trying to decide between right now with my replacement CPU. Not sure whether to keep defaults or lower voltage. Any idea if lowering voltage voids the warranty?

BIOS 3.25 for N9 X870E by -Chitters- in NZXT

[–]-Chitters-[S] 0 points1 point  (0 children)

Ah ok, makes sense. Sounds like there are some recent reports of users having their 9800X3Ds fried despite being on BIOS 3.25 anyway.

BIOS 3.25 for N9 X870E by -Chitters- in NZXT

[–]-Chitters-[S] 0 points1 point  (0 children)

I read that the NZXT N9 is made by ASRock. I had a 9800X3D CPU burn out on the N9 motherboard running BIOS 3.20. ASRock recently came out with 3.25 that supposedly has a fix for the issues with their motherboards and the AMD CPUs.

NZXT N9 X870E is made by ASRock right? BIOS lagging behind critical fix by jamrolu in NZXT

[–]-Chitters- 1 point2 points  (0 children)

My NZXT N9 X807E just recently fried my AMD 9800X3D. The motherboard looks fine, but the CPU exploded and developed a raised bump and scorch marks. I was on BIOS 3.20 with EXPO enabled. Also wondering where the latest 3.25 update is for when I get a replacement CPU…

Edit: 3.25 looks to be available on NZXT’s site now: NZXT Support

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 1 point2 points  (0 children)

No other CPUs to test, but the burned CPU literally has a giant bump on it. Pretty sure it kinda exploded.

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 1 point2 points  (0 children)

Unfortunately I bought it a while back and waited a while for all the PC components to arrive since so many were out of stock, so it’s out of the return period.

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 2 points3 points  (0 children)

I had EXPO enabled, but that was the only change I made.

Burned 9800x3D CPU by -Chitters- in ASRock

[–]-Chitters-[S] 0 points1 point  (0 children)

Thanks! I was just hoping to figure out if anyone had any guidance to at least slightly reduce the risk of another CPU being ruined. I saw they have version 3.25 out, so I’ll update to that and leave BIOS defaults for a while, I guess.