Monday, October 30, 2017

Windows 7 blue screen after CPU cooler died and got replaced

Okay, so here is the deal: We have a PC at home that used to be mine, it was running pretty well (though sometimes blue screen, but most likely due to faulty RAID controller, as now other 'strange' issues have been fixed aswell). It ran on Windows Vista on my own screen and keyboard/mouse.


Now I bought a new one and my dad got that one, installed Windows 7 on it and he is using his own screen and keyboard/mouse (not neccessarily marked as working with W7, but no problems in the actual usage).


PC was working fine, no other errors besides random strange things that were solved since the faulty RAID controller is no longer in use.


Then a few weeks ago the CPU cooler died and PC started to randomly Blue Screen after being on high load for some time.


When the cooler was still dead it would survive max 2 mins on 100% load, and would Blue Screen around 80 degrees celsius cpu temp, but don't think you can draw conclusions from that.


Now a new cooler is alive and kicking, but the PC still Blue Screens after 20 minutes.


Blue Screen errors are pointing towards ntoskrnl.exe and are being caused by DRIVER_IRQL_NOT_LESS_OR_EQUAL mostly and sometimes MEMORY_MANAGEMENT.


Would appreciate any help on this, but I would most likely want to hear a special relation between the fact that the CPU cooler died and that after that it is suddenly giving blue screens.


edit: On low usage the PC runs fine without any errors at all for long periods of time. This was already the case when the CPU cooler was dead, and is now still the case.


Edit 2, system specs:
CPU i7-920 (first series), can handle according to Intel up to 105 degrees celsius.
Motherboard Gigabyte X58-UD3R
RAM 12GB DDR3-1066 I believe
120GB Corsair Forza 3 SSD
2x 1TB HDD
GPU GTX285
Corsair TX850 power supply (maybe a little bit overkill)
- The pc is about 4 years old -

No comments:

Post a Comment

hard drive - Leaving bad sectors in unformatted partition?

Laptop was acting really weird, and copy and seek times were really slow, so I decided to scan the hard drive surface. I have a couple hundr...