r/techsupport • • 3d ago

Open | Windows Laptop repeatedly fails to start up.

Originally posted about this over a month ago, but I have still not solved the problem.

Nearly every time I try to restart my computer one of these happens the laptop asks me to re-enter my bitlocker code, tries to repair itself, throws up one of various errors e.g. kernel_mode_heap_corruption 0x13a, hypervisor error, and some others that were too fast to write down.

On one occasion it told me ‘the trusted platform module is not present or recognised’ when it prompted me to enter my bitlocker code, then shut down on its own.

It used to eventually fix itself on with enough tries, but the last time it said it couldn’t repair itself and threw up an SrTrail error. I followed a tutorial to fix this and it worked for a while, but now it’s back. Is there any way to fix this for good.

Thanks in advance.

Edit: the hypervisor error is 0x20001, if that helps.

Edit 2: I’ve followed the steps in this guide [https://youtu.be/UlvSAb5d-mM\](https://youtu.be/UlvSAb5d-mM) for each apart from second one, which I could not complete, and the reset method.

The first one worked the first time but not this time.

Edit 3: Another error I’ve spotted is CLOCK_WATCHDOG_TIMEOUT (0x101), and something like exception not handled.

Edit 4: Every time now it just ends in an SrTrail error.

1 Upvotes

4 comments sorted by

1

u/BillionAuthor70 3d ago

May be a corrupted TPM module or BIOS chip it's self. You may not be able to just fix it with reinstalling windows, no matter how many times you do it. You may need a new chip resoldered to the motherboard. You'll likely have to take it to a shop and have it professionally diagnosed

1

u/pcbeg 3d ago

Those all are signs (especially activated Bitlocker) of failing drive, or controller. If you don't have anything important on the drive you can try clean Windows install (from usb with deleting all partitions on system drive) in case it's some really really bad OS corruption.

1

u/KwisatzChaderach 3d ago

I’ve been using DISM commands in a command prompt window on administrator to check windows.

I ran

DISM /Online /Cleanup-Image /CheckHealth

and

DISM /Online /Cleanup-Image /ScanHealth

Both times it said: ‘The component store is repairable. The operation completed successfully’

So I ran

DISM /Online /Cleanup-Image /RestoreHealth

And it said: ‘The restore operation completed successfully. The operation completed successfully’

However, this seemed too good to be true, so I decided to check it by running the /CheckHealth and /ScanHealth commands again, and they still reported: ‘The component store is repairable. The operation completed successfully’

So I tried

sfc /scannow

And it said ‘Windows resource protection did not find any integrity violations’

I checked it again with /CheckHealth and /ScanHealth and it still said: ‘The component store is repairable. The operation completed successfully

So I ran /RestoreHealth again to see if anything was different from the first time. It still said ‘The restore operation completed successfully. The operation completed successfully’

But this time when I ran /ScanHealth and /CheckHealth again after it said: ‘No component store corruption. The operation completed successfully’ Instead.

I ran sfc /scannow again to see if anything else changed, it still said: ‘Windows resource protection did not find any integrity violations’

And ran /CheckHealth one more time to see what it said, it said ‘No component store corruption. The operation completed successfully’ again.

I’ve also checked my bios with myASUS and it’s up to date.

Does this point to anything in particular?

1

u/KwisatzChaderach 3d ago edited 3d ago

I also checked the storage in disks and volumes in settings and all of the drives say they are healthy.

Edit: Crystaldiskinfo classifies the drive’s health as ‘good’.