Sign in with
Sign up | Sign in
Your question

Random BSODs.

Tags:
Last response: in Windows 7
Share
June 18, 2012 4:04:29 AM

HELP! I have been getting BSODs. I have reinstalled Windows and they didn't stop. I downloaded WhoCrashed and got this:

On Mon 6/18/2012 3:39:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061712-10077-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80076BF028, 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 which cannot be identified at this time.

Any suggestions?

Thanks.

More about : random bsods

a b $ Windows 7
June 18, 2012 4:21:59 AM

Listing the hardware might help.

Run memtest.
m
0
l
a b $ Windows 7
June 18, 2012 2:06:54 PM

This BSOD is typical of an unstable OC, overheating, or a damaged CPU (VERY unlikely). I'd start by removing any OC and checking temps.

Do any other BSOD messages come up, or just 0x124: WHEA_UNCORRECTABLE_ERROR?
m
0
l
Related resources
June 18, 2012 2:30:44 PM

Did you recently replace hardware such as the motherboard?

The indicator is the HAL.dll which Windows wraps itself around the hardware. There are some fixes available for such things but they're not guarenteed.

If you restored from an image on new hardware, this would be an expected issue.

Provide some more details on the situation.
m
0
l
June 19, 2012 4:37:55 AM

No recent addition in hardware ran memtest and it came up with no errors. I'm setting everything back to stock clocks, including setting my 6950 back to original bios. We'll see how that goes.
m
0
l
June 19, 2012 3:36:11 PM

No luck. Got the same BSOD.
m
0
l
a b $ Windows 7
June 19, 2012 4:54:56 PM

As I said above run memtest. Bad or incorrectly configured RAM could very well be the problem.

It would really help if you listed the hardware. It's really hard to guess what might be wrong with no information.

Have you checked your temps?
m
0
l
June 19, 2012 6:53:56 PM

As I said above, I ran memtest and got 0 errors. Do I have to run individual sticks? I ran all four.



Hardware:

2500k
MSI P67A C43 B3
6950 DiRT 3 Sapphire
2 sticks of GSkill Ripjaws 1600 Cas 8
2 sticks of Kingston Hyper X 1600 Cas 9 running @ cas 8
SSD: OCZ Agility 3 120 gb @ 2.22 firmware
HDDs: 1 Seagate 1tb programs, 1 WD 1tb media
Wireless: Asus pce - n10
Asus DVD drive
Antec 650w PSU




Temps are not the problem. They were fine overclocked and are now really low because of going back to stock clocks.







BSOD logs as of posting:

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

computer name: ANDREW-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8559640576 total
VM: 2147352576, free: 1901232128



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 6/19/2012 4:54:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061912-6754-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80076F5028, 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 which cannot be identified at this time.


On Tue 6/19/2012 4:54:40 AM 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, 0xFFFFFA80076F5028, 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 which cannot be identified at this time.


On Mon 6/18/2012 5:52:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061812-7628-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002CD21C0)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007661028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown WHEA_UNCORRECTABLE_ERROR




On Mon 6/18/2012 3:39:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\061712-10077-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80076BF028, 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 which cannot be identified at this time.



--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.





m
0
l
a b $ Windows 7
June 19, 2012 7:08:26 PM

Did you run memtest for at least 8 to 10 hours?

Mixed RAM stands out as a potential problem. Is it at 1.5v? I have also seen low cas RAM cause issues with P67 boards.

Try running just matched sticks. Try the cas 9 stuff by its self.
m
0
l
June 19, 2012 7:12:26 PM

Yes, it is at 1.5v. I ran for 8 hours. I added the hyperx ram a few months ago, along with the ssd. I'll run matched together overnight tonight, and the other set overnight tomorrow.
m
0
l
a b $ Windows 7
June 20, 2012 1:25:47 PM

Looks like CPU/mobo right now; 0x124 is typical one of these components failing in some way...

Check the voltages in the BIOS and make sure the CPU is getting its required juice. Remove any OC as well.
m
0
l
June 22, 2012 3:17:59 AM

So I started getting a different error. Here's the log:

On Fri 6/22/2012 3:08:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062112-7082-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x19 (0x3, 0xFFFFF80002E50F30, 0xFFFFF80002E50F32, 0xFFFFF80002E50F30)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.

So it's RAM?
m
0
l
a b $ Windows 7
June 22, 2012 4:23:45 AM

You can try uninstalling and reinstalling all your drivers and see if that helps. Are you still running the RAM mixed? Try setting all of it to 9-9-9-27 2T.
m
0
l
June 22, 2012 5:14:04 AM

And another:

On Fri 6/22/2012 4:40:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062212-6520-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80086EAB30, 0xFFFFFA80086EAE10, 0xFFFFF80002FD5510)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
m
0
l
!