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

Page 1 of 4 123 ... LastLast

  1. Posts : 20
    windows 10
       #1

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


    Can any one help me?


    this the beta log collector zip file:
      My Computer


  2. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #2

    Hello fvsgvsgv,

    Welcome to TenForums!

    Please explain the history of the PC. Did you add any memory recently? Has this just started happening on the 9th March?
      My Computers


  3. Posts : 20
    windows 10
    Thread Starter
       #3

    philc43 said:
    Hello fvsgvsgv,

    Welcome to TenForums!

    Please explain the history of the PC. Did you add any memory recently? Has this just started happening on the 9th March?
    The PC was working fine with windows 7 and when upgraded to windows 10 using windows media creation tool the problem started, after one week i reinstalled windows 10 but it didn't fix anything.

    I didn't add any memory
      My Computer


  4. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #4

    Please can you fill in as many details as possible about you system in the My Computer area of your profile.

    The history tends to suggest the BSOD is most likely driver related. The crash dump does not show any drivers that might have caused it. I would like to see a few more crash dump files if you can post new log files after each crash over the next day or so.
      My Computers


  5. Posts : 20
    windows 10
    Thread Starter
       #5

    philc43 said:
    Please can you fill in as many details as possible about you system in the My Computer area of your profile.

    The history tends to suggest the BSOD is most likely driver related. The crash dump does not show any drivers that might have caused it. I would like to see a few more crash dump files if you can post new log files after each crash over the next day or so.
    Ok i will
    Thank you
      My Computer


  6. Posts : 20
    windows 10
    Thread Starter
       #6

    philc43 said:
    Please can you fill in as many details as possible about you system in the My Computer area of your profile.

    The history tends to suggest the BSOD is most likely driver related. The crash dump does not show any drivers that might have caused it. I would like to see a few more crash dump files if you can post new log files after each crash over the next day or so.
    my computer just crashed again
      My Computer


  7. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #7

    Same type of crash as before. Lets start to try and find any drivers that are playing up. Read and understand all the following details before starting.



    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please read and run driver verifier.

    If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  8. Posts : 20
    windows 10
    Thread Starter
       #8

    philc43 said:
    Same type of crash as before. Lets start to try and find any drivers that are playing up. Read and understand all the following details before starting.



    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please read and run driver verifier.

    If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
    please can you explain??
      My Computer


  9. Posts : 20
    windows 10
    Thread Starter
       #9

    and this
      My Computer


  10. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #10

    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 Computers


 

  Related Discussions
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 02:02.
Find Us




Windows 10 Forums