BSOD playing GTA V - hal.dll+12818

==================================================
Dump File : 041815-16302-01.dmp
Crash Time : 18/04/2015 14:42:38
Bug Check String : MACHINE_CHECK_EXCEPTION
Bug Check Code : 0x0000009c
Parameter 1 : 00000000`00000000
Parameter 2 : fffff880`02f6db70
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+12818
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+72a40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041815-16302-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 408.384
Dump File Time : 18/04/2015 14:45:26
==================================================






While playing the system freezes... can anyone known the problem ?

Can you upload the dump file?

Does this only occur when playing GTA V?
Given that it isn't a 0x124, either the WHEA hasn't been fully initialised, which occurs on boot, or there are no errors in the processor registers.
Most likely the latter, which means it will be difficult to find the source of the problem.

here the dump file, thanks for the fast response

View attachment 60567

Looks like there's been a request to flush the entire Translation Lookaside Buffer, but upon flushing the cache, we bugchecked with a machien check exception. Something has gone wrong in the cache, most likely, and the registers haven't been affected, which is probably why we got a 0x9C and not a 0x124.
The flushing cause is unknown, but ti can be as simple as a context switch, which invalidates a lot of page table entries, thus requiring to flush the TLB.

This looks almost certainly like a CPU failure. As do most 0x9Cs.
Is your CPU still under warranty? If so, I recommend you RMA it.

Thanks !! gonna do a stress test of the cpu with OCCT, to look for error.

So i was actually interested how this thread ends because i have the exact same issue. Please let me know if it was the CPU ?
I have this problem since i had my GTX970 installed.

Can someone look in my dmp files ?
View attachment 61228