I bought an Optiplex 5040, with an i5-6500TE, and 8 GB DDR3L RAM.

When I bought it, I installed Fedora Server on it. It got stuck every few days but I could never see the error. The services just stopped working, I couldn’t ssh into it, and connecting it to a monitor showed a black screen.

So, I thought let’s install Ubuntu Server, maybe Fedora isn’t compatible with all of its hardware. The same thing is happening, now, but I can see this error. Even when there’s nothing installed on it, no containers, nothing other than base packages, this happens.

I have updated the bios. I have tried setting nouveau.modeset=0 in the grub config file. I have tried disabling and enabling c-states. No luck till now.

Would really appreciate if anyone helps me with this.

UPDATE:

  • I cleaned everything and reapplied the thermal paste. I did not see any change in the thermals. It never goes over 55°C even under full load.
  • I reset the motherboard by removing that jumper thing.
  • I ran memtest86, which took over 2½ hours. It did not show any errors.
  • I ran a CPU stress test for over 15 hours, and nothing crashed.
  • I also ran the Dell’s diagnostic tool, available in the boot menu of the motherboard. The whole test took over 2 hours but did not show any errors. It tested the memory, CPU, fans, storage drives, etc.
  • just_another_person@lemmy.worldEnglish
    1·
    7 months ago

    Seen this before, and almost always has to do with hardware failure or bad hardware config.

    Reset the BIOS/CMOS jumper on the board, go back into BIOS setup and set the proper time. Do not touch the CPU or Memory timings. Boot with the defaults and see if it still happens. Check and update the BIOS if there is a newer version as well.

    Next longer steps: test memory, then stress test the CPU. I’d be shocked if it was a storage issue as I haven’t seen that be the culprit, but might was well run the long SMART tests.

  • rookbrood@lemmy.worldEnglish
    1·
    7 months ago

    It’s a long shot, but I had something similar on one of mine servers once. It was fixed by installing irqbalance and starting that daemon at startup.

    • nutbutter@discuss.tchncs.deOPEnglish
      2·
      5 months ago

      This actually worked. The CPU has to get stuck, it will in a day of being turned on, or it will keep working for weeks.

      Thanks a lot for this!

      • rookbrood@lemmy.worldEnglish
        2·
        5 months ago

        Haha completely forgot about this comment. But i’m very gald it helped! I remember struggling with that problem for a long time.

  • Shimitar@feddit.itEnglish
    1·
    7 months ago

    Had the same issues, it was heat.

    Cool down your server, add a fan or a cooler…

    I added a usb-powered fan sucking cooler air from outside the server area directly blowing it on the chassis.

    That fixed for me.

  • Decronym@lemmy.decronym.xyzBEnglish
    1·
    7 months ago

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

    Fewer Letters More Letters
    LTS Long Term Support software version
    PSU Power Supply Unit
    RAID Redundant Array of Independent Disks for mass storage
    SATA Serial AT Attachment interface for mass storage

    4 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.

    [Thread #907 for this sub, first seen 6th Aug 2024, 10:15] [FAQ] [Full list] [Contact] [Source code]