PC has been blue screening after enabling TPM 2.0

Kirk Pickford 0 Reputation points

My PC recently had issues loading valorant, every other game loaded fine but valorant would freeze upon trying to load into multiplayer game, I attempted to update to windows 11 so I enabled TPM 2.0 in the bios since then the PC has been doing the BSOD spontaneously even after disabling TPM 2.0, then after one of them windows 10 corrupted so I tried to repair but issue still occured, I tried to do a fresh install even formatting C drive and reinstalling from scratch from windows media creation tool on USB but issue still occurs then tried to update to windows 11 the same way but the issue is still occuring. I attempted SFC scannow but get this screen: User's image

I then tried DISM Scanhealth command and it stated about some parts that need repairing so I tried both the normal restorehealth command and the one for \source to try and run it through the windows 11 ISO I have downloaded but the issue still occurs:

User's image

User's image

I even went through DISK PART commands and attrib -h -r -s commands upon a previous BSOD Issue as well and nothing seems to of worked dism log file attached.dism.log

A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
5,040 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
8,880 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Wesley Li 6,360 Reputation points


    To analyzing the bsod issue, the dump (C:\Windows\memory.dmp or C:\Windows\minidump) may be useful.

    To open a dump file, here is a link for reference. Pay attention to configure the symbol file path.

    WinDBG - The Basics for Debugging Crash Dumps in Windows 10 | Tutorials (tenforums.com)

    It seems present system has got corrupted. I noticed you have tried to run dism to fix it. The dism log will not include the exact eror files. We need to check C:\Windows\Logs\CBS\CBS.log for the exact error message.

    To fix the corrupted files with the log analysis may be complicated. We may consider to perform an in-place upgrade repair with the installation media.

    0 comments No comments