bsod 124 after installing new GPU - gpu broken or not enough power?

Hello everyone,

Last month I bought a new GPU (ASUS GTX 1060-6G)
I am not entirely sure when it started but now i get randomly bluescreens since 2 weeks. (The oldest dumpfile is from 25.09.2017)

So I already did

Even then i got no bluescreens.
But It can happen randomly. While gaming or doing nothing, or browsing or whatever.

I uploaded the last 4 dumpfiles. Can somebody pls take a look at them?
(Listed from oldest to newest).


Here is my Computer Configuration:

CPU: I5-2500k @3.3 GHz
RAM: 2*8GB DDR3
GPU: ASUS GTX 1060-6G
MB: p67 pro3
PowerAdapter: bequiet! 530W Model Number:BQT- L7-530W
OS: Win7 x64 (up2date)


About overclocking:
At first i used the natural overclocking provided by the MB (even before replacing the GPU) and there wasnt a big problem.
Sometimes the Computer didnt / doesn't react anymore and I have to reboot it manually (even after disabling overclocking).


Here is an abstract of the newest minidump:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\100317-43243-01_first.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23889.amd64fre.win7sp1_ldr.170810-1615
Machine Name:
Kernel base = 0xfffff800`0484b000 PsLoadedModuleList = 0xfffff800`04a8d750
Debug session time: Tue Oct 3 17:20:41.034 2017 (UTC + 2:00)
System Uptime: 0 days 0:09:21.877
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800d0b4028, f2000000, 10019}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* 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: fffffa800d0b4028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000010019, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_GenuineIntel

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: Warhammer2.exe

CURRENT_IRQL: f

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:
fffff800`00ba6a98 fffff800`04814a3b : 00000000`00000124 00000000`00000000 fffffa80`0d0b4028 00000000`f2000000 : nt!KeBugCheckEx
fffff800`00ba6aa0 fffff800`049d4fdf : 00000000`00000001 fffffa80`0d0d5450 00000000`00000000 fffffa80`0d0d54a0 : hal!HalBugCheckSystem+0x1e3
fffff800`00ba6ae0 fffff800`04814700 : 00000000`00000728 fffffa80`0d0d5450 fffff800`00ba6e70 fffff800`00ba6e00 : nt!WheaReportHwError+0x26f
fffff800`00ba6b40 fffff800`04814052 : fffffa80`0d0d5450 fffff800`00ba6e70 fffffa80`0d0d5450 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff800`00ba6c90 fffff800`04813f0d : 00000000`00000004 00000000`00000001 fffff800`00ba6ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff800`00ba6cd0 fffff800`04807e88 : 00000000`5c293da0 000007ff`d8d8902f 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff800`00ba6d00 fffff800`048b926c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff800`00ba6d30 fffff800`048b90d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff800`00ba6e70 000007fe`f6d91f4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0012c9e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f6d91f4a


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_TLB

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_TLB

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x124_genuineintel_processor_tlb

FAILURE_ID_HASH: {b49c6f57-bc2b-eda7-054a-fc323ea8c38d}

Followup: MachineOwner
---------

0: kd> !errrec fffffa800d0b4028
===============================================================================
Common Platform Error Record @ fffffa800d0b4028
-------------------------------------------------------------------------------
Record Id : 01d33c59de7ff504
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 10/3/2017 15:20:41 (UTC)
Flags : 0x00000000

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa800d0b40a8
Section @ fffffa800d0b4180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal

Proc. Type : x86/x64
Instr. Set : x64
Error Type : TLB error
Flags : 0x00
Level : 1
CPU Version : 0x00000000000206a7
Processor ID : 0x0000000000000000

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa800d0b40f0
Section @ fffffa800d0b4240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000000
CPU Id : a7 06 02 00 00 08 10 00 - bf e3 9a 1f ff fb eb bf
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0 @ fffffa800d0b4240

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800d0b4138
Section @ fffffa800d0b42c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : GTLBL1_ERR (Proc 0 Bank 2)
Status : 0xf200000000010019
Reply to obi1989
2 answers Last reply
More about bsod 124 installing gpu gpu broken power
  1. If anything is overclocked, stop it and run on stock speeds. Test RAM one stick at a time. Test the system with a clean Windows setup, test without the video card. Maybe a CPU issue, there are a lot of resources out there about the WHEA errors, check and see what may work for you with your testing.
    Reply to hang-the-9
  2. hang-the-9 said:
    If anything is overclocked, stop it and run on stock speeds. Test RAM one stick at a time. Test the system with a clean Windows setup, test without the video card. Maybe a CPU issue, there are a lot of resources out there about the WHEA errors, check and see what may work for you with your testing.


    JFYI and other ppl: I read in the net that someone changed the vcore of the cpu. So I read what most ppl did and fixed the CPU to 1,25V with only 0,004V boost power. It runs smoothly at 4GHz now and only crashes very very very rarely.
    I dont know why the cpu suddenly didnt have enough power but well it works now..
    Reply to obi1989
Ask a new question Answer

Read More

Asus GPUs Blue Screen Power Gtx