BSOD Problems, Please help!

[epain]

Ok so I've been getting occasional BSOD's with the 124 error. I'm new to using WinDbg and after analyzing two dump files I believe that I have a faulty processor (I've owned this one since Black Friday and this problem has only recently started to occur). It should be noted that everything is at stock settings as well.

System Specs:
OS: Windows 8.1 Pro 64 Bit
CPU: Intel Core i7 4770k CPU @3.50 GHz
RAM: Crucial Ballistix Sport 8GB DDR3 1600 2x4
PSU: Corsair TX 650M
SSD: Samsung 840 EVO 120 GB
HDD: WD Caviar Blue 1TB 7200RPM
MOBO: Gigabyte GA-Z87X-UD4H running the latest BIOS version F9

dropbox link to dump files here:
https://www.dropbox.com/sh/bn8vmyevstnzbgb/zqCZ-9aRsf

[Volbet]

As far as I can tell your problem is with ntoskrnl.exe and hal.dll, both of which indicates a hardware fault.

 

If you have an overclock on anything, scale it back to the factory setting. Also monitor your CPU temperature while you are in Windows.

If non of these show anything out of the ordinary, try running Memtest86+, for 4-6 passes, just to check the RAM.

[epain]

As far as I can tell your problem is with ntoskrnl.exe and hal.dll, both of which indicates a hardware fault.

 

If you have an overclock on anything, scale it back to the factory setting. Also monitor your CPU temperature while you are in Windows.

If non of these show anything out of the ordinary, try running Memtest86+, for 4-6 passes, just to check the RAM.

 

My CPU temps are attached. They seem reasonable...

 

[Volbet]

My CPU temps are attached. They seem reasonable...

They do seem quite alright. How are they under load?

I would still recommend you to test the RAM, since ntoskrnl.exe usually indicates a RAM or driver error, and the RAM error is easier to find. 

[epain]

They do seem quite alright. How are they under load?

I would still recommend you to test the RAM, since ntoskrnl.exe usually indicates a RAM or driver error, and the RAM error is easier to find. 

 

Oh man, I thought that my CPU was faulty cause when I used WinDbg I was getting a Cache Error with a 124 bug labeled "GenuineIntel."

I hope it's just ram as that's way easier to replace and cheaper too in the even that warrenty doesn't cover it.

[Volbet]

Oh man, I thought that my CPU was faulty cause when I used WinDbg I was getting a Cache Error with a 124 bug labeled "GenuineIntel."

I hope it's just ram as that's way easier to replace and cheaper too in the even that warrenty doesn't cover it.

It can be that the CPU is faulty, but that is a rare event in my experience. It's more likely that it's a RAM problem, but I can't rule out the CPU 100%.

It could also the the motherboard, but that is usually a different error.

[epain]

Ok, I'm running memtest86+ right now. A Tom's Hardware forum member recommended that I enable XMP but as the error has been occurring with XMP disabled, I am running Memtest86+ in that state. I'll report back what I find. As well as load CPU temps. I should also not that while the error has occurred seemingly randomly, the last two times it has crashed my comp, I was running League of Legends and a Google Talk call.

[epain]

It can be that the CPU is faulty, but that is a rare event in my experience. It's more likely that it's a RAM problem, but I can't rule out the CPU 100%.

It could also the the motherboard, but that is usually a different error.

 

Ok, I'm running memtest86+ right now. A Tom's Hardware forum member recommended that I enable XMP but as the error has been occurring with XMP disabled, I am running Memtest86+ in that state. I'll report back what I find. As well as load CPU temps. I should also not that while the error has occurred seemingly randomly, the last two times it has crashed my comp, I was running League of Legends and a Google Talk call.

 

 

Memtest86+ ran for 5 passes with no errors, going to ran prime95 for a bit and got these load temps:

 

 

My fans are never working this hard when my computer crashes so I don't think that CPU temps have anything to do with it, but I'm relatively new to this and could be wrong.

[Volbet]

Memtest86+ ran for 5 passes with no errors.

OK, doesn't seem like it's a RAM error. 

To rule out the software aspect, you can try to run the PC in safe mode for a while. If it still BSoDs in safe mode, it's most likely a hardware error, and if it doesn't, it's most likely a software error.

 

Edit: And your load temps seem fine aswell.

[epain]

OK, doesn't seem like it's a RAM error. 

To rule out the software aspect, you can try to run the PC in safe mode for a while. If it still BSoDs in safe mode, it's most likely a hardware error, and if it doesn't, it's most likely a software error.

 

Edit: And your load temps seem fine aswell.

 

How long would you say is a while? This error hasn't been something that has occurred super frequently (the two dump files I provided were the most recent cases, and they occurred about a week apart). If it should occur again, should I assume that my CPU is at fault? Now that I think about it, I left prime95 running when I first built the thing while I went to class for a day. I came back and my computer had restarted. I assumed that it was from windows update and never really looked into it.

[Volbet]

How long would you say is a while? This error hasn't been something that has occurred super frequently (the two dump files I provided were the most recent cases, and they occurred about a week apart). If it should occur again, should I assume that my CPU is at fault? Now that I think about it, I left prime95 running when I first built the thing while I went to class for a day. I came back and my computer had restarted. I assumed that it was from windows update and never really looked into it.

I can see that a week in safe mode probably is to much pain for anyone to suffer. 

You can try to run a stresstest on the system while it's in safe mode, to speed the process up a bit. And it's not recommend to use Prime95 on Haswell chips. Intel Extreme Tuning Utility is the best alternative to that platform.

This is one of the problems with periodic failures. They are pretty hard to troubleshoot.

[epain]

I can see that a week in safe mode probably is to much pain for anyone to suffer. 

You can try to run a stresstest on the system while it's in safe mode, to speed the process up a bit. And it's not recommend to use Prime95 on Haswell chips. Intel Extreme Tuning Utility is the best alternative to that platform.

This is one of the problems with periodic failures. They are pretty hard to troubleshoot.

 

Oh, I didn't realize that about Prime95, I hope I didn't damage my PC running it...I'll run IETU while I'm at work tomorrow and report back with whatever I find. Thank you so much for your prompt and helpful responses!

[Volbet]

Oh, I didn't realize that about Prime95, I hope I didn't damage my PC running it...I'll run IETU while I'm at work tomorrow and report back with whatever I find. Thank you so much for your prompt and helpful responses!

Prime95 shouldn't damage your CPU, it's just not good at stability testing Haswell chips, due to the way it makes work tasks.

[epain]

Prime95 shouldn't damage your CPU, it's just not good at stability testing Haswell chips, due to the way it makes work tasks.

 

I ran a stress test for 8 hours last night using Intel Extreme Tuning Utility, and my computer crashed again. The new dump file is now included in the dropbox link.

[Volbet]

I ran a stress test for 8 hours last night using Intel Extreme Tuning Utility, and my computer crashed again. The new dump file is now included in the dropbox link.

I can only see two files in the Dropbox, and both of these were uploaded 22 hours ago.

 

Do you by any chance have a different CPU or motherboard, so that you  can swap out one of the two. It would help to know if the problem is the motherboard or the CPU, especially if it comes down to making an RMA.

Did you remember to run the stress test in safe mode? (I'm not even sure you can run it in safe mode, now that I think about it).

I know this might be a pain, but you could also try to reinstall Windows. This will rule out all possibilities of it being a software issue. 

[epain]

I can only see two files in the Dropbox, and both of these were uploaded 22 hours ago.

 

Do you by any chance have a different CPU or motherboard, so that you  can swap out one of the two. It would help to know if the problem is the motherboard or the CPU, especially if it comes down to making an RMA.

Did you remember to run the stress test in safe mode? (I'm not even sure you can run it in safe mode, now that I think about it).

I know this might be a pain, but you could also try to reinstall Windows. This will rule out all possibilities of it being a software issue. 

 

The file is still syncing to dropbox apparently, I'll try again now. And the stress test was unable to run in safe mode. As for the mobo CPU options: I don't have spare parts as this is my first build =\

[epain]

The file is still syncing to dropbox apparently, I'll try again now. And the stress test was unable to run in safe mode. As for the mobo CPU options: I don't have spare parts as this is my first build =\

 

Newest dump file is in the dropbox folder.

[Volbet]

The file is still syncing to dropbox apparently, I'll try again now. And the stress test was unable to run in safe mode. As for the mobo CPU options: I don't have spare parts as this is my first build =\

My best guess is that the .dmp file will show me the same thing as the other two, but I'll wait with my conclusions untill I have seen it.

 

I would advice you to try reinstalling Window, just to make sure it's not a software problem. If you PC still BSoDs then I would advice you to start an RMA for both the motherboard and the CPU, seein that you have no way of testing either. I don't know how the RMA and warranty system works where you live, so you might be a bit on your own there. 

 

Edit: Yep, the .dmp file still lists ntoskrnl.exe and hal.dll as the culprits. 

[epain]

I'm going to go ahead and RMA the CPU and Mobo as it only really costs shipping I believe, and I'd rather just get my machine in working order. I'll run a stress test when I get my new parts and update. Until then, thanks a ton, you've been a great help!