New
#11
Run verifier /querysettings from an Administrator Command Prompt. If inactive, output will look like this:
Code:>verifier /querysettings Verifier Flags: 0x00000000 Standard Flags: [ ] 0x00000001 Special pool. [ ] 0x00000002 Force IRQL checking. [ ] 0x00000008 Pool tracking. [ ] 0x00000010 I/O verification. [ ] 0x00000020 Deadlock detection. [ ] 0x00000080 DMA checking. [ ] 0x00000100 Security checks. [ ] 0x00000800 Miscellaneous checks. [ ] 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 Verified Drivers: None
iastora.sys is an INTEL rapid storage technology driver. Try to update these drivers from the Intel download page - they have an online driver update tool.
I did not quite understand the crash sequence but I had assumed the driver iastora.sys showed up when running the driver verifier. This is the reason I said to update it. It certainly fits with a critical structure type crash involving the storage system.
Here you go: https://downloadcenter.intel.com/