BSOD Playing Dragon Age: Inquisition

[slayman]

I get a blue screen whenever I've played for a while. I also get them rarely in Wasteland 2 but not as often and those are the only two games that bsod on me. I removed all OC from my GPU and still get bsod. And before that I ran hours of 3DMark and AIDA64 benchmarks with no stability issues. Still some OC on CPU that I've reduced but still happens.

i7-4790K @ 4.3 GHz with h100i cooling
GTX 780
Asus Maximus VII Hero
Samsung 840 EVO 250GB

Thanks!

 

[koolkat77]

[FONT="Lucida Console"]
Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\SLAYMAN-PC-2014-11-25_191556,18\112514-10498-01.dmp]
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`02e64000 PsLoadedModuleList = 0xfffff800`030a7890
Debug session time: Tue Nov 25 23:56:26.891 2014 (UTC + 6:00)
System Uptime: 0 days 1:10:25.577
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800d138028, bf800000, 124}

Probably caused by : GenuineIntel

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

2: 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: fffffa800d138028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, 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:  WmiPrvSE.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f6db58 fffff800`02e2da3b : 00000000`00000124 00000000`00000000 fffffa80`0d138028 00000000`bf800000 : nt!KeBugCheckEx
fffff880`02f6db60 fffff800`02ff0463 : 00000000`00000001 fffffa80`0d13ba60 00000000`00000000 fffffa80`0d13bab0 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6dba0 fffff800`02e2d700 : 00000000`00000728 fffffa80`0d13ba60 fffff880`02f6df30 fffff880`02f6df00 : nt!WheaReportHwError+0x263
fffff880`02f6dc00 fffff800`02e2d052 : fffffa80`0d13ba60 fffff880`02f6df30 fffffa80`0d13ba60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6dd50 fffff800`02e2cf0d : 00000000`00000008 00000000`00000001 fffff880`02f6dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6dd90 fffff800`02e20e88 : 00000000`00000002 fffffa80`0f309060 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02f6ddc0 fffff800`02ed84ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f6ddf0 fffff800`02ed8313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6df30 fffff800`02ee2db1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0e725540 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObfDereferenceObject+0x31


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------
[/FONT]

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

 

[slayman]

There is no way to know which piece of hardware is causing this?

 

[Laith]

Jag skulle börja med att kolla prossecorn.

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

Ladda ned Speecy också och se om du är överhättad. Ta en skärmbild av speecy och ladda up den här.