New
#1
Windows thinks it's installed on a different drive. Cause of BSOD?
Edit: My last post on this thread contains all the most recent information regarding the current state of my machine and Windows 10 installation.
Random hangs (not BSOD) once every 1~3 days while gaming.
Thought it related to OC so decided to incrementally lower the clock and voltage.
Tested stability with aida64 and it hung mid-test with a BSOD). That BSOD rendered Windows completely unstable.
After that I got random BSODs (Unexpected Kernel Mode Trap, among others - they seemed different each time), and other strange behavior (namely USB drive folder opening and closing automatically).
I installed Sandra HW monitoring app before testing stability.
Using a restore point BSOD frequency decreased a bit, but it'd still happen seemingly randomly (once within 6 minutes of simple usage like opening folders).
Trying to run sfc /scannow, dos reported the command as not recognized. I used this tutorial to to run sfc scannow in dos boot and it still reported corrupt files...)
Current State:
I chose to reset the PC and to keep personal files.
PC seems stable now but sfc /scannow is still reporting corrupt files (I ran it with nothing other than malwarebytes running).
Note: After resetting, I only installed MBAM (pro) and Firefox. Windows automatically installed an AMD driver (I think).
I'd like to know if the BSODs I was experiencing is the cause of scannow not working.
According to the CBS log msdelta and amd64_microsoft-windows-deltacompressionengine are errant.
List of all the devices I've connected to the PC at some point.
-logitech webcam (almost always connected but never used)
-wacom bamboo tablet (almost always disconnected)
-fostex headphone amplifier (always connected often used)
-steam controller (always connected not often used)
Any help would be extremely appreciated!
(I'll gladly post this in a different section if someone could tell me which is appropriate.)
Last edited by HansW; 21 May 2016 at 02:31. Reason: removal of unneeded info