Spontaneous Windows 11 crash while lying in bed listening to white noise, booted to BIOS

Every night I go to bed listening to a rain noise generator in Firefox. This morning I woke up coincidentally and continued to lay in bed trying to fall asleep, and that's when I heard the rain sounds turn into a horrible electronic screeching noise. My monitor was turned off so I couldn't see what was happening on the screen but I suspect BSOD. I got out of bed and went to my computer. By the time I turned on the monitor, the screeching had stopped and my computer was rebooting. Upon rebooting my computer immediately went into BIOS. I simply hit save and exit, which caused the computer to reboot again and enter BIOS again. Unsure what to do, I selected the option in BIOS to restore to the default optimized settings. I hit save and exit and this time I was able to access windows normally. I logged in and am using the computer now to make this post. I have no idea what caused the crash or why restoring default optimized settings allowed me to access windows normally (I just made that decision on instinct). It seems like a pretty severe crash and I'm worried it could happen again and might not be fixed so easily as I have no idea what caused it. Help!

I ran the V2 log collector and have zipped that into a file on my Google Drive, accessible here: Logs.zip

Windows version 23H2 (OS Build 22631.3296)

Please perform the following steps:


1) Run Tuneup plus > post a share link






2) Run Disk par info > post a share link





3) Post a share link disk management




4) Uninstall all Logitech drivers or uninstall and reinstall these Logitech drivers:

lgvirhid Logitech Gamepanel Virtual HID Device Driver (64-bit) c:\windows\system32\drivers\lgvirhid64.sys

lgbusenum Logitech Gaming Virtual Bus Enumerator Driver (64-bit) c:\windows\system32\drivers\lgbusenum64.sys



5) Uninstall the Nvidia and Intel GPU drivers using DDU > reinstall the Intel GPU drivers from the Gigabyte motherboard website and reinstall the Nvida GPU from the Nvidia website









6) The BIOS Version/Date American Megatrends International, LLC. FG, 9/12/2023

Upgrade the BIOS: FG > FH

zbook said:

Please perform the following steps:


1) Run Tuneup plus > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) Run Disk par info > post a share link

https://www.tenforums.com/attachments/bsod-crashes-debugging/355861d1640707960-batch-files-use-bsod-debugging-diskparinfo.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

3) Post a share link disk management

How to Post a Screenshot of Disk Management

How to Post a Screenshot of Disk Management at Ten Forums

www.tenforums.com

4) Uninstall all Logitech drivers or uninstall and reinstall these Logitech drivers:

lgvirhid Logitech Gamepanel Virtual HID Device Driver (64-bit) c:\windows\system32\drivers\lgvirhid64.sys

lgbusenum Logitech Gaming Virtual Bus Enumerator Driver (64-bit) c:\windows\system32\drivers\lgbusenum64.sys



5) Uninstall the Nvidia and Intel GPU drivers using DDU > reinstall the Intel GPU drivers from the Gigabyte motherboard website and reinstall the Nvida GPU from the Nvidia website

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download the latest official NVIDIA drivers

Download the latest official NVIDIA drivers

www.nvidia.com

https://download.gigabyte.com/FileList/Driver/mb_driver_666_graphicdch_31.0.101.3302.zip?v=285a0ff9130b241bfdd27d4ec3c202cf

Z790 AORUS ELITE AX (rev. 1.x) Support | Motherboard - GIGABYTE Global

Lasting Quality from GIGABYTE.GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ...

www.gigabyte.com

6) The BIOS Version/Date American Megatrends International, LLC. FG, 9/12/2023

Upgrade the BIOS: FG > FH

Z790 AORUS ELITE AX (rev. 1.x) Support | Motherboard - GIGABYTE Global

Lasting Quality from GIGABYTE.GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ...

www.gigabyte.com

Code:

LGBusEnum64.sys Fri Apr 22 11:26:40 2022 (6262F360)


LGVirHid64.sys Fri Apr 22 11:26:49 2022 (6262F369)

igdkmdn64.sys Mon Jul 24 17:37:03 2023 (64BF192F)

nvlddmkm.sys Wed Feb  7 09:39:32 2024 (65C3C054)

Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\IIGD_DCH.INF_AMD64_EFFE9612081E9042\IGDKMDN64.SYS (31.0.101.4577, 48.29 MB (50,633,296 bytes), 10/26/2023 9:19 PM)


Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPI.INF_AMD64_618B150331C5F4AD\NVLDDMKM.SYS (31.0.15.5176, 57.19 MB (59,969,568 bytes), 3/14/2024 11:25 AM)

Code:

Event[3470]
  Log Name: System
  Source: Microsoft-Windows-WinREAgent
  Date: 2024-03-14T11:29:12.4130000Z
  Event ID: 4502
  Task: N/A
  Level: Critical
  Opcode: Info  a
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: SuperCompy5000
  Description:
Windows Recovery Environment servicing failed.

Click to expand...

I'm in the middle of doing this and was able to delete every logitech driver using the Device Manager or by uninstalling logitech software except one: logi_joy_vir_hid.sys

I looked through the device list with a fine tooth comb and it doesn't seem to be associated with anything. I tried just deleting the file just to see and it's protected by TrustedInstaller

I've taken control of logi_joy_vir_hid.sys and renamed it to logi_joy_vir_hid.old

I hope it's okay to directly modify like this. If not let me know. Working on the other steps now.

I've now completed every step except step 6. I'm not sure what you're asking me to do. Does "Upgrade the BIOS: FG > FH" mean update using the FG download, then the FH download? Either way I don't know what to do with these files. Anyway, here are the files requested. I've also included a screenshot of a message that popped up after reinstalling the Intel GPU drivers, I'm not sure if it matters (the Program Comparability Assistant error)

That WinRE error isn't as serious as the crash you had, but I would recommend a clean-install, if you can't fix it by resizing the WinRE partition.
You most likely had 22H2, and that WinRE error, is a known issue. My 22H2 from September 20, 2022, suddenly had that error in later-2023, IIRC.

In fact, I almost kept my 22H2 from September 20, 2022! But I saw what looked like a hacking attempt, so I wiped the Western Digital Black SN850 1 TB SSD, installed 23H2 and changed the passwords in early-February, 2024.

Looks like UEFI-BIOS P3.40 on the ASRock B550 PG Velocita, has a faster boot time!
(P3.40 patches the LogoFail vulnerability, according to ASRock)

For that crash:

1: Reseat the video card.

2: Reseat the RAM.

RJARRRPCGP said:

That WinRE error isn't as serious as the crash you had, but I would recommend a clean-install, if you can't fix it by resizing the WinRE partition.
You most likely had 22H2, and that WinRE error, is a known issue. My 22H2 from September 20, 2022, suddenly had that error in later-2023, IIRC.

In fact, I almost kept my 22H2 from September 20, 2022! But I saw what looked like a hacking attempt, so I wiped the Western Digital Black SN850 1 TB SSD, installed 23H2 and changed the passwords in early-February, 2024.

Looks like UEFI-BIOS P3.40 on the ASRock B550 PG Velocita, has a faster boot time!
(P3.40 patches the LogoFail vulnerability, according to ASRock)

For that crash:

1: Reseat the video card.

2: Reseat the RAM.

Click to expand...

Most of this is going over my head. I did do a windows update after the crash, and you're saying I probably had a 22H2 version before I updated and the WinRE error (although I don't know what this means) is a known issue? So is it fixed by having updated? I don't knowing what resizing the WinRE partition means.

When you say "that crash" are you referring to the crash which lead to the BIOS loop? And you're telling me to reseat my video card and RAM to prevent that crash from happening?

Sorry, I just need some more clarity

I don't know how to read these logs so I don't know what my problem is

I'm guessing your issue was a failed Windows Update and your system did a roll back. My own unit did the same thing yesterday after I updated manually. It made a horrible racket in audio and it took me a few hours to get everything back. If this is your problem then I would advise skipping that update and waiting until Microsoft gets it sorted out. Originally, I thought it was my TPM module that I recently installed, but the same update also failed on my AMD build and made a mess of things as well. Just a guess, but Microsoft is getting a lot of feed back (no pun intended) on their website over it.

Foogoo said:

When you say "that crash" are you referring to the crash which lead to the BIOS loop? And you're telling me to reseat my video card and RAM to prevent that crash from happening?

Sorry, I just need some more clarity

Click to expand...

Yes, for that sound you heard and the auto-reboot!

Also, you should pull out and re-connect the SSD!

Upgrade the BIOS to the most up to date non-beta BIOS.

The motherboard BIOS version currently installed is FG.

Download and install FH so that the computer uses the most up to date non-beta BIOS.





After completing all of the steps in post #2:


1) Create a new restore point:



2) Post a new V2 share link into the newest post:




3) Open administrative command prompt and copy and paste:

dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"

Post share links.



4) Open administrative command prompt and copy and paste:

zbook said:

Upgrade the BIOS to the most up to date non-beta BIOS.

The motherboard BIOS version currently installed is FG.

Download and install FH so that the computer uses the most up to date non-beta BIOS.

Z790 AORUS ELITE AX (rev. 1.x) Support | Motherboard - GIGABYTE Global

Lasting Quality from GIGABYTE.GIGABYTE Ultra Durable™ motherboards bring together a unique blend of features and technologies that offer users the absolute ...

www.gigabyte.com

After completing all of the steps in post #2:


1) Create a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

2) Post a new V2 share link into the newest post:

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

3) Open administrative command prompt and copy and paste:

dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"

Post share links.



4) Open administrative command prompt and copy and paste:

Code:

reagentc /info
reagentc /disable
reagentc /info

Code:

diskpart
sel dis 0
sel par 3
shrink desired=1000
sel par 4
del par override
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes =0x8000000000000001
format quick fs=ntfs label=”Windows RE tools”
lis vol
exit

Code:

reagentc /enable
reagenc /info

Code:

    Disk 0 : SSD. It has 4 partition(s). Model: Samsung SSD 980 PRO 2TB

    The script has found the above 1 storage device(s) in total.
=======================================================================

Microsoft DiskPart version 10.0.22621.1

Copyright (C) Microsoft Corporation.
On computer: SUPERCOMPY5000

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online         1863 GB  1024 KB        *

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition   1862 GB  Healthy    Boot
  Volume 1                      FAT32  Partition    100 MB  Healthy    System
  Volume 2                      NTFS   Partition    674 MB  Healthy    Hidden

Disk 0 is now the selected disk.

Samsung SSD 980 PRO 2TB
Disk ID: {6CD0642F-08B4-4A10-994B-7A54EBCCDBB3}
Type   : NVMe
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(0600)#PCI(0000)#NVME(P00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : Yes
Pagefile Disk  : Yes
Hibernation File Disk  : No
Crashdump Disk  : Yes
Clustered Disk  : No

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition   1862 GB  Healthy    Boot
  Volume 1                      FAT32  Partition    100 MB  Healthy    System
  Volume 2                      NTFS   Partition    674 MB  Healthy    Hidden

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    System             100 MB  1024 KB
  Partition 2    Reserved            16 MB   101 MB
  Partition 3    Primary           1862 GB   117 MB
  Partition 4    Recovery           674 MB  1862 GB

Partition 1 is now the selected partition.

Partition 1
Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 1048576

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1                      FAT32  Partition    100 MB  Healthy    System

Partition 2 is now the selected partition.

Partition 2
Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
Hidden  : Yes
Required: No
Attrib  : 0X8000000000000000
Offset in Bytes: 105906176

There is no volume associated with this partition.

Partition 3 is now the selected partition.

Partition 3
Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Hidden  : No
Required: No
Attrib  : 0000000000000000
Offset in Bytes: 122683392

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 0     C                NTFS   Partition   1862 GB  Healthy    Boot

Partition 4 is now the selected partition.

Partition 4
Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden  : Yes
Required: Yes
Attrib  : 0X8000000000000001
Offset in Bytes: 1999691055104

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2                      NTFS   Partition    674 MB  Healthy    Hidden

===============================================================================

Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: f55eee36-74dd-11ee-8170-9f379d7b2dc5
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.
 
===============================================================================

Click to expand...

Awesome thanks! Done. I barely understand what I did with the CMD prompt but I appreciate you spelling out the instructions for me lol. I don't know if that last "code:" box is supposed to mean anything to me though. I didn't "do" anything with that

I've attached the driver file you requested, the updated Log Collector V2 log is apparently just a little too big to upload so here it is from my Google Drive: Updated Log V2 (2024-03-14_22-56-53)_2.zip

btw that last command "reagenc /info" wasnt recognized, i assume that was a typo from the earlier command "reagentc /info" so I used the latter for that step, I'm assuming that's correct

Please make sure that any / all logitech hardware are detached.



Open administrative command prompt and copy and paste:

pnputil /delete-driver oem24.inf /uninstall /force



Run DDU again to uninstall the Intel GPU drivers.

Do not manually reinstall.

Perform Windows updates > indicate any prompt to reinstall > post a new V2.


Post new share links for:

dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"

https://www.tenforums.com/attachmen...atch-files-use-bsod-debugging-diskparinfo.bat

zbook said:

Please make sure that any / all logitech hardware are detached.



Open administrative command prompt and copy and paste:

pnputil /delete-driver oem24.inf /uninstall /force



Run DDU again to uninstall the Intel GPU drivers.

Do not manually reinstall.

Perform Windows updates > indicate any prompt to reinstall > post a new V2.


Post new share links for:

dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"

https://www.tenforums.com/attachmen...atch-files-use-bsod-debugging-diskparinfo.bat

Click to expand...

That first instruction is a bit of an obstacle since I only own logitech peripherals... how necessary is that part

Which peripheral?

See if you can temporarily use another peripheral for a complete uninstall or a complete uninstall and reinstall.


In startup programs it displayed:

Logitech Download Assistant c:\windows\system32\rundll32.exe c:\windows\system32\logilda.dll,logifetch Public HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

zbook said:

Which peripheral?

See if you can temporarily use another peripheral for a complete uninstall or a complete uninstall and reinstall.


In startup programs it displayed:

Logitech Download Assistant c:\windows\system32\rundll32.exe c:\windows\system32\logilda.dll,logifetch Public HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Click to expand...

Both my mouse and keyboard are Logitech, and I don't own any other mouse or keyboard. If it's truly necessary I can buy a cheap mouse and keyboard combo from a different manufacturer

Then temporarily uninstall and reinstall.
Use safe mode (shift + restart) as needed.

Download the new drivers to the desktop before the uninstall.

zbook said:

Then temporarily uninstall and reinstall.
Use safe mode (shift + restart) as needed.

Click to expand...

I'm sorry I still don't understand. Temporarily uninstall what? Are you saying I should proceed with the DDU uninstall of the Intel GPU drivers while using my Logitech keyboard and mouse, or are you saying I need to get a mouse and keyboard that are not Logitech before I do the DDU uninstall?

If possible reinstall logitech software / drivers after a complete uninstall.
(these were the latest misbehaving drivers (in March))
(it is not necessary to use alternative peripherals)





DDU is to make sure that the error message in the earlier post is addressed.
(these were the misbehaving drivers in February)

zbook said:

If possible reinstall logitech software / drivers after a complete uninstall.
(these were the latest misbehaving drivers (in March))
(it is not necessary to use alternative peripherals)

Software

support.logi.com

Download Logitech Options Customization Software

Logitech Options unlocks features and lets you customize your mice, keyboards and touchpads for optimal productivity and creativity.

www.logitech.com

DDU is to make sure that the error message in the earlier post is addressed.
(these were the misbehaving drivers in February)

Click to expand...

Ah, I see. I did uninstall all my logitech software and drivers already. Or at least I tried to. LogiLDA.DLL is indeed still in my System32 directory, but there's no program associated with it I can uninstall as I already uninstalled everything I can. Should I just delete the LogiLDA.DLL file?