New
#1
BSOD with Gigabyte G1 Gaming GTX970 in SLI while gaming
Hi guys,
This is my first post in this forum since I have not received any help from elswhere.
You guys are my only hope.
Okay, so I recently bought two G1 Gaming GTX970 graphics cards.
The first driver install went bad by windows using its own drivers, so I got the Display Driver Uninstaller from 3dguru, scrubbed the drivers in safe mode. After restart windows still used its own drivers at first but everything worked and I updated with the latest nVidia drivers.
Now to the issue...
After gaming for some time graphically demanding games (AC:Unity, FarCry4) the PC would freeze and I would have a BSOD on my hands. Interestingly enough this has happened with nVidia supported games, but I've managed to play Alien: Isolation for an extended period of time which is AMD supported. Have not had any problems with Borderlands Pre Sequel (nVidia supported) either but it's also not as heavy on the GPU. When the BSOD has happened it has happened approx within an hour of gaming, sometimes within minutes. The BSOD does not happen when I'm watching movies or browsing the net or working on the PC, just when gaming heavy does it occur, I run the system SLI enabled. I'm going to include two crash dumps below.
By the looks of it, it seems to be a driver issue, so what are my options here?
I've reinstalled the drives but still the problem has persisted.
Any help or insight into the BSOD errors I'm getting would be greatly appreciated.
Thanks in advance,
Nahkman
Code:Debugging Details: ------------------ BUGCHECK_STR: 0x9C_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: ACU.exe CURRENT_IRQL: f ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre LAST_CONTROL_TRANSFER: from fffff80003014818 to fffff800030c0b80 STACK_TEXT: fffff880`009f9b38 fffff800`03014818 : 00000000`0000009c 00000000`00000000 fffff880`009f9b70 00000000`00000000 : nt!KeBugCheckEx fffff880`009f9b40 fffff800`03013f57 : 00000000`00000004 00000000`00000000 00000000`00000004 00000000`00000000 : hal!HalpMcaReportError+0x164 fffff880`009f9c90 fffff800`03007e88 : 00000000`00000001 00000000`79db6e00 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f fffff880`009f9cc0 fffff800`030bf46c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`009f9cf0 fffff800`030bf2d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`009f9e30 00000001`4584026a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 00000000`03d0f668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00000001`4584026a STACK_COMMAND: kb FOLLOWUP_IP: nt!KxMcheckAbort+6c fffff800`030bf46c 488d8c2400010000 lea rcx,[rsp+100h] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!KxMcheckAbort+6c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 51fb06cd IMAGE_VERSION: 6.1.7601.18229 FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x9c_genuineintel_nt!kxmcheckabort+6c FAILURE_ID_HASH: {bfc05df6-1f6e-272c-6108-703420c3f047} Followup: MachineOwnerCode:Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre STACK_TEXT: fffff880`033e05b0 fffff800`032cdca9 : fffffa80`097418d0 fffffa80`06d09040 00000000`00000006 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c fffff880`033e0ad0 fffff800`031aee97 : fffffa80`097418d0 fffff800`032282d8 fffffa80`06d09040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49 fffff880`033e0b00 fffff800`03116285 : fffff800`03289b40 00000000`00000001 fffffa80`0976a9a0 fffffa80`06d09040 : nt!WheapProcessWorkQueueItem+0x57 fffff880`033e0b40 fffff800`0308c261 : fffff880`015a4e00 fffff800`03116260 fffffa80`06d09000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25 fffff880`033e0b70 fffff800`03320bae : 00000000`00000000 fffffa80`06d09040 00000000`00000080 fffffa80`06cf5450 : nt!ExpWorkerThread+0x111 fffff880`033e0c00 fffff800`030738c6 : fffff880`03165180 fffffa80`06d09040 fffff880`0316ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033e0c40 00000000`00000000 : fffff880`033e1000 fffff880`033db000 fffff880`033e02e0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: GenuineIntel IMAGE_NAME: GenuineIntel DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae_prv FAILURE_ID_HASH: {435e2195-e498-1e77-0526-f8d7450275e5} Followup: MachineOwner