Debugging a hanging system with no memory dump

Hi,

I'm having troubles with my Windows 10 laptop freezing when it comes out of sleep mode. I get the login screen and can move the mouse but I cannot click any buttons or type into the login box. The time also remains static and there are no entries for the time it was woken up in the event viewer.

To try and debug what might be causing it to hang I tried forcing a system crash using CTRL + SCR LK. This worked, but unfortunately Windows wasn't able to create a memory dump - it remained at 0% indefinitely. I tried forcing a system crash in a normal state to check it wasn't an issue with my setup e.g. the paging file being disabled, and can confirm it was able to create a memory dump fine in this scenario.

This means I'm am now stuck on what to try next. Does anyone have any suggestions?

Thanks, axe0. I ran memtest for 9 passes and it didn't detect any errors with the ram.

Due to this, I thought I'd try debugging it remotely. I brought my work laptop home with me and set up WinDbg so that I could break into it from my work laptop over the LAN. I thought I'd test the setup before debugging the actual problem and this worked perfectly.

Unfortunately my SSD didn't like being shut down incorrectly and I can no longer get Windows to boot (I get a lovely "No Bootable Device" error message). In the past when it's hung and I've had to cut power to the computer I've also seen this message, but usually it sorted itself out after 15 minutes (http://acer--uk.custhelp.com/app/ans...ystem%E2%80%9D).

However, in this case, it's been days and I am still unable to boot from it. I booted from my Windows 10 rescue disk and noticed I could access my files fine, so the next thing I did was take an entire disk clone using DD. I tried runing a dskchk on the disk a couple of times, but this didn't fix the issue. So I then tried running the System File Checker on it, but that also did not help. Lastly, I've tried using the Bootrec commands found on [FIX] Windows 10 Master Boot Record Is Corrupted. However, when I run the last one (to rebuild the BCD) it finds the Windows installation but gives me "The requested system device cannot be found" on adding it to the boot list. I tried Googling for this and found: bcdedit - Problem recreating BCD on Windows 7 64bit - The requested system device cannot be found - Super User, but none of these worked for me.

I'm going to try recreating the BCD manually following Fixing the Windows Bootloader via the setup DVD as the next step, and if that doesn't work I'm stummped.

I could probably just format the drive and reinstall everything, but that's nowhere near as interesting. I also noticed if I booted into Linux and tried to mount the disk I got an error about Windows cache data still being present, which I can no longer replicate so I assume something I've done has fixed this. The drive is also bitlockered so wasn't expecting to get far with that anyway.

OK, I'm back to cause trouble with my original problem. I've received my new SSD and I used DD to put the clone I took of the my old disk onto the new disk. As expected the problem with Windows hanging when resuming from sleep still persists. It also won't write a memory dump when I force a BSOD.

Something I noticed from having the boot issues was that the problem wasn't there when I was using my cloned disk on my spare HDD. Does this suggest that the issue is with it being able to write to the disk when it wakes up? I'm assuming it can read fine as I get my lock screen when I wake it up.