BKoolReturns Posted June 6, 2015 ID:967664 Share Posted June 6, 2015 Hello all, After installing some bluetooth drivers this morning and updating windows via windows update, my ASUS G73 will not boot in any mode (Normal, safe mode, last known good configuration, etc.) I ran windows Self Repair with the following results:Problem Event Name: StartupRepairOfflineProblem Signature 01: 6.1.7600.16385Problem Signature 02: 6.1.7600.16385Problem Signature 03: unknownProblem Signature 04: 21200830Problem Signature 05: ManualRepairProblem Signature 06: 2Problem Signature 07: BadDriverOS Version: 6.1.7600.2.0.0.256.1Locale ID: 1033 I ran FRST64 on the system and have attached the log file. I'm requesting a fixlist so I can boot and run malwarebytes if needed! Any assistance would be greatly appreciated.FRST.txt Link to post Share on other sites More sharing options...
TwinHeadedEagle Posted June 7, 2015 ID:967824 Share Posted June 7, 2015 Hello, What exactly happens when you try to boot? Link to post Share on other sites More sharing options...
BKoolReturns Posted June 7, 2015 Author ID:967825 Share Posted June 7, 2015 When I boot the system, I get the ASUS splash screen, following my the list of drivers loading prior to Windows log in. However, the system just hangs on the driver load screen every time now. Link to post Share on other sites More sharing options...
TwinHeadedEagle Posted June 7, 2015 ID:967826 Share Posted June 7, 2015 You can boot to recovery, right? Link to post Share on other sites More sharing options...
BKoolReturns Posted June 7, 2015 Author ID:967827 Share Posted June 7, 2015 I can boot to repair tools, yes. But windows startup repair fixes nothing with the results as previously shown. Further, command prompt is virtually unusable in repair tools for sfc/scannow or chkdsk because it believes a repair is active. Lastly, I've had no luck booting from a recovery CD as I think that drive is dead. Link to post Share on other sites More sharing options...
TwinHeadedEagle Posted June 7, 2015 ID:967828 Share Posted June 7, 2015 Download attached fixlist.txt and save it to your USB flashdrive as fixlist.txt >> Boot into Recovery Environment Start FRST in a similar manner to when you ran a scan earlier, but this time when it opens .... Press the Fix button once and wait. FRST will process fixlist.txt When finished, it will produce a log fixlog.txt on your USB flashdrive.>> Exit out of Recovery Environment and post me the log please. Try to boot Windows normally...fixlist.txt Link to post Share on other sites More sharing options...
BKoolReturns Posted June 7, 2015 Author ID:967829 Share Posted June 7, 2015 Ran the fixlist, fix log attached. Normal boot still hung on "Loading Windows Files" screen.Fixlog.txt Link to post Share on other sites More sharing options...
TwinHeadedEagle Posted June 7, 2015 ID:967830 Share Posted June 7, 2015 I've made one mistake. Let's try again: Download attached fixlist.txt and save it to your USB flashdrive as fixlist.txt >> Boot into Recovery Environment Start FRST in a similar manner to when you ran a scan earlier, but this time when it opens .... Press the Fix button once and wait. FRST will process fixlist.txt When finished, it will produce a log fixlog.txt on your USB flashdrive.>> Exit out of Recovery Environment and post me the log please. Try to boot Windows normally...fixlist.txt Link to post Share on other sites More sharing options...
BKoolReturns Posted June 7, 2015 Author ID:967834 Share Posted June 7, 2015 Here you go. Looks like it failed again.Fixlog.txt Link to post Share on other sites More sharing options...
BKoolReturns Posted June 7, 2015 Author ID:967841 Share Posted June 7, 2015 Ok! Progress. I was able to complete src/scannow after I deleted a pending.xml from X:. 100% complete, Windows Resource Protection did not find any integrity violations. Link to post Share on other sites More sharing options...
TwinHeadedEagle Posted June 7, 2015 ID:967844 Share Posted June 7, 2015 Okay, now let's try with Chkdsk Download attached fixlist.txt and save it to your USB flashdrive as fixlist.txt >> Boot into Recovery Environment Start FRST in a similar manner to when you ran a scan earlier, but this time when it opens .... Press the Fix button once and wait. FRST will process fixlist.txt When finished, it will produce a log fixlog.txt on your USB flashdrive.>> Exit out of Recovery Environment and post me the log please. Try to boot Windows normally...fixlist.txt Link to post Share on other sites More sharing options...
Root Admin AdvancedSetup Posted June 11, 2015 Root Admin ID:968653 Share Posted June 11, 2015 Due to the lack of feedback this topic is closed to prevent others from posting here. If you need this topic reopened, please send a Private Message to any one of the moderating team members. Please include a link to this thread with your request. This applies only to the originator of this thread. Other members who need assistance please start your own topic in a new thread. Thanks! Link to post Share on other sites More sharing options...
Recommended Posts