|Hello - I'm starting to hate this month, as it's been a rough one on this computer. :( I'm trying to figure out what caused today's error so I can prevent it happening again.|
Earlier today, I decided to plug in my external hard drive. (Which didn't have Autoplay run when I plugged it in yesterday or today, not sure why.) When I checked Process Explorer to see if I could remove it, it said that explorer.exe was still using a folder I had closed an hour ago.
I had had luck one other time logging off and logging back on to get explorer to let go, so that is what I did. It seemed to take a long time on the wallpaper before it logged off, but it's hard to tell, as I have no reason usually to log off. It did successfully log off and logged back on.
After I logged back on, I opened Process Explorer to see if all was clear and I could remove the external drive. It seemed to be scanning for a long time, so I canceled the scan - and it didn't cancel. I closed the program, and the scan window stayed open. I closed the window, and the end program dialogue box came up. As soon as I clicked 'end now', my computer blue screened and restarted.
I've been trying to find out what happened - I did find this error message in my event viewer, and it's all I could find so far: "The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x80568d36, 0xafeba8ec, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini121712-01.dmp."
I have run an sfc /scannow, and the event viewer said it completed successfully. I have not yet tried re-opening Process Explorer - I generally only use it to see why I can't safely remove usb drives.
I know that a %systemroot%\system32\dumprep 0 -k has been added to my startups. I did google it to see that it's an error reporting service by Windows.
Is there anything else I should try, or should I just assume I tried to run Process Explorer too soon after logging on?