So, my laptop is sick
About a month ago, my laptop BSODed and rebooted to BIOS after I unplugged it from its charger. It wouldn't boot for a while, but after I got home that day, it didn't have any problems, so I didn't think much of it. Then, two weeks ago, the same thing happened again, which made me think it might be something I'd need to look into. Last week, it started happening consistently, and started only booting to BIOS or a BSOD. The first time that the problem started happening consistently, one of my programs gave a low RAM error right before the BSOD, which came with the error of unexpected store exception. The PC rebooted, then BSODed with error critical process died. Then it booted to bios. When I got it to boot to not BIOS, it booted to chkdsk. It rebooted to another critical process died BSOD, then to BIOS.
A bit later, I was able to get the system to boot to Windows, at which point I ran chkdsk from the booted system. It came back saying that the volume was in use and wouldn't run. I restarted the computer, and it then put itself into a boottime chkdsk boot loop.Eventually it booted to automatic repair, after which I was able to get to an RE command prompt. I got there, then tried running chkdsk again, where it found no problems. Someone suggested I try running chkdsk with the /r and /f flags, which gave the error "Cannot open volume for direct access". Then it returned again to booting only to BIOS.
Someone then suggested that I try removing hibrfile.sys, if it existed, from a Linux USB. So, I did, but that didn't fix the problem. The PC rebooted to automatic repair after that, and its repairs failed. It provided a log file, srttrail.txt: https://www.pastebin.com/VKumDrA2 . While I was booted to the Linux OS, I made a backup of my drive. During the backup, the OS told me that there was one bad sector on the drive but that it was otherwise fine.
After seeing the srttrail.txt text, a Discord user sent me this link (https://superuser.com/questions/1286232/windows-10-unable-to-boot-failure-to-repair-loop-refer-to-srttrail-txt-inside), but none of the solutions provided there worked on my issue. I then tried running DISM from the RE which returned "An error occurred closing a servicing component in the image", and the log file said a bunch of stuff about failing to load providers and such. The first thing that was actually logged as an error was on trying to get the OS version. SFC scans returned that the requested operation could not be performed.
At this point, since I now had a backup of all my data, I decided to try reinstalling Windows. So, I did, and it worked! Well, it worked for a day, at least. I reinstalled in the morning, started getting my data copied onto the new system, and, that evening, the BSODs and BIOS booting started again.
I tried a reinstall once more the day after, but decided to install hardly anything at all, and see if the problem still persisted. So I installed only programs that I'd normally put on my Ninite installer, then didn't use the computer until that evening. The system not having crashed all day, I used the web browser for a bit, but soon after, the problem returned once more.
And now we have gotten to the present time, at which I am sitting, staring at a BIOS screen. I have tried running the Sysnative tool, but am unable to get the system to boot for long enough. I will see if I can get a crash dump off of the system from a Linux USB. I will also see what I can do about running the hard drive and memory diagnostics, but I don't think these are faulty, as I think they would have caused errors in creating backups of my files, but I was able to use the backups just fine when I reinstalled Windows the first time. But I will run the diagnostics nonetheless.
As I cannot run Speccy, here's the information about my laptop that I know:
· System Manufacturer: Asus
· Exact model number (if laptop, check the label on bottom): Q553U
· OS - Windows 10, 8.1, 8, 7, or Vista? Windows 10. I don't know what version of it, though
· x86 (32-bit) or x64 (64-bit)? 64-bit
· What was original installed OS on system? Win10
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Uhh not really sure. Win10 came preactivated but I have since then reinstalled.
· Age of the computer (hardware): 2 years
· Age of OS installation - and whether you have re-installed the OS: When the problem started, it was around 6 months on that installation. Each reinstall since then lasted about 12 hours before problems started.
· Laptop or Desktop computer? Laptop
· CPU: i7-6500U
· Video Card: NVIDIA 940M
Anyway, sorry for this extremely long post. Thanks in advance for your help!
Edited by sasschary, 02 August 2018 - 06:07 PM.