BSOD ntoskrnl.exe, error 0x00000124

[sharp461]

Just today when I got home from work and turned on my PC, it started freezing. just this morning it was working fine (ive had random restarts before but rarely like maybe once or twice a month.) This problem first started out by just freezing, can't move mouse or anything, holding power button don't work either so have to shut the power switch. It now seems to either BSOD or freeze whenever I boot normally (and sometimes the BSOD doesnt even make a dmp.) I either freeze/BSOD on the welcome screen or after a few min when the desktop comes up. Safe mode works fine though (as I am also in it now to post this,) and I have tried system restore to no avail. I've tried testing my RAM sticks by moving them to different slots and testing one at a time and still same problem persists. One forum mentioned video drivers so i uninstalled mine and still nothing. I went to try windows repair but i get some error message saying the utility doesn't match my version (not sure why as its the same disc I used to install with.) I would normally just re-format and install but a few forums mention that not working so I got a little more worried and am now coming to here to see what you guys think? I read initial post and ran the file collection app and have the zip uploaded. One note though: the system health report would not work, just gave me an error screen (maybe because im in safe mode, but like I said can't leave it or I will freeze.) My basic system specs are below, thanks for taking the time to read this and hope you can solve it!

Windows 7 Pro 64 bit (got it from my computer courses in college as we part of some partnership with microsoft.)
16GB RAM (2x 8GB sticks)
AMD FX 8150 8-core CPU (3.6 GHz)
Nvidia GTX 560 Ti
ASUS Sabertooth MB
This rig I built in March and ran fine until today. Windows 7 I had for over a year (same disc, just reinstalled.)

 

[writhziden]

It does not appear you let the jcgriff2 utility run to completion. It sometimes appears it is not doing anything when it actually is, so do not stop it. Go get a cup of coffee or a meal while you wait.

Analysis:

BugCheck 0x124

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS​
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.​
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.
​

 

[Vir Gnarus]

What did you use to test your RAM? If you were using Windows Mem Diag Tool, don't bother, it's not very reliable. Memtest86+ is the de facto standard for memory testing. Run it for at least 7 passes. That's a long time for 16GBs, but do it with individual sticks to expedite the process.

All of the bugchecks are WHEA errors stating failure in reading generic cache. Generic cache commonly is your RAM and this can occur if crosstalk between your RAM and CPU fails.

Before dabbling with hardware, your first thing you should do is reset your BIOS to factory defaults, this includes any OCing you may have done. Then, go to ASUS website and download and update all drivers for your motherboard and your BIOS. Also, do not download, and in fact, uninstall all motherboard software that came with your motherboard. This includes but not entirely consists of temp/voltage monitoring software, overclocking software, and anything pertaining to USB. All of them are gimmicky, buggy, broken messes that are known for causing hardware false positives. You should only have BIOS updates and all component drivers (NOT USB or "quiet drive" drivers) installed.

If all that does not resolve your issue, then you may very well have a motherboard, CPU or PSU problem. Unfortunately, nothing really can definitely determine which is causing your woes, but I would put most blame on motherboard (if RAM or software/drivers didn't cause this).

 

[sharp461]

It does not appear you let the jcgriff2 utility run to completion. It sometimes appears it is not doing anything when it actually is, so do not stop it. Go get a cup of coffee or a meal while you wait.

I was pretty sure I did, its over when it opens the folder it makes by itself right? As soon as I saw it open I figured it was done and there was no program to close after that. Also for the other replies, how I tested my RAM was booting up with one stick at a time, different slots as well incase it was a faulty slot. Also the temps seem to be working fine, between 28 C and 34 C. I never OC anything and im at the factory settings. When I got the MB I just put it in the case and put everything on the board. I never did check the hdd so I will run those tests and repost. I will also repost jcgriff2 (remember I am running all this in safe mode so it may be possible the tests won't work 100%)

EDIT: I tried running seatools and it won't allow me to in safe mode (and normal mode is not an option.) Also I have attached an up to date version of that jcgriff to the post below. I keep seeing people mentioned hardware and such, but according to the .dmp its the ntoskrnl that is the problem, and that is supposedly linked to booting (which makes sense to me since I only freeze either on welcome screen or a few min after I see my desktop). I run perfectly fine in safe mode so I can't see the problem being cpu or RAM (RAM which I tested physically.) I would think running the system recovery options on the windows disc would fix it (possibly) but I can't even get that to run becomes it comes up with the error: "This version of System Recovery Options is not compatible with the version of Windows you are trying to repair..." Only thing I can think of now is to reformat (always worked for me) but I have read a few forums saying that never worked, but not sure if they have the same exact issue. Hopefully you can think of something else? I thought maybe, just maybe, it was a virus I have somehow and maybe hijackthis log can point out the problem.

 

[sharp461]

Here is the up to date griff zip. Seatools would not run in safemode.

 

[Vir Gnarus]

These are definitely hardware generated faults. The CPU itself is informing the Windows OS kernel that there was an internal error during a generic cache read and Windows therefore issued a bugcheck. All of them say the same thing: generic cache read error. As said before, this is an issue with the crosstalk between your CPU and your RAM. Most likely what's happening is the CPU is reading RAM contents to be placed into one of its internal caches and the operation failed.

When you ran the memory test, did you run the one built in Windows? If so, don't; rather you should use Memtest86+. Also, it didn't seem like you ran Prime95 as instructed by writhziden. Make sure to run that overnight while in Safe Mode, running Blend instead of Small FFTs which was instructed by the article linked.

In addition, make absolutely sure that you've uninstalled all software that came with your motherboard (temp monitors, OCing software, USB junk, etc.) and update all drivers (besides "USB drivers", uninstall those) and your BIOS. I've often seen buggy motherboard software, BIOS or mobo drivers rigger hardware faults such as this, making it appear like hardware is the issue when it isn't.

I can assure you that we aren't really dealing with HD here, but RAM, CPU or Motherboard, with a chance the PSU is involved. Hence it's best to check the crosstalk between the RAM and CPU, and Prime95 on Blend is probably your best option here. If your system BSODs from it despite having cleaned up all motherboard software and drivers as recommended, then you most likely have a RAM or motherboard failure.

 

[sharp461]

I ran prime95 for about 2 hours, so far things past. I talked to my PC buddy and gave him my details and he instantly told me what was wrong. the CHIPSET on the MB seems to be the issue (CPU is possible but considering safe mode works fine and stress test to its highly unlikely.) Like you guys said its the talking between the CPU and the chipset (you guys said RAM but its the VRAM, on the chipset.) That would also explain why safe mode runs fine because it doesnt use the cache memory on the chipset so I don't freeze. Luckily for my MB (everything else too ) is all under warranty so I will just be sending it back and hope it was the problem. Thanks for all of your help and when I get it back I will repost with an update on whether or not the MB Chipset was the cause. Thanks again.

 

[Vir Gnarus]

That doesn't really make any sense. The VRAM should not be accessed from your mobo's chipset because you are using a video card, so it should not be defaulting back to the onboard video controller for any reason, unless you specifically requested it do so through a BIOS option.

Either way, it does sound very much like your mobo is to blame. We'll see how it turns out when you get the replacement. Remember, do not install any mobo software that comes with it, and don't really even bother using the disc included with it but just go straight to the ASUS site and download and install the updated drivers from there. That'll make absolutely sure we aren't dealing with old messed up chipset drivers n whatnot (don't forget BIOS too).

 

[sharp461]

That doesn't really make any sense. The VRAM should not be accessed from your mobo's chipset because you are using a video card, so it should not be defaulting back to the onboard video controller for any reason, unless you specifically requested it do so through a BIOS option.

Either way, it does sound very much like your mobo is to blame. We'll see how it turns out when you get the replacement. Remember, do not install any mobo software that comes with it, and don't really even bother using the disc included with it but just go straight to the ASUS site and download and install the updated drivers from there. That'll make absolutely sure we aren't dealing with old messed up chipset drivers n whatnot (don't forget BIOS too).

Yeah, maybe not VRAM then but still its the cache memory. And yeah only divers ill get from disc are the network ones (so I can actually get the updated ones later ) When talking to ASUS he had me update BIOS anyway to test, still messed up so at least I know the version wasnt the problem. And sadly we couldnt check the chip ourself because it came with its own fancy heatsink and didnt really want to mess with it sine I still got warranty. Its in UPS atm so Ill update on any news (possibly a week-2 weeks at most ) Thanks again for help.

 

[Vir Gnarus]

The only cache memory available to a CPU that I can recall with the exception of onboard VRAM would be RAM and the internal CPU caches L0-L3.

Hope the return goes well.