New
#31
That's the thing; this problem is random and inconsistent. Sometimes the system won't have a BSOD until many hours or even a few days later; my initial instance hasn't had a BSOD now in four days. So how can I know whether installing the second instance determined or eliminated a cause? I would need to stay in the second instance (potentially) for days to see whether it has a BSOD.
Here's something interesting in the initial instance: While reviewing the System log for Criticals, Errors, and Warnings, I notice the following error since the last BSOD (I also see these prior to the BSOD):
Source: volsnapThis error has occurred 37 times over the last 96 hours, referencing the C:, D:, and M: volumes.
Event ID: 8
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description: The flush and hold writes operation on volume C: timed out while waiting for a release writes command.
I also see two instances of this error:
Source: NtfsI see similar errors three weeks ago, naming a different ShadowCopy. Any thoughts?
Event ID: 55
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Description: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShadowCopy14.
While I wait for your reply, I will boot back into the new instance and then watch for BSODs; I will also review the System log to see if these errors occur there.