BSOD when playing games

[kokonutz]

Hello,

I've been getting BSODs since upgrading to Win8 last year but after a while I decided to format my HDD and get back to Win7 hopping it would help with the blue screens. It didn't.

It only seems to happen when I play relatively demanding games after 1 hour or so... So, Dota 2, CS:GO and even WoW, and yet I can play Hearthstone for hours with no problem. Does that mean it's a memory problem?

If any further step is required to make your life easier, please ask and I will do/give anything needed!

 

[Arc]

First of all, the display driver version applied there is a bad one.

fffff880`05615000 fffff880`060fa000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
[COLOR=Red]    Image name: nvlddmkm.sys
    Timestamp:        Fri Jun 21 14:36:16 2013[/COLOR] (51C41788)
    CheckSum:         00AB87FF
    ImageSize:        00AE5000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Stress test the CPU.
Hardware - Stress Test With Prime95

Update your BIOS to Version 0902 from ASUSTeK Computer Inc. -Support- Drivers and Download M4N68T-M LE V2.

Let us know the results.
______________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f64180, 2}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88002f64180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`03316528 fffff800`02cdca89 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx
fffff880`03316530 fffff800`02c8feb7 : fffff800`00000000 fffff800`00000002 00000000`00002710 fffff880`03316650 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`033165c0 fffff800`031f9895 : fffff800`0321f460 fffff880`03316770 fffff800`0321f460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`033166c0 fffff800`02c81b73 : 00000000`2fcf7776 fffff800`02df7e80 00000000`00000000 2aaaaaaa`aaaaaaab : hal!HalpHpetClockInterrupt+0x8d
fffff880`033166f0 fffff800`02c8b200 : fffff800`02df7e80 fffffa80`00000001 00000000`00000000 fffff800`02df3c48 : nt!KiInterruptDispatchNoLock+0x163
fffff880`03316880 fffff800`02ce8ced : 00000000`00000002 00000000`00000001 fffff880`03316ba0 00000000`000002ec : nt!KeFlushMultipleRangeTb+0x260
fffff880`03316950 fffff800`02cfe685 : fffff880`04ae9c00 fffff800`00000001 00000000`00000001 fffff880`03316bb0 : nt! ?? ::FNODOBFM::`string'+0x229d4
fffff880`03316b00 fffff800`02c70206 : 00000000`000014f0 00000000`00000000 fffffa80`00000000 00000000`00000003 : nt! ?? ::FNODOBFM::`string'+0x4d886
fffff880`03316b80 fffff800`02c706c3 : 00000000`00000008 fffff880`03316c10 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`03316bd0 fffff800`02f22cce : fffffa80`06af1600 00000000`00000080 fffffa80`06a09740 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`03316d40 fffff800`02c76fe6 : fffff880`02f64180 fffffa80`06af1600 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03316d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


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_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------