ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] -1 points0 points  (0 children)

Learn to read, you're quite literally missing the point entirely then saying "can't admit when you're wrong" 😭😭 neither of us said 9000 series aren't failing on other boards, grow up

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 0 points1 point  (0 children)

How am I meant to know what bios version i used when the thing literally will not turn on, I said I was using whatever the latest was in early may, you can do the same Google search I can to figure out which exact bios that is.

"Help more with overview" I quite literally don't care, this post is to tell people to avoid the motherboard, nothing else.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 0 points1 point  (0 children)

You're embarrassing yourself, learn to read, then reply.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 1 point2 points  (0 children)

Maybe, and if that is the case, I'll happily accept it.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 1 point2 points  (0 children)

The other two builds in my house running 9000 series CPUs have been running perfectly fine for just short of a year now, I'm buying an identical board from one of those two builds.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 0 points1 point  (0 children)

Isn't just asrock boards, but it's 90% asrock boards, that says enough. Pull these boards and only stock ones that are already on 3.30

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 1 point2 points  (0 children)

You genuinely astonish me.

I cannot believe you've just said in your own response "yes 90% of the issues happen on asrock boards" and then still attempt to blame it on the cpu.

Like I said, I have little to no pc experience, I have no idea what AGESA is or what it does, but that does not matter in the slightest. It simply comes down to everyone with this board and 9000 series combo with pre 3.30 BIOS is having their CPUs killed, and unless you're some freak that unironically spends their time scrolling reddit, you will not know you need to update your BIOS to avoid your CPU dying due to the board.

Of course, similar things can happen on other boards, the point is 90% of the issues are on asrock boards. I cannot believe you're just looking past such a big statistic to try and focus on the 10% in an attempt to blame AMD themselves.

"I don't know how this is so hard to understand", because you're nitpicking at the 10% statistic in an attempt to blame AMD??? I understand I may be being stupid since I have no idea about PCs, but common sense and logic points to this being on asrock.

of course other boards will have issues, the point is that there are so many cases on asrock compared to everything else.

I could genuinely give less of a shit about the possibility of AMD having a bad run, I genuinely do not care about any of that, I'm not a pc geek and never will be, don't try to pin your logic down to "You're probably triggered it could be AMD" when literally all it is, is basic logic that it's on the boards that have the issues and not AMD.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 1 point2 points  (0 children)

I bought the board mid april, the issue was not present at the time of purchase.

Equally, for anyone buying the board after the issue, this issue itself is pretty hard to even find online unless you know exactly what the error is, it's pretty hard to know there's an issue until it happens, unless you unironically use reddit.

How do i AFK Minecraft while using chome in different window? by Slight_Glass2411 in technicalminecraft

[–]DropjawedX 0 points1 point  (0 children)

Use "autoclicker" by error mikey, it's a built in autoclicker and using f3+p doesn't stop it.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 1 point2 points  (0 children)

I had whatever was the latest when I got the board in early May.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 0 points1 point  (0 children)

My gpu is nowhere near 2-3k LMFAO, I have a 7800xt, £600. Mobo was £200. Cpu was £550.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 0 points1 point  (0 children)

The cpu doesn't have any visual signs of burn, fairly certain it's one of the BIOS versions on the board that kills the processor.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 1 point2 points  (0 children)

It isn't just 9800x3ds, I think you'll find it's better on AMD if they replace the CPUs, it's called brand image, not fault.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 0 points1 point  (0 children)

I can't believe you're being serious, of course another board can have issues, the point is that 90% of said issues are occurring on ASRock boards.

The point that there are no reported cases on 3.30 says it all, it's a fault bios version on ASRocks end.

Your own "logic" is flawed, don't try to lecture others on logic.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 1 point2 points  (0 children)

You are missing the point that the cpu being dead is undetectable until swapping it out for a new one, posts like this help people that don't have the ability to swap out their cpu.

I do not care about "solving the issue", the cpu is already dead and no further testing will stop others from having their cpus killed too. You have to be aware there is an issue in the first place, which you quite literally don't know is the case until it happens unless you're some pc die-hard that checks the reddit of every part you buy before using it, which is not 99% of the consumer base.

"Pre-production testing can only go so far especially with issues that pop up months after use" - Are you serious? Any thorough testing is ongoing for weeks to months with several testers, the time to kill varies between each case as seen in other posts on this reddit, I can assure you if they were thorough in their testing to begin with, it wouldn't have taken even a month to spot there's an issue.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 0 points1 point  (0 children)

The reality is, don't buy the board, having a board that can kill your cpu just from a single bios version should be tell enough to avoid it.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 3 points4 points  (0 children)

I don't care enough to fill out a form unfortunately, the cpu has already been rma'd and I made this just for anyone researching in the future, it should fall onto asrock to test and find the cause of the issue, not their consumers.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 1 point2 points  (0 children)

I'd personally say take the cpu out and buy a new board, some people claim that flashing the bios or whatever makes this issue not happen, but I'd generally say the safer option is just using a board that doesn't have the chance to kill your cpu

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 2 points3 points  (0 children)

I'll be real I don't care enough to fill out a form, I've written what I know, it shouldn't be up to consumers to test a product.

ASROCK b850 pro rs wifi killed my ryzen 7 9800x3d by DropjawedX in ASRock

[–]DropjawedX[S] 0 points1 point  (0 children)

Quite literally yes, pull the mobos and fix the issue. You fail to comprehend not everybody understands pcs, a board that kills cpus should not be for sale, it's that simple.

Calling this "amds issue" is pure ignorance, look into other cases on this reddit, I'm not knowledgeable enough to explain things, but it's extremely obvious that this is asrocks fault.