BCCode 124 happening randomly
-
Wednesday, May 26, 2010 3:49 PM
Hi, for quite some time I'm getting mentally attacked by BCCode 124, it happens randomly and out of the blue...
every single of the memory dump has the same cause
System:
CPU: Core-i7 920 @ 2.7GHz
RAM: 5x1GB A-Data 1333MHz CL9 (currently set at 1066MHz CL8)
MOBO: Gigabyte GA-EX58-DS4 (rev 1.0)
Video: ATI Gainward HD4850 512MB
OS: Windows 7 x64 Ultimate==================================================
Dump File : 052610-42369-01.dmp
Crash Time : 2010.05.26 18:00:34
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`058c6028
Parameter 3 : 00000000`fa000000
Parameter 4 : 00000000`00400405
Caused By Driver : hal.dll
Caused By Address : hal.dll+12903
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052610-42369-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================Their appearance differs when changing BIOS settings, as I found that my CPU Core-i7 920 supports only 1066MHz RAM, but i have 5x1GB 1333MHz chips.
Optimized settings are auto(sets 1066MHz in BIOS), if I set it manually to 1333MHz it works, but for a short while, the BSOD appears and ruins the day.
If i lock PCI-E speed at 100MHz BSODs happen whenever they feel like, so i leave it auto.
I've been messing with BIOS a lot, some settings makes the BSOD appear only in games, which need a lot of resources(RAM, CPU, Video).
Today i had BSODs just when started windows booted up. Yesterday i had a BSOD while watching a movie and one while playing Lineage 2.
About 7 months before these BSODS were so bad that NO GAME was able to run without them, but after some time they vanished on most of the games, so i am assuming this is driver related, but don't know which one, i always install the newest drivers whenever they come out.
Another weird phenomenon is an invisible BSOD. For example: I'm playing a game(every occurrence of this was in-game) then suddenly screen changes to 1 color, usually something brown or the color that was most present in the image(i'm guessing this is a VPU crash, but there is no VPU-recovery in the Catalyst Control Center to test while it is on, so i don't know if it's ON or OFF
It would be wonderful if anyone could help me resolve this.
- Edited by IntoDEV Thursday, May 27, 2010 2:32 PM
All Replies
-
Wednesday, May 26, 2010 4:51 PM
Hi,
Bug Check 0x124 = WHEA_UNCORRECTABLE_ERROR
This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
http://msdn.microsoft.com/en-us/library/ff557321%28VS.85%29.aspx
Please upload the dmp files from your Windows\Minidump folder to your Skydrive (copy the dmp files first to your desktop, otherwise you can't upload them) and post a link here, so that we can look at the dumps.
best regards
André
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
Wednesday, May 26, 2010 8:49 PM
http://cid-cf7c79e295204b4a.skydrive.live.com/browse.aspx/MemDumps
all memdumps indicate the same problem, only one had something else, but i don't know if i still have it.
-
Wednesday, May 26, 2010 10:18 PM
Hi,
your Intel Xeon(R) CPU is damaged:
-------------------------------------------------------------------------------
Record Id : 01cafcb9501d20e4
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 5/26/2010 14:58:30
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa80058c60a8
Section @ fffffa80058c6180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Micro-Architectural Error
Flags : 0x00
CPU Version : 0x00000000000106a4
Processor ID : 0x0000000000000004
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa80058c60f0
Section @ fffffa80058c6240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000004
CPU Id : a4 06 01 00 00 08 10 04 - bd e3 98 00 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 @ fffffa80058c6240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa80058c6138
Section @ fffffa80058c62c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : Internal unclassified (Proc 4 Bank 5)
Status : 0xfa00000000400405Sadly, the cause is not readable. It only says internal unclassified.
Replace the CPU and your PC will work again.
best regards
André
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/- Proposed As Answer by Andre.ZieglerMicrosoft Community Contributor Wednesday, May 26, 2010 10:18 PM
-
Thursday, May 27, 2010 12:24 AM
how can my cpu be damaged if it works ok and most stress tests pass, also mine is not Intel Xeon(R) CPU, it's Core-i7 920
maybe overheat possible?
or maybe it's the incompatibility between i7 920 and 1333MHz RAM :@
after resetting BIOS i hadn't had a BSOD, i'll see what happens if i play Split/Second...
-
Thursday, May 27, 2010 3:07 AMModerator
This kind of issue is mainly related to hardware itself. You may need to update the BIOS and chipset driver. You can run the Intel® Driver Update Utility to detects the latest updates.
If the issue persists, to solid troubleshoot this kind of issue, I recommend you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently.
Best Regards
Dale
- Marked As Answer by Dale QiaoModerator Friday, May 28, 2010 2:07 AM
-
Thursday, May 27, 2010 10:56 AM
i always update to the newest drivers :)
i updated BIOS to F11(i had F9), and then load optimized defaults, set enhance performance from Turbo to Standard and the BSODs are no longer present, only that 1 color screen which is the mother of all weird stuff.
To ensure that CPU is not at fault, i'm running "CPU Stability Test 6.0", 20 minutes, system working normally, i'll leave it for 1 day to see how it does.
So i'm guessing that screen is not a BSOD, since when rebooted windows does not report an unexpected shutdown, when the screen appears num lock works(good for checking if computer is hung up or not) if i have music playing, it is playing and changes(computer is not hung up yet, the screen is hung up) but if i press alt+f4, alt+tab, ctrl+alt+del or any other combination, cpu hangs, num lock is not working, music still plays, but ends or starts repeating the last ms of sound, and it gets like "GDGHDGHDGHDHGDHGRGRRGRGRGRGRGRHGRRZGRZRGGZRHGRZGRHZRGHR" or something like that. My guess is, that the Video Memory or RAM is at fault. I check temperatures from time to time and MCH(Memory Controller Hub) is always at ~64C, recently i installed a Case Fan, temp dropped to 60(on high load, ~56 idle). i'll go test some other settings and i'll try to run memtest to see how it does :)
- Marked As Answer by Dale QiaoModerator Friday, May 28, 2010 2:06 AM
-
Thursday, May 27, 2010 12:35 PM
how can my cpu be damaged if it works ok and most stress tests pass, also mine is not Intel Xeon(R) CPU, it's Core-i7 920
Ok, I've used the CPUID command from WinDbg and I searched the ww for the Modell number and found that is it a Xeon. So the information on that site was wrong.
But it doesn't change anything. The CPU has an issue. Running a stability test for 20 minutes says nothing! The WHEA architecture is very reliable in reporting errors. Your CPU detects itself, I have an issue and sends it to Windows which generates this bug check to prevent your PC from being damaged!
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/ -
Thursday, May 27, 2010 2:31 PM
how can my cpu be damaged if it works ok and most stress tests pass, also mine is not Intel Xeon(R) CPU, it's Core-i7 920
Ok, I've used the CPUID command from WinDbg and I searched the ww for the Modell number and found that is it a Xeon. So the information on that site was wrong.
But it doesn't change anything. The CPU has an issue. Running a stability test for 20 minutes says nothing! The WHEA architecture is very reliable in reporting errors. Your CPU detects itself, I have an issue and sends it to Windows which generates this bug check to prevent your PC from being damaged!
"A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
well if you read my whole post, you should have noticed that my CPU(as stated in the intel website supports 1066MHz RAM, but not 1333MHz) and my ram are 1333MHz and all current issues are memory related, i'm leaning towards MCH, since it's heating a lot(my video card is on top of it, so it does not have a lot of breathing room) and these errors disappear more or less when i update drivers for video or BIOS, today i loaded optimized defaults for the new BIOS that i installed today, and just disabled memory enhance(from turbo to standart) the BSODs no loger appear like previously, they appear if i mess with RAM or PCI-E settings, i'll check RAM chips and connections for any damage. A couple of times when i opened the case i've accidentally spilled my blood somewhere in the mobo(lol) s i'll check the mobo for stains, since one time it was on the case, but the first time(before the BSODs and creepy 1 color screens) i've not found any stains on the case, so i think there is a possibility that i spilled some on the mobo or on some critical parts, i usually strangely cut myself when taking out ram chips...this is kinda stupid. well, my BSODs problems are solved, so i think this BSOD issue can be called solved, since no the only weird thing left is the 1 color screen, but i think it might be a VPU error and i dont have the option to turn it on or off, on Windows 7 Beta version i did not have these errors, but i did have VPU crashes from time to time(the vpu recovery was working for some reason). But since i started using RC1 and further versions this weird stuff started to happen. so as i can say for now, this is stilla mystery for me. I'll update this post if i'll find the cause of this phenomenon. Now i'm going to install the new ATI 10.5 drivers that have been released yesterday. -
Friday, May 28, 2010 2:06 AMModerator
Firstly, I’m glad to see that BSOD issue is resolved.
BTW, as the 1 color screen issue, it can be caused by the graphic driver, display cable or motherboard. Please try other version of graphic driver and check the display cable connecting between the display and host computer, make sure it is well connected. Maybe you could test the standard display driver to see if the issue persists:
1) Click "Start", type "DEVMGMT.MSC" in the Search textbox and press Enter.
2) Expand "Display adapters".
3) Right click on your Graphic Card, select "Properties"
4) Click "Driver" tab, click Disable (Disable the selected device). Click OK
5) Please restart the computer.
Best Regards
Dale
-
Friday, May 28, 2010 8:51 AM
This did not help me to test if it's the drivers, because that weird thing happens only in gaming(mostly new games), whenever a game comes out there is like a 50% chance that it will work perfectly or with that weird thing, the screen either turns black(power saving mode) or changes to a random colo, computer does not hang, until i request something with a keyboard shortcut. I installed new drivers, i'll go test right now :)Firstly, I’m glad to see that BSOD issue is resolved.
BTW, as the 1 color screen issue, it can be caused by the graphic driver, display cable or motherboard. Please try other version of graphic driver and check the display cable connecting between the display and host computer, make sure it is well connected. Maybe you could test the standard display driver to see if the issue persists:
1) Click "Start", type "DEVMGMT.MSC" in the Search textbox and press Enter.
2) Expand "Display adapters".
3) Right click on your Graphic Card, select "Properties"
4) Click "Driver" tab, click Disable (Disable the selected device). Click OK
5) Please restart the computer.
Best Regards
Dale
-
Saturday, May 29, 2010 10:46 PM
At the moment the problem is solved :)
It was due to incorrect BIOS Settings.Previous settings: BCKL 133, SPD 8.0, Multiplier(CPU) 20 = 1066MHz RAM and 2.6GHz CPU
Current settingsL BCKL 166, SPD 8.0, Multiplier(CPU) 16 = 1333MHz RAM and 2.6GHz CPUif i re-encounter the problem in the future i'll post here :) or i'll go to intel or gigabyte forums to continue solving this problem, but for now thanks for the help you gave.
- Marked As Answer by Dale QiaoModerator Sunday, May 30, 2010 3:52 PM
-
Tuesday, February 21, 2012 8:34 PM
Hi,
I am having the same issue code 124 just wondering if someone can read the dmp file and inform me of the error.
Here is a skydrive link
-
Friday, February 24, 2012 11:39 PMModerator
This crash was related to your intelppm.sys driver.
Other contributing factors
Old \drivers
SSPORT.sys 8/11/2005 6:07:32 PM fffff880`0a1e5000 fffff880`0a1ed000 0x00008000 0x42fbda34
SiWinAcc.sys 6/14/2007 7:02:02 PM fffff880`01614000 fffff880`0161d000 0x00009000 0x4671d6fa
SiRemFil.sys 6/20/2007 2:42:10 PM fffff880`02246000 fffff880`0224e000 0x00008000 0x46798312
ALSysIO64.sys 4/19/2009 2:41:04 PM fffff880`0c914000 fffff880`0c91c000 0x00008000 0x49eb7e50
IOCBIOS.SYS 7/9/2009 12:47:22 PM fffff880`09ce7000 fffff880`09cf1000 0x0000a000 0x4a562d2aYour .dmp file shows a stop error of 0x124 which is a general hardware error .A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress
Some generic advice.If you are overclocking STOP. Return to the default settings at least for now.If you are running a RAID update its driver.You can read more on this error and what to try here.. .http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html
-
Wednesday, February 29, 2012 7:36 PM
Thanks for the response, oddly enough I haven't had the issue come up again since that day wherein it occured 3 times in a row.
But thanks again.
Best regards
-
Friday, April 13, 2012 3:49 AM
Hi, my system has been randomly crashing for the last few months and nothing I do seems to help. I installed the latest drivers, replaced RAM and PSU, and updated the BIOS to it's most current release. I'll be doing something as simple as opening a webpage and suddenly my system will either freeze and repeat the last sound it played on hyper fast playback or BSOD and restart or just go black and restart. While monitoring my CPU/GPU temps I'm not seeing anything outrageous while it's under load. Hours of MEMTEST86 being run in various RAM configs are showing nothing and FURMARK isn't bringing my system down either. I've tried almost every variable in BIOS to try and increase stability and no change.
I'm completely out of ideas here. I feel like declaring it a brick and a terrible idea that I built my own system. Any ideas out there? I love my system when it's running right but I hate that I feel like I can never trust it.
CPU: Intel Core-i7 870 @ 2.93GHz
Here's the dmp file. https://skydrive.live.com/redir.aspx?cid=a1c27f4610e7b84b&resid=A1C27F4610E7B84B!113&parid=A1C27F4610E7B84B!111
RAM: 4x4GB 1600MHz Corsair XMS3
MOBO: Gigabyte GA-P55A-UD3R (rev 2.0)
Video: NVIDIA GTX 560 TI
OS: Windows 7 x64 Ultimate
- Edited by Grevin Friday, April 13, 2012 4:09 AM
.png)
