Repeated BSOD with Error 0x00000124

[Relough]

My computer has recently been "randomly" giving me a BSOD. Now, I am pretty sure it is happening because I also recently overclocked my cpu, however, I did have problems before overclocking it (although not as often). I find my computer tends to BSOD either overnight, when I only have Folding@Home running, or during the day when all I have running is Chrome (F@H is running, but paused). I have also noted that my gpu (1x GeForce GTX 560 Ti) almost always fails while running F@H in the first 24hrs the system is up. However, my main concern is the BSOD.

Now the reason I stated that I have had problems before oc my cpu is that ever since I first powered it up nearly 10 months ago I have had problems with the computer freezing on me. Note this was before I oc my cpu, and even before I installed F@H. Originally I thought it might be bad memory, but testing has ruled this out I just restarted my computer, and it now only detects 4.00 GB of installed memory, when it should detect 8.00 GB. The system will hang, sometimes for a few seconds, but most often for a couple of minutes, before suddenly "fixing" itself. This has, on occasion, led to a BSOD, though most of the time it resolves itself. Also, on occasion it doesn't fix itself and I have to do a hard reboot. After a while I decided to have task manager open on my second monitor at all times so that I could monitor the cpu usage and memory, incase something odd happened when it froze. Doing so, I noticed that every time the computer froze, all four cores of my cpu would shoot up to 100% and then drop back down after the system resolved itself. However, memory usage never changed (note this was also done with F@H not running). Also, the source of the freezing seemed to change. Sometimes my monitors would go black for a few seconds and then everything would come back. A message would pop up on my task bar stating something along the lines of "your graphics display driver/kernel has crashed and successfully recovered." Other times, a window would pop up stating that "the memory instruction could not be read" and giving me some error code. Still other times the system would resolve itself and nothing would happen, no error message or temporary black screens. Anyways, here is my info:

- Windows 7 Home Premium 64 bit Service Pack 1
- Original installed OS
- OEM full retail (OEM I installed)
- System is about 9-10 months old
- original OS installation (9-10 months old)

 

[Relough]

Also, please note that the System Health Report did not detect an antivirus, but I am running AVG Anti-Virus Free Edition 2012.

 

[Relough]

UPDATE: under system properties it lists my computer as having only 4 GB of memory (when really I have 2x 4 GB of memory). However, running Memtest86+ it says I have 8GB and gives me no errors after 7 passes. Does anyone know why this might be?

 

[Relough]

UPDATE 2: I have tested both sticks by themselves.

• Slot 0: Both sticks work.
• Slot 1: Both sticks work.
• Slot 2: Neither stick works.
• Slot 3: Both sticks work.

Obviously slot 2 is faulty on my mobo.
Since the board is configured so that the sticks must be in either slots 0 and 2 or 1 and 3, I changed the sticks from their original configuration of 0 and 2 to 1 and 3. Unfortunately, this did not solve the problem as I had hoped, and my computer still only recognizes one stick (even though I know they both work). Also, I noticed that when I boot up and go to the ASRock UEFI setup utility, it shows my total memory to be 4096 MB and my state to be single-channel memory mode. Any ideas on what could be causing this and how to fix it?

 

[Relough]

UPDATE 3: well I managed to get the computer to recognize both sticks, but only if I put them in slots 0 and 1. Unfortunately this means that they are both running in single channel memory mode, but I guess that is better than only having one stick working. Anyways, I still need to get my BSOD problem resolved, so if anyone can help me, that would be appreciated.

 

[writhziden]

I was going to look up your motherboard manual when I noticed you did not let us know what motherboard you have. I then hoped it would be included in your crash report, but instead I found

System Manufacturer:       To Be Filled By O.E.M.
System Model:              To Be Filled By O.E.M.

Please provide your motherboard model so we can provide more assistance with your RAM troubles. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html may help in this regard.


Security Software (this is just a check that you have it and it is working properly; nothing needs to be done with this information at this time):

avgcsrva.exe	c:\program files (x86)\avg\avg2012\avgcsrva.exe	404	8	200	1380	4/11/2012 8:07 AM	12.0.0.1786	507.34 KB (519,520 bytes)	8/15/2011 6:21 AM
avgemca.exe	c:\program files (x86)\avg\avg2012\avgemca.exe	3012	8	200	1380	4/11/2012 8:07 AM	12.0.0.1854	1.52 MB (1,593,696 bytes)	9/21/2011 7:53 PM
avgidsagent.exe	c:\program files (x86)\avg\avg2012\avgidsagent.exe	2640	8	200	1380	4/11/2012 8:07 AM	12.0.0.1855	4.23 MB (4,433,248 bytes)	10/12/2011 7:25 AM
avgnsa.exe	c:\program files (x86)\avg\avg2012\avgnsa.exe	2972	8	200	1380	4/11/2012 8:07 AM	12.0.0.1883	1.90 MB (1,987,424 bytes)	11/28/2011 1:19 AM
avgtray.exe	c:\program files (x86)\avg\avg2012\avgtray.exe	3948	8	200	1380	4/11/2012 8:08 AM	12.0.0.1912	2.30 MB (2,416,480 bytes)	1/24/2012 5:24 PM
avgwdsvc.exe	c:\program files (x86)\avg\avg2012\avgwdsvc.exe	2172	8	200	1380	4/11/2012 8:07 AM	12.0.0.1773	188.26 KB (192,776 bytes)	8/2/2011 6:09 AM

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


Loading Dump File [D:\Kingston\BSODDmpFiles\Relough\Windows_NT6_BSOD_jcgriff2\041112-24616-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*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 Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`03296650
Debug session time: Wed Apr 11 03:57:35.815 2012 (UTC - 6:00)
System Uptime: 0 days 6:17:43.783
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004b66028, be200000, 5110a}

Probably caused by : hardware

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: fffffa8004b66028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  FahCore_a4.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fdda58 fffff800`0301ba3b : 00000000`00000124 00000000`00000000 fffffa80`04b66028 00000000`be200000 : nt!KeBugCheckEx
fffff880`02fdda60 fffff800`031deb33 : 00000000`00000001 fffffa80`052c2ea0 00000000`00000000 fffffa80`052c2ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02fddaa0 fffff800`0301b700 : 00000000`00000728 fffffa80`052c2ea0 fffff880`02fdde30 fffff880`02fdde00 : nt!WheaReportHwError+0x263
fffff880`02fddb00 fffff800`0301b052 : fffffa80`052c2ea0 fffff880`02fdde30 fffffa80`052c2ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fddc50 fffff800`0301af0d : 00000000`00000004 00000000`00000001 fffff880`02fddeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fddc90 fffff800`0300ee88 : 00000000`c17af80c 00000000`05a6bacc 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02fddcc0 fffff800`030cd56c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fddcf0 fffff800`030cd3d3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdde30 00000000`006d7fbe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`0360bb80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6d7fbe


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

FahCore_a4.exe is being blamed for the crash. The crash itself is a 0X124 crash.

• If you are overclocking any hardware, please stop.
  
  
• See http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for information about this crash. The following step may help supplement the information provided in that link.
  
  
• 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 a 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).
  
  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.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

 

[Relough]

Sorry, I thought I had included that with my system specs, but it appears I did not. I have an ASRock P67 Extreme4 B3 Intel P67 ATX DDR3 2133 Motherboard.

I am currently overclocking my cpu from 3.3 GHz to 4.3GHz, so I will reset it. However, I have tested it with Prime95, and all four cores made it through 12 passes before I stopped it. I also have been using Core Temp to monitor my cpu, and the highest I have ever seen temps go is 68C, while my Max is 98C (all while under full load). I have a feeling that it is probably due to my gpu, seeing as it has failed before while running f@h, and do to the error message I sometimes receive when my computer freezes, notifying me that my "display driver has successfully recovered."

Anyways, woke up this morning, and once again, my computer had crashed overnight. I've attached a new report.

 

[writhziden]

Your latest crash is nearly identical to the previous 124 crash with FahCore_a4.exe to blame.

While you are not getting the 0x116 crash, the display driver recovering message is a TDR error, which is what can cause 0x116 crashes. Recommend reading through http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

Please disable overclocking for the time being as it adds another variable to crashes that can make pinpointing the actual cause more difficult for us. Often, crash reports will blame the hardware that is overclocked rather than the true cause of the crash.


As for the RAM, we should check for incompatibilities with your board.

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.