Windows 10 SRT.Trail.txt BSOD. Please help me.

I turned my laptop on today, and out of no where it will BSOD during boot and restart in to recovery mode rinse and repeat.

my windows was absolutely perfect before this.

Ive tried command prompt in recovery options

Chkdsk C: , fixboot, ive tried everything.

I’ve gone through several other fixboot steps on YouTube and such related to SRT.TRAIL.TXT

Nothing will work or fix this.

what should I do???

 

Probably a botched up Windows Update causing it. If you were on 1903 and it decided to move you to 1909 that might have triggered it. I've never had any luck fixing that error. Haven't seen it for a really long time... maybe like 2016 or so. The last time I did I had to restore using Macrium image. I tried every suggestion I could find online as you have and nothing worked. If you do not have a drive image you might be looking at a clean OS install.

As a last resort, have you already tried running these commands, in the order listed, from an admin command prompt?

sfc /scannow

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

 

this was caused after the latest update.

I’ll try it out though. If it doesn’t work, it is time for a complete wipe and reinstall.

 

Sorry it happened, bro. Sucks that it did. At least the clean install is not difficult... just an inconvenient time-wasting exercise. But, still better than having to pay money for replacing parts and/or labor.

 

reinstalling windows is no big deal for me. I had some performance concerns with the current windows anyways. And I’m certainly OCD about optimal performance, the current windows would show abnormally high cpu usuage in even the simplest task.

And during gameplay I was seeing GPU usage fall down from 99% even when my FPS was well below the 144hz refresh rate in certain title which I thought was odd. And shouldn’t happen. CPU was running cool at 5Ghz, and GPU was running around 82C.


This current windows had a different language pack installed. It also took some effort to get the CPU and GPU to downclock properly. So I dunno what was going on with this windows previously.


I could right click + left click really really fast on the desktop and ramp CPU usage to 60-70% lol.

Which is just wrong lol.

sounds crazy lol, and due to having slow internet. I was trying to avoid reinstall. Re-downloading over 400GB in games.

 

Well, if it makes you feel any better, the same thing happened to me this morning. I allowed my MECH-15 to download the latest update feces last night and when I turned it on for work this morning I ended up getting the same SRT.Trail.txt BSOD. It already had 1909 before that. System Restore failed. Farted around with a couple more things to try and fix it. No dice. Ain't nobody got time for that. Said screw it and restored my Macrium Reflect image for 1903. Back in the saddle again.
@Papusan @Vasudev

 

I don’t have the time for M$ flaws. And I have no desire to upgrade the OS. New is not always better. Only more chance for new unwanted bugs (one fixed means only one or two new bugs will be added). People has to stop thinking new is always better. Not the way it works!

 

I never got 1903/1909 to install on my PC and v1809 is the only one which worked for me.

 

I don't have the time or desire for it either. That's why I use the Macrium sledgehammer. I don't rely on it and don't recommend that anyone else do so. Operating in a multi-boot environment creates a no-strings attached relationship with the disease for me and affords the freedom of tinkering with a crash test dummy installation. Windows 10 is a severely flawed, inferior and unreliable product no matter what version is installed. It is a reflection of the incompetence of its software engineers.

My only basis for having 1909 installed is to play Gears 5 and to speak with greater authority when I am critical of rubbish. If I haven't touched the feces it doesn't carry as much weight with those who are predisposed to be Kool-Aid drinkers. If I have their poop splattered on my shoes and have been exposed to the filth, nobody can make a logical argument that I am unreasonably biased or just anti-Windows 10. (I am biased, but with a solid basis for it. I have their poop splattered on my shoes, for Pete's sake.)

 

In-place upgrade from 1809 to 1909 worked but not clean install. It seems that old fixed bugs from 1607 W10 has come up when multiple disks are Online. I used to install Win 10 v1803+ by offlining the disks now its buggy on 1903/1909. AW BGA BIOS now doesn't detect my drives at all. Damn!!! Even after restore from MR it looks like I need to open it up again!

 

That's too bad. Sorry to hear that.

Whenever possible, I do a clean install with all drives removed/disconnected. I clean installed 1909 on a spare NVMe on my desktop. So far it seems OK. The MECH-15 developed this BSOD problem about 4 or 5 days after doing the in-place upgrade from 1903.