Windows 7 BSoD when Gaming - Windows 7 Pro

[nurdfest]

Hi all,

I built this PC about 8 months ago and have not had many problems with it until the last month or so. I am getting BSoD when playing Counter-Strike:GO, Darksiders 2, and also once while playing League of Legends. I initially thought this was an problem with my RAM, so this morning before work I started Memtest86+. Memtest ran for 9hours and 8 complete passes while I was at work. I returned home to find that Memtest had produced no errors. Now I am turning to this forum for help.

My PC specs are as follows:
ASRock Z68 Extreme3 Gen3 - BIOS 1.2 (There is a new version available)
Intel Core i5 2500 (Not the K model)
G Skill DDR3 PC3-12800 (Rated for 9 timing but I set in the BIOS to 8 which produced no errors in Memtest)
NVIDIA GeForce GTX 560 (Newest drivers)
Western Digital Caviar Blue 500GB SATA III 7200RPM

I also attached a zip file containing the information from SF Diagnostics, Screencaps of all tabs in CPUZ, and the HTML output from RAMMon. As I said, the blue screens only occur when the PC is in heavy use (gaming) and not when doing everyday activities. If anymore information is request or more diagnostics need to be run, I am willing to do whatever is needed. Thank you all in advance.

Link Removed

 

[kemical]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


CRITICAL_STRUCTURE_CORRUPTION (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 [B]Link Removed due to 404 Error[/B]
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: a3a039d89cc127d7, Reserved
Arg2: b3b7465eef3df73d, Reserved
Arg3: fffff8000353f9ac, 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


Debugging Details:
------------------




BUGCHECK_STR:  0x109


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT


PROCESS_NAME:  System


CURRENT_IRQL:  0


LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003292d40


STACK_TEXT:  
fffff880`033b6498 00000000`00000000 : 00000000`00000109 a3a039d8`9cc127d7 b3b7465e`ef3df73d fffff800`0353f9ac : nt!KeBugCheckEx




STACK_COMMAND:  kb


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: Unknown_Module


IMAGE_NAME:  Unknown_Image


DEBUG_FLR_IMAGE_TIMESTAMP:  0


FAILURE_BUCKET_ID:  X64_0x109_ANALYSIS_INCONCLUSIVE


BUCKET_ID:  X64_0x109_ANALYSIS_INCONCLUSIVE


Followup: MachineOwner

[FONT=Segoe UI]The CRITICAL_STRUCTURE_CORRUPTION bug check has a value of 0x00000109. This indicates that the kernel has detected critical kernel code or data corruption.

[/FONT][h=3]CRITICAL_STRUCTURE_CORRUPTION Parameters[/h][FONT=Segoe UI]The following parameters are displayed on the blue screen.[/FONT]
[TABLE]
[TR]
[TH="bgcolor: #EDEDED"]Parameter[/TH]
[TH="bgcolor: #EDEDED"]Description[/TH]
[/TR]
[TR]
[TD]1
[/TD]
[TD]Reserved
[/TD]
[/TR]
[TR]
[TD]2
[/TD]
[TD]Reserved
[/TD]
[/TR]
[TR]
[TD]3
[/TD]
[TD]Reserved
[/TD]
[/TR]
[TR]
[TD]4
[/TD]
[TD]The type of the corrupted region. (See the following table later on this page.)
[/TD]
[/TR]
[/TABLE]
[FONT=Segoe UI] [/FONT]
[FONT=Segoe UI]The value of Parameter 4 indicates the type of corrupted region.[/FONT]
[TABLE]
[TR]
[TH="bgcolor: #EDEDED"]Parameter 4[/TH]
[TH="bgcolor: #EDEDED"]Type of Corrupted Region, Type of Corruption, or Type of Action Taken That Caused the Corruption[/TH]
[/TR]
[TR]
[TD]0x0
[/TD]
[TD]A generic data region
[/TD]
[/TR]
[TR]
[TD]0x1
[/TD]
[TD]A function modification or the Itanium-based function location
[/TD]
[/TR]
[TR]
[TD]0x2
[/TD]
[TD]A processor interrupt dispatch table (IDT)
[/TD]
[/TR]
[TR]
[TD]0x3
[/TD]
[TD]A processor global descriptor table (GDT)
[/TD]
[/TR]
[TR]
[TD]0x4
[/TD]
[TD]A type-1 process list corruption
[/TD]
[/TR]
[TR]
[TD]0x5
[/TD]
[TD]A type-2 process list corruption
[/TD]
[/TR]
[TR]
[TD]0x6
[/TD]
[TD]A debug routine modification
[/TD]
[/TR]
[TR]
[TD]0x7
[/TD]
[TD]A critical MSR modification
[/TD]
[/TR]
[/TABLE]

Hi,

I would apply those bios updates asap as it looks like that could be the cause of your issue. Also a few drivers could do with updating like sound, network and the intel management engine driver (you can find an updated version on the motherboard website).