Hey, need some help with a BSOD

[dyllan]

I just recieved my new I5 4670k and Asus Z87-A after many issues with newegg and I installed it, fresh copy of windows, everything was going great until I started getting BSOD's. Its always BCCode 124, cant really tell any specific time its happening but basically everywhere I check people say its a hardware issue. Ive ran 4 hours of Prime95 without issue, and 3 passes of Memtest86+ without issue aswell, I have up to date drivers for my GPU, honestly not too sure of everything else, I did the update package off of the Asus website for my board so I assume thats all up to date.

System Specs;
PSU - CX600M
CPU - I5 4670k (no OC as of yet)
Heatsink - Hyper 212 Evo
RAM - HyperX Beast 1866 8gigs.
Motherboard - Asus Z87-A
HDD/SSD 500gb WD Blue / Samsung 840 Pro (OS on SSD)
Graphics Card - N580GTX Lightning 1.5gb

I am sort of out of ideas, the only things left to me would be either the motherboard of the CPU, which if thats the case im getting extremely tired of trying to deal with newegg after being charged 40 dollars extra ontop of my canadian prices to ship my CPU from a NJ warehouse.

Here is what I have from BlueScreenView.

==================================================
Dump File : 121113-3229-01.dmp
Crash Time : 12/11/2013 3:47:19 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0793b028
Parameter 3 : 00000000`bf800000
Parameter 4 : 00000000`00000124
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\121113-3229-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,648
Dump File Time : 12/11/2013 3:47:47 PM
==================================================

If you guys need anything else from me just let me know and ill try to provide it, and thank you for helping.

EDIT - If this is in the wrong spot on the forum im sorry, just let me know and ill move it.

 

[ATMINSIDE]

Did you manually set your RAM speed/timings/voltage?

 

[dyllan]

I have them set to XMP profile 1, has the correct timings/voltages/speed. Anything past that would be a no.

 

[ATMINSIDE]

I have them set to XMP profile 1, has the correct timings/voltages/speed. Anything past that would be a no.

Try setting them back down to the standard settings, like 1333MHz or whatever it was when you first plugged in.

Last time I had a 124 BSOD it was RAM.

 

[dyllan]

I will do that but it will bother me lol, its 1866 memory for a reason

 

[ATMINSIDE]

I will do that but it will bother me lol, its 1866 memory for a reason

If it changes though, that most likely points to RAM. Mine would pass Memtest just fine. Do you have another set you can try?

 

[dyllan]

I do not unfortunately, I sold my other ram not too long ago. I changed the timings to auto and theyre showing at 1333 in BIOS, CPU-Z is showing DRAM Frequency at 934.8 right now though and as i understand its supposed to report at 1/2 of the actual frequency. so is it wrong to still be picking it up at that frequency?

 

[ATMINSIDE]

I do not unfortunately, I sold my other ram not too long ago. I changed the timings to auto and theyre showing at 1333 in BIOS, CPU-Z is showing DRAM Frequency at 934.8 right now though and as i understand its supposed to report at 1/2 of the actual frequency. so is it wrong to still be picking it up at that frequency?

Make sure you save your BIOS settings when you exit out, that's still the 1866 speed.

 

[dyllan]

Sorry you were right, I forgot to change something. Now showing 667.7mhz, however this time on start up I recieved a CPU Fan Error. I used this Hyper 212 Evo with my last build which was an amd fx8350 and it worked great and im seeing even lower temps with it on this at the moment (not over clocked as I said before), is it likely to be something with the motherboard or a problem with the CPU fan you think, or just an abnormality?

 

[ATMINSIDE]

Sorry you were right, I forgot to change something. Now showing 667.7mhz, however this time on start up I recieved a CPU Fan Error. I used this Hyper 212 Evo with my last build which was an amd fx8350 and it worked great and im seeing even lower temps with it on this at the moment (not over clocked as I said before), is it likely to be something with the motherboard or a problem with the CPU fan you think, or just an abnormality?

Just make sure the CPU fan is plugged into the correct header.

 

[dyllan]

It is plugged into the CPU_FAN header, there is also a CPU_OPT header that is available right beside it but from my understanding for the pc to start up the BIOS requires something to be plugged into the FAN header, not to mention that would probably be the correct one to begin with anyway, right?

Other than that issue, I havent had a BSOD as of yet, theyre pretty far between but still not right. Ill post back here if/when it does happen, and thank you very much.

 

[ATMINSIDE]

CPU_OPT is for a secondary CPU fan.

If it doesn't happen again, I would contact Kingston.

 

[dyllan]

Another BSOD, was changing some stuff in the BIOS, turned down my lower limit on my cpu fan so it didnt give me an error on start up sometimes, thats working fine, no heat problems so I thought this would be okay. As soon as windows loaded and I hit the desktop it BSOD'd. I have checked both stick of ram individually with memtest by now aswell. If you guys do think its the ram still I can go out and buy some new ram as this stuff isnt covered under waranty anymore I dont believe. Is it possible to be the headers on either the mobo or in the CPU Fan, could that cause this if the mobo for some reason stops getting information about the fan for a little bit?

From BlueScreenViewer

==================================================
Dump File : 121113-3229-01.dmp
Crash Time : 12/11/2013 3:47:19 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0793b028
Parameter 3 : 00000000`bf800000
Parameter 4 : 00000000`00000124
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\121113-3229-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,648
Dump File Time : 12/11/2013 3:47:47 PM
==================================================

 

[ATMINSIDE]

What parts do you have access to that you can swap out to troubleshoot with?

 

[dyllan]

for the amount of time that it takes to see a bsod, none really. I cant disassemble my work computer for that long since I use it for my business, I really wish these were more descriptive as to where the failure happened or what caused it lol.

 

[dyllan]

Honestly, I feel like its probably the ram aswell,I think I might pick up some new stuff. What would you recommend? I was looking at this set of Gskill Sniper I was also considering just going up to 2133, dont know if thats a good or bad choice but its only 5-10 dollars more. Also, may it be an issue with the OS, would another fresh install help do you think? Honestly I just want it working and im very frustrated with how long it took to get these parts at the prices I payed and its not even working the way its supposed to :/

If I could get a list of things to try and just dedicate a day to getting this work that would be incredibly helpful. Thank you!

 

[ATMINSIDE]

If you want to go get more RAM without testing, go ahead. I see no real reason for 2133 over 1866. Performance benefits start diminishing. Sniper is good stuff though.

Z87-A QVL for RAM. They only tested one set of Kingston at 1866, quite a few G.SKILL sets tested. I would stick to one on this list, just to make sure you're covered.

It wouldn't be my first run, but it seems like RAM.

 

[dyllan]

I was actually in the middle of writing a response while updating windows, I had tons of issues with updating it earlier, it kept failing updates giving error codes, which is mostly gone now, I had to use different troubleshooting software from microsoft to try and get that working a bit, however I was just trying to update like I said and it BSOD'd again. I was also going to say I had dropped my 500gb HDD off my table by accident onto a carpeted floor during the build but thats my D drive anyway.

==================================================
Dump File : 121113-3229-01.dmp
Crash Time : 12/11/2013 3:47:19 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`0793b028
Parameter 3 : 00000000`bf800000
Parameter 4 : 00000000`00000124
Caused By Driver : hal.dll
Caused By Address : hal.dll+12a3b
File Description : Hardware Abstraction Layer DLL
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
Processor : x64
Crash Address : ntoskrnl.exe+75b80
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\121113-3229-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,648
Dump File Time : 12/11/2013 3:47:47 PM
==================================================

same everything I believe.

EDIT - I lied, im still getting a lot of update errors and failures.

 

[ATMINSIDE]

I would try a reinstall then RAM.

Definitely grab something off the QVL though.

 

[dyllan]

Alright, Ill try a new OS install and let you know what happens, thank you very much for the help aswell.