BSOD-IRQL GT Zero at System Service

[JSquibb]

I have been getting BSOD from almost every game- LoL, Payday2, Civ5, Diablo 3, etc. Sometimes I will blue screen while my pc is idling and nothing is happening. I have received many many different BSOD messages, but this was the most recent one. I am pretty new in terms of trying to figure these things out, however, I have been reading other posts to try and see if I could solve this on my own. I have been failing repeatedly though!

I have noticed you guys have been having much success in terms of clearing people's issues up so I am hoping you can clear this mess up for me. I think i correctly figured out how to get the .dmp logs from the blue screens. Let me know if you need anything else or if I am missing something!

 

[koolkat77]

First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.

• Create a Dump File when you get a BSOD

Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.

 

[JSquibb]

Thank you, I have set the option to "small memory dump." I had previously had it on kernel memory dump. I also created a folder in my windows folder. I will update with any new information I have as soon as I encounter another crash.

 

[JSquibb]

I keep getting the BSOD, however, I am not receiving any dumps from the errors? I have tried a few other things I read on here but no matter what I keep trying I cannot find any of my .dmp files.

 

[koolkat77]

That's alright.
please upload the latest grab.

 

[JSquibb]

I had two back to back blue screens while on League of Legends, however, I had been playing simcity for a few hours previously without any issue. I always seem to get a different blue screen error message. One of them being the clock interval one, the GT zero at system service, etc.

 

[koolkat77]

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 - What it means and what to try

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_05-09-2013_JSquibb\SF_05-09-2013\090413-16785-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`03063000 PsLoadedModuleList = 0xfffff800`032a6670
Debug session time: Thu Sep  5 09:22:49.630 2013 (UTC + 6:00)
System Uptime: 0 days 0:00:07.973
Loading Kernel Symbols
......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8007a098f8, 0, 0}

Probably caused by : AuthenticAMD

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

3: 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: fffffa8007a098f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031686f0 fffff800`03323ca9 : fffffa80`07a098d0 fffffa80`06a9e040 00000000`0000000b 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03168c10 fffff800`03204e87 : fffffa80`07a098d0 fffff800`0327e2d8 fffffa80`06a9e040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03168c40 fffff800`0316c285 : fffff800`032dfae0 00000000`00000001 fffffa80`079fe820 fffffa80`06a9e040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03168c80 fffff800`030e2251 : fffff880`0116be00 fffff800`0316c260 fffffa80`06a9e000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03168cb0 fffff800`03376ede : 00000000`00000000 fffffa80`06a9e040 00000000`00000080 fffffa80`06a1c740 : nt!ExpWorkerThread+0x111
fffff880`03168d40 fffff800`030c9906 : fffff880`03088180 fffffa80`06a9e040 fffff880`03093040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03168d80 00000000`00000000 : fffff880`03169000 fffff880`03163000 fffff880`04322890 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE_PRV

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

3: kd> !errrec fffffa8007a098f8
===============================================================================
Common Platform Error Record @ fffffa8007a098f8
-------------------------------------------------------------------------------
Record Id     : 01cea9e72f513de4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/5/2013 3:22:49 (UTC)
Flags         : 0x00000002 PreviousError

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Data Write
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100fa0
Processor ID  : 0x0000000000000005

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

Local APIC Id : 0x0000000000000005
CPU Id        : a0 0f 10 00 00 08 06 05 - 09 20 80 00 ff fb 8b 17
                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  @ fffffa8007a09b10

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

Error         : DCACHEL1_DWR_ERR (Proc 5 Bank 0)
  Status      : 0xf6004000f4000145
  Address     : 0x000000022f3e4b00
  Misc.       : 0x0000000000000000

 

[JSquibb]

I have been going through all of the help issues in the link you provided me with, but still continuing to experience blue screens. Here is my newest dump log. This time I was blue screening while trying out the new elder scrolls online game. I kept receiving the "System Service Exception."

Thanks,
JSquibb

 

[x BlueRobot]

Your installation is clearly counterfeit, you have a OEM_SLP key on a retail motherboard. Please format and install with a genuine key.