[SOLVED] Win11 in boot loop: BSOD exception_thread_not_handled, tbtbusdrv.sys

pejar

Member
Joined
Mar 25, 2024
Posts
5
Hi,

So, my new laptop all of sudden wanted to go boot loop over night, with normal shutdown.
I can't enter os winRE, since it says "trying to automaic repairs" second later i got BSOD with details:

exception_thread_not_handled sometimes no extra info, sometimes origin: tbtbusdrv.sys

What I've tried: is to contact asus support, so from there i performed bios EC RESET.
and microsoft support only AI responded so that was a hour waisted, also its damn slow to repond.

I would love to know if it's a hardware issue or software issue. Since there is still warranty left for my laptop.
But for now i just would wish to get the machine to work.

Correct me if i'm wrong: The install media commandprompt doesn't automatically mount my drives ?
so doing manually SFC and/or DISM only targets for the usb install media, right ?

Also repair boot says error, disable latest update says error, recovery install says error - you must run this from os drive.
Nothing works, and i really really really wish not to perform clean install.

I'm miserable situation: nothing works and seems just a faculty driver cripples the whole system in state that is not recoverable.

Please help,
Petri
 
Try downloading the Windows 11 iso here. Use the media creation tool to create a bootable USB. Boot from the USB and try an in place upgrade choosing to keep personal files and programs.
 
The tbtbusdrv.sys driver is a Thunderbolt driver - do you have anything plugged in to the Thunderbolt USB port? Remove it if you do.

Without any system specs it's really hard to give sensible advice. It sounds as though you have data on drives in there that may not be backed up? Get a SATA or M.2 (or both?) caddy similar to M.2 caddy, SATA caddy. These will allow you to plug you drives into another PC/laptop and copy all the essential data off. With you data backed up you can then replace the drives and be a bit more aggressive with your troubleshooting.

To answer the questions you asked...
The install media command prompt doesn't automatically mount my drives ?
It depends on whether specific drivers are needed for the NVMe drives. SATA/ACHI drives are mounted automatically.

Doing manually SFC and/or DISM only targets for the usb install media, right ?
Yes.
 
Okay... after a long time figuring out... so, it had nothing to do with thunderbolt drivers after all. old starforce was the cause of the issue.
So first things first: intall media couldn't access the nvme, so i needed to install the drivers to the install media.
After that I was able to access the C drive. I removed some updates and ran system restore point. without no help.
I tried offline sfc /scannow, but it obviously didn't find anything, no luck.

Next thing I tried to remove starforce drivers:
system32\drivers\sfsync03.sys
system32\drivers\sfhlp02.sys
system32\drivers\sfdrv01.sys

After that I booted, and voila: no need to install system again everything works like a charm.
After 4 days I finally figured it out. Thanks for help.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top