New
#1
BSOD PROBLEM, error code 0x00000109 (normal use/gaming)
Can any one help me?
this the beta log collector zip file:
Can any one help me?
this the beta log collector zip file:
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?
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.
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.
WarningPlease 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.
NoteYour 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.
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.