this post was submitted on 29 Feb 2024
682 points (94.3% liked)

linuxmemes

21272 readers
422 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    682
    Classic Nvidia (feddit.de)
    submitted 8 months ago by Hubi@feddit.de to c/linuxmemes@lemmy.world
    35 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] MystikIncarnate@lemmy.ca 13 points 8 months ago

    I had a problem like this with a CPU.

    Fresh from the box OEM hardware, either Dell or HP... I forget. A laptop system.

    We couldn't get the damn thing to do windows updates, which was part of our initial prep for the system. It kept crashing, no useful info from logs.

    I booted off of an Ubuntu live image I had on a USB. Turns out, one of the CPU cores on die was faulty. If I reduced the CPU cores visible to the system to one, it worked fine. All enabled? Crash.

    A call to support and a quick service visit sorted out the system, but Microsoft's error reporting was useless at diagnosing the issue.