After updating my laptop HP Omen 15 to Windows 11, I have been frequently met with BSOD

[KisukeUrh]

Hello, I few days ago i decided to make a clean install of Windows 11 on my Laptop HP Omen 15, unfortunetly im constantly met with BSOD. I have updated all my drivers to the latest versions. In addition i have downloaded the HP Support Center to check further if im missing something, but everything seems to be fine. I cannot seem to find the cause of this issue and i have not experienced anything like that before. My only concerns are that, it might something to do with enabling tpm 2.0 for Win 11. Please, i would appreciate any help that would lead to solving my problem. Thanks in advance.

[Alden4]

Hi @KisukeUrh,

Welcome to HP Support Community.

Thank you for posting your query, I will be glad to help you.

It sounds frustrating to experience frequent BSODs after a clean install of Windows 11 on your HP Omen 15. Since you've already updated all drivers and run HP Support Center diagnostics, here are a few more things you can try to resolve the issue.

Check Event Viewer for BSOD Error Codes

• Open Event Viewer by typing eventvwr.msc in the search bar and hit Enter.
• Go to Windows Logs > System and look for critical errors or warnings related to the BSODs. The error codes or messages can provide clues about the cause (e.g., 0x0000007E, IRQL_NOT_LESS_OR_EQUAL, etc.).
• If you see an error code or driver name, this can guide you to the specific issue.

Run Memory Diagnostics

• Faulty RAM can also lead to BSODs. Try running the Windows Memory Diagnostic Tool to check for memory issues:
  1. Type "Windows Memory Diagnostic" in the search bar.
  2. Select "Restart now and check for problems."
  3. Follow the instructions to let it check for any issues.

Disable TPM 2.0 Temporarily

Since you mentioned TPM 2.0, it could be causing issues with Windows 11. Some systems have compatibility problems with TPM 2.0 enabled, especially with specific configurations. To disable TPM:

1. Restart your laptop and enter BIOS/UEFI settings (usually by pressing F10 or ESC during startup).
2. Navigate to Security or Advanced settings.
3. Disable TPM 2.0 or Intel Platform Trust Technology (PTT), depending on what your system uses.
4. Save and exit BIOS.

After disabling TPM 2.0, check if the BSODs persist. If they stop, it may be related to TPM compatibility.

Check for Driver Issues

Even though you updated your drivers, there could be a conflict or outdated firmware. You can try the following:

• Rollback Drivers: Sometimes, newer drivers can introduce bugs. Try rolling back to a previous driver version for your graphics, chipset, or network adapter.
  1. Open Device Manager (devmgmt.msc).
  2. Right-click on the device (e.g., graphics card or network adapter).
  3. Select Properties > Driver tab > Roll Back Driver (if available).
• Check Device Manager for any yellow exclamation marks that indicate problematic drivers or devices.

Run SFC / DISM Commands

Corrupted system files can cause instability. To repair them:

1. Open Command Prompt as Administrator.
2. Run the following commands:
   • sfc /scannow
   • After completion, run: DISM /Online /Cleanup-Image /RestoreHealth
3. Restart your laptop after the scan completes.

[Alden4]

Update BIOS/UEFI

Sometimes, BIOS updates include fixes for TPM or hardware compatibility with newer OS versions. Check the HP Support website for your laptop model to see if there is a new BIOS version available. If there is, follow the instructions on HP’s website to update the BIOS.

Perform a Clean Boot

A clean boot can help eliminate third-party software as the cause of the issue. To perform a clean boot:

1. Press Windows + R, type msconfig, and press Enter.
2. Go to the Services tab and check Hide all Microsoft services.
3. Click Disable All for non-Microsoft services.
4. Go to the Startup tab and disable all startup items.
5. Restart your computer and check if the BSODs persist.

Consider Rolling Back to Windows 10

If the BSODs continue after trying these steps, you could consider rolling back to Windows 10 temporarily while waiting for any potential updates or patches that address the issue. You can do this within 10 days of upgrading to Windows 11, through the Settings > Update & Security > Recovery menu.

I hope this helps.

Take care and have a good day.

Please click “Accepted Solution” if you feel my post solved your issue, it will help others find the solution. Click the “Kudos/Thumbs Up" on the bottom right to say “Thanks” for helping!

Alden4

HP Support 

[KisukeUrh]

Hello,

Thank you for your response. I tried but so far nothing has changed the situation.

I did opened the Event Viewer and got the following results. I have no idea what im looking for exactly so i wrote down all types of errors and warnings. I hope this helps.



Warning:

1 - (Source: DistributedCOM, Event ID 10016, Description: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.)

2 - (Source: DistributedCOM, Event ID 10016, Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user ***** SID (S-1-5-21-566201930-2015692601-2336879868-500) from address LocalHost (Using LRPC)  running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.)

2 - (Source: DistributedCOM, Event ID 10016, Description: Its the same like the 2nd but the names are:  CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D})

3 -  (Source: DNS Client Events, Event ID 1014, Description: Name resolution for the name t-ring-fdv2.msedge.net timed out after none of the configured DNS servers responded. Client PID 9564.)




Error: 

1 - (Source: volmgr, Event ID 46, Description: "Crash dump initialization failed!") 

2 - (Source: TPM-WMI, Event ID 1796, Description: "The Secure Boot update failed to update a Secure Boot variable with error The parameter is incorrect")

3 - (Source: DistributedCOM, Event ID 10010, Description: The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.)

Critical:
1 - (Source: Kernel-Power, Event ID 41)