Sign in with
Sign up | Sign in
Your question
Closed

BSOD BCCode 124

Last response: in Windows 7
Share
January 26, 2012 6:18:05 PM

Been having issues with BSOD here is the info:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800DD668F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

It happens when i play games mostly but sometimes when its idle. playing graphics intensive games cause it to bsod fairly fast but it also does this on games that are not. left idle it will blue screens about 1 every 9 hours but if i'm doing anything like watching videos or surfing the web it blue screens roughly every 2-4 hours. my drivers are all updated using the lates bios on my motherboard. Using a xfx radeon 5850 BE clock speed is 775/1125. if anyone has any idea why this is happening i would appreciate some insight into this issue.

my system:

MB: ASUS Sabertooth 990FX AM3+ (bios version 0901)
http://www.newegg.com/Product/Prod [...] 6813131736

CPU: AMD FX-8120 3.1ghz
http://www.newegg.com/Product/Prod [...] 6819103961

RAM: CORSAIR Vengeance 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 1600 (currently running at 1333mhz)
http://www.newegg.com/Product/Prod [...] 6820233143

PSU: PC Power and Cooling Silencer 760W High Performance 80PLUS Silver SLI CrossFire ready Power Supply
http://www.newegg.com/Product/Prod [...] 6817703030

GPU: XFX Radeon 5850 BE

HD: seagate 700gb <-- don't know all the specs had it for over 3 years now

OS: Windows 7 professional sp1

More about : bsod bccode 124

a b $ Windows 7
January 26, 2012 6:41:35 PM

Can you provide the mini dump information? It should look something like this:

Files that help describe the problem:

C:\Windows\Minidump\050610-22713-01.dmp

But off the top of my head - it sounds like RAM problems. Have you tried running memtest86? If you have - and there are errors, try 1 memory stick at a time.
January 27, 2012 3:11:56 AM

Chainzsaw said:
Can you provide the mini dump information? It should look something like this:

Files that help describe the problem:

C:\Windows\Minidump\050610-22713-01.dmp

But off the top of my head - it sounds like RAM problems. Have you tried running memtest86? If you have - and there are errors, try 1 memory stick at a time.


As for the memory sticks being the issue i ran memtest on them last night for a full 9 hours with no errors i also ran prime95 today for 12 hours with no errors but as soon as i ran furmark the computer shut down. I'm beginning to think it has something to do with the video card. As for the minidump here is the info.

1st:
012612-29608-01.dmp
1/26/2012 4:58:18 PM
0x00000124
00000000`00000000
fffffa80`0e67c038
00000000`00000000
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+4b16cc
NT Kernel & System
Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7601.17640 (win7sp1_gdr.110622-1506) x64
ntoskrnl.exe+4b16cc
C:\Windows\Minidump\012612-29608-01.dmp
8
15
7601
262,144

2nd:
012612-38984-01.dmp
1/26/2012 2:53:30 PM
0x00000101
00000000`00000019
00000000`00000000
fffff880`02fd7180
00000000`00000003
atikmdag.sys
atikmdag.sys+102cff
x64 ntoskrnl.exe+7cc40
C:\Windows\Minidump\012612-38984-01.dmp
8
15
7601
276,152

3rd:
012612-31590-01.dmp
1/26/2012 12:32:00 AM
0x00000124
00000000`00000000
fffffa80`0e60b028
00000000`f0800000
00000000`00010e0f
hal.dll
hal.dll+12a3b
x64 ntoskrnl.exe+7cc40
C:\Windows\Minidump\012612-31590-01.dmp
8
15
7601
276,152

these are all within 1 week i started getting these issues on 1/19/2012
Related resources
Can't find your answer ? Ask !

Best solution

a b $ Windows 7
January 27, 2012 12:56:14 PM
Share

Your first error appears to be caused by an actual BSOD from the ntoskrnl.exe. Do you have a Win 7 DVD that you could try doing a repair on your system?

The second BSOD appears to be caused by your Video card drivers "atikmdag.sys". Can you try deleting your drivers, and installing a fresh copy? You may need to sweep your system of old drivers first though. I believe driver sweeper can do this.

Lastly, your 3rd BSOD is related to your Hardware Abstraction layer (hal.dll) and the ntoskrnl. So one of the pieces of your hardware does not seem to agree with what you were doing. This can point to a few things - possibly BIOS problem, or even something wrong with your HDD (bad sectors possibly).

Open up your command prompt as administrator - and type this in sfc /scannow
January 27, 2012 1:32:52 PM

Chainzsaw said:
Your first error appears to be caused by an actual BSOD from the ntoskrnl.exe. Do you have a Win 7 DVD that you could try doing a repair on your system?

The second BSOD appears to be caused by your Video card drivers "atikmdag.sys". Can you try deleting your drivers, and installing a fresh copy? You may need to sweep your system of old drivers first though. I believe driver sweeper can do this.

Lastly, your 3rd BSOD is related to your Hardware Abstraction layer (hal.dll) and the ntoskrnl. So one of the pieces of your hardware does not seem to agree with what you were doing. This can point to a few things - possibly BIOS problem, or even something wrong with your HDD (bad sectors possibly).

Open up your command prompt as administrator - and type this in sfc /scannow



I did a fresh install of windows last night since i couldn't use my windows 7 cd to repair the ntoskrnl.exe. i have yet to stress my system which i will do today and tomorrow to check for stability. After running the sfc /scannow it found no integrity violations. i will update you if there is another bsod
a b $ Windows 7
January 27, 2012 1:50:59 PM

Alright sounds good. Hopefully it doesn't crash on you again after the fresh install.
a b $ Windows 7
January 27, 2012 2:06:29 PM

Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

Basically, a hardware problem. The reason the Kernal crashed is because it tried to handle a General Protection Fault caused by the problem, and crashed in the process. Hence, the BSOD blames the Kernal. [BSOD's are almost always double faults, so you see the Kernal and key system drivers 99% of the time on BSOD's].

Odds are, its the GPU.

a b $ Windows 7
January 27, 2012 2:07:47 PM

As an aside, I'm getting REALLY tired of the starting advice of "Format the entire system". This makes it much harder to track down the real issue, since the majority of BSOD's are either driver related, OC related, or hardware related. I'm still astounded people don't actually look at the error message and figure out what hte problem actually is before trying to fix it...
a b $ Windows 7
January 27, 2012 2:13:56 PM

@gamer Stuff happens :p 

Oh well, hopefully the OP gets the issue fixed with his install. Sometimes it is just easier to do a fresh install than to try and go through pages and pages of error information.

I've done that before...try and troubleshoot something - unable to troubleshoot it (after spending too many hours on it), and a fresh install was much quicker than troubleshooting the issue.
January 29, 2012 7:48:14 AM

@gamerk316

I didn't want to reformat my whole system it was kinda a last ditch effort in fixing the issue. The BSOD's were going on for a good week before i finally posted on the forums for help. i looked everywhere some sites said it was a driver issue and to update drivers and bios, i spent 1 1/2 days trouble shooting the issue with drivers, reading info. on it and going through my system clearing out drivers and updating but that did not solve the issues. others said it was a hardware issue to check my ram, cpu, power supply, was i getting enough airflow(2 120mm scythe slipstream 130cfm intake, 1 120mm scythe slipstream 130cfm exhaust and a corsair H80 in push pull intake in a nzxt m59 case) temps read low 20s to low 40s across the board cpu idles at 11c-17c full loads at 19c-24c only thing that is even considered kind of hot is my gpu at 44c. So i spent another day taking apart my new system cleaning out all the fans (very little dust) and reassembling the fans no change in bsods. As for the ram i ran memtest on them for 9 hours straight no errors took each one out of my system used dust off on all the sockets incase there was something there. tested each stick in each slot, none failed to boot but all triggered memok function and was downclocked to 1333mhz talked to corsair they said it wasn't a memory stick issue and for me to talk to asus (still waiting to get a response) CPU is brand new no issues with it so far i have yet to try overclocking since its pointless without a stable pc. took my PSU out and tested it in my brother in laws PC it booted fine no issues. others said it was my gpu and that the memory on the card was going bad thats why when i play any games it would bsod fairly quickly, no idea how to trouble shoot that issue mostlikely a rma since i have lifetime warranty on the card but again waiting on a response from my ticket to xfx.

@Chainzsaw

After the fresh install and driver updates i ran prime95 9 hours no issues, furmark 4 hours no issues then i started the windows updates and now i'm getting BSOD now could it be because one of the updates or a few of the updates are bad and is affecting my system? checked all my drivers they are the same but i'm getting the same BSOD erros bccode 124 with hal.dll and ntoskrnl.exe


012912-31387-01.dmp
1/29/2012 12:51:31 AM
0x00000124
00000000`00000000
fffffa80`0e612028
00000000`f4800000
00000000`00020e0f
hal.dll
hal.dll+12a3b
x64 ntoskrnl.exe+7cc40
C:\Windows\Minidump\012912-31387-01.dmp
8
15
7601
276,152

012812-26410-01.dmp
1/28/2012 3:09:16 PM
0x00000124
00000000`00000000
fffffa80`0dd7f8f8
00000000`00000000
00000000`00000000
ntoskrnl.exe
ntoskrnl.exe+4b16cc
NT Kernel & System Microsoft® Windows® Operating System
Microsoft Corporation
6.1.7601.17640 (win7sp1_gdr.110622-1506) x64
ntoskrnl.exe+4b16cc
C:\Windows\Minidump\012812-26410-01.dmp
8
15
7601
262,144

i'm all out of ideas unless i go back to me restore point and install 1 windows update at a time till i find out what is causing these issues. Thanks for the help btw i appreciate it.

a b $ Windows 7
January 29, 2012 3:00:42 PM

Ouch. I'm also running out of ideas for you to try out. Your HAL.dll is a hardware problem - so one piece in your whole system is messing up, and it sounds like it's from a windows update as well.

It may be highly possible theres a windows update that doesn't agree with your system. I know there has been 4 updates released since December from Microsoft in relation the Zambezi/bd that supposedly increase performance a little, the first 2 were supposed to have ben withdrawn as they weren't ready, but the 2 released not too long ago (this month) haven't been withdrawn yet - I wonder if you accidentally somehow got those old updates?

It might take a long time to go through the windows updates 1 at a time, but it might be the only way to find out which update (if it indeed is an update), that is causing the bsod.

I don't know if you tried this yet....but can you shut off your comp, unplug it from the wall, and take out the CMOS battery (from motherboard), and leave it off for a good 15 minutes? For some reason I dont think this will work, but worth a shot if you haven't already.
February 5, 2012 2:34:11 AM

I went through each update and installed 1 by 1. found 2 errors with the updates for bd processors once i deleted them and installed them in the correct order i stopped getting blue screens. I don't know if that was what was causing the issue but i had to shut off turbo core function and all power saving functions cause some people here in my town were saying that it was causing my pc to overclock when it needed more processing power and was causing it to bsod. I am not sure if that is correct but i don't know how and auto overclock by the cpu can cause my system to bsod, wouldn't the auto overclock only overclock to a safe speed? and what is with the power saving functions i was told that it will lower my voltage to save power but that could cause my system to fail. How does that happen if i do not overclock my cpu? why would a overclock effect a display driver? wouldn't there be a different error with an overclock? why would a powersaving function cause a hardware issue? not getting enough voltage? if that is the cause why do we have a power saving functions built in? Well this just brought out more questions. so as of now my system has been stable for about 6 days prime95, furmark, and memtest shows no errors. and i have not recieved any further bsods. I am still getting the mem ok successfully booted your system error everytime i shut down and restart. still waiting on asus man there customer support is slow. I am still waiting for xfx to reply to see if it was a hardware issue with the video card but they are also slow to reply. anyways thanks for the help chainsaw.
February 5, 2012 2:36:40 AM

Best answer selected by wooshna.
a b $ Windows 7
February 5, 2012 11:59:54 AM

This topic has been closed by Nikorr
!