this post was submitted on 14 May 2025
305 points (98.1% liked)

Technology

70031 readers
4352 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
305
Researchers discover new security vulnerability in Intel processors (ethz.ch)
submitted 1 day ago* (last edited 1 day ago) by Pro@programming.dev to c/technology@lemmy.world
35 comments fedilink hide all child comments
 
  • The new class of vulnerabilities in Intel processors arises from speculative technologies that anticipate individual computing steps.
  • Openings enable gradual reading of entire privilege memory contents of shared processor (CPU).
  • All Intel processors from the last 6 years are affected, from PCs to servers in data centres.
you are viewing a single comment's thread
view the rest of the comments
[–] x4740N@lemm.ee 2 points 5 hours ago* (last edited 5 hours ago)

I don't know if amd does this for your specific issue but you might have a problem had with amd driver conflicts, I had this issue and was going through great lengths to Tey and figure out what was causing this until the helpful people at toms hardware helped

https://forums.tomshardware.com/threads/sporadic-bsods-in-windows-11-professional.3877530/#post-23472239

Edit: also try turning off memory context restore and there was something about ram power levels thst might cause bsods of similar nature to other people but I don't remember the bios setting name at this time unfortunately but am just leaving this here incase you figure out the name

I'd also recomend making an account snd posting on tomshardware forums because they helped me figure out what was causing my own BSOD's

And run memtest86 and memtest86+ just to rule out bad ram

Windows ram diagnostics is useless