Possible Internal CPU error? 0x124 error

O

Ohmec

Member
Joined
Dec 1, 2013
Posts
13
So I will occasionally have a blue screen error, which, unfortunately, is a WHEA 0x124 error. I know this usually means hardware, and from the Minidump analysis its looking like its my CPU. For some reason I only have one minidump file in the folder, so that is what I will upload. Any help would be greatly appreciated, as I spent a butt load of money on this system and am dreading the thought of returning hardware after 3 months of use.

The error will only occur occasionally, such as when I am playing a demanding game on high settings. Temperatures on my CPU have never gotten above 80c, but my 2 770s do get to about ~82c.



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




Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available




************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9200.16581.amd64fre.win8_gdr.130410-1505
Machine Name:
Kernel base = 0xfffff803`f2084000 PsLoadedModuleList = 0xfffff803`f2350a20
Debug session time: Sun Dec 1 13:33:00.738 2013 (UTC - 6:00)
System Uptime: 0 days 9:22:34.171
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffd8018). Type ".hh dbgerr001" for details
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 124, {0, fffffa800b1d2028, be000000, 100110a}


Probably caused by : GenuineIntel


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


4: 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: fffffa800b1d2028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.


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




BUGCHECK_STR: 0x124_GenuineIntel


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


PROCESS_NAME: AC4BFSP.exe


CURRENT_IRQL: f


ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre


STACK_TEXT:
fffff880`0174d968 fffff803`f204593d : 00000000`00000124 00000000`00000000 fffffa80`0b1d2028 00000000`be000000 : nt!KeBugCheckEx
fffff880`0174d970 fffff803`f21e4ca9 : 00000000`00000001 fffffa80`07110850 00000000`00000000 fffffa80`0b1d2028 : hal!HalBugCheckSystem+0xf9
fffff880`0174d9b0 fffff803`f20456e3 : 00000000`00000728 00000000`00000004 fffff880`0174db10 fffffa80`07110850 : nt!WheaReportHwError+0x249
fffff880`0174da10 fffff803`f204500c : 00000000`00000010 fffffa80`07110850 fffff880`0174dbc8 fffffa80`07110850 : hal!HalpMcaReportError+0x53
fffff880`0174db70 fffff803`f2044f07 : fffffa80`07074d90 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xd4
fffff880`0174dbc0 fffff803`f2044d64 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe3
fffff880`0174dc00 fffff803`f2045edb : fffffa80`07074d90 fffff880`0174de30 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xd4
fffff880`0174dc30 fffff803`f20dc77b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0174dc60 fffff803`f20dc52e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
fffff880`0174dda0 00000000`0076aabb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x16e
00000000`0612fdec 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76aabb




STACK_COMMAND: kb


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: GenuineIntel


IMAGE_NAME: GenuineIntel


DEBUG_FLR_IMAGE_TIMESTAMP: 0


IMAGE_VERSION:


FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE


BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE


ANALYSIS_SOURCE: KM


FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache


FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}


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

Attachments

Hi,

The attached DMP file is of the WHEA_UNCORRECTABLE_ERROR (124) bugcheck.

A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).

If we run an !errrec on the 2nd parameter of the bugcheck (address of the WER structure) we get the following:

Code: 
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800b1ce0a8
Section       @ fffffa800b1ce180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
[COLOR=#ff0000][I][B]Error Type    : Cache error[/B][/I][/COLOR]
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000005

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

[COLOR=#ff0000][U][I][B]Error         : GCACHEL2_ERR_ERR (Proc 5 Bank 5)[/B][/I][/U][/COLOR]
  Status      : 0xbe0000000100110a
  Address     : 0x000000021e6ff0c0
  Misc.       : 0x0000005084000086

Cache error + GCACHEL2_ERR_ERR - Looks like faulty L2 Cache on Processor 5 and Cache Bank 5.

MODULE_NAME: hardware

IMAGE_NAME: hardware

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE

^^ Implies that this was NOT caused by any sort of software complication (drivers, etc) but hardware. PROCESSOR_CACHE also furthers our diagnosis in the CPU itself (L2 Cache) possibly being faulty.

There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:

1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps - Speccy - System Information - Free Download

2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting - How To Clear CMOS (Reset BIOS)

3. Ensure your BIOS is up to date.

4. The only software conflict that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.

5. If all of the above fail, the only left to do is replace your processor as it is faulty.

Regards,

Patrick
 
Code: 
[COLOR=#ff0000]BugCheck 124[/COLOR], {[COLOR=#0000cd]0[/COLOR], [COLOR=#008000]fffffa800b1ce028[/COLOR], be000000, 100110a}

Probably caused by : GenuineIntel

Just to chime in and to add some additional information, the first parameter indicates the error source, this in not necessarily the actual error, since it only technically indicates who found the hardware error. The supported error sources are loaded by the Windows Kernel, by querying PSHED (Platform Specific Hardware Error Driver), and listing all the hardware platforms. In this example, a Machine Check Exception would a hardware platform and the error source. Each error source has a LLHEH (Low Level Hardware Error Handler) associated with it, which handle and then produce a hardware error packet. This error packet is produced as a structure called WHEA_ERROR_PACKET.

The hardware error packet (!errpkt), is then sent to the PSHED for addition of more specific information about the hardware error, and that once completed, the error packet is formatted into error sections by Windows to produce a hardware error record as seen in parameter 2, which as already said by Patrick is contained within a data structure called WHEA_ERROR_RECORD.

Here's some basic BIOS and motherboard information to help you identify the correct update if any are available:

Code: 
5: kd> [COLOR=#008000]!sysinfo machineid[/COLOR]
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3050]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = [COLOR=#ff0000]F5[/COLOR]
BiosReleaseDate = [COLOR=#ff0000]05/16/2013[/COLOR]
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = [COLOR=#ff0000]Z87X-UD4H[/COLOR]
SystemFamily = To be filled by O.E.M.
SystemVersion = To be filled by O.E.M.
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = [COLOR=#ff0000]Z87X-UD4H-CF[/COLOR]
BaseBoardVersion = x.x
 
Do you by chance have any Kernel Memory dumps? They'll be located within this folder path:

Code: 
C:\Windows\MEMORY.DMP

If any files are present, then please compress and place in a zipped folder, to upload to a file sharing site such as SkyDrive or Dropbox, and then post the URL to the file in your next post.

There's a couple of debugger extensions I would like to try, which aren't available with a Minidump.
 
A STOP 0x124 error is an error that your CPU reports to Windows
I would not suggest replacing your CPU until you've run a complete set of hardware diagnostics - along with the typical troubleshooting that we do for other BSODs

I suggest the diagnostics here: Hardware Diagnostics

Both jcgriff and I have seen that the errors can easily be driver errors ever since this error first debuted with Windows Vista

Sent from my phone
 
Thank you guys for the quick reply!

Yes actually I do, however the file size is around 580mb. I'm uploading it to drop box as we speak. I'll edit in just a minute with the link. But as of right now its looking like a faulty processor? I will try resetting and re-updating my BIOS, and I have no GIGABYTE software on my computer. This has been happening since about a week after my build, and it will happen in spurts. Its very unusual.

I'm dreading exchanging my processor as thatll leave me without a computer for a while, and getting my noctua D14 off without taking my entire mobo out is going to be a massive pain. I really do appreciate your help on this.

EDIT: Link to Memory dump is here: https://www.dropbox.com/s/i9ebu1osizg1szs/MEMORY.rar
 
usasma said:
A STOP 0x124 error is an error that your CPU reports to Windows
I would not suggest replacing your CPU until you've run a complete set of hardware diagnostics - along with the typical troubleshooting that we do for other BSODs

I suggest the diagnostics here: Hardware Diagnostics

Both jcgriff and I have seen that the errors can easily be driver errors ever since this error first debuted with Windows Vista

Sent from my phone
Click to expand...

Which tests would you specifically suggest that I run?
 
Have you followed Patrick's suggestions? Personally, I would start with the CPU tests, do the Intel Test and the Prime95. Run all the tests under that program. For example, with the Prime95 program, run Small FFT's Large FFT's and Blend test individually for a few hours each. Start with the Small FFT's.

Thanks for getting the file.
 
Alright, so I just flashed and updated my BIOS, but since this problem only happens rarely I will not be able to immediately test to see if there is a crash. Prime 95 worked just fine in a brief (~5 minute) test run of all tests. I updated my previous post with the memory dump file, and it can also be found here: https://www.dropbox.com/s/i9ebu1osizg1szs/MEMORY.rar. Intel test is a pass, and I will run the Prime95 test while I am at work. I have a significant cooler on my CPU (Noctua D14), would there be any problem with having Prime95 running for about 8 hours?
 
x BlueRobot said:
It depends, if your CPU doesn't overheat or not, and a few hours should be suffice.
Click to expand...

Alright well Ive got a custom torture test set up on Prime 95 for 2 hours per test that will start when I head to work .My CPU never gets above 61c even at 100% load, so I think it will be fine for the duration of the tests. I will let you guys know tomorrow if there have been any errors since then. I greatly appreciate all the help I've received here, and for everyone to take their time to attempt to help me is greatly appreciated. I've spent far to much money on this rig to be getting BSODs!
 
Code: 
4: kd> [COLOR=#008000]!whea[/COLOR]
Error Source Table @ fffff803f2305798
[COLOR=#ff0000]4 Error Sources[/COLOR]
Error Source 0 @ fffffa800b170010
   Notify Type      : {0b1d5bd0-fa80-ffff-a057-30f203f8ffff}
   Type             : [COLOR=#ff0000]0x0[/COLOR] (MCE) <<< Machine Check Exception
   Error Count      : 1
   Record Count     : 8
   Record Length    : 728
   Error Records    : wrapper @ fffffa800b1d2000  record @ [COLOR=#0000cd]fffffa800b1d2028[/COLOR]
                    : wrapper @ fffffa800b1d2728  record @ fffffa800b1d2750
                    : wrapper @ fffffa800b1d2e50  record @ fffffa800b1d2e78
                    : wrapper @ fffffa800b1d3578  record @ fffffa800b1d35a0
                    : wrapper @ fffffa800b1d3ca0  record @ fffffa800b1d3cc8
                    : wrapper @ fffffa800b1d43c8  record @ fffffa800b1d43f0
                    : wrapper @ fffffa800b1d4af0  record @ fffffa800b1d4b18
                    : wrapper @ fffffa800b1d5218  record @ fffffa800b1d5240
   Descriptor       : @ fffffa800b170069
      Length                     : 3cc
      Max Raw Data Length        : 141
      Num Records To Preallocate : 8
      Max Sections Per Record    : 4
      Error Source ID            : 0
      Flags                      : 00000000
Error Source 1 @ fffffa800b1d5bd0
   Notify Type      : {0b1d9bd0-fa80-ffff-1000-170b80faffff}
   Type             : 0x1 (CMC) <<< Checked Machine Check
   Error Count      : 0
   Record Count     : 8
   Record Length    : 728
   Error Records    : wrapper @ fffffa800b1d6000  record @ fffffa800b1d6028
                    : wrapper @ fffffa800b1d6728  record @ fffffa800b1d6750
                    : wrapper @ fffffa800b1d6e50  record @ fffffa800b1d6e78
                    : wrapper @ fffffa800b1d7578  record @ fffffa800b1d75a0
                    : wrapper @ fffffa800b1d7ca0  record @ fffffa800b1d7cc8
                    : wrapper @ fffffa800b1d83c8  record @ fffffa800b1d83f0
                    : wrapper @ fffffa800b1d8af0  record @ fffffa800b1d8b18
                    : wrapper @ fffffa800b1d9218  record @ fffffa800b1d9240
   Descriptor       : @ fffffa800b1d5c29
      Length                     : 3cc
      Max Raw Data Length        : [COLOR=#ff0000]141[/COLOR]
      Num Records To Preallocate : 8
      Max Sections Per Record    : 4
      Error Source ID            : 1
      Flags                      : 00000000
Error Source 2 @ fffffa800b1d9bd0
   Notify Type      : {09dab010-fa80-ffff-d05b-1d0b80faffff}
   Type             : 0x3 (NMI) <<< Non Maskable Interrupt
   Error Count      : 0
   Record Count     : 1
   Record Length    : 6c0
   Error Records    : wrapper @ fffffa800b170740  record @ fffffa800b170768
   Descriptor       : @ fffffa800b1d9c29
      Length                     : 3cc
      Max Raw Data Length        : 100
      Num Records To Preallocate : 1
      Max Sections Per Record    : 3
      Error Source ID            : 2
      Flags                      : 00000000
Error Source 3 @ fffffa8009dab010
   Notify Type      : {f23057a0-f803-ffff-d09b-1d0b80faffff}
   Type             : 0x7 (BOOT) <<< Self Explanatory 
   Error Count      : 0
   Record Count     : 0
   Record Length    : 0
   Error Records    :    Descriptor       : @ fffffa8009dab069
      Length                     : 3cc
      Max Raw Data Length        : 400
      Num Records To Preallocate : 1
      Max Sections Per Record    : 1
      Error Source ID            : 3
      Flags                      : 00000000

The fffffa800b1d2028 in the error record which was present within the dump file, and is most likely the error record which contains the information which caused the crash. The others indicate recoverable errors, which may or may not have been able to be recovered by the hardware. The Type field will appear as the the first parameter of each bugcheck.

The output also indicates the amount of hardware platforms supported on x86/x64 by PSHED. The Max Raw Data Length field shows the amount of raw data within the error packet which is obtained from the error source. Additonal information may be added here by PSHED or by a PSHED plug in which is provided by a hardware vendor, for very specific information gathering.

You can check the WHEA_ERROR_SOURCE_DESCRIPTOR structure in the WDK for more information about the fields.
 
So what you're telling me is that there is a log or record that will specifically tell me what caused the crash? Is there some way I could locate it?
 
What Patrick posted with the !errrec extension with the error record of the crash, it's the most specific information a Stop 0x124 will provide, in regard to a crash. They tend to not conserve much information for some reason.

Code: 
4: kd> !errrec fffffa800b1d2028
===============================================================================
Common Platform Error Record @ fffffa800b1d2028
-------------------------------------------------------------------------------
Record Id     : 01ceee7d8d27c110
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 12/1/2013 19:33:00 (UTC)
Flags         : 0x00000000

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

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000306c3
Processor ID  : 0x0000000000000004

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

Local APIC Id : 0x0000000000000004
CPU Id        : c3 06 03 00 00 08 10 04 - bf fb da 7f 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  @ fffffa800b1d2240

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

Error         : GCACHEL2_ERR_ERR (Proc 4 Bank 5)
  Status      : 0xbe0000000100110a
  Address     : 0x000000000465bd00
  Misc.       : 0x000000d086000086
 
Here's a scenario:

Program A is started and establishes it's own set of memory addresses
Program B is started and it does something wrong with the address spaces owned by Program A
Then Program B exits (and there's no evidence left that it did this)
A short while later, Program A accesses the problem address space, it finds something wrong with it and crashes.
The crash will blame Program A as there's no evidence of any other program operating at that time - even though Program B is actually to blame.

Another issue that complicates these things is if the information obtained for the error report is corrupted, then the report itself may be corrupted. This is sorta like your checkbook - if you have an error in the .01 column, it's not as noticeable or critical as if it's in the 1,000.00 column.

Finally, there's a difference between "caused by" and "occurred in". Unfortunately the debugger isn't very clear-cut on this distinction - so that's why you'll see things blaming ntoskrnl.exe even though it's not at fault.

As for stress tests - if everything works correctly the system will work just fine.
But if it doesn't, then theres a chance of damage to the system. I'd only run stress tests when you're at home to keep an eye on the system (just in case).

Good luck!
 
So I ran 2 hours each of the stress tests and no error occurred. I guess this will just have to be something that I deal with?
 
The attached DMP file is of the DRIVER_VERIFIER_DETECTED_VIOLATION (c4) bug check.

This is the general bug check code for fatal errors found by Driver Verifier.

The driver it detected in violation was nvlddmkm.sys which is the nVidia video driver.

Code: 
STACK_TEXT:  
fffff880`20ae59e8 fffff800`14ccf1ac : 00000000`000000c4 00000000`000000f6 00000000`000005b0 fffffa80`0db6f940 : nt!KeBugCheckEx
fffff880`20ae59f0 fffff800`14cd6c88 : fffffa80`0db6f940 00000000`00000000 fffff880`00000000 fffffa80`071064e0 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`20ae5a30 fffff800`14ab85a8 : fffff8a0`0256edb0 fffffa80`0e907800 fffff880`20ae5c40 fffff880`20ae68a8 : nt!VfCheckUserHandle+0x1b8
fffff880`20ae5b10 fffff800`146de453 : ffffffff`80000078 fffffa80`0e907800 fffff880`20ae5c40 00000000`00000000 : nt!NtClose+0x477
fffff880`20ae5bc0 fffff800`146e3630 : fffff880`0618e90a fffff880`20ae68ba fffff880`20ae5de0 fffff880`20ae68a8 : nt!KiSystemServiceCopyEnd+0x13
fffff880`20ae5d58 fffff880`0618e90a : fffff880`20ae68ba fffff880`20ae5de0 fffff880`20ae68a8 fffff880`20ae5ef0 : nt!KiServiceLinkage
fffff880`20ae5d60 fffff880`0618e0c2 : 00000000`00000000 00000000`00000000 fffff880`20ae5ef0 fffff880`20ae5ef0 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0x9a90a
fffff880`20ae5e10 fffff880`061d8cbe : fffff880`0618e045 fffff980`015f2bd0 fffffa80`0cc59000 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0x9a0c2
fffff880`20ae5eb0 fffff880`061a71d4 : fffff880`20ae6870 00000000`00000004 fffff880`20ae69a8 fffffa80`0cc59000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0xe4cbe
fffff880`20ae5f30 fffff880`06199e5c : fffff880`20ae6478 00000000`00000000 fffff880`20ae6080 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0xb31d4
fffff880`20ae5f80 fffff880`06a0e1c3 : 000007ff`958c5870 00000000`03edbb28 00000000`03edbb70 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0xa5e5c
fffff880`20ae6390 fffff880`0619930b : fffff880`06624b30 fffff880`20ae6489 fffffa80`0cc59000 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]!nvDumpConfig+0x29fdeb
fffff880`20ae63d0 fffff880`069f09b9 : fffff880`20ae6798 fffff880`20ae6559 fffff880`20ae6798 fffff880`20ae6798 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]+0xa530b
fffff880`20ae64f0 fffff880`06a8ec05 : 00000000`00000000 00000000`00000000 00000000`4e562a2a 00000000`01000003 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]!nvDumpConfig+0x2825e1
fffff880`20ae65c0 fffff880`058ee618 : 00000000`00000000 00000000`00000000 fffff880`20ae6a00 00000000`00000000 : [COLOR=#ff0000][I][B]nvlddmkm[/B][/I][/COLOR]!nvDumpConfig+0x32082d
fffff880`20ae65f0 fffff880`058edee8 : 00000000`00000000 fffff880`20ae6b80 fffff880`20ae6ad0 00000000`00000000 : [COLOR=#ff0000][I][B]dxgkrnl[/B][/I][/COLOR]!DXGADAPTER::DdiEscape+0x48
fffff880`20ae6620 fffff960`00286bd7 : fffff6fb`41ffe570 fffffa80`0e907800 00000000`03d9fbe0 00000000`00000000 : [COLOR=#ff0000][I][B]dxgkrnl[/B][/I][/COLOR]!DxgkEscape+0x478
fffff880`20ae6ab0 fffff800`146de453 : 00000000`00000008 00000000`0000001c 00000000`00000201 fffff880`20ae6b00 : win32k!NtGdiDdDDIEscape+0x43
fffff880`20ae6b00 000007ff`9cb20d3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03edac28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007ff`9cb20d3a

We can see a few Direct X Kernel and nVidia calls.

Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

Regards,

Patrick
 
Thank you Patrick I will try reinstalling my video drivers. This is strange to me though as I've never had a BSOD from a video driver error. Could this possibly be causing my original 0x124 crash?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top