0

MY PC AND WHAT I WAS TRYING TO DO

I wanted to update from win 10 to win 11, and I read that, to do it, I had to enable tpm 2.0. The pc is a custom build and I have a meg z590 ace motherboard. Windows 10 is installed on an SSD.

PROBLEMS

So I open the bios and enable tpm 2.0. After enabling it, windows crashes after like 10 seconds I log in my user profile: I get blue screens error “WHEA_UNCORRECTABLE_ERROR” or the “WATCHDOG_CLOCK_TIMEOUT” one.

I tried to reset the BIOS to factory settings, but I keep getting the errors.

The only option that seems to solve this is to “ripristinate windows”, but by doing that I loose all applications installed, and I prefer to avoid it.

QUESTION 1

Is there a way to fix this? Windows should technically be still win 10 since I wasn’t able to update it because of the problem.

  • Note: I’m not very familiar with custom builds and a friend of mine helped me and installed for me windows 10 on the USB key.
Improve this question
10
  • Try updating the BIOS and any other drivers you can (Power Driver should be updated). It is something in your machine (I have not been able to pinpoint), but TPM V2 works fine without crashing on my own machines.
    – anon
    Commented Jan 19, 2023 at 14:34
  • 1
    "Windows 10 is installed on an USB key." - Are you positive that would suggest you are running a Windows to Go installation, which can't be upgraded, I have my doubts the problem is connected to enabling fTPM from within the firmware because if it was caused by that action disabling it would resolve the problem.
    – Ramhound
    Commented Jan 19, 2023 at 14:48
  • We can't really help unless you provide the Bugcheck Analysis which is generated by Windbg.exe. Of course I understand that is difficult without a machine that can run that tool.
    – Ramhound
    Commented Jan 19, 2023 at 14:58
  • 1
    @Ramhound ah ok, so if I understood correctly, you think that the problems are not really related to enabling tpm 2.0 itself, but to enabling it on a windows to go installation? Anyway, I’ll update the question and the comments as soon as I know if it really is a windows to go installation or not
    – selenio34
    Commented Jan 19, 2023 at 15:23
  • 1
    these errors are usually hardware related, especially cpu overclock and memory. If your bios has an "auto cpu boost" or other overclock setting, try turning it off or less aggressive. If you have discreet GPU, try disabling the CPU-integrated graphics. etc.
    – Yorik
    Commented Jan 19, 2023 at 21:32

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .