C:\Windows\System32\Logfiles\Srt\SrtTrail.txt ” error after Win 10 Auto repair


Joined
Aug 17, 2016
Messages
2
Reaction score
0
C:\Windows\System32\Logfiles\Srt\SrtTrail.txt” after Win 10 Auto repair

Hi Guys just installed Win 10 Pro 14393 build over Win 7 Pro on a older P6T Asus Mobo and I keep getting this error code saying it cannot repair after Automatic Win repair has finished ..The machine seems to work ok but after a day or 2 it might crash and I have to try to repair again and the same error comes up when running Win 10 Auto repair.. I have posted the srt .txt log files which were in the system32 folder . I would be really appreciative if somebody could point me in right direction to remedy this error please. I feel it could be a bad driver? I really dont know but I have tried everything chksk-DISM-Disable signature-Tweak Pro-ect ect

ASUS P6T
i7 960
Radeon 6900 HD
8GB

I would like to know if this is a fatal error or can I work with it if I have to ? because I dont want to do a clean install for many many reasons.

Thanks to all that reply

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎8/‎16/‎2016 11:10:08 PM (GMT)
Number of repair attempts: 1


Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\Windows
AutoChk Run = 0
Number of root causes = 1


Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms


Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms


Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms


Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code = 0x0
Time taken = 31 ms


Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code = 0x0
Time taken = 141 ms


Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code = 0x0
Time taken = 1078 ms


Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 47 ms


Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 0 ms


Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code = 0x0
Time taken = 78 ms


Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code = 0x0
Time taken = 16 ms


Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code = 0x0
Time taken = 15 ms


Root cause found:
---------------------------
Boot status indicates that the OS booted successfully.

Disc layout

Microsoft DiskPart version 10.0.14393.0


Copyright (C) 1999-2013 Microsoft Corporation.
On computer: MININT-GF0CCRJ


Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 1863 GB 0 B
Disk 1 Online 1863 GB 0 B


Disk 0 is now the selected disk.


WDC WD20EFRX-68EUZN0 ATA Device
Disk ID: EFA284A3
Type : ATA
Status : Online
Path : 0
Target : 1
LUN ID : 0
Location Path : ACPI(_SB_)#ACPI(PCI0)#ACPI(SATA)#ACPI(CHN0)#ATA(C00T01L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No


Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 1 C OFFICE AR W NTFS Partition 498 GB Healthy
Volume 2 E DATA AR OFF NTFS Partition 1363 GB Healthy
Volume 3 F NTFS Partition 450 MB Healthy Hidden


Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 G DVD-ROM 0 B No Media
Volume 1 C OFFICE AR W NTFS Partition 498 GB Healthy
Volume 2 E DATA AR OFF NTFS Partition 1363 GB Healthy
Volume 3 F NTFS Partition 450 MB Healthy Hidden
Volume 4 D OFFICE Sche NTFS Partition 1863 GB Healthy


Volume 1 is the selected volume.


Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
* Disk 0 Online 1863 GB 0 B


Read-only : No
Hidden : No
No Default Drive Letter: No
Shadow Copy : No
Offline : No
BitLocker Encrypted : No
Installable : Yes


Volume Capacity : 498 GB
Volume Free Space : 392 GB


Disk 0 is now the selected disk.


WDC WD20EFRX-68EUZN0 ATA Device
Disk ID: EFA284A3
Type : ATA
Status : Online
Path : 0
Target : 1
LUN ID : 0
Location Path : ACPI(_SB_)#ACPI(PCI0)#ACPI(SATA)#ACPI(CHN0)#ATA(C00T01L00)
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No


Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 1 C OFFICE AR W NTFS Partition 498 GB Healthy
Volume 2 E DATA AR OFF NTFS Partition 1363 GB Healthy
Volume 3 F NTFS Partition 450 MB Healthy Hidden


Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 Primary 498 GB 1024 KB
Partition 2 Recovery 450 MB 498 GB
Partition 3 Primary 1363 GB 499 GB


Partition 1 is now the selected partition.


Partition 1
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 1048576


Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 1 C OFFICE AR W NTFS Partition 498 GB Healthy


Window Booot Manager

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
resumeobject {fd55df8f-621f-11e6-8d7f-806e6f6e6963}
displayorder {a9eedcc3-62b6-11e6-a711-f29c7f7cf818}
{a9eedcc4-62b6-11e6-a711-f29c7f7cf818}
timeout 30


Windows Boot Loader
-------------------
identifier {a9eedcc3-62b6-11e6-a711-f29c7f7cf818}
device partition=C:
path \Windows\system32\winload.exe
description Windows 10 Pro
locale en-US
recoverysequence {current}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {fd55df8f-621f-11e6-8d7f-806e6f6e6963}
bootmenupolicy Standard


Windows Boot Loader
-------------------
identifier {a9eedcc4-62b6-11e6-a711-f29c7f7cf818}
device partition=C:
path \Windows.old\WINDOWS\system32\winload.exe
description Windows 10 Pro
locale en-US
osdevice partition=C:
systemroot \Windows.old\WINDOWS
bootmenupolicy Standard


Windows Boot Loader
-------------------
identifier {current}
device ramdisk=[F:]\Recovery\WindowsRE\Winre.wim,{a9eedcc6-62b6-11e6-a711-f29c7f7cf818}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[F:]\Recovery\WindowsRE\Winre.wim,{a9eedcc6-62b6-11e6-a711-f29c7f7cf818}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes


Resume from Hibernate
---------------------
identifier {fd55df8f-621f-11e6-8d7f-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 10 Pro
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No


Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US


Device options
--------------
identifier {a9eedcc6-62b6-11e6-a711-f29c7f7cf818}
description Windows Recovery
ramdisksdidevice partition=F:
ramdisksdipath \Recovery\WindowsRE\boot.sdi
 

Regedit32

Moderator
Joined
Mar 4, 2016
Messages
2,937
Reaction score
910
Hi cistec,

Welcome to the forum.

Your log does not appear to display any particular issue.

Windows 10 however is rather obsessed with Signed Drivers, so your guess that a driver may be the issue is probably correct.

One thing you could try is the built in Advanced Startup where you could try a couple of minor things to see whether this resolves your issue.
  • Warning! The following steps will forcefully close any open applications so save any files your need to save and close applications before proceeding with steps below.
  • Left-click on Start
  • Left-click on Settings icon
  • Left-click on Update & security
  • In the left pane click on Recovery
  • Now in the main window below Advanced Startup click Restart now button
  • Your computer will shutdown and restart and after a moment will boot to the Choose an option screen. On this screen click Troubleshoot
  • This opens the Troubleshoot screen. Here click on Advanced Options
  • This opens the Advanced Options screen. Here click on Startup Settings
  • This opens the Startup Settings screen. Here click on the Restart button.
  • Your computer will restart and display a numerical list of options. On your numeric pad press 7, or if you prefer press the function key F7. This will select the option 7. Disable driver signature enforcement and then your computer will boot to the normal lock screen / login page.

    That may resolve your issue for you.

    If it doesn't then one driver you may need to address is your Display driver. While your log does not appear to point to this as an issue; one way of testing whether it is the cause of the error would be to repeat the above steps and either press on your numeric pad 3 or press the function key F3 to select the option 3. Enable low-resolution video. If that resolves the issue then the next thing to do is go to manufacturer website and update your graphics card, or graphics chipset drivers.

Regards,

Regedit32
 
Ad

Advertisements

Joined
Aug 17, 2016
Messages
2
Reaction score
0
Hi Regedit32

Thank you so much for your quick advice I will try and let you know ...unfortunatley the problem is intermittent and occurs when you least expect it and I have tried to replicate the error but murphy's law say it will only happen when you dont want it to. But I will let you know as soon as it happens. Also I have checked to see if I have the correct video driver and it says I have, but I cannot be sure it is the video card..it feels like it is or my memory ram sticks..just a gut feeling nothing technical.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top