Possible Internal CPU error? 0x124 error
- Thread starter Ohmec
- Start date
- May 7, 2013
- 10,400
The Stop 0x124 didn't specify the operation being performed on the cache, which makes it difficult too.
Sorry to resurrect an old thread, but I assumed it was better than making a new one. I have not stopped receiving BSOD's, and I even have gotten a few from what I believe to be video driver errors. Most, however, are the same 0x124 WHEA UNCORRECTABLE ERROR. I posted a .rar with all the minidumps in it. Thank you guys so much for your help. I can troubleshoot general PC problems pretty well, but this is beyond me. You have really been the only help I've been able to get!
Hi,
We still have a *124:
We're still getting L2 Cache errors, but on Processor 1 and Cache Bank 6 this time.
In addition to the *124 bug checks, we're seeing:
SYSTEM_SERVICE_EXCEPTION (3b)
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
This indicates that the video scheduler has detected a fatal violation.
STACK_TEXT:
fffff880`0a97c648 fffff880`045ef55d : 00000000`00000119 00000000`0000000a 00000000`001c579b 00000000`001c209c : nt!KeBugCheckEx
fffff880`0a97c650 fffff880`0440a92a : 00000000`00000000 fffffa80`0f8ed4d0 fffffa80`0f8ed4d0 fffffa80`0de32000 : watchdog!WdLogEvent5_WdCriticalError+0xcd
fffff880`0a97c690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiResetEngine+0x446
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiResetEngine+446
BUCKET_ID: X64_0x119_dxgmms1!VidSchiResetEngine+446
^^ Direct X MMS.
-----------------
Given we're seeing *124's + *3B's + *119's, this is very likely a faulty video card (and RAM is a possibility now as well). I would say it's just a simple graphics driver issue, but as we have all of these bug checks coming together, it's not looking like that's the case whatsoever. With this said, let's run a Memtest for NO LESS than ~8 passes (several hours) to see if your RAM is healthy:
Memtest86+:
Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool
Which should I download?
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
FAQ : please read before posting
--------------------
If Memtest gets no errors over the 8 pass period, I would go ahead and uninstall your video card drivers, shut down, physically remove the video card, enable integrated graphics (if available), install latest integrated graphics drivers, and use the system as you would regularly. If you receive no crashes, your video card is faulty. You can also try a DIFFERENT graphics card as well if available, but you must also uninstall and reinstall drivers before and after removal.
Regards,
Patrick
We still have a *124:
Code:
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa800b1db0a8
Section @ fffffa800b1db180
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 : 0x0000000000000001
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800b1db138
Section @ fffffa800b1db2c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
[COLOR=#ff0000][I][B]Error : GCACHEL2_ERR_ERR (Proc 1 Bank 6)[/B][/I][/COLOR]
Status : 0xbe0000000100110a
Address : 0x000000004d4bcd80
Misc. : 0x0000021086000086We're still getting L2 Cache errors, but on Processor 1 and Cache Bank 6 this time.
In addition to the *124 bug checks, we're seeing:
SYSTEM_SERVICE_EXCEPTION (3b)
This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
This indicates that the video scheduler has detected a fatal violation.
STACK_TEXT:
fffff880`0a97c648 fffff880`045ef55d : 00000000`00000119 00000000`0000000a 00000000`001c579b 00000000`001c209c : nt!KeBugCheckEx
fffff880`0a97c650 fffff880`0440a92a : 00000000`00000000 fffffa80`0f8ed4d0 fffffa80`0f8ed4d0 fffffa80`0de32000 : watchdog!WdLogEvent5_WdCriticalError+0xcd
fffff880`0a97c690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiResetEngine+0x446
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiResetEngine+446
BUCKET_ID: X64_0x119_dxgmms1!VidSchiResetEngine+446
^^ Direct X MMS.
-----------------
Given we're seeing *124's + *3B's + *119's, this is very likely a faulty video card (and RAM is a possibility now as well). I would say it's just a simple graphics driver issue, but as we have all of these bug checks coming together, it's not looking like that's the case whatsoever. With this said, let's run a Memtest for NO LESS than ~8 passes (several hours) to see if your RAM is healthy:
Memtest86+:
Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool
Which should I download?
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
FAQ : please read before posting
--------------------
If Memtest gets no errors over the 8 pass period, I would go ahead and uninstall your video card drivers, shut down, physically remove the video card, enable integrated graphics (if available), install latest integrated graphics drivers, and use the system as you would regularly. If you receive no crashes, your video card is faulty. You can also try a DIFFERENT graphics card as well if available, but you must also uninstall and reinstall drivers before and after removal.
Regards,
Patrick
That is good information! So basically my entire system is getting errors from different sectors? My CPU, graphics cards (plural, two EVGA 770s), AND RAM? This is... Worrisome.. I hate asking people to explain things like I am 5, but it would greatly benefit me to break down what these errors are saying in the simplest terms possible.
No, not exactly. At this current moment, it appears that either your RAM or one of your video cards (and if worst luck both) is causing L2 Cache errors. As I said, we cannot know for sure until we run diagnostics for RAM. Run the Memtest as I advised first, and if it goes 8 passes with no errors, do what I said in regards to video cards. Since you have both, remove one at a time, swap, etc.
Regards,
Patrick
Regards,
Patrick
Well, my memory test came back fine after 9 passes, so its not my ram (I wish it was!). It must be my graphics card then. Since I was getting these errors before I installed my second graphics card I am going to assume it is my primary one. This is a blue screen I only get occasionally, so I guess it'll have to be something I just have to deal with. I understand that this post is going very far back, and you don't likely remember it when I first posted, but my original 0x124 error pointed to a problem with the L2 Cache on my 5th core of my CPU, would an issue with my graphics card still cause this problem?
We still remember!
Yes, it's very likely your video card (one of them). As I said here:
You don't have to deal with this, you could simply remove a video card and test the newer one. I'd rather have a non-crashing system with one video card than a system that's unstable and crashes, potentially causing file system corruption.
Regards,
Patrick
Yes, it's very likely your video card (one of them). As I said here:
You don't have to deal with this, you could simply remove a video card and test the newer one. I'd rather have a non-crashing system with one video card than a system that's unstable and crashes, potentially causing file system corruption.
Regards,
Patrick
Thank you very much, Patrick! Ill try running with just my primary, see if I get a crash, then run with just my second. Considering they're new cards it shouldn't be too annoying. (I'm spoiled). Luckily, EVGA has a fantastic customer return policy (not to mention a lifetime warranty), so this should be (fairly) painless. Thanks so much for your help! Ill let you know if I discover the problem!
Has Sysnative Forums helped you? Please consider donating to help us support the site!