Sign in with
Sign up | Sign in
Your question
Solved

Reoccuring BSOD - First time after 6 months

Tags:
  • Blue Screen
  • Build
  • CPUs
Last response: in CPUs
Share
August 2, 2014 6:04:53 PM

Hello again,

Six months ago I came here looking for a solution to my Blue Screen problems. The error code I receive when my computer blue screens is still 0x00000124 which indicates a hardware related problem.

The first time I got this was right after I assembled this build and I would receive these errors randomly and frequently, playing games, watching Youtube and even from opening multiple tabs on Google Chrome. I had tested my entire build using programs such as MemTest, AIDA64, FurMark and running Chkdsk. Stressing my CPU seemed to have caused the most of my BSOD's at the time. In the end I had to return certain parts of my build, since I purchased them in a bundle back to Scan.co.uk, which included my CPU - i7 4930K @ 4.6Ghz (which they overclocked), motherboard - Asus IV Rampage Extreme, Corsair Vengeance 4x4Gb @ 2133Mhz, CPU Cooler - Corsair H100i. After a few weeks they sent my parts back to me and had informed me that they had replaced the CPU.

All has been well until now, however. My partner had been surfing around the web and downloading a game on Origin when she had got up and left my computer idle (For around an hour at most) and when I arrived home from work I noticed the popup indicating that Windows has recovered from an unsuspected shutdown. I asked her if she had put the computer to sleep as I know it can cause problems with Overclocked systems but she didn't, and had nothing out of the ordinary open or downloading. Using BlueScreenView it appears with the same error code as the previous ones six months ago, and mentions that it was caused by driver "hal.dll" and by the address "hal.dll+12a3b".

In reality i'm just looking for advice, do you think that I should send the CPU back and have them check it, or does it sound like another piece of hardware is causing the issue? I'm quite worried as the saying goes "lightning doesn't strike twice"...

Any advice would be appreciated!

Regards,

Syketh

More about : reoccuring bsod time months

a b à CPUs
August 2, 2014 6:28:12 PM

you can post the memory .dmp file on a cloud server with public access. Someone can look at it with the windows debugger and
issue the !errrec command to dump the info on why the CPU issued the bugcheck.

Most often it is a error in the cache memory. This is most often caused by overclocking or overheating or sometimes cause by power fluctuations to the CPU. power drops a little and you get cache memory errors, and the CPU calls a bugcheck. If it drops a lot then the CPU resets and your system reboots. (no memory dump or bugcheck produced)
m
0
l
a b à CPUs
August 2, 2014 6:29:20 PM

Your issues are being caused by the overclock! You need to adjust it manually. Raise the voltage of the Vcore slightly if your temps under load in Aida64 using Realtemp are under 80C, id they are 80C or over reduce the OC by 100Mhz. This will fix the BSODs you have been getting. :) 

Good luck!
m
0
l
Related resources
a b à CPUs
August 2, 2014 6:33:35 PM

may help providing your current pc spec if it different than before,usually bsod cause by memory failure the the simple step check memory is to remove all sticks of memory living only one in place and run test then insert another one do the same test with each of one.
m
0
l
August 2, 2014 6:51:34 PM

Hey, thanks for the quick responses. Firstly here's my specs:

I7 4930k
H100i
2 x EVGA GTX 780 ti SC
Asus Rampage Extreme
16GB Corsair Vengeance 2133Mhz
Corsair AX1200i
Corsair 900D

As I mentioned before, the over clock was done by the 3XS team at Scan, where I purchased all of the above. When the last series of Blue screens occurred I ended up testing everything, including testing each stick of ram.

I will run AIDA64 for a few hours tomorrow (any idea how many hours is enough?)

Alex, I'm afraid If I alter the over clock I may void my warranty or Scan may refuse to help me. :s

Johnbl, every time I'm on the computer I have EVGA Precision X open along with CPU Temp. Both cards run at 33c idle and never exceed 60c usually when running one of my most demanding games with a custom cooling curve, the cpu cores are around 27c idle and never exceed 55c normally (not sure when stress testing).

I will run AIDA64 and put the file up on Cloud tomorrow and report back in. Thanks a bunch for the advice so far!
m
0
l
a b à CPUs
August 2, 2014 6:58:56 PM

syketh said:
Hey, thanks for the quick responses. Firstly here's my specs:

I7 4930k
H100i
2 x EVGA GTX 780 ti SC
Asus Rampage Extreme
16GB Corsair Vengeance 2133Mhz
Corsair AX1200i
Corsair 900D

As I mentioned before, the over clock was done by the 3XS team at Scan, where I purchased all of the above. When the last series of Blue screens occurred I ended up testing everything, including testing each stick of ram.

I will run AIDA64 for a few hours tomorrow (any idea how many hours is enough?)

Alex, I'm afraid If I alter the over clock I may void my warranty or Scan may refuse to help me. :s

Johnbl, every time I'm on the computer I have EVGA Precision X open along with CPU Temp. Both cards run at 33c idle and never exceed 60c usually when running one of my most demanding games with a custom cooling curve, the cpu cores are around 27c idle and never exceed 55c normally (not sure when stress testing).

I will run AIDA64 and put the file up on Cloud tomorrow and report back in. Thanks a bunch for the advice so far!


All good!
They will not refuse to help you if you follow my advice. Only raise the voltage by 0.05 though, and only if your temps in AIDA are okay. Otherwise just reduce the oc by 100mhz. :) 
m
0
l
August 2, 2014 8:08:33 PM

I'll have a go at that tomorrow Alex, after I check my temps on AIDA64 and see how they go. I'll leave it on for two hours, if I get a BSOD I'll do what you have said or if the temp exceeds 80c.

Regards,
m
0
l
a b à CPUs
August 2, 2014 8:10:02 PM

syketh said:
I'll have a go at that tomorrow Alex, after I check my temps on AIDA64 and see how they go. I'll leave it on for two hours, if I get a BSOD I'll do what you have said or if the temp exceeds 80c.

Regards,


Sounds great! Looking forward to hearing the results.

Best of luck to you, syketh. :) 
m
0
l
August 3, 2014 3:03:26 PM

Alex Kelly said:
syketh said:
I'll have a go at that tomorrow Alex, after I check my temps on AIDA64 and see how they go. I'll leave it on for two hours, if I get a BSOD I'll do what you have said or if the temp exceeds 80c.

Regards,


Sounds great! Looking forward to hearing the results.

Best of luck to you, syketh. :) 


Hey Alex, apologies for only getting back to you. I work anti-social hours at the weekend, i'm about to try your advice out now. Do you have a recommended time for how long I should stress test my CPU using AIDA64? If it reaches above 80c should I stop?

I'm completely clueless to overclocking, which is why I bought the CPU and MB already overclocked from Scan. It appears that they haven't done it right.... Twice.

Again, I appreciate your help! :) 
m
0
l
a b à CPUs
August 3, 2014 3:07:38 PM

No worries! OC'ing is a very delicate process, I'm not surprised they didn't get it quite perfect.
Temps are only a real worry if the get to 85C or above after around 20 mins of testing in Aida. If you're getting temps around these numbers, try reducing the frequency of the CPU core clock by 100Mhz, as adding more voltage will cause it to get even hotter.
Let me know how you go! :D 
m
0
l
August 3, 2014 3:20:15 PM

Alex Kelly said:
No worries! OC'ing is a very delicate process, I'm not surprised they didn't get it quite perfect.
Temps are only a real worry if the get to 85C or above after around 20 mins of testing in Aida. If you're getting temps around these numbers, try reducing the frequency of the CPU core clock by 100Mhz, as adding more voltage will cause it to get even hotter.
Let me know how you go! :D 


Ok, so I tested my system as it is now without changing anything. After a minute and a half I got another BSOD. The hottest core reached 76c. I'll reduce the frequency (if I can) by that amount and have another try. If that doesn't work i'll inform Scan tomorrow over the phone that I would like them to replace it, or tune the overclock down. Sad thing is, I was charged an extra £30 - £40 for the overclock and it's still not working as it should. It's just worrying that I got a BSOD after six months of everything running fine and the computer running basically idle.

I'll keep you posted!
m
0
l
a b à CPUs
August 3, 2014 3:22:30 PM

Those temps are fine, and a BSOD in aida indicates you need more voltage! Increase the voltage on the CPU core by 0.05 in the BIOS and try again, before you reduce the frequency. :) 
m
0
l
August 3, 2014 3:35:27 PM

Alex Kelly said:
Those temps are fine, and a BSOD in aida indicates you need more voltage! Increase the voltage on the CPU core by 0.05 in the BIOS and try again, before you reduce the frequency. :) 


OK i'm back on. I changed my Vcore fro 1.375 to 1.425, adding that 0.05 you said to do. Should I check it out?

Also, I'm not sure if you would have any knowledge of this other issue I've been having, I actually made a separate thread this morning but I haven't received any word back on it. Basically, when I turn my computer off at the mains, the next time I go to boot the system up my power supply starts then powers down for around 5 seconds, then boots up normally. Someone did mention it could be because I have my Power Saving options disabled in the bios due to the overclock. But anything in the bios is all of Scan's doing, not mine. I didn't want to hijack the thread but you've been really helpful, just wanted to see if you know anything about it.

Anyway, i'll wait for the go ahead before I start AIDA64 again. :)  Thanks!
m
0
l
August 3, 2014 4:00:34 PM

Alex Kelly said:
Those temps are fine, and a BSOD in aida indicates you need more voltage! Increase the voltage on the CPU core by 0.05 in the BIOS and try again, before you reduce the frequency. :) 


Just finished running AIDA64 for a total of 7 minutes 42 seconds before the 4th core reached 86c, which is where I decided to stop. Nice step up from 1 minute 30 seconds. No BSOD but i'm afraid to leave AIDA64 running if it reached that temperature so far.

Thing is, next month i'm going to upgrade to a custom water cooling loop, so heat wont be an issue. But I would rather sort the CPU out now, or have it looked at instead of running into further hardware issues down the line.
m
0
l
a b à CPUs
August 3, 2014 7:11:46 PM

Argh! My bad. I made a typo. I meant to suggest going up in increments of 0.005.
Try a Vcore of 1.38. :) 
The other issue you are having does not sound like an issue with you BIOS settings. Can you link me to your other thread?
m
0
l
August 4, 2014 5:32:43 AM

Alex Kelly said:
Argh! My bad. I made a typo. I meant to suggest going up in increments of 0.005.
Try a Vcore of 1.38. :) 
The other issue you are having does not sound like an issue with you BIOS settings. Can you link me to your other thread?


Ahh, I see. I pumped it up to 1.425 last night on the OC Profile. I'll turn that down to 1.38 and have a go! Also, i'm about to ring Scan now and see what they think of it, whether I should return the bundle to them to have a look or if they could even guide me to reduce the overclock to 4.3Ghz.

Here's a link to the other thread I made concerning my PSU's behavior.
http://www.tomshardware.co.uk/answers/id-2245079/ax1200...

Thanks for the help, i'll let you know how it goes.
m
0
l
a b à CPUs
August 4, 2014 5:34:48 AM

I don't think you need to call scan, as I can guide you through everything. :D 
I'll take a look at your other thread.
m
0
l
August 4, 2014 6:07:03 AM

Alex Kelly said:
I don't think you need to call scan, as I can guide you through everything. :D 
I'll take a look at your other thread.


Sorry Alex, by the time I read this I was already off the phone to them. They didn't offer much advice at all, they just told me to run the computer without the Overclock profile and to try it out for a few days. They gave me a reference number to contact them after a day or two. If everything is running they said it's down to the overclock (Which I already know it is).

While I was on the phone I left AIDA64 running, without the overclock profile and it did not exceed 64c. I left it running for 21 minutes. So i'm guessing the non-clocked profile is perfectly fine compared to the other.

Anyhow, i'll give that 1.38 a go now!
m
0
l
August 4, 2014 6:23:17 AM

Alex Kelly said:
I don't think you need to call scan, as I can guide you through everything. :D 
I'll take a look at your other thread.


Back with more depressing news, the 1.38 didn't work. Got about 2 mins 45 seconds in and another blue screen occurred. Back using the Stock Profile for now.
m
0
l

Best solution

a b à CPUs
August 4, 2014 6:30:10 AM

Bump it up a bit man, that's perfectly fine that you got a BSOD! Try 1.39 and get back to me.
You will get it stable eventually, I promise. If 1.39 doesn't work, try 1.4 and so on. As long as you don't go past 85C in Aida you're completely fine.
:) 
Share
August 4, 2014 7:46:57 AM

Alex Kelly said:
Bump it up a bit man, that's perfectly fine that you got a BSOD! Try 1.39 and get back to me.
You will get it stable eventually, I promise. If 1.39 doesn't work, try 1.4 and so on. As long as you don't go past 85C in Aida you're completely fine.
:) 


Hey, just got back from testing out 1.85. I ran AIDA64 for 30 minutes exactly, no blue screen! Not sure if that means it's fixed, however. Is 30 minutes enough to tell? Before that I tested 1.8 again and it lasted 21 minutes before blue screening.

Running the overclocked profile at the moment.
m
0
l
a b à CPUs
August 4, 2014 7:52:15 AM

It sounds like 1.85 will be perfect for you! If you blue screen again, just bump it up to 1.9 and you will be all set.
Hope I have helped, man!
If all is sorted, please consider picking one of my answers as the solution. :) 
m
0
l
August 4, 2014 7:54:48 AM

Alex Kelly said:
It sounds like 1.85 will be perfect for you! If you blue screen again, just bump it up to 1.9 and you will be all set.
Hope I have helped, man!
If all is sorted, please consider picking one of my answers as the solution. :) 


I certainly will, pal. Thank you kindly for all your help. If I run into further problems with my overclock do you mind if I private message you? You've been by far the most helpful person I've spoke to regarding this matter, from Scan, Reddit and other forums I've posted on!

Thanks a bunch! :) 
m
0
l
a b à CPUs
August 4, 2014 7:59:05 AM

Thank you! And no worries at all, you're very welcome.
Yes, if you come across any issues or have any questions, feel free to PM me, I'd be more than happy to help out. :) 
m
0
l
!