BSOD before & after fresh Windows install during game

1st I'd like to say hello to all, I just joined the forum. And now to the problem:

I have been playing games lately and have had 2 BSODs on the same game before and after fresh Windows installation. Before BSOD's the game kept crashing occasionally with multiple NvStreamSvc errors in Windows event/alert log during the fall and current moment.
After I got my 1st BSOD, I installed fresh Windows in, because I believed it was caused my some sort of driver problem.

Game crashed again and I did few "fixes". I set all power savings from Windows and Geforce management off and put bar from Quality to Performance from 'Geforce control panel'
Then I set "NVIDIA Streamer service" from automatic to manual.

After these procedures I got to play the game without crashes for about 5 days (which earlier was about 30min per crash). Until tonight I got BSOD again.

This custom PC is fairly new, got it in the summer 2013. (System specs are in specs menu.) I ran memtest for memories over night and got 0 errors for them about 7 pass if I recall right.

I installed Windows diagnostics tool, and got something out of crashdumps. Game is called War Thunder and that's the aces.exe in PROCESS_NAME parameter, which was running when BSOD struck.

Here's a part where symbols are loaded:


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: fffffa800906c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, 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: aces.exe

CURRENT_IRQL: f

STACK_TEXT:
fffff800`00ba8a98 fffff800`02a20a3b : 00000000`00000124 00000000`00000000 fffffa80`0906c028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba8aa0 fffff800`02be3463 : 00000000`00000001 fffffa80`08fbb470 00000000`00000000 fffffa80`08fbb4c0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba8ae0 fffff800`02a20700 : 00000000`00000728 fffffa80`08fbb470 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
fffff800`00ba8b40 fffff800`02a20052 : fffffa80`08fbb470 fffff800`00ba8e70 fffffa80`08fbb470 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba8c90 fffff800`02a1ff0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba8cd0 fffff800`02a13e88 : 00000000`201dab14 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba8d00 fffff800`02acb4ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba8d30 fffff800`02acb313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba8e70 00000000`6afdb5b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`01f0ed4c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6afdb5b2


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

--------------------------------------------------------

So the main question I have is that could this be related to my graphics card (nvstreamsvc in earlier windows log), CPU (Genuine Intel) or is this just related to the game (aces.exe)? I got then crashes also on other game, but no BSODs yet from it.
I've been looking the game forums, but haven't seen this problem with anyone else.

Welcome to SF trigsu :).

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. - H2SO4

The generic nature of the 0x124 (Arg1=0) stop code means we would have to take
the trail & error approach.

The single dump file uploaded is a generic L2 Cache error, I would like to have some more if possible.
I see you have CCleaner installed, please stop using it for the remainder of our troubleshooting
efforts as is deletes the dump files which we need.

Code:

Error Type    : Cache error
Operation     : Generic

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800906c138
Section       @ fffffa800906c2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : GCACHEL2_ERR_ERR (Proc 0 Bank 7)
  Status      : 0xbe0000000100110a
  Address     : 0x00000001178da700
  Misc.       : 0x000000d080000086

What is the make, model and age of your PSU?
Fill out this form and post back the result:

• Power Supply Calculator

Good practice, open up the case and re-seat all types of connection.

• SATA Cables (HDD/SSD/ODD).
• SATA-Power.
• Motherboard 24-pin.
• Motherboard 4/8-pin (CPU).
• Re-seat the RAM.
• Re-seat the GPU.

Make sure that every slot / cable head is free of dust or other obstruction.
Make sure that every connection is seating properly and firmly in-place.


Test for thermals and stability:

• Download HWinfo and post a Screenshot of the sensors window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
  
  • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).
  
  
     Note

  It is not mandatory to run both tests simultaneously, although possible as long as the temperatures are under constant monitoring.

Reset the BIOS back to default:

• CLR CMOS

   Note

Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

If any component is overclocked reset it back to stock speeds!

Good places to read more:

• Stop 0x124 - what it means and what to try
• Stop 0x124 Troubleshooting - 'New Method'

Thanks for the added info :).
Actually 3.8GHz is the stock turbo clock for your i5 4670K, so that is normal.
You are describing a TDR, Timeout Detection and Recovery so I want to add
a little more information.

Code:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout  failed.

What you're experiencing is called a TDR (Timeout Detection Recovery) is not a bugcheck in the true sense in that something
has went terribly wrong in the kernel which forced the machine to crash.

TVeblen said:

"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:

• Poor Cooling
• Problems with the power supply
• Overclocking Issues
• Bad System memory or incorrect memory timings
• Defective PC Components

• Read the full post.

Testing the RAM:

koolkat77 said:

Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• Pay close attention to part 3 of the tutorial "If you have errors"
• Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

When done with the testing procedure take a picture and upload it here.

This will help you to determine where the issue is origination from (if any):

Arc said:

First run it with all the existing/installed RAM modules. If it comes with no error, all is good.

But if it starts showing errors, Stop testing. Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Post back with the results.

Thanks for the nicely organized update :).

Your CPU is overheating!! reaching ~97-98°C.
What CPU cooler are you using?
Please check the fans / the mounting points and see if it is seated correctly.
Also if you manually applied the thermal paste you might have put a little too much (?).

CPU has stock cooler. Planning to get better. Machine was ready made custom, I doubt the guys in that particular store would have put paste wrong.

Idle 38-40'C in Asus Suite.
Prime95 65'C in Asus Suite

After put Power Saving mode in bios (3,4GHz).
Prime95 80'C in HWinfo instead of 97'C @ 3,8GHz .

Memtest picture

Hi :).
The latest dump is the same as in post #2.
I see that Asus has release a new BIOS, is flashing something you are comfortable with?