isXander

I forgot to mention, after disabling EXPO the system works again. I can't really live without memory context restore on DDR5, it's so slow otherwise! Will try retraining expo tomorrow and see if it's fixed.

I believe it's an October 23 BIOS. I just don't understand the sudden change?

I'm on AM5 platform Ryzen 7700x, with 5600mhz 2x16gb kit. MSI b650 gaming plus mobo. For months EXPO has been running a dream. Now suddenly, my computer locked up and got in a boot loop. Even the recovery volume was freezing after about a minute. This included bluescreens from many different sys files. My question is, how can a rock solid EXPO profile go from fine to can't even stay in the recovery partition for more than a minute? Bad RAM? Bad CPU?

Bump

1. I just logged on to my PackardBell iMedia PC and just as I got to the desktop, it BSOD with the stop code IRQL_NOT_LESS_OR_EQUAL. (I used this pc just yesterday and have had no prior issues with it) This bsod screen appeared to have a graphical glitch that got worse every frame. I waited for a while but it seemed to get stuck at 25% so I held down the powerbutton to hard shutdown. 2. When turning it on again, the power light turns on, I hear the usual hard drive startup sound, hard drive light starts flickering followed with 1 beep then it immediately shuts down. (I didn't even get any display output in this time and this whole event happened in about a second of pressing the powerbutton.) Now the pc is stuck looping this so I held down the powerbutton to hard shutdown. I tried turning it on again and it did the exact same thing. 3. I left it for about 5 minutes and tried again. Success! It was doing windows update. It got to the blue screen with the percentage on and soon bluescreened again. DRIVER_IRQL_NOT_LESS_OR_EQUAL (dxgmms2.sys). It now got stuck at 45% so I hard shutdown and now it is doing the beep loop thing again. 4. Repeat paragraph 2 indefinitely. Please help...

idek what grub I am using. or if my windows is uefi... or how to reinstall grub

os-prober doesnt output anything in this occasison. in that thread it detects it

Grub bootloader does not detect my windows installation. Windows is installed on a different disk than grub. Am I right in thinking that grub does not search for installs on different disks? Windows is mounted to /run/media/isxander/Windows. I have used update-grub and os-prober but nothing works. Edit: I have had problems with grub in the past. Manjaro made grub hidden by default. Also, when peeking in grub.cfg, a lot of things are uncommented when they said uncomment if which suggests manjaro has changed it quite a lot Edit 2: I am new with linux so I am not comfortable with changing configs unless it is step-by-step (hope you understand)

it was an msi monitor haha Ryzen 7 3700x RTX 2070 SUPER 32 GB DDR4 3600 MHZ RAM MSI B450 Gaming Plus Motherboard

Just wanted to ask how I properly save my settings. I make AOC monitor to be X screen 1 which prompts me I need to save and restart. I click apply and it says: Could not apply all changes. Apply what it can? I click yess and then I click save to X config file. This works just fine. I reboot to find that the driver decided instead my AOC monitor is now on X Screen 0 again. I believe this issue is why I am getting horrible screen tearing because the MSI monitor is set to 144hz and the aoc one is set to 60. Also, force full composition timeline also does not save which I have found people saying it is a fix to tearing.

I don't know if this helps but my Windows disk is mounted to /run/media/isxander/Windows

os-prober just does this [isxander@xander-manjaro ~]$ sudo os-prober [isxander@xander-manjaro ~]$ it takes about 3 seconds with good hardware

sudo blkd /dev/nvme0n1p1: UUID="652A-48EE" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="87db2a76-ce75-3a45-9d82-45254aa1683d" /dev/nvme0n1p2: UUID="ab979285-b46f-4939-96dc-b1c12213cd30" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f5b75c80-cd74-ba44-8c6a-2085effa3b69" /dev/sda1: LABEL="System Reserved" BLOCK_SIZE="512" UUID="DC68CB3968CB1166" TYPE="ntfs" PARTUUID="84556d8b-01" /dev/sda2: LABEL="Windows" BLOCK_SIZE="512" UUID="3E06CD4906CD033F" TYPE="ntfs" PARTUUID="84556d8b-02" /dev/sda3: BLOCK_SIZE="512" UUID="422042A420429EB3" TYPE="ntfs" PARTUUID="84556d8b-03" /dev/sdb1: LABEL="Data" BLOCK_SIZE="512" UUID="DC0A62110A61E94A" TYPE="ntfs" PARTUUID="37df4821-01" cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a device; this may # be used with UUID= as a more robust way to name devices that works even if # disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> UUID=652A-48EE /boot/efi vfat umask=0077 0 2 UUID=ab979285-b46f-4939-96dc-b1c12213cd30 / ext4 defaults,noatime 0 1 lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk ├─sda1 8:1 0 549M 0 part ├─sda2 8:2 0 222.2G 0 part └─sda3 8:3 0 831M 0 part sdb 8:16 0 931.5G 0 disk └─sdb1 8:17 0 931.5G 0 part nvme0n1 259:0 0 465.8G 0 disk ├─nvme0n1p1 259:1 0 300M 0 part /boot/efi └─nvme0n1p2 259:2 0 465.5G 0 part / sudo find /boot/efi/ -print /boot/efi/ /boot/efi/EFI /boot/efi/EFI/Manjaro /boot/efi/EFI/Manjaro/grubx64.efi /boot/efi/EFI/boot /boot/efi/EFI/boot/bootx64.efi

Wow thanks! It is super weird why Manjaro would choose to hide grub by default. However... Windows is not an option. Just Manjaro. How can I make grub see Windows? I have tried "sudo os-probe" and just used "sudo update-grub" so idk

That is my problem: I cannot locate grub