So I just got a BSOD that has the same error code as the last two I had this month. They all seem to happen at random and once while I was playing CS:GO. Today I was just doing some light tasks when my monitor went to black and then showed the BSOD screen. The bug check code was 0x00000109. I don't really know for sure what could be the problem but I'm thinking maybe bad memory.
Hello, Adechi welcome to the forums. I will try to help. These are your last 3 dump files
Code:
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8a5b91aca, b3b7465ef835ea20, fffff800033360b0, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR="Red"]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8a4b4baa5, b3b7465ef73189fb, fffff80003336030, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR="Red"]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8a43ba77e, b3b7465ef6b876d4, fffff800033362e0, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
[COLOR="Red"]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption
Please Run Memtest86+
Information
Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip
Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes all run in one session to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask
Based on your 16 GB of memory, I would suspect the test to take about 18-20 hours. Please let me know the results of the test. If you get an error, stop the test. Even 1 error is a fail. Please be sure to download the test from the link above. You will be able to download an ISO file which should be burned to a CD, or an Auto Installer for USB, which will install the test on a USB Flash drive. Then boot from the media you chose and the test will run automatically and run until you stop it. Be sure to let it run for a minimum of 8 passes.
Please go to Windows Update, and in the left column click Installed Updates. Search for KB3022345 and KB3068708. If you find them Uninstall them (http://www.sevenforums.com/tutorials/24373-windows-update-uninstall-update.html). Then watch the Updates because they will come back. When you see them, right click them and select Hide. Then they shouldn't come back.
Then please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
It looks like you have some corrupted system files and the scan may be able to repair them.
Adechi, please fill out your system specs in more detail with manufacturer and model. Please include what graphics card you have, what hard drives you have, your PSU, CPU cooler all of the items listed. This is what I usually post and maybe it will help you, or you can click at the bottom left of this post and see mine to see what we would like.
Please fill out your System Specs
Information
Your System Specs will help us to help you, and doing it in this manner will make them available to all helpers in every post and keep us from hunting for them. We ask that you fill them out in as much detail as possible including Desktop or Laptop, Model number if it is an OEM computer and all components with the Manufacturer and Model number if possible.
If you will go to your last post and click the 'System Specs' in the bottom left of the post, you will find a link to update your system specs. Please fill those out in as much detail as possible, making sure to click save at the bottom of the page. If you would like to know what we would like, you can click 'My System Specs' at the bottom left of this post to see mine. If you do not know what your components are, this will help you accomplish this task. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html
Please upload the BSOD posting instructions again. Based on what I could read in your last upload and what I saw in the files, it appears you have system corruption. I need to figure out why and how to repair it. A clean install would fix it, but we will try a couple of other things.
Please back up all your personal files, and create a system restore point. It is possible this could cause you to have to do a clean install, but we take every precaution we can to keep that from happening. It has never happened with me, but is a possibility. Please also create a System Repair disk too. If you need to know how, please ask.
What is Driver Verifier:
It puts stress on the drivers, and tries to make the faulty driver crash the computer. It is designed this way, to attempt to trap the offending driver.
What you will notice:
It will tend to make the computer rather slow and sluggish because the drivers are being stressed.
Warning
Before enabling DV, make sure you have created a system restore point before enabling Driver Verifier. make a System Restore Point manually before enabling DV.
Tip
If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
Let us know the results, with the subsequent crash dumps, if any. If you have a BSOD please upload the BSOD posting instructions. http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html. If you have any questions, feel free to ask. here is a video of driver verifier being set up on Windows 10. It is the same procedure as Windows 7. Just sort the drivers by provider and select all drivers not provided by Microsoft. Do not enable it on any drivers from Microsoft.
Sorry for the delay. My internet has been down. But this is the result of the last dump
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8baf886d3, b3b7465f0d755629, fffff80003336290, 1}
*** WARNING: Unable to verify checksum for win32k.sys
[COLOR=red]Probably caused by : memory_corruption[/COLOR]
Followup: memory_corruption
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
[COLOR=red]CRITICAL_STRUCTURE_CORRUPTION[/COLOR] (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See [url=http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx]Kernel patch protection for x64-based operating systems[/url]
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8baf886d3, Reserved
Arg2: b3b7465f0d755629, Reserved
Arg3: fffff80003336290, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
I'm struggling to see anything beyond RAM here, no drivers are showing and nothing hints towards drivers at all. I'll have a think and try and work the dump files again, very strange.
My Computer
Computer type
PC/Desktop
Computer Manufacturer/Model Number
Custom Build
OS
W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
Adechi, I asked Boozad to come take a look because all I could see is Ram. I asked you to run Driver Verifier because you ran Memtest86+ and it was still crashing. Sometimes a bad driver will cause a ram error. It seems that is not the case here.
Please look in Add Remove Programs and Uninstall any of the programs you find there. They are all Gigabyte utilities
Code:
APP Center
V-Tuner
System Information Viewer
Smart Recovery 2
Smart Time Lock
Fast Boot
EZ Setup
EasyTune
@BIOS
Cloud Station
USB Blocker
On/Off Charge™ / On/Off Charge™ 2
CFOS Speed Internet Accelerator Software
Then I need you to run memtest86+ again for as many passes as possible. If you get an error, stop the test.
Please Run Memtest86+
Information
Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip
Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask
OK, I just wanted to be sure about the Gigabyte programs. I hate to ask you to run it again, but everything we can find in the dump files says Memory Corruption. Let it run as many passes as you can and before shutting it down, please post a picture of the screen. I just want to see what information it is reading.