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.
  • Shimitar@feddit.itEnglish
    7·
    4 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.

    • nutbutter@discuss.tchncs.deOPEnglish
      1·
      3 months ago

      I cleaned everything and reapplied the thermal paste. That did not solve the problem. Also, the CPU is only of 35 watts and never goes over 55°C.

  • tenchiken@lemmy.dbzer0.comEnglish
    3·
    4 months ago

    That server sounds a bit older in the teeth… Has new thermal paste been applied to the cpu? Even if the reported temps are under 90c, you might be getting hot spots causing glitches inside the package.

    Worth trying a couple of different generations of kernel as well, both newer and older. You might be hitting a regression somewhere.

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

      I cleaned everything and reapplied the thermal paste. That did not solve the problem. Also, the CPU is only of 35 watts and never goes over 55°C.

  • just_another_person@lemmy.worldEnglish
    3·
    4 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.

    • nutbutter@discuss.tchncs.deOPEnglish
      1·
      3 months ago

      I did reset it. It did not help. I ran memtest86 for over 2 hours and did a CPU stress test for over 15 hours. Nothing crashed during the testing.

  • solrize@lemmy.worldEnglish
    1·
    4 months ago

    Try running memtest86 for a few days to test memory. That is fairly easy to do though it involves booting from a flash drive. Web search should find info.

    • nutbutter@discuss.tchncs.deOPEnglish
      1·
      3 months ago

      I just ran it. It took over 2 hours to finish. Showed no errors. Is there a benefit of running it for a few days?

      • solrize@lemmy.worldEnglish
        2·
        3 months ago

        If the problem is intermittent then longer run has better chance of catching it, but 2 hours with no errors is a good sign, with regard to the memory.

  • Decronym@lemmy.decronym.xyzBEnglish
    1·
    3 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]

  • lolonaut@discuss.tchncs.deEnglish
    1·
    4 months ago

    I had problems with soft locks because somehow the PSU was in corrupt state, maybe through a black out or something. The problem persisted through reboots and power offs, only cutting power helped.

  • rookbrood@lemmy.worldEnglish
    1·
    4 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·
      1 month 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·
        1 month ago

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

  • TheBigBrother@lemmy.worldEnglish
    02·
    4 months ago

    Set watchdog to reboot every day and juice it until the last drop before it definetly crashes.

    Edit: that’s just a workaround if you really want try to fix it my answer would be restoring BIOS defaults, then clean install of the OS and then check it everything works fine, if the error persist try installing another OS if it still fail then go to the first step.