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

Page 2 of 4 FirstFirst 1234 LastLast
  1.    #11

    philc43 said: View Post
    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??
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 7,701
    Windows 10 Pro X64 1809 17763.437
       #12

    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 ComputersSystem Spec

  3.    #13

    Ztruker said: View Post
    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
      My ComputerSystem Spec

  4.    #14

    philc43 said: View Post
    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
      My ComputerSystem Spec

  5.    #15

    Ztruker said: View Post
    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
    BSOD PROBLEM, error code 0x00000109 (normal use/gaming) Attached Files
      My ComputerSystem Spec

  6. philc43's Avatar
    Posts : 4,033
    64bit Win 10 Pro ver 1809 Build 17763.437 and W10 Insider Build 18362 and 18865
       #16

    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.
      My ComputersSystem Spec

  7.    #17

    philc43 said: View Post
    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
      My ComputerSystem Spec

  8. philc43's Avatar
    Posts : 4,033
    64bit Win 10 Pro ver 1809 Build 17763.437 and W10 Insider Build 18362 and 18865
       #18

    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.
      My ComputersSystem Spec

  9.    #19

    philc43 said: View Post
    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??
      My ComputerSystem Spec

  10. philc43's Avatar
    Posts : 4,033
    64bit Win 10 Pro ver 1809 Build 17763.437 and W10 Insider Build 18362 and 18865
       #20
      My ComputersSystem Spec


 
Page 2 of 4 FirstFirst 1234 LastLast

Related Threads
BSOD error 0x00000109 in BSOD Crashes and Debugging
Hello my pc keeps having bsod cant figure out why heres the error code : BSOD (randomly) error 0x00000109
Random BSOD 0x00000109 Lenovo m91f in BSOD Crashes and Debugging
I bought a refurbished lenovo PC on newegg that looked like a great deal. It had been updated to Windows 10 Pro so for $180 it sounded like a great deal. It immediately started crashing randomly. I really don't want to send it back just yet. ...
Hi, For the past couple of weeks I have been having unexpected shut downs while playing games. In particular, my computer seems to shut down most frequently when I am playing Overwatch and then tab out to launch Chrome. It has also crashed while...
Solved BSOD while in Firefox, error code 0x00000109 in BSOD Crashes and Debugging
Hey, Had a BSOD this morning, first one since I upgraded to Windows 10 many months ago. My CPU has been running at 4,2 ghz ever since. I did try 4,4 ghz yesterday evening, but I reversed it almost immediately following a 2 minute torture test in...
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 10:58.
Find Us