GUI does not indicate corrupt/missing save file in an obvious way

[kc0tfb]

I have a windows 8.1 x64 host running 4.3.24 which cannot start a Windows 7 Enterprise x64 guest with saved state after rebooting the host OS. Something appears to have removed or corrupted the save-state file, but the GUI does not indicate this in an obvious way (it does appear in the log, however).

More desirable behavior would be a "Save file is missing or corrupt. Restart VM?" dialog. Instead, I get this, which is also symptomatic of a large number of other (more complex) failures:

Failed to open a session for the virtual machine CDW Win7.
The VM session was closed before any attempt to power it on.
Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {12f4dcdb-12b2-4ec1-b7cd-ddd9f6c5bf4d}

The Log:

VirtualBox VM 4.3.24 r98716 win.amd64 (Mar  2 2015 14:18:45) release log
00:00:03.174146 Log opened 2015-03-16T13:53:05.920532400Z
00:00:03.174149 Build Type: release
00:00:03.174155 OS Product: Windows 8.1
00:00:03.174157 OS Release: 6.3.9600
00:00:03.174158 OS Service Pack: 
00:00:03.258341 DMI Product Name: 20246
00:00:03.262022 DMI Product Version: Lenovo IdeaPad Yoga 11S
00:00:03.262030 Host RAM: 8071MB total, 5351MB available
00:00:03.262033 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:03.262034 Process ID: 4556
00:00:03.262035 Package type: WINDOWS_64BITS_GENERIC
00:00:03.262679 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={VM cannot start because the saved state file 'C:\Users\P\VirtualBox VMs\CDW Win7\Snapshots\2015-03-14T16-48-25-963707000Z.sav' is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting the VM}, preserve=false
00:00:03.263825 UIMediumEnumerator: Medium-enumeration finished!
00:00:03.264472 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 0 as 640x480
00:00:03.268691 UIMachineView::storeGuestSizeHint: Storing guest size-hint for screen 1 as 640x480

[kc0tfb]

Worth mentioning, perhaps: The save state file is 0 bytes. Not sure why that is, but I've already overwritten too many logs to track that one down.