I coded up a little app (with help from the good folks at StackOverflow) to dump out the status of the drive. It shows the one and only virtual drive - C: - is powered-up the whole time. So it's not some kind of virtual power-down state.
// DrivePowerStateCheck.cpp : Defines the entry point for the console application.
//
#include "stdafx.h"
int _tmain(int argc, _TCHAR* argv[])
{
for (int DriveNumber = 0; DriveNumber < 128; ++DriveNumber) {
TCHAR Drive[128];
_stprintf(Drive, _T("\\\\.\\PHYSICALDRIVE%d"), DriveNumber);
HANDLE hDevice = CreateFile(Drive, 0, FILE_SHARE_READ | FILE_SHARE_WRITE, 0, OPEN_EXISTING, 0, 0);
if (hDevice != INVALID_HANDLE_VALUE) {
BOOL DeviceIsOn = FALSE;
if (GetDevicePowerState(hDevice, &DeviceIsOn) != 0) {
_tprintf(_T("Physical Drive %d is Powered %s (DeviceIsOn=%d)\n"), DriveNumber, DeviceIsOn ? _T("On") : _T("Off"), (int) DeviceIsOn);
}
CloseHandle(hDevice);
}
}
return 0;
}
I guess I can go through resurrecting a virgin installation, and add all my tweaks and augments in methodically, all the while testing for the recurrence of this problem (assuming it doesn't happen in the virgin Win 10 setup).
Would capturing another sequence of logs help you?
-Noel
|
