BSOD with Gigabyte G1 Gaming GTX970 in SLI while gaming

[Nahkman]

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

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: MachineOwner

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

 

[Ytook1]

I've been having a very similar issue, I've only got the one Gigabyte 970 G1, and I've only really tested 2 games (AC Unity and Civ Beyond Earth) and while playing both after usually a few hours they'll freeze then I'll get a bsod. They're always Bug Check Code: 0x00000124 and all have the Crash Address: ntoskrnl.exe+4ae61c.

I've run windows memory diagnostic with no results, I've reseated my card, performed multiple clean driver installs, checked temperatures with no problems. I can't figure out what's causing it and this is the only similar problem I can find online. I really wish I could help but it seems we're in much the same boat

 

[Nahkman]

Hi,

Well, i'm glad i'm not alone with my problem but I still feel bad for you.
Have you tried reinstalling windows from scratch? I'm thinking about doing it but before I gotta take some time to make a backup of everything. Some have suggested in other threads to run driver verifier, maybe I'll do that before a complete reinstall. I was wondering does someone know of any other tools that we might use to pinpoint the problem?

Anyways, let me know how your search for a solution is going Ytook1.

--edit--
Just ran driver verifier, could not get windows to start, right after showing windows starting I got a BSOD:

This is a daemon tools associated driver but after uninstalling daemon tools I still got the same BSOD, guess the conflicting driver remains...

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff8800433a360, The address in the driver's code where the error was detected.
Arg3: fffff9800383ae10, IRP address.
Arg4: 0000000000000000, Status code.

Debugging Details:
------------------


OVERLAPPED_MODULE: Address regions for 'kbdclass' and 'WUDFRd.sys' overlap

BUGCHECK_STR:  0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  23e

FAULTING_IP: 
dtsoftbus01+1360
fffff880`0433a360 4053            push    rbx

FOLLOWUP_IP: 
dtsoftbus01+1360
fffff880`0433a360 4053            push    rbx

IRP_ADDRESS: fffff9800383ae10

DEVICE_OBJECT: fffffa800ae3a2a0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff800035664ec to fffff800030d8b80

STACK_TEXT:  
fffff880`0350e568 fffff800`035664ec : 00000000`000000c9 00000000`0000023e fffff880`0433a360 fffff980`0383ae10 : nt!KeBugCheckEx
fffff880`0350e570 fffff800`0357058a : fffff800`03564b00 fffff880`0433a360 fffff980`0383ae10 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0350e5b0 fffff800`0357145e : 00000000`0000023e 00000000`00000000 fffff980`0383ae10 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`0350e600 fffff800`0357c82f : fffffa80`0b370820 fffffa80`0b2bc410 fffffa80`0b2bc4c8 fffff880`0433e228 : nt!VfErrorReport6+0x6e
fffff880`0350e6d0 fffff800`0357cc73 : fffffa80`0b2bc410 00000000`00000002 fffffa80`0ae3a2a0 fffff880`0433a430 : nt!IovpCallDriver2+0x13f
fffff880`0350e730 fffff800`03582d3e : fffff980`0383ae10 fffff980`0383ae10 00000000`00000002 fffffa80`0ae3a2a0 : nt!VfAfterCallDriver+0x353
fffff880`0350e780 fffff800`03581d52 : fffff980`0383af28 00000000`00000002 fffffa80`0b0c0190 fffffa80`0b2bc410 : nt!IovCallDriver+0x57e
fffff880`0350e7e0 fffff800`03582d26 : fffff980`0383ae10 00000000`00000002 fffffa80`0b0c0040 fffff800`0357e505 : nt!ViFilterDispatchPower+0x62
fffff880`0350e810 fffff880`01637a8a : 00000000`00000000 fffff880`0350e8f0 fffffa80`0b0c07e0 fffffa80`0b2bc1e0 : nt!IovCallDriver+0x566
fffff880`0350e870 00000000`00000000 : fffff880`0350e8f0 fffffa80`0b0c07e0 fffffa80`0b2bc1e0 fffffa80`00000020 : iaStorF+0x1a8a


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  dtsoftbus01+1360

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dtsoftbus01

IMAGE_NAME:  dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51c2adcb

FAILURE_BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1360

BUCKET_ID:  X64_0xc9_23e_VRF_dtsoftbus01+1360

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xc9_23e_vrf_dtsoftbus01+1360

FAILURE_ID_HASH:  {59a4cf06-cdeb-d558-6268-21dce698e966}

Followup: MachineOwner

Cheers,
Nahkman

 

[Ytook1]

Hi there

If you're still following this I posted on a forum called Tom's Hardware and got some useful responses, haven't fully tested yet to see if the error is resolved but you might get some use from this:

Gigabyte G1 GTX 970: BSOD after a few hours in-game - Gtx - Graphics & Displays