Dell Inspiron 7375 Randomly freezing and needing hard shutdown

Hi fellow Manjaro Users,

I have BIG problems with my new Dell Inspiron 7375.
The laptop randomly freezing and needing hard shutdown.
Sometimes, after the hard shutdown (or after a normal shutdown too !), the system won't boot and display a message with LVM mirrors not mounting with an infinite limit of time

  • I upgraded the BIOS of the laptop,
  • used several different kernel (4.19 and 5.1),
  • use different distro (Fedora, Debian..)
  • followed the Arch Wiki page for this laptop,

and I still have this issue for 3 months. After some research on the web, a lot of people seems to have this problem but I have found 0 solutions.

I'm seriously thinking of giving up and ask a refund as the problem seems to be the same on Windows. But before that guys, have you got an idea of what's going wrong ?

Thanks :wink:

Oh and, for informations ^^ :

inxi -Fxzc0
System:    Host: Sulaco Kernel: 5.2.20-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 Desktop: KDE Plasma 5.16.5 
           Distro: Manjaro Linux 
Machine:   Type: Laptop System: Dell product: Inspiron 7375 v: 1.4.1 serial: <filter> 
           Mobo: Dell model: 0GTNWX v: A00 serial: <filter> UEFI: Dell v: 1.4.1 date: 06/04/2018 
Battery:   ID-1: BAT0 charge: 34.0 Wh condition: 34.0/42.0 Wh (81%) model: BYD DELL FW8KR81 status: Full 
CPU:       Topology: Quad Core model: AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen 
           L2 cache: 2048 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 35151 
           Speed: 1536 MHz min/max: 1600/2200 MHz Core speeds (MHz): 1: 1463 2: 1462 3: 1370 4: 1370 5: 1369 6: 1373 7: 1593 
           8: 1392 
Graphics:  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Dell driver: amdgpu v: kernel 
           bus ID: 02:00.0 
           Display: wayland server: X.Org 1.20.5 driver: amdgpu FAILED: ati unloaded: modesetting resolution: 1920x1080~60Hz 
           OpenGL: renderer: AMD RAVEN (DRM 3.32.0 5.2.20-1-MANJARO LLVM 8.0.1) v: 4.5 Mesa 19.2.1 direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Dell driver: snd_hda_intel 
           v: kernel bus ID: 02:00.1 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
           bus ID: 02:00.6 
           Sound Server: ALSA v: k5.2.20-1-MANJARO 
Network:   Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel 
           bus ID: 01:00.0 
           IF: wlp1s0 state: up mac: <filter> 
           Device-2: Qualcomm Atheros Touchscreen type: USB driver: btusb bus ID: 3-2.1:4 
Drives:    Local Storage: total: 476.94 GiB used: 236.76 GiB (49.6%) 
           ID-1: /dev/sda vendor: A-Data model: SU800NS38 size: 476.94 GiB 
Partition: ID-1: / size: 459.50 GiB used: 236.74 GiB (51.5%) fs: ext4 dev: /dev/sda2 
           ID-2: swap-1 size: 8.80 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 67.0 C mobo: 49.0 C sodimm: 36.0 C gpu: amdgpu temp: 66 C 
           Fan Speeds (RPM): cpu: 4096 
Info:      Processes: 291 Uptime: 1m Memory: 11.43 GiB used: 2.55 GiB (22.3%) Init: systemd Compilers: gcc: 9.2.0 Shell: bash 
           v: 5.0.11 inxi: 3.0.36

does seem like hardware, if its doing the same thing on all OSes...

Could be over heating, check temps

you say you checked this already ?

https://wiki.archlinux.org/index.php/Dell_Inspiron_7375
https://wiki.archlinux.org/index.php/Dell_Inspiron_7375#Improve_Cooling

Could also be bad memory, do a memcheck.

I'd do the tests under Windows just to rule out any linux OS problems.

Hi ant !

Ant wrote :

does seem like hardware, if its doing the same thing on all OSes...

This is what I'm starting to think...

Ant wrote :

you say you checked this already ?
https://wiki.archlinux.org/index.php/Dell_Inspiron_7375
https://wiki.archlinux.org/index.php/Dell_Inspiron_7375#Improve_Cooling

Yes I did, no effects.

Ant wrote :

Could also be bad memory, do a memcheck.

Good idea, I will and will report any error code / message

It will be hard to do test under Windows as I'm not dualbooting for years and this laptop is used for my daily business. I will find a solution for rulling out linux OS problems.

Thanks for your answer :wink:

Could also be bad memory, do a memcheck.

Done. All the test have been passed and nothing to say so far.

Are they any logs that I could read for having a clue of the problem ?

Have a look through this, save me typing it again :wink:

I used the journalctl -p 3 -xb and this is the result :

-- Logs begin at Wed 2019-08-28 17:11:57 CEST, end at Thu 2019-10-10 15:32:26 CEST. --
oct. 10 14:00:44 Sulaco kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[4] not in IVRS table
oct. 10 14:00:44 Sulaco kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[5] not in IVRS table
oct. 10 14:00:44 Sulaco kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
oct. 10 14:00:44 Sulaco kernel: AMD-Vi: Disabling interrupt remapping
oct. 10 14:00:44 Sulaco kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20190509/dswload2-159)
oct. 10 14:00:44 Sulaco kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190509/psobject-220)
oct. 10 14:00:44 Sulaco kernel: pci 0000:00:00.2: AMD-Vi: Unable to write to IOMMU perf counter.
oct. 10 14:00:44 Sulaco systemd-modules-load[305]: Failed to find module 'vboxsf'
oct. 10 14:00:44 Sulaco kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xbf774000-0xbf777fff]
oct. 10 14:00:45 Sulaco systemd-modules-load[551]: Failed to find module 'vboxsf'
oct. 10 14:00:45 Sulaco systemd[1]: Failed to start Load Kernel Modules.
-- Subject: L'unité (unit) systemd-modules-load.service a échoué
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
-- 
-- L'unité (unit) systemd-modules-load.service a échoué, avec le résultat failed.
oct. 10 14:00:45 Sulaco systemd-modules-load[563]: Failed to find module 'vboxsf'
oct. 10 14:00:45 Sulaco systemd[1]: Failed to start Load Kernel Modules.
-- Subject: L'unité (unit) systemd-modules-load.service a échoué
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/technical-issues-and-assistance
-- 
-- L'unité (unit) systemd-modules-load.service a échoué, avec le résultat failed.
oct. 10 14:00:45 Sulaco kernel: pcieport 0000:00:01.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
oct. 10 14:00:45 Sulaco kernel: pcieport 0000:00:01.1: AER:   device [1022:15d3] error status/mask=000000c0/00006000
oct. 10 14:00:45 Sulaco kernel: pcieport 0000:00:01.1: AER:    [ 6] BadTLP

I have seen similar errors on the web in this case, especially the OAPIC and ACPI ones
but I don't know what I can do with these informations, or even if I can do something.
I have also have something mentionning TLP, are we talking about the "laptop" part of power-management of the OS ? :



-- L'unité (unit) systemd-modules-load.service a échoué, avec le résultat failed.
oct. 10 14:00:45 Sulaco kernel: pcieport 0000:00:01.1: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
oct. 10 14:00:45 Sulaco kernel: pcieport 0000:00:01.1: AER:   device [1022:15d3] error status/mask=000000c0/00006000
oct. 10 14:00:45 Sulaco kernel: pcieport 0000:00:01.1: AER:    [ 6] BadTLP                
oct. 10 14:00:45 Sulaco kernel: pcieport 0000:00:01.1: AER:    [ 7] BadDLLP               
oct. 10 14:00:45 Sulaco kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
oct. 10 14:00:45 Sulaco kernel: kfd kfd: Failed to resume IOMMU for device 1002:15dd
oct. 10 14:00:45 Sulaco kernel: kfd kfd: device 1002:15dd NOT added due to errors
oct. 10 14:00:45 Sulaco systemd-backlight[777]: Failed to get backlight or LED device 'backlight:acpi_video1': No such device
oct. 10 14:00:45 Sulaco systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video1.
-- Subject: L'unité (unit) systemd-backlight@backlight:acpi_video1.service a échoué
-- Defined-By: systemd

Are you running Manjaro is a Virtualbox environment or just loading one?

Hi @Carbonkid,

the problem seems to be the same on Windows.

If you retained windows, i.e you are dual booting, go to Del'sl diagnose page: https://www.dell.com/support/home/uk/en/ukbsdt1/product-support/product/inspiron-13-7375-2-in-1-laptop/diagnose and follow the instructions, for their quick test, it will at least eliminate and narrow the possible issue.

Press F2 and enter BIOS at boot-up and have a look in the System logs, (at bottom), and click on Thermal Event. My elderly 5430, kept shutting down, it was registered in the logs. I changed the heatsink, bought at a reasonable price on eBay. This sorted the issue, but it does seem to run hot. Can't compare to previous as I did not take note of its usual working temperature.

If your laptop is still within warranty, I've found Dell to honour them, regardless of OS installed.

Service manual:

:wink:

Try adding this to the grub command line, you can add it at boot, for that session see if any journal errors got removed.
pcie_aspm=off
failing that I don't know

post your inxi -Fxzc0 as well please, for other potential helpers :wink:

Are you running Manjaro is a Virtualbox environment or just loading one?

@ c00ter I'm running it on real hardware, but I installed Virtualbox for other OS & distros

If you retained windows, i.e you are dual booting, go to Del'sl diagnose page: https://www.dell.com/support/home/uk/en/ukbsdt1/product-support/product/inspiron-13-7375-2-in-1-laptop/diagnose and follow the instructions, for their quick test, it will at least eliminate and narrow the possible issue.

@mack I'm not using Windows on dualboot, I tested it one month ago and it have the same problem, so I erased it.

Press F2 and enter BIOS at boot-up and have a look in the System logs, (at bottom), and click on Thermal Event. My elderly 5430, kept shutting down, it was registered in the logs. I changed the heatsink, bought at a reasonable price on eBay. This sorted the issue, but it does seem to run hot. Can't compare to previous as I did not take note of its usual working temperature.

@ I can't do that, it's still under warranty, it is only three month old ^^

If your laptop is still within warranty, I've found Dell to honour them, regardless of OS installed.

Which is a good thing, I kept that option in my mind but I don't want to give up... for now. But thank you for sharing your experience with Dell :wink:

Try adding this to the grub command line, you can add it at boot, for that session see if any journal errors got removed.
pcie_aspm=off
failing that I don't know

Ok, I will try to do that !

My laptop have crash once again but for the first time with Linux 5.2 kernel, and for the first time I can access to a VTY. Here is the dump of a "journalctl -p err" just after the graphic shell crash :

oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:42 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out or interrupted!
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: [gfxhub] retry page fault (src_id:0 ring:0 vmid:1 pasid:32768, for process Xorg pid 836 thread Xorg:cs0 pid 981)
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0:   in page starting at address 0x0000000107500000 from 27
oct. 10 18:29:47 Sulaco kernel: amdgpu 0000:02:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
oct. 10 18:29:49 Sulaco kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered

Pretty sure you should be using the latest kernel with that Hardware!?

post your inxi -Fxzc0 please.

I'm using it and the laptop crashed 4 times in 10 minutes.

I tried with Plasma Wayland, when I launch Signal in flatpak format, exactly the same crash.
Tried a second time, exactly the same crash. Tried other flatpak : no crash.

But I wasn't using Signal before, when the laptop crash several times.

I really can't understand the logic of this situation :frowning_face: ...

The command on the grub line pcie_aspm=offhave erased the BadTLP error, but still crashing anyway.

post your inxi -Fxzc0 please.

I posted it on the initial post :wink:

1 Like

From your inxi output:

Wayland support in plasma is not stable (enough), switch to X11.

I was using X11until one hour ago. Currently trying Wayland and gaming under Steam (so, XWayland with that), no crash until now.

there are other threads here on the forum as well as instructions on how to put together the correct kernel parameter (it not one size fits all) but i dont remember exactly where so you'd have to do some google-fu. IIRC this alone causes lockups without the kernel parameter to correctly define IOAPIC[4] and IOAPIC[5]

do you have the latest bios update?

edit: just noticed the arch wiki on your model includes the correct ones (i think?)

Kernel and Grub Parameters

System will be unstable with kernel bellow 4.20, while you have older kernel add this parameters to grub

quiet radeon.dpm=1 acpi_osi=Linux acpi_backlight=vendor amd_iommu=on ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 idle=nomwait

you can use grub-customizer to make it easier

if you followed that wiki, i hope you ignored the last bit about using grub-clusterfcukstomizer :wink:

post output:

cat /proc/cmdline

@dglt

Didn't use grub-customizer as I think it's more a problem creator than a problem solver :wink:

1 Like

FINALLY, I found some solutions after three month of research.
As it affect a lot of Dell Inspiron 7375 users, I hope it will work to other users. Should I write it into the documentation page of this model ?

So, mains problem were :

1. System often doesn't boot, taken in a loop with LVM mounting impossibilities.
The solutions (at least for Manjaro) are :

  • Update the f****** DELL bios to the 1.5 version.
    The 2019 edition of Inspiron 7375 is still sold with a 1.1 version of the BIOS
  • Use the Linux 5.2 Kernel, minimum

2. Xorg crash randomly whatever the app, scenario or use case :
The solutions (at least for Manjaro) are :

  • Update Kernel to 5.2 for better handling of AMD Vega Graphics and Ryzen processors
  • Stop using Xorg if it's possible for you and use Wayland, Wayland has a few minor bugs at this time but it will not completely crash and if it crash it will restart by itself without closing your session and losting your work (had few minor crash on my laptop but relaunch itself within a second)
  • Certains flatpak apps seems to make the Display Server to crash (Signal & Dolphin-Emulator), so I stopped using the flatpak version of these apps. Other flatpak apps (Freetube, Spotify...) doesn't crash the Display Server. I have to investigate about these.

I mark this as a solution, but I still have few minor crash of both Wayland (relaunched itself) & Xorg (crash miserably). When Xorg crash, I still can't have access to any TTY.

I think you'll probably be just fine once kernels & firmware catch up to your new hardware. It took about a month or so recently when this 9th Gen Coffee Lake Refresh was brand new, and the same with my Haswell machine back in 2014, both Dells.

Good catch on your BIOS/EFI update! Same thing happened here.

regards

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by