Random Lag spikes, Blue Screen after installing EVGA GTX 970

DZ469

Honorable
May 17, 2013
5
0
10,510
Hi all,

Yesterday I installed an EVGA GTX 970 (the 2974) in my system. I uninstalled the old drivers, updated the firmware for the ACX 2.0, and then installed the new NVIDIA drivers. After installing the new GPU, though, I noticed that my computer now has random massive spikes of input lag where the keyboard won't type characters and then spits out a dozen or so and the mouse jumps across the screen. It happens both when I'm just surfing the web (as I'm typing this, my mouse is acting very jumpy) and sometimes when I am in game. The only thing I changed in my computer was the GPU; could it be a bad card? I also notice coil whine like many others have with the 970s; is that an issue?

What do you guys think would be causing this?

my specs:
Mainboard : ASUSTeK COMPUTER INC. P8Z77-V LK
Processor : Intel Core i5 2500K @ 3300MHz
RAM : 16384 MB DDR3-SDRAM
Video Card : NVIDIA GeForce GTX 970
Hard Disk : KINGSTON SNV425S2128GB (128GB)
Hard Disk : Samsung SSD 840 PRO Seri (128GB)
Hard Disk : Seagate ST1000DM003-9YN162 (1000GB)
Network Card : Realtek Semiconductor RTL8168/8111 PCIe Gigabit Ethernet Adapter
Operating System : Windows 7 Home Premium (64-bit)
DirectX : Version 11.00

EDIT: I just reran the Windows Experience Index tool, since my score was out of date and my graphics score dropped from a 7.8 with a GTX 560 Ti to a 6.0 with my new GTX 970!

EDIT 2: Just got a blue screen, stop code 124. The crash dump is below:
*******************************************************************************
* 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: fffffa800fc5a028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, 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: System
CURRENT_IRQL: f
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:
fffff800`00ba6a98 fffff800`03429a3b : 00000000`00000124 00000000`00000000 fffffa80`0fc5a028 00000000`be000000 : nt!KeBugCheckEx
fffff800`00ba6aa0 fffff800`035ec463 : 00000000`00000001 fffffa80`0d795c40 00000000`00000000 fffffa80`0d795c90 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba6ae0 fffff800`03429700 : 00000000`00000728 fffffa80`0d795c40 fffff800`00ba6e70 fffff800`00ba6e00 : nt!WheaReportHwError+0x263
fffff800`00ba6b40 fffff800`03429052 : fffffa80`0d795c40 fffff800`00ba6e70 fffffa80`0d795c40 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba6c90 fffff800`03428f0d : 00000000`00000004 00000000`00000001 fffff800`00ba6ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba6cd0 fffff800`0341ce88 : fffff800`00b9a940 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba6d00 fffff800`034d44ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba6d30 fffff800`034d4313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba6e70 fffff800`034defb1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff800`00b9a8f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeReleaseInStackQueuedSpinLock+0x41

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
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_mae
FAILURE_ID_HASH: {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
Followup: MachineOwner
 
Solution
Had exactly the same issues with my 970 and bluescreens in idle with hardware error 0x124, after raising the PCH Voltage 0,06V everything works fine. seems that autosettings were too low for the GTX970. (Zotac H77 Wifi-B + Zotac GTX 970, Seasonic S12IIB 330W).

Vitric9

Distinguished
Can you do a run through with a benchmark tool with GPU-Z open and MSI afterburner with RTSS has lots of OSD and graph options. Valley 1.0 is good for GPU testing. Mind the GPu usage, voltage, power, for starters. It may be a power limit holding it back. When the GPU Boost 2.0 kicks in it will keep going depending on the voltage. Though if the power limit is anything like Kepler, that 106% is going to cause stutter.
 

Jamod

Reputable
Jan 3, 2015
1
0
4,520
Had exactly the same issues with my 970 and bluescreens in idle with hardware error 0x124, after raising the PCH Voltage 0,06V everything works fine. seems that autosettings were too low for the GTX970. (Zotac H77 Wifi-B + Zotac GTX 970, Seasonic S12IIB 330W).
 
Solution