BSOD while gaming in general

[Coderdude]

Hello everyone,

Well I had this computer for about a year now and just recently had to replace the CPU and Motherboard. So for the past month I have been trying to deal with trying to figure out why these BSOD are occurring.

I have ran prime95 once but I'm not to crazy good with computers and it had some errors. I then ran memtest86+ to try and see if my ram had issues. I tested each individual stick in the most left slot of my motherboard. Reported no errors and all 4 sticks.

I've ran antivirus, malwarebytes and all that jazz to see if it was that and nothing.
So here I am heh.

Here's the SF Diagnostics Tool file and thanks!

 

[x BlueRobot]

[COLOR=red]BugCheck 109[/COLOR], {a3a039d89f6b7844, b3b7465ef1e8479a, fffff80003d1ee30, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : [COLOR=red]memory_corruption[/COLOR]

[B]Usual causes:[/B]  Device driver, Breakpoint set with no debugger attached, Hardware (Memory in particular)

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: More Help and Information with Driver Verifier - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Run some hard-drive diagnostics and follow these steps:

• Hard Drive Diagnostic Procedure

Find your hard-drive manufacturer and run their tests.


Additional Tests:

• SeaTools for DOS | Seagate
• CrystalDiskInfo - Software - Crystal Dew World

Post a screenshot of Crystal Disk Info summary:

• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

:info: Make sure you have the latest firmware for SSD, and ensure all the SATA and Power cables are connected to the drive.


Check for any file system errors and bad sectors using Option #2 of:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Use this command with Disk Check:

chkdsk C: /f /r