PC Master Race

22342 readers

529 users here now

A community for PC Master Race.

Rules:

No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
Be respectful. Everyone should feel welcome here.
No NSFW content.
No Ads / Spamming.
Be thoughtful and helpful: especially when new beginners have questions.

founded 3 years ago

MODERATORS

_MoveSwiftly@lemmy.world

The_Vampire@lemmy.world

Fudgeknuckles98@lemmy.world

Brunbrun6766@lemmy.world

IowaMan@lemmy.world

BobaFett26@lemmy.world

CatZoomies@lemmy.world

Xeon@lemmy.ml

geosoco@kbin.social

our second raptor lake cpu fail (infosec.pub)

submitted 2 months ago by adarza@piefed.ca to c/pcmasterrace@lemmy.world

9 comments fedilink hide all child comments

re: raptor lake 'issues'

this one is a 14th gen on an asus board. less than a year old, i think. constant crashes and other 'quirks'. system builder (wasn't my purchase decision) is known to be a pain to deal with on warranty service. so we'll see what happens.

the first was a 13th gen xps. problems from first boot up. dell was great on addressing intel's issue. swapped the board and chip, and it had a brand-spankin'-new firmware that wasn't even pushed to their website yet. paid freight both ways, including priority overnight air return.

you are viewing a single comment's thread
view the rest of the comments

[–] osaerisxero@kbin.melroy.org 5 points 2 months ago (1 children)

Yeah, 14th gens you have to explicitly configure to undervolt or underclock (or both :( ), and until you do you're just rolling the dice every time they spin up. I got lucky with mine and found the settings that were both safe and it liked before it failed 3 death saves, but with the way it was behaving I wouldn't be surprised if it was on 2 of 3.

[–] adarza@piefed.ca 2 points 2 months ago

the one here was running the original firmware, probably factory original from asus. the board was on a 'performance' preset setting--and defaulted to that when i tried a bios reset to defaults. when i updated the firmware, that setting changed to a 'normal' one when i reset to defaults again.

i didn't really dig into that too much because i knew it was already an rma case, but i think part of it had to do with boosted power draw. it still crashed on 'normal' and that's what it was set on when i ran intel's diagnostics (which took a few tries just to have it not crash before finishing with a result).