Windows 10: BSOD srttrail.txt, no fix, installed W10 on different SSD, how to fix it on original SSD?

Hey guys,


Two days ago I encountered BSOD srttrail.txt. I tried to fix it in many different ways, tried everything described here:


https://www.auslogics.com/en/articles/fix-srttrail-txt-bsod-error-win10/


no luck. I tried to repair system from bootable pendrive with W10, didn't work neither, it said that it needed to be done from the operating system level.


Finally I plugged new, empty SSD and installed new copy of W10 there. So at this point I have C: with new W10 instalation, that I can access and D: with broken W10 installation causing BSOD srttrail.txt.


Is there any way to fix W10 instalation on D: from operation system being booted from C:? All W10 options that I can see refer to the copy installed on C:.


I'd really like to fix somehow installation from D: without loosing data, programs, apps etc. I know that the last resort is to format D: and make a clean instalation there, but I'd prefer to avoid this.


Thanks for your time!

:)

 

Is my SSD killing Windows? [UPDATE: fixed]

Ok, looks like I nailed it: the SATA cable or it's connection at the mobo end, suspect a poor contact. My PC is working sweet now and I'm posting this from Edge on a brand new digital entitlement activated W10 install on my SSD before customising anything. *Smile Here's how the troubleshooting went down, for the techies here.

The SSD worked fine on my old rig with a solid 23 hours uptime, no glitches whatsoever.

The main rig also worked fine on the HDD the whole time. Note that it was connected to a different SATA port, however. It would have been better to run it off the suspect port with the suspect cable, but never mind, I didn't think of it.

I reconnected the SSD to the original SATA port using the original cable. This is port 1, a Marvell 6Gbp/s port, not an Intel port, which can only manage 3Gbp/s.

I began installing W10 again on the SSD and the installer locked up at the 8% preparing files point. Note that the capslock/numlock keys and mouse pointer continued to work, but there was nothing else happening. Reset the PC and tried again, this time bombed out with an AHCI driver error again. Nice, this is what I want to see for a fault confirmation. Definitely a problem with this port or cable.

Changed the cable and all was well - W10 installed fine. Used the suspect cable on an Intel port with my WD 640GB Black HDD and W10 installed fine. Twice. Reconnected the suspect cable to the original Marvell SATA port and the SSD and again it installed fine, twice. Note that I connected the cable the same way round, too. Therefore, it looks like the connection with the mobo port perhaps wasn't too good even though the cable was fully connected. I had seen all these problems over time despite me having already changed the cable once before. I've therefore changed the cable out and put the suspect one in my old rig to see if the fault transfers. Perhaps the port is faulty after all, but only very slightly which is why it's working now.

So far, it looks like I've fixed the problems. If they come back over time, I'll try the second Marvell port, as I don't want to lose half my SSDs performance by using the slower ones. If this is also bad, then I can only conclude that the Marvell controller is bad.
Thanks for all your help and suggestions people, much appreciated. *Toast :toast:

EDIT 20.11.15

Besides the cable which definitely looks suspect and has been replaced, it appears that the Marvell 6G port is also iffy as I still got some bsods, but that's much harder to say absolutely. Since I moved to the Intel 6G port a few days ago, these bsods appear to have stopped, although it hasn't been long enough to say conclusively yet. There's more troubleshooting details in further posts here from me and other members.

 

SSD install

Thank you Ugo.

I finally fixed my problem by switching the sata connections on the motherboard. My old/original hard drive was plugged into sata port #1 and new SSD was plugged into sata port #2. I switched them out and the went into bios and changed around boot order
to boot off of new SSD and now everything is fine. System is showing SSD as master and old HDD as slave drive. Everything is now in order and computer loads blazingly fast.

Thank you for your help and suggestions!

greg

 

Z Book BSOD with Second SSD Drive

Hi all

I have an issue with an HP Z Book. It is a new Generation 6 device and came with a pre-installed second SSD drive.

All worked fine until I tried to put our corporate image onto the primary OS SSD.

Firstly, the new OS installed onto the secondary SSD rather than the primary.

So I disconnected/removed the secondary, recreated the partition on the primary and loaded our stock OS.

The machine now works absolutely fine, as long as I do not try to re-introduce the second SSD drive.

If I reinstall this, the machine boots up OK for a second or two and then BSOD's.

Can anyone suggest the reason for this issue - the BSOD message reported a kernel error.

Any ideas on steps to take to resolve this?

Thanks

Phil