Gave it a try and while I was playing Arma2 the game crashed with the error (out of memory)
Maybe there is something else wrong with my CPU OC or voltage some where, i am not really sure
--------------------------------------------------------------
Not sure if this will help but a week or so ago after months of stability with no changes I did get a random blue screen with the error code (0xD1), not had one since. I do believe that code meant
*0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
Could this be causing the issues? I have no idea.
---------------------------------------------------------------
I dug this out for you to check just incase it helps in anyway:
On Fri 08/11/2013 21:25:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110813-11216-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xC350, 0x2, 0x8, 0xC350)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 08/11/2013 21:25:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xD1 (0xC350, 0x2, 0x8, 0xC350)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.