Sure, I'll take a shot at guessing. Who cares if you might be wrong even if you only have guessing and past experiences to base it in. Overheating GPUs - More likely to display broken output out upon boot. Overheating CPUs - Usually locks up while trying to load the OS, although CPU problems are subjective and depending on your RAM and the number of programs you have running at startup, it's difficult to determine. Viruses - Possibly. If you got something truly malicious where it loads like 16 programs (named something like ~!13jhsk.exe), you could easily get the BSOD. Damaged RAM - Very likely, especially dependent on the number of sticks and how many were damaged. This is what I voted for. Damaged HDD - Less likely. Hard Drives are a bitch to repair and on top of that, you'd be pissed that you lost all of your data. Windows 7 retardation - This is a general statement, so this is my 2nd choice.
CPU's do not overheat anymore. They have tech to slow down the processor to stop it over heating. This is very important to know when overclocking - as you might find the PC works fine, but keeps throttling back the CPU. So you need to monitor this to confirm the pc is actually running at 100%. http://www.intel.com/technology/itj...d_thermal_management/p03_power_management.htm
I don't think this is 100% accurate. On one side you say "CPUs" but you only link to an Intel webpage. On the other side, I recently started having BSODs and sudden shutdowns due to CPU overheating (when I checked the CPU temperature was 117 Celsius). It's an AMD Phenom X3.
Windows 7 was just being generally retarded... As much as i have loved Windows 7 having dual booted from beta with it up until release when i moved over to is as my only OS i can see it randomly having problems which fix themselves and never return. Had some problem where i wasn't able to get into windows as it crashed just before the windows boot screen or sometimes just on it but upon removing sata cabes from DVD drive it booted up fine. Plugged the drive back in and it's all good now.
Motherboards can still have their own independent systems to shut down the entire thing if it overheats. Intel CPUs have had throttling built in since the P4 days. I know AMD didn't implement it in the Athlon and Athlon XP lines but I can't say the same for the Athlon 64 and above. Throttling as in "remove the heatsink and exposure it directly to the air and it won't fry itself due to lowering the clock rate and thus thermal energy output". The Pentium III under those conditions would cause Windows to BSOD without permanent damage - usually.
That's pretty cool, although I'd still say that a wide variety of other problems related to CPUs overheating prevent it from being a complete fix. Bad sockets, damaged CPUs, or generally any errors in the intricate connection of the two could still cause the CPU to overheat regardless of any higher-level safety mechanisms.
100% correct. My brothers PC had my old Dual-Core clocked at 1.8 GHz. It was working perfectly fine. He would play Super Street Fighter 4 etc, with no lag or issues. One day, he said his computer was going really slow. So I checked the software, but I did not check the hardware! (lesson learned here) I bought even a new Intel LGZ-775 fan + sink to be sure it was not the old fan! Turns out, after re-installing Windows 7, and doing a benchmark test, checking other stuff... that the fan controller IC(?) died on the mainboard. From not running the CPU with a fan for nearly a week, he caused serious damage to it. The benchmark score halved. So, it fried itself. Still works, but the performance is terrible. So I soldered it to +12 in the end, and it has been working fine ever since... I have no idea, why the thermal controller died, and why it did not auto turn off the system, as the thermal threshold for the CPU was set to 65 degrees Celsius. His CPU, was hitting 120+ when I first checked the BIOS... Gigabyte motherboard has failed me for the first time (though, it was a second hand board, so who knows what has happened to it )
Every AMD CPU since the Athlon 64 has had it implemented. Luckily my first AMD computer was an Athlon 64 when I forgot to replace the heatsink after an upgrade.
Well the blue screen was caused by an Overheated GPU. My graphics card had a thick layer of dust on the heatsink. The fan would not even move!
I'm not defending anyone nor mean to offend anyone, but seriously: what did you expect? There were 6 possible options; it had to be one of these... and the root cause behind it could be anything... even something as simple as dust.