Sometimes BSOD while playing games.

I have experienced 2 BSODs so far. They all happened this year, and I fail to understand why or what is causing it. It is not frequent so it doesn't really bother me. My computer is 1 year old. I have not experienced any errors last year.

I have my FX 6300 overclocked from 3.5ghz to 4.1 ghz
My ASUS GTX 760OC is overclocked by 71+mhz core clock.

I did One one and half hour prime test with my CPU and I had no errors so Overclock should be stable. I also did tests with my graphic card and also no errors or crashes. Sometimes I play games 8 hours a day and I experience no issues. But sometimes once in 3 months I experience this blue screen and I would like to know what is causing it. These are the extracted DMP files. I have also included the DMP Files in a rar archive as an attachement.

Blue screen 1:

Code:

==================================================
Filename          : ntoskrnl.exe
Address In Stack  : ntoskrnl.exe+18c463
From Address      : fffff800`02c4c000
To Address        : fffff800`03231000
Size              : 0x005e5000
Time Stamp        : 0x531590fb
Time String       : 4. 3. 2014 10:38:19
Product Name      : Microsoft® Windows® Operating System
File Description  : NT Kernel & System
File Version      : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
Company           : Microsoft Corporation
Full Path         : C:\Windows\system32\ntoskrnl.exe
==================================================

Blue screen 2

Code:

==================================================
Dump File         : 031914-17877-01.dmp
Crash Time        : 19. 3. 2014 18:43:12
Bug Check String  : 
Bug Check Code    : 0x00000124
Parameter 1       : 00000000`00000000
Parameter 2       : fffffa80`07bc9028
Parameter 3       : 00000000`b0800000
Parameter 4       : 00000000`00040151
Caused By Driver  : hal.dll
Caused By Address : hal.dll+12a3b
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Crash Address     : ntoskrnl.exe+75bc0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\031914-17877-01.dmp
Processors Count  : 6
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 292 648
Dump File Time    : 19. 3. 2014 18:44:28
==================================================

Thank you for your support.

Respectfully.

Hello Accuracy,

Please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions, and post back with the needed information. One of our BSOD experts should be by later when able to further help. :)

Just from seeing that 0x124 with the two kernel drivers that control all hardware, the first thing I would suggest is stop overclocking until the system is stable. Overclocking deteriorates electronic components. Also check for overheating. The dump(s) and the files from the utility in the BSOD posting instructions can save a lot of time diagnosing the problem.

You didn't provide the information requested and the dump provided is inconclusive. It indicates a possibility that the CPU is failing. The error shown is a L1 Cache error. However, it also shows a double fault right after a graphics DMA transfer. It could be a graphics card failure or both.

It's not known if its being caused by elevated temperatures since you didn't provide the data. You'll need to monitor the temperatures yourself. One drawback to AMD processors is that they will run until they go up in smoke. They don't have a throttle feature like the Intel.

Added: By the way, passing Prime95 means nothing unless we know what parameters were used.

Code:

 
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  bf3.exe
CURRENT_IRQL:  f
STACK_TEXT:  
fffff880`009bbb08 fffff800`02c15a3b : 00000000`00000124 00000000`00000000 fffffa80`07d1d028 00000000`b0800000 : nt!KeBugCheckEx
fffff880`009bbb10 fffff800`02dd8463 : 00000000`00000001 fffffa80`079b48a0 00000000`00000000 fffffa80`079b48f0 : hal!HalBugCheckSystem+0x1e3
fffff880`009bbb50 fffff800`02c15700 : 00000000`00000728 fffffa80`079b48a0 fffff880`009bbeb0 fffffa80`07604200 : nt!WheaReportHwError+0x263
fffff880`009bbbb0 fffff800`02c15052 : fffffa80`079b48a0 fffff880`009bbeb0 fffffa80`079b48a0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009bbd00 fffff800`02c08e8f : 00000000`00000000 00000000`00000001 fffff880`009bbf30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009bbd40 fffff800`02cc04ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`009bbd70 fffff800`02cc0313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009bbeb0 fffff880`1101d24d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`0c0300f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x1d9
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
Followup: MachineOwner
---------

Code:

 
4: kd> !errrec fffffa8007d1d028
===============================================================================
Common Platform Error Record @ fffffa8007d1d028
-------------------------------------------------------------------------------
Record Id     : 01cf82eeef7e68a8
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/8/2014 12:14:06
Flags         : 0x00000000
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007d1d0a8
Section       @ fffffa8007d1d180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Instruction Execute
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000600f20
Processor ID  : 0x0000000000000004
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007d1d0f0
Section       @ fffffa8007d1d240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
Local APIC Id : 0x0000000000000004
CPU Id        : 20 0f 60 00 00 08 06 04 - 0b 32 98 3e ff fb 8b 17
                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  @ fffffa8007d1d240
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007d1d138
Section       @ fffffa8007d1d2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
Error         : ICACHEL1_IRD_ERR (Proc 4 Bank 1)
  Status      : 0xb080000000040151

Accuracy said:

So once again. What information do you require me to post?

The information it tells you to provide in the link in post #2.

Still incomplete. I'm done here.

What we are seeing is the Overclocking is indeed causing the issue. The CPU is at one point in a blue moon failing.
Download Speccy and follow the tutorial. The Whole tutorial not just part. You were asked to follow the tutorial here but evidently something got skipped please follow it fully.
Is the system Water cooled? if not Stop Overclocking
Is the system using Glycol based coolant? If not Stop Overclocking
Have a spare CPU in case of failure? Again stop Overclocking.

Simply step it down a notch and see if it stabilizes. You are not going to lose that much in performance but will gain in longevity.

It could also be a failing rail in the PSU. Have a Spare? Don't overclock till you do.

Have a good day :)