Windows 7: BSOD playing any games.

cwhite · 27 Feb 2013

Any game I play after a few minutes the computer freezes and locks. I have tried updating the video drivers.

Operating System
Microsoft Windows 7 Home Premium 64-bit SP1

CPU
Intel Core 2 Extreme QX9650 @ 3.00GHz

RAM
8.00 GB Dual-Channel DDR3

Motherboard
Rampage Extreme

Graphics
GeForce GTX 460

Hard Drives
SAMSUNG HE753LJ

**Pauly** · 27 Feb 2013

Hello cwhite, Welcome to SF

Both of your dump files indicate an 0x124 error which is a hardware error heres some more info for you
BSOD Index
Stop 0x124 - what it means and what to try

To be more specific your files state
BUSL0_SRC_ERR_M_NOTIMEOUT_ERR
this indicates the processor sent out a read request to L0 cache, and there was a delay in return

if your system is overclocked in anyway stop straight away if not check your cpu cooling as this may be caused by overheating, check your system/cpu temps and if they seem ok then try some stress testing of the cpu but be careful to monitor cpu temps at all times while stressing
Hardware - Stress Test With Prime95

Hope this helps post back with your results or any questions

cwhite · 28 Feb 2013

Things I have since tried

1. Tried to blow out as much dust as I could.

2. Prime5 for two hours and passed

3. Windows Memory test and passed

4. ran sfc/verifyonly and found no errors.

With core temp I had two screenshots where one core seems to run 5-10 degrees hotter.

The left screenshot when using prime5.

After all this I still can't play any games without locking up.

Golden · 28 Feb 2013

Quote: Originally Posted by cwhite

3. Windows Memory test and passed

That is an insufficient test - you need to tun MemTest86+ for a minimum of 8 passes to comprehensively test your RAM. Use this guide:

RAM - Test with Memtest86+

Please re-run a CPU test using this - it takes about 20 minutes- and report back:

CPU - Stress Test Using IntelBurnTest

Regards,
Golden

cwhite · 01 Mar 2013

Things I did since last post.

1. Ran Memtest with 5 passes and no errors

2. Ran Iburn with standard, high, and Very high tests and they all seem fine

3. Ran FurMark for 10 minutes and leveled out to 82c and no anomalies

4. Ran chkdsk

At this point the only other thing I can think of is a reformat.

Latest BSOD and screen shots from the Iburn tests.

**Pauly** · 02 Mar 2013

Last dump same as the others, still blames a hardware error relating to cpu

Code:

Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03661000 PsLoadedModuleList = 0xfffff800`038a5670
Debug session time: Fri Mar  1 20:03:32.910 2013 (UTC + 0:00)
System Uptime: 0 days 0:00:09.221
Loading Kernel Symbols
..................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007ec17a8, 0, 0}
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8007ec17a8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
 
BUGCHECK_STR:  0x124_GenuineIntel
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`033b66f0 fffff800`03922ca9 : fffffa80`07ec1780 fffffa80`06a31b50 fffff8a0`00000008 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033b6c10 fffff800`03803077 : fffffa80`07ec1780 fffff800`0387d2d8 fffffa80`06a31b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033b6c40 fffff800`0376a435 : fffff800`038deae0 00000000`00000001 fffffa80`079b1da0 fffffa80`06a31b50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033b6c80 fffff800`036dfca9 : fffff880`0112de00 fffff800`0376a410 fffffa80`06a31b00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033b6cb0 fffff800`0397734a : 00000000`00000000 fffffa80`06a31b50 00000000`00000080 fffffa80`06a20040 : nt!ExpWorkerThread+0x111
fffff880`033b6d40 fffff800`036c7946 : fffff880`03164180 fffffa80`06a31b50 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033b6d80 00000000`00000000 : fffff880`033b7000 fffff880`033b1000 fffff880`033b62c0 00000000`00000000 : nt!KiStartSystemThread+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME:  GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS_PRV
Followup: MachineOwner
---------
0: kd> !errrec [fffffa8007ec17a8]
===============================================================================
Common Platform Error Record @ fffffa8007ec17a8
-------------------------------------------------------------------------------
Record Id     : 01ce16b7d57f21a5
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/1/2013 20:03:32 (UTC)
Flags         : 0x00000002 PreviousError
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007ec1828
Section       @ fffffa8007ec1900
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 0
CPU Version   : 0x0000000000010676
Processor ID  : 0x0000000000000000
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007ec1870
Section       @ fffffa8007ec19c0
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000000
CPU Id        : 76 06 01 00 00 08 04 00 - bd e3 08 00 ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
Proc. Info 0  @ fffffa8007ec19c0
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007ec18b8
Section       @ fffffa8007ec1a40
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 0 Bank 0)
  Status      : 0xf200084000000800

Arc · 02 Mar 2013

Disable nVidia Update service Daemon.
Services - Start or Disable

How many HDDs do you have? Can you change the Sata port 2 ..... unplug the cable from sata port 2 and plug it in another unused port in the motherboard?

After doing these two, if you see that the problem continues, follow the guide: Stop 0x124 - what it means and what to try. It will help you to find out the failing hardware.