Sign in with
Sign up | Sign in
Your question

Weekly BSOD with BCCode 124

Tags:
  • Windows 7
  • Crash
  • troubleshooting
Last response: in Windows 7
Share
April 30, 2014 6:38:56 AM

I've been getting weekly BSODs for months now, about once a week, and I can't figure out why. I know many people get BSODs because of RAM issues, and that may be a possibility. However, it started around the same time I started having problems with my USB ports.

After overclocking my PC, my USB ports would often not work upon booting, or would stop working shortly after. I solved this, oddly, by disabling the Bluetooth functionality in my motherboard settings, after which it worked fine for a while. Lately, these crashes have resurfaced, and I'm not sure why. Weirder still, after the crashes, I'll reboot my PC and half the time the computer won't send signals to my monitors, and I'll have to reboot it again, maybe even twice more, to get it sending a signal via DVI to my monitors. I have two 560TI graphics cards in SLI.

Also with regards to the USB issue, sometimes my external hard drive and USB microphone will not be recognized on boot. Weirdly enough, if I unplug the microphone (which is plugged in but not recognized) and keep plugging/unplugging until it finally is recognized (the connection is certainly damaged inside the mic, it's taken many falls over the years), my external HD will suddenly be recognized as well and the "Searching for Content" dialog box will appear and start scanning the drive (which has many bad sectors and is also damaged).

I've also noticed the crashes coincide with video playback: they usually happen when I'm playing a video in VLC or when I'm cutting a video in Sony Vegas, though this isn't an absolutel

If I do format my drive to reinstall Windows, I won't lose anything I keep on my F: or H: drives, will I? Windows will still recognize the drives/folders and such?

Also, whenever my computer boots, there'll be an ASUS boot screen that says I can press Del to get to the BIOS, but I can't. This goes to a black screen that says:

JMicron Technology Corp. PCI Express to SATA II HOST Controller ROM v1.07.23
Copyright 2005-2010 JMicron Technology Corp.
Detecting Drives: Done: No Drives Found._

It disappears almost instantly and is replaced by the same ASUS boot screen, except now I can actually press Del to go to BIOS. Is this normal behavior and is this possibly affecting my PC?

Any help you guys can provide is appreciated.

Here is the debug info on the most recent crash:

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

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


Here is the WhoCrashed report for the last two months' worth of crashes:

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: SWAGMACHINE
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8Z68-V GEN3
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17145413632 total
VM: 2147352576, free: 1885560832




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 4/30/2014 1:03:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\043014-7254-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D40F028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 4/30/2014 1:03:25 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D40F028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 4/21/2014 1:45:02 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042014-9001-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41284, 0xFFFFF900C50D9001, 0x777, 0xFFFFF90000812000)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 4/18/2014 5:43:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041814-8143-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D51D028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Fri 4/11/2014 10:09:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041114-9781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004ED41F0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 3/20/2014 6:48:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032014-8377-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D51D028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 3/1/2014 11:01:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030214-7207-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8004ED41F0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 2/28/2014 4:26:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022814-8034-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800D4B6028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: 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).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


---------------------

So, there it is. Any idea what the problem might be?

More about : weekly bsod bccode 124

April 30, 2014 7:50:42 AM

BCCode 124 is usually hardware (or power) related. But seeing as how you are having issues with your USB ports, and your drives aren't being detected part of the time, would lead me to believe your motherboard is dying.
m
0
l
April 30, 2014 7:57:58 AM

It's not a lack of power supply (I have 1200W), but there may be a bad connection in my motherboard somewhere, specifically with regards to my USB ports, it's true. Could there be something preventing my mobo from receiving adequate power?
m
0
l
!