So here's what's up. I came home at the end of last weekend to the wonderful sight of my Asus gaming laptop running Windows 8.1 having BSOD'd. Fun stuff. Haven't had much time to fix it till today. The following are its symptoms:
Windows immediately BSOD's on Boot (after the Asus logo, no Windows logo occurs) with the note "System Service Exception". It then auto-restarts, BSOD's once more then attempts to "repair" and "Diagnose", landing me on a prompt to try a windows restore point (which I have exhausted) before giving me advanced options.
Thankfully, I am able to boot into Safemode with Networking. Huzzah.
*NOTES* I noted that windows wanted me to do/allow some automatic update before the weekend. I told it to wait. It must have automatically prompted for it again and restarted while I was away. Checking my recent updates shows that no windows update has happened since august, though I did find that Windows Defender updated most recently.
The bugcheck was: 0x0000003b (0x00000000c0000005, 0x0000000000000000, 0xffffd0003ea8c7a0, 0x0000000000000000).
Most recent Minidumps here:
I've also followed the posting instructions, ran the DM Log Collector and attached the zip folder to this post.
Things I have done:
Ran Malwarebytes Anti-malware, came up Clean
Ran CCleaner, Nothing of note was found
Ran Control Pannel>Troubleshooting>System and Security> Fix Windows update. I am informed that "Windows update components must be repaired" and that "One or more Windows Update components are configured incorrectly."
*At this point I learned about the windows defender update. I have since disabled windows defender for the time being.*
Ran Admin CMD, "Chkdsk /scan" found some unindexed files.
Ran "Chkdsk /F" to fix those, restarted to run it on C, ran to 100% completion, No change. Running chkdsk again produces the same results as original scan.
Ran Admin CMD, "sfc /scannow"
There were some "corrupt files" that were unable to be fixed
Then at microsoft's customer service's request, ran "dism /online /cleanup-image /restorehealth" which completed successfully.
Ran "sfc /scannow" again, still finds "corrupt files" but was unable to fix them
Ran a Windows Memory Diagnostic, came up clear.
I have pretty much exhausted my knowledge of fixing things. Not really sure how to analyze memory dumps. Further google searching of the bugcheck type makes me think this might be a driver issue? No idea if that's true. No idea how to find which/what driver is doing this, if that's the case.
One really strange thing to note:
Before I tried booting up safemode originally, I entered the cmd via windows advanced options. I wanted to first check that all my files still existed on my PC and it wasn't a hard drive failure. haha. Paranoid, I know.
When I ran "DIR" on each drive I noticed something strange. Checking my C drive produced stuff that was normally on a different partition, namely F:. Checking my other drives, i found that the normal contents of my C: drive (all the windows OS files) were showing up on E:
Like something switched the drive letters.
strangely enough, when I boot to Safemode, there is no evidence of this. Running "DIR" oin my drive letters in cmd while in safemode produces my normal file directories, all as they should be.
Thought it strange, seemed interesting to report.
Anyway, any help with this would be very much appreciated. I'm home all day today so I'll be checking in periodically.
Thanks so much!
Tim's Channel - YouTube