Page 2 of 4 FirstFirst 1234 LastLast
  1.    11 Sep 2017 #11
    Join Date : Oct 2016
    Posts : 327
    seL4

    If you upload another memory.dmp you may wish to compress it first, to save yourself some time.
      My ComputerSystem Spec
  2.    11 Sep 2017 #12
    Join Date : Sep 2017
    Posts : 24
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    OK. Odd - this dmp must be from before I activated verifier - verifier /querysettings returned driver results, so it should have been active. I'll see if I can trigger another BSOD and see if the dmp file updates.

    Is there anything useful in there even without driver verifier entries? I wasn't asked to activate that originally, so I don't want to side-track if it isn't needed

    BTW - I truly appreciate the help!
      My ComputerSystem Spec
  3.    11 Sep 2017 #13
    Join Date : Nov 2015
    Posts : 2,868
    64bit Win 10 Pro ver 1709 Build 16299.64

    Looked to see if any of your device nodes were having pnp or power problems:

    The webcam was picked up as being disabled and your SCSI Virtual Clone Drive had an error:

    Code:
    ********************************************************************************
    Dumping devnodes with problems...
    ********************************************************************************
    
    Dumping IopRootDeviceNode (= 0xffffd88b7cf35d30)
    DevNode 0xffffd88b7f92d010 for PDO 0xffffd88b7f925060
      InstancePath is "USB\VID_046D&PID_0809&MI_00\7&4e7b938&0&0000"
      ServiceName is "LVUVC64"
      State = DeviceNodeInitialized (0x302)
      Previous State = DeviceNodeUninitialized (0x301)
      Problem = CM_PROB_DISABLED
      Problem Status = 0x00000000
    DevNode 0xffffd88b7d1fdd30 for PDO 0xffffd88b7d1fd060
      InstancePath is "ROOT\SCSIADAPTER\0000"
      ServiceName is "VClone"
      State = DeviceNodeStartPostWork (0x307)
      Previous State = DeviceNodeStartCompletion (0x306)
      Problem = CM_PROB_INVALID_DATA
      Problem Status = 0xc0040038
    Could the V Clone be involved - what do you do with this?
      My ComputersSystem Spec
  4.    11 Sep 2017 #14
    Join Date : Sep 2017
    Posts : 24
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Quote Originally Posted by philc43 View Post
    Looked to see if any of your device nodes were having pnp or power problems:
    The webcam was picked up as being disabled and your SCSI Virtual Clone Drive had an error:
    ...Could the V Clone be involved - what do you do with this?
    The webcam is disabled as its the last driver I updated - so I disabled as part of troubleshooting.

    Virtual CloneDrive was installed for a project several years back - you can mount iso images virtually. I haven't used it in over a year (actively), and I tried disabling the virtual drive after I grabbed the .dmp - no difference.

    EDIT - also this happens in safe mode, and VCD is not loaded when booting into safe mode, so it shouldn't be involved.
    Last edited by dtolman; 11 Sep 2017 at 10:53. Reason: clarification
      My ComputerSystem Spec
  5.    11 Sep 2017 #15
    Join Date : Jan 2017
    Karlsruhe
    Posts : 733
    Windows 10 Pro

    Thousands of errors in windows eventlog regarding disk, disk controller, file system etc...

    Code:
    2017-07-09 22:21:24  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-07-09 22:21:24  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume12'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-07-10 03:11:35  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-10 03:32:23  Warning: The IO operation at logical block address 0xb4938 for Disk 2 (PDO name: \Device\0000004d) was retried.   
    2017-07-10 03:35:03  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 03:37:43  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 03:45:03  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 03:47:03  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 03:51:43  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 03:57:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:02:29  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:04:29  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:09:09  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:09:49  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:14:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:21:15  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:26:37  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:31:59  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:36:41  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:42:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:47:32  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:52:57  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 04:58:21  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:03:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:08:29  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:13:52  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:19:16  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:24:01  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:29:27  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:34:51  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:40:13  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:44:57  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:50:19  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 05:55:44  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:01:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:05:52  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:11:14  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:16:39  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:22:01  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:26:43  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:31:25  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:36:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:42:10  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:47:32  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:52:14  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:57:38  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 06:58:18  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:07:43  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:08:23  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:11:43  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:17:03  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:21:43  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:27:06  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:33:12  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:39:19  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:44:00  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:49:22  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:54:46  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 07:59:27  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 08:04:49  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 08:10:12  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 08:15:34  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 08:20:17  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:19:53  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:20:06  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-10 17:20:33  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:26:37  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:32:02  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:34:05  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:34:45  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:38:45  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:40:05  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:41:25  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:42:05  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:47:30  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:52:58  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 17:54:58  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:01:00  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:06:23  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:12:27  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:18:35  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:24:00  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:29:22  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:34:06  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:39:26  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:44:47  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:50:08  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 18:54:50  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:00:10  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:05:32  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:10:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:15:37  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:20:58  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:26:21  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:31:02  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:36:22  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:41:47  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:47:10  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:51:53  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 19:57:18  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:02:42  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:08:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:12:52  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:18:13  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:23:35  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:29:00  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:33:41  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:39:06  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:44:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:49:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:54:33  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 20:59:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:05:17  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:10:37  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:15:21  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:20:45  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:26:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:30:50  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:36:12  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:41:34  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:46:56  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:47:36  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:52:56  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 21:59:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:05:11  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:09:56  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:15:21  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:20:43  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:25:25  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:30:47  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:36:12  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:41:34  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:46:17  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:51:42  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 22:57:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 23:02:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 23:04:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 23:07:11  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 23:11:51  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 23:17:57  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 23:24:01  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 23:30:11  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-10 23:36:11  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 06:54:44  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-11 06:59:16  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:04:41  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:10:06  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:15:30  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:16:10  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:16:50  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:19:30  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:24:50  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:30:57  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:37:06  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:42:29  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:48:32  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:53:55  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 07:58:35  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:04:01  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:09:25  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:14:46  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:19:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:21:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:26:51  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:28:51  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:34:15  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:40:20  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 08:45:40  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:21:01  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:21:26  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-11 20:26:07  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:31:27  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:36:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:38:08  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:38:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:42:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:44:08  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:45:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:46:08  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:46:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:51:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:52:08  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:52:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:53:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 20:54:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:00:08  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:00:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:18:08  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:24:11  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:30:56  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:35:36  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:40:56  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:46:16  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:51:37  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 21:56:21  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:01:41  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:07:02  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:12:22  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:13:03  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:18:23  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:19:03  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:21:03  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:21:43  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:26:23  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:32:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:37:51  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:43:12  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:47:52  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:53:14  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 22:58:36  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:03:57  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:08:39  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:14:00  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:19:23  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:24:47  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:29:30  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:34:52  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:40:14  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:45:07  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-11 23:47:48  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:52:33  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-11 23:57:58  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-12 00:03:20  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-12 00:08:03  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-12 00:13:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-12 00:18:52  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-12 00:32:12  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: F:, DeviceName: \Device\HarddiskVolume5. ({Drive Not Ready}   
    2017-07-12 04:16:46  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-12 17:46:22  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-13 06:57:07  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-13 16:20:51  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-13 20:14:58  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-14 06:57:52  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-14 11:13:11  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-14 16:57:09  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-15 07:13:06  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-15 21:33:03  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-15 23:19:53  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-16 08:13:17  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-17 06:57:28  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-17 07:21:07  Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit.   
    2017-07-17 19:43:42  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-18 06:51:34  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-18 19:59:03  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-19 06:57:19  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-19 17:14:31  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-19 23:40:20  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-21 06:57:18  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-22 06:39:36  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-22 19:05:33  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-23 07:31:45  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-24 06:57:38  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-24 17:01:15  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-25 06:57:31  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-25 16:09:46  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-25 18:48:46  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-26 06:57:14  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-26 16:50:09  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-26 23:20:04  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-27 06:56:48  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-27 16:29:47  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-27 20:28:08  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-28 06:58:03  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-28 16:22:29  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-29 08:19:42  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-29 23:03:25  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-30 07:43:41  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-30 07:53:36  Warning: The IO operation at logical block address 0x1609db93 for Disk 4 (PDO name: \Device\000000c3) was retried.   
    2017-07-30 07:53:46  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume7. (A device which does not exist was specified.)   
    2017-07-30 19:17:30  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume14'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-07-30 19:17:30  Warning: An error was detected on device \Device\Harddisk3\DR8 during a paging operation.   
    2017-07-30 19:17:30  Warning: An error was detected on device \Device\Harddisk3\DR8 during a paging operation.   
    2017-07-30 20:58:25  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume16'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-07-30 20:58:25  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume16'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-07-30 22:36:09  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-31 06:56:53  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-07-31 08:04:16  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:04:19  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:04:29  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:04:46  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:04:50  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:11:36  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:11:39  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:11:49  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:22:42  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:22:45  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:22:48  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:26:28  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:26:34  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:26:45  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:27:20  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:27:24  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 08:27:27  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-07-31 16:03:03  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-01 06:56:47  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-01 07:54:16  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 07:54:21  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 07:54:26  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 07:54:30  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 07:54:39  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 07:54:44  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 07:54:48  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 07:54:51  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 07:54:55  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:11:17  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:11:21  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:11:40  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:11:53  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:11:56  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:12:00  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:12:04  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:12:07  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:12:10  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 09:16:15  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:09:33  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:09:38  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:09:46  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:09:50  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:09:55  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:10:02  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:10:06  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:10:09  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:10:14  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:19:02  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:19:07  Error: The device, \Device\Harddisk3\DR13, has a bad block.   
    2017-08-01 22:19:29  Warning: The IO operation at logical block address 0x16016e47 for Disk 3 (PDO name: \Device\000000e8) was retried.   
    2017-08-01 22:19:39  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume23. (A device which does not exist was specified.)   
    2017-08-02 06:56:36  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-02 07:57:32  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 07:57:37  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 07:57:46  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 07:57:50  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 07:57:55  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 07:58:00  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 07:58:04  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 07:58:07  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 07:58:11  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:00:37  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:00:39  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:00:42  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:00:48  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:00:50  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:00:54  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:00:57  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:01:00  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:01:03  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:02:34  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:02:45  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:02:52  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:04:10  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:04:18  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:05:12  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:05:16  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:05:19  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:05:25  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:05:28  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:05:31  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:05:37  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:06:24  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:06:28  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:06:31  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:07:07  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:07:10  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:07:13  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:07:17  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:07:20  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:19  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:22  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:31  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:34  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:38  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:42  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:46  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:50  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:53  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:56  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:10:59  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:02  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:05  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:09  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:12  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:17  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:24  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:27  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:30  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:33  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:36  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:39  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:42  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:46  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 08:11:49  Error: The device, \Device\Harddisk3\DR17, has a bad block.   
    2017-08-02 14:58:53  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-02 15:01:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume27. (A device which does not exist was specified.)   
    2017-08-02 15:01:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume27. (A device which does not exist was specified.)   
    2017-08-02 15:01:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume27. (A device which does not exist was specified.)   
    2017-08-02 15:01:31  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume27. (An operation was attempted to a volume after it was dismounted.)   
    2017-08-02 16:04:44  Warning: The IO operation at logical block address 0xc006c for Disk 2 (PDO name: \Device\0000005e) was retried.   
    2017-08-02 17:00:57  Warning: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.   
    2017-08-02 17:01:27  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-03 06:57:02  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-03 16:38:34  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-04 06:57:54  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-04 08:31:41  Warning: An error was detected on device \Device\Harddisk4\DR4 during a paging operation.   
    2017-08-05 07:17:27  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-05 09:07:25  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-05 23:15:13  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-06 08:30:59  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-06 10:32:43  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-06 17:47:55  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-06 19:07:47  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume16'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-06 19:07:47  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume16'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-06 19:19:48  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume18'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-06 19:19:48  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume18'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-07 06:56:43  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-07 07:27:59  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:28:02  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:28:16  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:28:42  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:28:45  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:28:55  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:28:58  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:29:14  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:41:58  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:42:49  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:42:52  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:42:57  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:43:11  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:43:54  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:43:57  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:00  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:17  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:24  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:36  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:39  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:42  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:47  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:50  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:54  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:44:59  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:02  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:05  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:15  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:17  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:22  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:31  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:34  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:37  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:49  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:45:52  Error: The device, \Device\Harddisk2\DR7, has a bad block.   
    2017-08-07 07:46:13  Warning: The IO operation at logical block address 0x18e44539 for Disk 2 (PDO name: \Device\000000c5) was retried.   
    2017-08-07 07:46:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)   
    2017-08-07 07:46:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)   
    2017-08-07 07:46:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)   
    2017-08-07 07:46:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)   
    2017-08-07 07:46:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)   
    2017-08-07 07:46:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)   
    2017-08-07 07:46:54  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)   
    2017-08-07 19:29:14  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-08 07:04:51  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-08 12:25:19  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-08 16:47:10  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-09 06:06:28  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-10 01:20:33  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-10 12:05:54  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-10 15:20:17  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-11 06:57:38  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-11 06:58:11  Warning: The IO operation at logical block address 0x1992c7ab for Disk 2 (PDO name: \Device\000000a7) was retried.   
    2017-08-11 16:56:27  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-11 17:40:30  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-12 07:40:32  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-12 12:09:33  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-13 07:40:26  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-13 10:37:01  Warning: An error was detected on device \Device\Harddisk3\DR11 during a paging operation.   
    2017-08-13 10:37:13  Warning: An error was detected on device \Device\Harddisk3\DR11 during a paging operation.   
    2017-08-13 10:37:13  Warning: An error was detected on device \Device\Harddisk3\DR11 during a paging operation.   
    2017-08-13 10:37:20  Warning: An error was detected on device \Device\Harddisk3\DR11 during a paging operation.   
    2017-08-13 10:37:33  Warning: An error was detected on device \Device\Harddisk3\DR11 during a paging operation.   
    2017-08-13 10:38:02  Warning: An error was detected on device \Device\Harddisk3\DR11 during a paging operation.   
    2017-08-13 10:38:03  Warning: An error was detected on device \Device\Harddisk3\DR11 during a paging operation.   
    2017-08-13 19:26:24  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume25'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-13 19:26:24  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume25'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-13 19:47:24  Warning: The IO operation at logical block address 0x40028 for Disk 5 (PDO name: \Device\000000df) was retried.   
    2017-08-13 22:46:21  Warning: The IO operation at logical block address 0x6cd69bf for Disk 2 (PDO name: \Device\000000c0) was retried.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume12. (A device which does not exist was specified.)   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume12. (A device which does not exist was specified.)   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume12. (A device which does not exist was specified.)   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume12. (A device which does not exist was specified.)   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume12. (A device which does not exist was specified.)   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume12. (A device which does not exist was specified.)   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume12. (A device which does not exist was specified.)   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: An error was detected on device \Device\Harddisk2\DR9 during a paging operation.   
    2017-08-14 00:57:28  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume12. (A device which does not exist was specified.)   
    2017-08-14 00:57:49  Error: The driver detected a controller error on \Device\Harddisk4\DR4.   
    2017-08-14 00:57:57  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-14 00:58:29  Warning: The IO operation at logical block address 0x1bc0b80f for Disk 2 (PDO name: \Device\000000e8) was retried.   
    2017-08-14 01:10:24  Warning: The IO operation at logical block address 0x1e9bff83 for Disk 2 (PDO name: \Device\000000e8) was retried.   
    2017-08-14 01:11:31  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:11:35  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:11:38  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:11:50  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:11:53  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:11:55  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:12:04  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:12:07  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:12:11  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:12:19  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:12:22  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:12:25  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:12:52  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:12:54  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:01  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:09  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:12  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:17  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:24  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:27  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:30  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:34  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:37  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:40  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:45  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:47  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:50  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:53  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:13:56  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:04  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:08  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:10  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:13  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:17  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:20  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:23  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:26  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:30  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:33  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:38  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:44  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:47  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:50  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:53  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:56  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:14:58  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:15:01  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:15:04  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:16:33  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:16:38  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 01:16:41  Error: The device, \Device\Harddisk2\DR21, has a bad block.   
    2017-08-14 17:38:01  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-14 17:49:07  Warning: The IO operation at logical block address 0xb3d67 for Disk 2 (PDO name: \Device\000000e8) was retried.   
    2017-08-14 22:40:35  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-15 06:57:09  Warning: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.   
    2017-08-15 06:57:09  Warning: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.   
    2017-08-15 06:57:09  Warning: An error was detected on device \Device\Harddisk2\DR2 during a paging operation.   
    2017-08-15 06:57:38  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-15 08:27:52  Error: The device, \Device\Harddisk2\DR4, has a bad block.   
    2017-08-15 08:27:55  Error: The device, \Device\Harddisk2\DR4, has a bad block.   
    2017-08-15 16:59:38  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-15 22:07:39  Error: The device, \Device\Harddisk2\DR4, has a bad block.   
    2017-08-15 22:07:42  Error: The device, \Device\Harddisk2\DR4, has a bad block.   
    2017-08-16 06:19:52  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-23 20:19:19  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 20:19:24  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 20:19:29  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 20:32:10  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume14'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-23 20:32:10  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume14'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-23 20:41:05  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 20:42:04  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 20:42:08  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:03  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:06  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:10  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:31  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:34  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:37  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:41  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:43  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:47  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:50  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:53  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:23:56  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:05  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:08  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:14  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:18  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:21  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:25  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:32  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:35  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:38  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:42  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:45  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:48  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:51  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:54  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:24:58  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:02  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:05  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:07  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:11  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:15  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:18  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:21  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:25  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:38  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:42  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:45  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:48  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:51  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-23 22:25:54  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-24 06:56:46  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-24 17:06:42  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-25 06:57:04  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-25 16:53:49  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-25 18:56:35  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-25 23:58:53  Error: The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit.   
    2017-08-26 08:09:29  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-26 12:41:19  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-27 08:05:54  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-27 19:14:10  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume28'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-27 19:14:10  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume28'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-27 19:50:17  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-27 20:11:45  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume30'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-27 20:11:45  Error: Filter Manager failed to attach to volume '\Device\HarddiskVolume30'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.   
    2017-08-28 06:57:13  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-28 17:04:35  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-28 19:17:52  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:18:17  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:18:20  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:18:23  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:20:19  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:20:45  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:20:48  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:20:51  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:21:24  Error: The device, \Device\Harddisk2\DR2, has a bad block.   
    2017-08-28 19:21:44  Warning: The IO operation at logical block address 0x1601155f for Disk 2 (PDO name: \Device\0000004d) was retried.   
    2017-08-28 19:21:55  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume5. (A device which does not exist was specified.)   
    2017-08-28 19:21:55  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume5. (A device which does not exist was specified.)   
    2017-08-28 19:21:55  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume5. (A device which does not exist was specified.)   
    2017-08-28 19:21:55  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume5. (A device which does not exist was specified.)   
    2017-08-28 19:21:55  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume5. (A device which does not exist was specified.)   
    2017-08-28 19:21:55  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume5. (A device which does not exist was specified.)   
    2017-08-28 19:21:55  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume5. (An operation was attempted to a volume after it was dismounted.)   
    2017-08-28 23:19:32  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-29 18:07:39  Warning: The IO operation at logical block address 0xb32ab for Disk 3 (PDO name: \Device\00000070) was retried.   
    2017-08-29 18:07:40  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
    2017-08-29 18:07:40  Warning: An error was detected on device \Device\Harddisk3\DR3 during a paging operation.   
    2017-08-29 18:07:40  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume6. (A device which does not exist was specified.)   
    2017-08-29 18:07:40  Warning: The system failed to flush data to the transaction log. Corruption may occur in VolumeId: I:, DeviceName: \Device\HarddiskVolume6. (A device which does not exist was specified.)   
    2017-08-30 06:57:10  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-30 17:34:39  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-31 06:58:30  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-31 08:37:08  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-08-31 17:43:28  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-09-01 06:57:16  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-09-01 08:09:04  Warning: Reset to device, \Device\RaidPort1, was issued.   
    2017-09-02 08:07:45  Warning: The file system structure on volume C: has now been repaired.   
    2017-09-02 08:07:50  Warning: The file system structure on volume C: has now been repaired.

    This is from msconfig:

    Code:
    Name    Virtual CloneDrive
    Manufacturer    Elaborate Bytes AG
    Status    Error
    PNP Device ID    ROOT\SCSIADAPTER\0000
    Driver    c:\windows\system32\drivers\vclone.sys (5.4.7.0, 36.00 KB (36,864 bytes), 7/24/2013 11:02 AM)
      My ComputerSystem Spec
  6.    11 Sep 2017 #16
    Join Date : Sep 2017
    Posts : 24
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Quote Originally Posted by BSODHunter View Post
    Thousands of errors in windows eventlog regarding disk, disk controller, ...
    A lot of that is from USB attached disks (anything above drive E is a USB disk), which aren't normally attached.
      My ComputerSystem Spec
  7.    11 Sep 2017 #17
    Join Date : Jan 2017
    Karlsruhe
    Posts : 733
    Windows 10 Pro

    Code:
    Name	Virtual CloneDrive
    Manufacturer	Elaborate Bytes AG
    Status	Error
    PNP Device ID	ROOT\SCSIADAPTER\0000
    Driver	c:\windows\system32\drivers\vclone.sys (5.4.7.0, 36.00 KB (36,864 bytes), 7/24/2013 11:02 AM)
      My ComputerSystem Spec
  8.    11 Sep 2017 #18
    Join Date : Sep 2017
    Posts : 24
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Quote Originally Posted by BSODHunter View Post
    Code:
    Name    Virtual CloneDrive
    Manufacturer    Elaborate Bytes AG
    Status    Error
    PNP Device ID    ROOT\SCSIADAPTER\0000
    Driver    c:\windows\system32\drivers\vclone.sys (5.4.7.0, 36.00 KB (36,864 bytes), 7/24/2013 11:02 AM)
    Yeah - I'm going to try uninstalling to be sure in case it isn't playing well with the latest Win10 updates - but this shouldn't be loaded in Safe Mode (when it is still Blue Screening) so I don't _think_ its a likely source.
      My ComputerSystem Spec
  9.    11 Sep 2017 #19
    Join Date : Sep 2017
    Posts : 24
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    Confirmed verifier is on- hopefully next dump will have more. Seems last few crashes did not result in a new dump file

    verifier /querysettings


    Verifier Flags: 0x000209bb


    Standard Flags:


    [X] 0x00000001 Special pool.
    [X] 0x00000002 Force IRQL checking.
    [X] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [X] 0x00000020 Deadlock detection.
    [X] 0x00000080 DMA checking.
    [X] 0x00000100 Security checks.
    [X] 0x00000800 Miscellaneous checks.
    [X] 0x00020000 DDI compliance checking.


    Additional Flags:


    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.


    [X] Indicates flag is enabled.


    Boot Mode:


    Persistent


    Rules:


    All rules are using default settings


    Extensions:


    wdm: rules.default


    Verified Drivers:


    All Drivers
      My ComputerSystem Spec
  10.    11 Sep 2017 #20
    Join Date : Sep 2017
    Posts : 24
    Microsoft Windows 10 Pro 64-bit 15063 Multiprocessor Free
    Thread Starter

    I just had another BSOD - and no dump was created. No minidump either (none this weekend in fact, despite several).
    Could this be because of the driver verifier?

    I uninstalled virtual clone drive... so if it happens again, that is ruled out.
      My ComputerSystem Spec

 
Page 2 of 4 FirstFirst 1234 LastLast


Similar Threads
Thread Forum
BSOD in safe mode Build 16215
Hi all, I updated my two computers to build 16215, but both encounter BSOD when trying to enter safe mode. The screen says mssecflt.sys is the problem. But sfc /scannow says no integrity problems found. How should I enter safe mode? I...
Windows Insider
Solved BSOD Can't boot to safe mode or desktop
Hi all, I put my PC into sleep mode before heading out last night and upon my return I was presented with a BSOD. So I'm not actually sure if it went into sleep mode. I'm kinda at a loss as in to what is causing my bsod. It happens after the...
BSOD Crashes and Debugging
Solved BSOD Critical_Process_Died (After booting into Safe Mode)
This might not be the place to post this issue, but I'm not sure where else to put it. I'm having a problem with my computer that displays the "It looks like Windows didn't load correctly" error-thing when I try to boot it up. I already tried...
BSOD Crashes and Debugging
BSOD - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED on boot, even safe mode.
Hi, I'm getting a BSOD with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED every time I try to boot. I even get this BSOD when trying to get into safe mode. There's no sys file specified. OS is Windows 10 Pro x64 (10.0.10586) 56647 I can get to it the...
BSOD Crashes and Debugging
BSOD - when trying to resume from sleep mode - CRITICAL_PROCESS_DIED
While running a fresh install of Windows 10, when the computer tries to resume from sleep mode, it always crashes and the BSOD says "Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:45.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums