BSOD PROBLEM, error code 0x00000109 (normal use/gaming)

philc43 said:

Basically the crash analysis is showing that your system is experiencing repeated "Critical Structure Corruption" in the kernel region which is not tolerated by the operating system and in order to protect your system from potential damage to the files or hardware the system shuts down with the bugcheck. The analysis does not reveal which driver is causing it but the evidence suggests it is most likely a driver rather than hardware failure. ntoskrnl is not the problem - this is a Microsoft file and not the cause, the WhoCrashed simply can't find anything else to blame.

The next step is therefore to run Driver Verifier, as the tutorials I linked to will explain, this tests the non-Microsoft drivers and attempts to identify any drivers that do not work as expected. This can help you to track down the ones that need updating.

how do i know if driver verifier is running??

Ztruker said:

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

ok thank you

philc43 said:

Basically the crash analysis is showing that your system is experiencing repeated "Critical Structure Corruption" in the kernel region which is not tolerated by the operating system and in order to protect your system from potential damage to the files or hardware the system shuts down with the bugcheck. The analysis does not reveal which driver is causing it but the evidence suggests it is most likely a driver rather than hardware failure. ntoskrnl is not the problem - this is a Microsoft file and not the cause, the WhoCrashed simply can't find anything else to blame.

The next step is therefore to run Driver Verifier, as the tutorials I linked to will explain, this tests the non-Microsoft drivers and attempts to identify any drivers that do not work as expected. This can help you to track down the ones that need updating.

My pc just crached will driver verifier is running but didn't want to restart because of this driver '' iastora.sys'' so i disabled driver verifier by command prompt and restated the pc but the dump file is the same as the other ones

Ztruker said:

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

My pc just crached will driver verifier is running but didn't want to restart because of this driver '' iastora.sys'' so i disabled driver verifier by command prompt and restated the pc but the dump file is the same as the other ones

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.

philc43 said:

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.

and this will fix the problem? Because when my pc crashed the error message was : CRITICAL STRUCTURE CORRUPTION

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.

philc43 said:

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.

Can you send me the link of this tool??

Here you go: https://downloadcenter.intel.com/