BSOD Killing me

[Mdb173]

DMP FILES

https://skydrive.live.com/redir?resid=2F4CF9D4E534095D!124



Hey guys. I am new to the forums, but was hoping for some help.

I have not installed any new hardware, but for some reason my computer started to get these BSODs

It started yesterday slowly, and has now been speeding up to every hour or so. I can be doing anything.

They always happen to be something like 0x0008004 or something like that, and tell me it is a hardware failure.

I have not installed anything new however, and i am nearly positive all my hardware is still working, it is a year old computer.

I have attatched the dmp files. Thank you !!!


SPECS:

Windows 7 Ultimate 64-bit

P67A-UD4-B3

BIOS: Award Modular Bios v6.00PG
Processor: Intel i7 2600k sandy bridge 3.4 ghz
Memory: Corsair 16 gb
Video Card: Hawk Radeon 5770

Thank you for the help!

 

[C12Friedman]

I'm going to point my finger in two directions here (tricky huh?). One, memory. Go through your memory modules one at a time running memtest. Two, PSU check all of your power connections, swap out PSU with known working one (if possible)
Good luck

 

[gamerk316]

Download Bluescreenview and post what the BSOD STOP code/error message is.

In the meantime, running memtest86+ for a few passes would be a good first step.

 

[Mdb173]

Here is what it says

Here is some of what BlueScreen viewer said

hal.dll hal.dll+12a3b fffff800`02a15000 fffff800`02a5e000 0x00049000 0x4ce7c669 11/20/2010 8:00:25 AM
ntoskrnl.exe ntoskrnl.exe+18cb03 fffff800`02a5e000 fffff800`03046000 0x005e8000 0x4fa390f3 5/4/2012 3:18:59 AM Microsoft® Windows® Operating System NT Kernel & System 6.1.7601.17944 (win7sp1_gdr.120830-0333) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe


121412-45349-01.dmp 12/14/2012 11:12:30 AM 0x00000124 00000000`00000000 fffffa80`0e3c6028 00000000`be000000 00000000`00800400 hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121412-45349-01.dmp 8 15 7601 274,808
121412-19359-01.dmp 12/14/2012 11:04:22 AM 0x00000124 00000000`00000000 fffffa80`0e350028 00000000`be000000 00000000`00800400 hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121412-19359-01.dmp 8 15 7601 274,808
121412-25896-01.dmp 12/14/2012 4:04:39 AM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`81d82c08 00000000`00000000 fffff800`02a9fb38 00000000`00000005 hal.dll hal.dll+7b7f x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121412-25896-01.dmp 8 15 7601 274,808
121412-19312-01.dmp 12/14/2012 3:16:55 AM 0x00000124 00000000`00000000 fffffa80`0e308028 00000000`be000000 00000000`00800400 hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121412-19312-01.dmp 8 15 7601 274,808
121412-34476-01.dmp 12/14/2012 2:30:02 AM 0x00000124 00000000`00000000 fffffa80`0e21b028 00000000`be000000 00000000`00800400 hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121412-34476-01.dmp 8 15 7601 274,808
121412-21574-01.dmp 12/14/2012 2:16:18 AM 0x00000124 00000000`00000000 fffffa80`0e1f4028 00000000`be000000 00000000`00800400 hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121412-21574-01.dmp 8 15 7601 274,808
121412-21606-01.dmp 12/14/2012 2:12:49 AM 0x00000124 00000000`00000000 fffffa80`0e240028 00000000`be000000 00000000`00800400 hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121412-21606-01.dmp 8 15 7601 274,808
121412-18829-01.dmp 12/14/2012 12:12:35 AM 0x00000101 00000000`00000019 00000000`00000000 fffff880`009b3180 00000000`00000004 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121412-18829-01.dmp 8 15 7601 274,808
121312-24632-01.dmp 12/13/2012 10:46:51 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`85c0e170 00000000`00000000 fffff800`02af6b38 00000000`00000005 hal.dll hal.dll+7b7f x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121312-24632-01.dmp 8 15 7601 274,808
121312-32495-01.dmp 12/13/2012 10:40:30 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`844090a8 00000000`00000000 fffff800`02af1b38 00000000`00000005 hal.dll hal.dll+7b7f x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\121312-32495-01.dmp 8 15 7601 274,808
112512-21138-01.dmp 11/25/2012 12:39:57 PM 0x00000101 00000000`00000019 00000000`00000000 fffff880`009b3180 00000000`00000004 ntoskrnl.exe ntoskrnl.exe+7efc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.17944 (win7sp1_gdr.120830-0333) x64 ntoskrnl.exe+7efc0 C:\Windows\Minidump\112512-21138-01.dmp 8 15 7601 274,808
092912-22588-01.dmp 9/29/2012 7:04:33 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`8566d998 00000000`00000000 fffff800`02af8d48 00000000`00000005 hal.dll hal.dll+7b7f x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\092912-22588-01.dmp 8 15 7601 274,808
080712-24960-01.dmp 8/7/2012 10:16:40 PM PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 ffffffff`859120a8 00000000`00000000 fffff800`02aa6d48 00000000`00000005 hal.dll hal.dll+7b7f x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\080712-24960-01.dmp 8 15 7601 274,728
080712-32385-01.dmp 8/7/2012 8:28:49 PM 0x00000124 00000000`00000000 fffffa80`0e1f7028 00000000`be000000 00000000`00800400 hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7f1c0 C:\Windows\Minidump\080712-32385-01.dmp 8 15 7601 274,728

 

[Mdb173]

I just read this: http://answers.microsoft.com/en-us/windows/forum/windows_7-system/asus-bsod-haldll-stop-0x124/1f50097f-af6b-4888-a593-f3ff3e91c245

What i gathered from it, is that when turning on my M-Audio Profire 2626 a few times a day, (recording studio computer) something must have gotten messed up.

When i think of it actually, the profire caused the first 2 BSOD's 0x050 and then immediately after i started getting these new 0x0124 ones.

If i just uninstall and reinstall the drivers, would that be sufficient?

Hal.Dll is my big problem apparantly

 

[Mdb173]

I was seriously begining to think the problem is the Texas Instruments 1394 OHCI Complement Host Controller. That something must have gotten corrupted.


However I switched drivers from the Texas instruments 1394, to the Legacy one. While my profire would not work then, I figured that would solve the crash.

Unfortunately, after about 20 minutes my computer got the same BSOD, making me believe the problem is infact something with the profire drivers... maybe, hopefully?

The whole time however, I kept the M-audio drivers installed, and had the profire connected and on. While it was not working because I was not using the drivers it needed (TI 1394) it still was installed.




In my computer I use a LaCie FW400 PCI card. Connected to that via firewire is my audio interface, (Profire 2626) After uninstalling both the profire's drivers, and the OHCI drivers, the problem seems to be gone for the most part. However, once I reinstall the profire drivers I get a blue screen fairly quickly. Is there a workaround or something anyone can think of?

The LaCie's manual states this :"The PCI card has drivers built into the BIOS for these operating system "

Does that mean I should maybe change something in the BIOS FW section?

 

[gamerk316]

Looks like a CPU problem. 0x124 typically indicates an unstable CPU, and 0x101 is VERY rare; only time I've ever seen it happen is when the CPU or GPU overheats. The PAGE_FAULT BSOD's indicate RAM, but I'm not convinced thats the root problem.

First and formost, make sure the CPU settings in the BIOS are correct, and make sure nothing is overheating.

Failing that, run memtest86+. I don't think this is a memory problem, but it wouldn't hurt to check just to make sure.

 

[Mdb173]

Looks like a CPU problem. 0x124 typically indicates an unstable CPU, and 0x101 is VERY rare; only time I've ever seen it happen is when the CPU or GPU overheats. The PAGE_FAULT BSOD's indicate RAM, but I'm not convinced thats the root problem.

First and formost, make sure the CPU settings in the BIOS are correct, and make sure nothing is overheating.

Failing that, run memtest86+. I don't think this is a memory problem, but it wouldn't hurt to check just to make sure.

Hmmmmm..Nothing has changed at all though. That is why this is weird. My computers heat remains at 33 degrees celsius and i havent touched the bios. I would be very suprised though if the cpu just started to fail all of a sudden. While i am not writing that off as possible, it would actually shock me as the probability is relatively low. Memtest ran for hours and had no errors thoughh. Is there any solutions u maybe can think of? A different set of bios i can install or any things you can maybe think of? I tried a system restore, seemed to be working well, and then died again. The problem never happened in safe mode. Anyways, i really do appreciate your help!!

 

[gamerk316]

Didn't think it was RAM...

My main concern are the 0x124 and 0x101 BSOD messages. Its VERY unlikely Software would cause the 0x101 (CLOCK_WATCHDOG_TIMEOUT), and 0x124 (WHEA_UNCORRECTABLE_ERROR) is generally a symptom of an underpowered or overheating CPU. Its possible the PSU could be at fault, especially if its a cheap/old model. Also could be motherboard related.

 

[Mdb173]

Didn't think it was RAM...

My main concern are the 0x124 and 0x101 BSOD messages. Its VERY unlikely Software would cause the 0x101 (CLOCK_WATCHDOG_TIMEOUT), and 0x124 (WHEA_UNCORRECTABLE_ERROR) is generally a symptom of an underpowered or overheating CPU. Its possible the PSU could be at fault, especially if its a cheap/old model. Also could be motherboard related.

The computer is only a year old and all the specs were top notch at the time. I made sure to buy the highest quality stuff with the lowest chance of failing, but also made sure everything was going to run smoothly and be powerful enough for eachother.


Butt interestingly enough,
I was looking through my Bios, and I had everything set on the standard mode. But for some reason, there was some tab asking if I wanted my computer to go above the normal speed. It had Auto selected, and I changed that to disabled. I will see if maybe that works, but so far it has been running smoothly.

I also had RAM set to 1600 for some reason, but i changed that to 1333. I am going to see if maybe this makes any difference, but hopefully it does? Thanks again for taking the time to help me man



-Mike