Am I getting BSOD because of HDD temperature?

Toggle sidebar Toggle sidebar
B

Bozdra

Reputable
Jan 3, 2017
9
0
4,510
For the last month I've been getting the BSOD a lot, they are very diverse like error 124, 7f, 3d, and sometimes the PC just turns off suddenly. After doing S.M.A.R.T. test from speedfan it told me that my WDC WD5002ABYS-18B1B0 is running at 48 degrees Celsius but the supposed max is 44! But my PC crashed even in the morning when the temp should be low! I'm 100% sure it is a hardware problem because I reinstalled windows completely a few days after I started getting BSOD, even as I was installing new windows 7 my PC crashed... If it's not the HDD, is it even possible for me to check what is causing this issue without paying a pro?
 
Solution
J
if all of your bugchecks are being caused by a service host (svchost.exe)
you will have to try to figure out which service host is causing the problem. Most often you would have to run microsoft process explorer to figure it out. https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

svchost.exe is a generic name so you would have to use process explorer and expand all of the service hosts to see what .exe is rolled up in them. Most likely it will be a third party .exe that is the cause of the problem.

you have a very old computer so you might want to also run hardware diagnostics


Sort by date Sort by votes
Hi Bozdra.

Sorry to hear about the issues you're currently experiencing. 🙁

Your drive's operation temperature is from 0°C to 60°C, so 48°C should be OK. However those errors you're getting might be indicating a hardware failure of some sort. Did you see anything out of the ordinary when you've checked the drive's SMART data? I'd recommend that you backup your most important data as soon as possible, just to be on the safe side. After that I'd suggest that you download DLG and run both tests (Quick and Extended) to see what's the situation with the HDD: How to test a drive for problems using Data Lifeguard Diagnostics for Windows.
You could also try the drive with a different SATA port and cables, in case the reason for your problems turns out to be a faulty connection.

Here are some more suggestions regarding error 124 specifically: https://answers.microsoft.com/en-us/windows/forum/all/blue-screen-error-124/78d310d7-4585-4f37-995e-c08d49f9869a. Here are included driver updates, memory tests, etc.

Hope that helps. Please let me know how everything goes.
Boogieman_WD
 
Upvote 1 Downvote
I will check 124 again, thing is I'm pretty PC illiterate so having difficulty with posts like that. I don't have any important data. I have a new problem, my PC won't start in normal mode, it crashes when amd catalyst loads (2-3 seconds after entering windows) but not the BSOD crash (I still see desktop but can't move mouse or do commands on keyboard), and I can shutdown my PC with the press of on/off button (when it crashed before and it wasn't BSOD, I had to unplug power). I am in safe mode now and it still crashes, it crashed specifically once when I ran DLG in administrator mode. Also 20 seconds after opening DLG the program stops working and Windows troubleshoots. I have no idea what's happening. I don't know how to notice if SMART tests were strange, and in safe mode I can't run them anyway.
Also I just got a "1e" BSOD in safemode doing nothing...
Thanks for the fast answer!
 
Upvote 0 Downvote
generally, a bugcheck ox124 is going to be a power problem to the CPU if the first parameter of the bugcheck is 0
you would want to remove overclocking, reset the bios to defaults. (over heated CPU, old bios with new CPU can also cause this)

generally, a quick look at the minidump can give an idea as to the cause of the bugcheck.

this would not be caused by a hard drive. You would get a different bugcheck code and sub error code.




 
Upvote 1 Downvote
Ok, no overclocking on my PC and the CPU temp is normal. Also 124 is just one of many BSOD's I got. I will try the BIOS part
Do you want me to post the mini dumps?
 
Upvote 0 Downvote
sure, the bugcheck 0x124 can also come from other hardware subsystems and it is useful to know what hardware is shutting down the system with the bugcheck.



 
Upvote 0 Downvote
Give it a try with John's suggestions. I took a look at some of the minidump files and it definitely looks like a hardware error. Unfortunately it's a bit difficult to determine exactly what could it be so some troubleshooting should be done here. The good news is that you don't have any important data on the drive, so go ahead and try the drive with a different computer if possible, by connecting it either externally (via a SATA to USB adapter, external enclosure, or a dock station), or internally, so that you can try and test it, to see what's going on.
Other than that you should try testing your RAM as well, by following this tutorial: http://www.sevenforums.com/tutorials/715-memory-diagnostics-tool.html if you're able to get to that part.
 
Upvote 0 Downvote
overall, the power to your CPU is fluctuating, It can be your power supply but more likely your GPU is using too much power or is overheating. Blow out any dust and make sure the fans are spinning. I would disable the GPU audio driver if you don't have sound provided by a video cable. (hdmi)

-----------
4th bugcheck 0x124 caused by another CPU cache error but the system timer was 10 seconds so your CPU was in the process of rebooting. (ignore)
---------
third bugcheck 0x125 was caused by a cache read error on processor 0 cache bank 1
system up timer was 1 hour 10 minutes. while playing a game
I would be blowing out the dust out of the CPU fan and the GPU fan and power supply fan. This can be a heat related problem.

if you do not get sound from a speakers inside your monitor, I would disable the graphics card sound using the windows control panel device manager. This will lighten the load on the graphics card. If the graphic card pulls too much power during a game the motherboard will reset the cpu OR the CPU voltage will drop and you will get cache memory errors.


------------
second bugcheck was caused by a internal CPU error most likely because the CPU was reset do to a power problem. bugcheck 0x124 (system up timer was 13 seconds) (ignore)
--------
first bugcheck was caused because of a service host made a system call using a bad memory address.
svchost.exe




machine info:
ASUSTeK Computer INC.
P5E-VM DO
BIOS_VERSION: 0803

BIOS_DATE: 07/23/2008

Processor Version Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
Processor Voltage 8dh - 1.3V
External Clock 266MHz
Max Speed 3800MHz
Current Speed 2400MHz


 
Upvote 0 Downvote
I've cleaned my PC and specifically my gpu, but it still won't start normal mode, only safe mode!

EDIT: I've just ran startup repair and restored my PC to a previous version, so now it can run normal mode, but if I try to play a game, watch a video or listen to music it still crashes after 20-30 seconds
 
Upvote 0 Downvote
if all of your bugchecks are being caused by a service host (svchost.exe)
you will have to try to figure out which service host is causing the problem. Most often you would have to run microsoft process explorer to figure it out. https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

svchost.exe is a generic name so you would have to use process explorer and expand all of the service hosts to see what .exe is rolled up in them. Most likely it will be a third party .exe that is the cause of the problem.

you have a very old computer so you might want to also run hardware diagnostics






 
Upvote 0 Downvote
Solution
My problem was that my electrolites got boiled inside because the main fan at the end was turned upside down so the heat remained inside the pc, it all got fixed, thank you very much for helping!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom