Help with a BSOD

[SmileAsTheyDie]

Hello all. Over the past 2 or 3 months i have been getting this random BSOD. It usually happens every other week and its random in the sense that sometimes i am browsing the internet, sometimes im playing a game, sometimes im just organizing my files. There dosent seem to be any consistency to something "causing" the cause of the BSOD. With that said though the "reason" for the BSOD is the same (hal.dll and ntoskrnl.exe). Im not sure what could be casuing this BSOD and it happens so infrequently to be able to do any real testing on it (but it happens frequently enough to be annoying and worrisome).

 

My setup:

i5 4670k @ 4.2

ASUS Z87-A

8GB(2x4) 1600mhz RAM

ASUS R9 280x

Corsair CX600

 

It might be worth mentioning that i have had my CPU overclocked for about 9-10 months now and only as of about 3 months ago have these BSOD's started. Also i run a dual monitor setup that uses both my 280x and the integrated 4600 graphics on my CPU.

 

If someone could tell me possibly what is wrong and how i could go upon fixing it, i would greatly appreciate it.

 

Link to the DMP file: https://www.dropbox.com/s/i258qzyorcdywrh/071915-9609-01.dmp?dl=0

[JefferyD90]

What does event viewer say?

[Guest]

"organizing my files" ( ͡° ͜ʖ ͡°)

[Valandil]

I had this come up when i had a ram issue.

 

- remove the overclock

- run a startup repair

- run a memory test

- run a test on your ssd / hard drive

 

I followed this when it happened

http://answers.microsoft.com/en-us/windows/forum/windows_7-system/blue-screen-dumps-due-to-haldll-and-ntoskrnlexe/0482409d-88f8-4bd7-9671-386003e8d924?auth=1

[Sanjeev]

Do a scan using programs like Whocrashed and bluescreen viewer ,they might be able to give better info on what is causing the BSOD. If that doesn't help use linux ubuntu for a while it can be booted form a usb drive as well and BSOD don't occur on linux distributions if you see get any problems with linux like a system freeze then most probably it's a hardware problem ,if linux is working well then it's something software / driver related issue ,A fresh OS install might solve it.

[Robin88]

Hello all. Over the past 2 or 3 months i have been getting this random BSOD. It usually happens every other week and its random in the sense that sometimes i am browsing the internet, sometimes im playing a game, sometimes im just organizing my files. There dosent seem to be any consistency to something "causing" the cause of the BSOD. With that said though the "reason" for the BSOD is the same (hal.dll and ntoskrnl.exe). Im not sure what could be casuing this BSOD and it happens so infrequently to be able to do any real testing on it (but it happens frequently enough to be annoying and worrisome).

 

My setup:

i5 4670k @ 4.2

ASUS Z87-A

8GB(2x4) 1600mhz RAM

ASUS R9 280x

Corsair CX600

 

It might be worth mentioning that i have had my CPU overclocked for about 9-10 months now and only as of about 3 months ago have these BSOD's started. Also i run a dual monitor setup that uses both my 280x and the integrated 4600 graphics on my CPU.

 

If someone could tell me possibly what is wrong and how i could go upon fixing it, i would greatly appreciate it.

 

Link to the DMP file: https://www.dropbox.com/s/i258qzyorcdywrh/071915-9609-01.dmp?dl=0

It sounds like your overclock is unstable, can you try bumping the CPU vCore by 0.01V and try running Intel Burn Test or OCCT and see if the BSOD occurs please?

Overclocking CPU's causes them to degrade over time, and you've been running with one for long enough for that to start happening, so see if upping the voltage fixes it, just be aware that the longer you run the overclock the worse it gets, so eventually it'll start happening again even if you stop it from happening now and when it does you'll have to bump the voltage again.

Btw, 0x124 BSOD's usually mean an unstable CPU, and you'll see it around 90% of the time when overclocking, if your memory controller is unstable then you'll see 0x101 BSOD's accompanying it as well, but in your case you probably won't see it.

[SmileAsTheyDie]

It sounds like your overclock is unstable, can you try bumping the CPU vCore by 0.01V and try running Intel Burn Test or OCCT and see if the BSOD occurs please?

Overclocking CPU's causes them to degrade over time, and you've been running with one for long enough for that to start happening, so see if upping the voltage fixes it, just be aware that the longer you run the overclock the worse it gets, so eventually it'll start happening again even if you stop it from happening now and when it does you'll have to bump the voltage again.

Btw, 0x124 BSOD's usually mean an unstable CPU, and you'll see it around 90% of the time when overclocking, if your memory controller is unstable then you'll see 0x101 BSOD's accompanying it as well, but in your case you probably won't see it. at maximum stress for 10 

 

I upped the voltage .01 up to 1.135 and ran intel burn test for 10 runs. I didnt BSOD during it (and i reached a maximum of 91C on two cores) but one thing i noitced via CPU-Z was my voltage was actually going as high as 1.2 during the intel burn test so idk if that factored into it not BSODing.

[Robin88]

I upped the voltage .01 up to 1.135 and ran intel burn test for 10 runs. I didnt BSOD during it (and i reached a maximum of 91C on two cores) but one thing i noitced via CPU-Z was my voltage was actually going as high as 1.2 during the intel burn test so idk if that factored into it not BSODing.

Can you try setting LLC to a higher value and see if that curbs the high voltage, it shouldn't be overvolting like that, if you already have LLC enabled can you try dropping it and test again, IBT gets CPU's hot, much hotter than anything would reasonably get a CPU to, but it shouldn't be that hot, nor should your CPU be overvolting unless that motherboard is too aggressive with LLC or is sloppy with controlling the voltage.

 

[SmileAsTheyDie]

Can you try setting LLC to a higher value and see if that curbs the high voltage, it shouldn't be overvolting like that, if you already have LLC enabled can you try dropping it and test again, IBT gets CPU's hot, much hotter than anything would reasonably get a CPU to, but it shouldn't be that hot, nor should your CPU be overvolting unless that motherboard is too aggressive with LLC or is sloppy with controlling the voltage.

If I could ask. What is LLC? Also could it be overvolting due to me using adaptive voltage?

[Robin88]

If I could ask. What is LLC? Also could it be overvolting due to me using adaptive voltage?

LLC stands for Load Line Calibration, and it's supposed to make sure that the voltage is closer to what is set in the BIOS at the risk of potentially of overvolting the CPU, if the LLC is too aggressive then it'll push the voltage too high. But at the same time the motherboard could be really sloppy with it's power delivery and could be overvolting even with it turned off.

Adaptive voltage could be the issue actually, I've had issues with my mobo where on one boot it'll set the base voltage to 1.22V and then add the +0.105V offset on top, but the very next boot it'll set the base voltage at 1.45V and also add the +0.105V on top of that, so it could very well be that adaptive voltage is causing it to overvolt.

In your case it isn't anywhere near as extreme as mine is, but it's a possibility, I loathe to use adaptive voltage and I prefer to use fixed voltage, but on my motherboard it refuses to boot even at stock clocks while using fixed voltage, so it's a case of needs must