4 ms·
I have an "impossible" debugging situation right now, though it's a little outside the scope I think. My Windows C drive, an SSD, died unexpectedly after less
by mrguyorama 5y ago
I have an "impossible" debugging situation right now, though it's a little outside the scope I think.
My Windows C drive, an SSD, died unexpectedly after less than a year of operation (I literally checked the SMART stats the day before, for what little info they offer). I bought a new Samsung SSD, installed it, restored from a backup (which was harder than it should have been backblaze) and now I get random bluescreens. No issue, I've had BSODs before, I know how to use WinDbg to explore them.
Problem 1; BSOD claims it is an "unrecoverable hardware error"
Problem 2; No dump file is generated, and I have no idea why. My system is set to generate one, I've turned off autorestart, Windows claims the SSD volume is "healthy" after restart, but it does not write the file
My only hope is that I'll figure out how to set up remote debugging or something
- wizzwizz4 5y agoI had an impossible debugging situation. One day, my Windows 10 machine decided that it would get a NTFS_FILE_SYSTEM error on boot. A BSOD on boot means it'll try the recovery partition… which caused a FAT_FILE_SYSTEM error just after the first conhost.exe window appeared. After “recovering”, it'd try to boot normally again – looping between two slightly different OSs, getting basically the same error over and over. Eventually, I gave up on debugging, and tried to re-install. I put in the recovery disk… and it FAT_FILE_SYSTEM BSOD'd, too. When booting off a completely different device, with which there were definitely no file system errors. So I put Debian on the machine. No problems, for some reason.
- breakingcups 5y agoAt the risk of going further off-topic, what issue did you experience with Backblaze? I rely on them for my backup too (yes, 3-2-1 rule, etc.)