Hiya, it's me again! Unfortunately I have ran into a new issue, and after exhausting everything I know and then some, I'm still stuck.
First and most importantly, the PC in question is my old rig now used by my partner. It's the exact same PC I used when I posted here with GPU issues back in October (I did get it fixed in the end! It was a faulty GPU. RMA'd & new one works great) minus the GPU & PSU, which I took with me to my new PC and returned the previous ones into this PC where they have worked perfectly fine as they have for years before up until Sunday (2 days ago) when this issue first started and has continued since.
Specs:
Mobo - Msi x370 gaming pro carbon (MS-7A32, Bios ver E7A32AMS.1L0)
CPU - Ryzen 7 1700 @ 3.0GHz
RAM - 2x 8GB Corsair Vengeance LPX DDR4, in slot 2 and 4 (DIMMB2 & DIMMA2)
GPU - MSI GTX 980
PSU - Novatech Power Station 750w Black Edition
Boot drive: Kingston 120GB SSD running Windows 10 on latest version & updates
Issue:
As much as I wish I could just easily say "this is the problem exactly", it's not that simple, as it varies depending on different factors.
When I say freeze, I mean a proper unrecoverable freeze which no amount of time waiting will resolve. The PC becomes completely unresponsive, including the power button, and a hard reboot (hold down power button until it dies) is the only solution.
Here's the steps I've taken so far to try and solve this:
Now about the Ubuntu with different launch options - When running with "quiet" and "splash" disabled, I found that there are only 2 messages on which the system does it's usual freeze. "nomodeset" does not affect this in any way whatsoever. The messages are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
OR
Freeing initrd memory: 73352K
The "EFI stub" message is the only message displayed. The other one has a bunch of stuff before it, which would take too long to write out there. I've included a picture of the monitor with the text to this post. There doesn't seem to be a rhyme or reason for why it sometimes freezes on the first message and at others allows it to progress a bit before freezing again on the second message. I've been able to get both results to happen with the different RAM configs I tried. I also tried waiting a different amount of time on GRUB a few times before booting to see if that has an effect and nope. Like I said already, nomodeset does not make a difference.
I've inspected every inch of the motherboard & the GPU and found nothing odd - everything looks fine from that aspect. If we ignore the freezing, the PC works just as it has done forever, with nothing out of the ordinary or any hints that something is not right.
I'm still baffled about how memtest86 or grml work just fine yet everything else seems to have a problem, and just how out of the blue this issue has come on. If I could get some help It'd be much appreciated!
First and most importantly, the PC in question is my old rig now used by my partner. It's the exact same PC I used when I posted here with GPU issues back in October (I did get it fixed in the end! It was a faulty GPU. RMA'd & new one works great) minus the GPU & PSU, which I took with me to my new PC and returned the previous ones into this PC where they have worked perfectly fine as they have for years before up until Sunday (2 days ago) when this issue first started and has continued since.
Specs:
Mobo - Msi x370 gaming pro carbon (MS-7A32, Bios ver E7A32AMS.1L0)
CPU - Ryzen 7 1700 @ 3.0GHz
RAM - 2x 8GB Corsair Vengeance LPX DDR4, in slot 2 and 4 (DIMMB2 & DIMMA2)
GPU - MSI GTX 980
PSU - Novatech Power Station 750w Black Edition
Boot drive: Kingston 120GB SSD running Windows 10 on latest version & updates
Issue:
As much as I wish I could just easily say "this is the problem exactly", it's not that simple, as it varies depending on different factors.
- Windows 10 on boot drive - POSTs fine, begins loading windows, and freezes at a random point between a few seconds in, up to displaying the login screen (before it's fully loaded in).
- Windows 10 Automatic Repair - POSTs fine, begins loading automatic repair, freezes before it can progress from that stage, so around 1 to 5 seconds in.
- Windows 10 Installation media (USB 1 and 2 tested) - POSTs fine, begins loading and freezes anywhere from 1 to 5 seconds.
- Windows 11 Installation media (USB 1) - See above.
- Ubuntu 24.04 Live CD (USB 2) - POSTs, loads into GRUB just fine, running the default option or safe mode (nomodeset) results in a freeze at the splash screen. I have ran it with "quiet" and "splash" off and will touch on the results of that later. Apart from a few times, I have almost always been using the safe mode (nomodeset), even though there's absolutely no difference in behaviour.
- SystemRescueCD 11 (USB 2) - POSTs, loads into GRUB fine, running any option which launches SystemRescue results in all text going away as if it's getting ready to load it and freezes while still displaying the blank sky blue GRUB background it uses.
- Memtest86 v7 (Included in SystemRescueCD 11) - Works fine. No, seriously. It loads in and performs the tests. Not an issue in sight. RAM passed with flying colours (default options: 4 passes, 10 tests)
- Memtest86 v10.7 (USB 1 and 2 tested) - Again, this works fine, even with its fancy user interface. And once again, RAM passes (default options: 4 passes, 10 tests)
- grml 2024.02 (USB 2) - Well would you look at that, it works fine too! Only when using the "debug" launch item, the "graphical" one does not work due to an issue with grml itself and not the PC.
- BIOS itself - Works fine. Spent a few hours in there at one point and did not encounter an issue.
When I say freeze, I mean a proper unrecoverable freeze which no amount of time waiting will resolve. The PC becomes completely unresponsive, including the power button, and a hard reboot (hold down power button until it dies) is the only solution.
Here's the steps I've taken so far to try and solve this:
- Tried normal boot up a few times
- Tried forcing Automatic Repair to appear, which it did, only to also freeze as already described
- Switched monitors to make sure it wasn't a dying display
- Tried running Windows 11 Installation media a couple of times
- Tried running Windows 10 Installation media a few times
- Unplugged all drives, including the boot drive. From here on out, even right now, they have not been reconnected again.
- Tried running Windows 10 & 11 Installation media again a few times
- Ran Ubuntu 24.04 Live CD from USB twice
- Ran Memtest86 v10.7 and allowed it to complete all 4 tests successfully
- Ubuntu again
- Switched to using Displayport instead of HDMI to make sure it's not just a dying HDMI port
- Tried SystemRescueCD from USB a few times
- Tried Memtest86 v7 that's included in SystemRescueCD and once again allowed it to complete all 4 tests successfully
- Ran grml 2024.02 debug successfully a few times to ensure it's not a fluke.
- Tried grml graphical and failed to boot. Found out it's an issue with grml itself.
- Reset BIOS
- Tried windows 10 installation media again, and when that failed...
- ...I reset bios by removing CMOS battery, hitting the power button a few times, and leaving it for overnight + most of the next day. I hit the button a few more times before reinserting the battery and plugging back the power
- Left bios at default settings
- Tried ubuntu again
- Tried Windows 10 media again
- Switched to a different dp port on the GPU does in case
- Windows 10 media a few more times
- Verbally abused the PC, followed by begging it for forgiveness... Was worth a try!
- Tried Ubuntu, but this time removing the "quiet" and "splash" options. More on this later. Tried this ~20 or so times
- On the advice of a computer repair shop who said "it's either RAM or Mobo", I tried different ram configs with Ubuntu & Windows 10 media
- Swapping RAM around (from R1 in DIMMB2 and R2 in DIMMA2 to R2 in DIMMB2 and R1 in DIMMA2)
- Running in 1-3 instead of 2-4 (R1 in DIMMB1 and R2 in DIMMA1)
- Running 1 stick (R1) in DIMMB2
- Swapping which stick is in DIMMB2 (R2)
- Trying the same thing with DIMMB1
- 1-3 again, but R1 and R2 are swapped
- Tested single stick in the 3 other slots as well, as well as switching sticks and doing it again
- Out of defeat, I tried windows 10 media a few more times.
Now about the Ubuntu with different launch options - When running with "quiet" and "splash" disabled, I found that there are only 2 messages on which the system does it's usual freeze. "nomodeset" does not affect this in any way whatsoever. The messages are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
OR
Freeing initrd memory: 73352K
The "EFI stub" message is the only message displayed. The other one has a bunch of stuff before it, which would take too long to write out there. I've included a picture of the monitor with the text to this post. There doesn't seem to be a rhyme or reason for why it sometimes freezes on the first message and at others allows it to progress a bit before freezing again on the second message. I've been able to get both results to happen with the different RAM configs I tried. I also tried waiting a different amount of time on GRUB a few times before booting to see if that has an effect and nope. Like I said already, nomodeset does not make a difference.
I've inspected every inch of the motherboard & the GPU and found nothing odd - everything looks fine from that aspect. If we ignore the freezing, the PC works just as it has done forever, with nothing out of the ordinary or any hints that something is not right.
I'm still baffled about how memtest86 or grml work just fine yet everything else seems to have a problem, and just how out of the blue this issue has come on. If I could get some help It'd be much appreciated!
Attachments
-
975 KB Views: 8