Alienware 17 R4 2017 review
Specs: Q8300, P5Q SE, GTX 260, 4GB Corsair 800mhz, OCZ Fatality 550W PSU, Windows 7 32-bit
A couple of days ago my PC suddenly grinded to a laggy halt. I could jerkily move the mouse around but nothing else would respond. Eventually I just switched it off at the back. I wasn't running anything particularly taxing, just an MSN conversation, a browser window and Spotify.
Upon powering back up, I was immediately warned about a CPU temperature problem. I checked in the BIOS and indeed, it read 87.5C. I suspect that one (or more) of the push pins on the heatsink popped out, as this happened once before last year and there always seems to be a lot of tension when seating it.
Anyway, I replaced the processor and heatsink with an older one (E5200, stock heatsink), and my PC worked as normal. After presumably eliminating other parts as the problem, I decided to give the original processor another shot so I replaced the thermal grease and re-installed it. Temperatures were about what I'm used to (~35C idle up to around 60C if playing a demanding game) but now the system was crashing constantly. BSODs relating to a whole range of dlls. One of the more interesting BSODs said:
The stack memory was corrupted by a device driver, likely due to attempt by malicious software to gain control of the system.
If I underclock the processor the system runs quite happily. At stock speeds it will crash consistently, sometimes before Windows can even finish loading.
I'm fairly sure that I'm going to be buying a new component (or two) before this issue is fixed, but what is the most likely problem here? Processor seems obvious but if it was really damaged the other day I wouldn't expect it to work at all.
Any feedback would be greatly appreciated.
just tested link it does not for some reason take you to the page with the relevant info on...
You still may find the info with the error message the BSOD throws at you from the link ( just goes to home page)...
Ok, odd update to this.
I ran the processor at 2.25ghz with no problems, so I figured that if it could run perfectly at 90% of its usual speed, it was strange that it ran so badly at stock numbers. So I turned the FSB up to 400 (3ghz), a speed I've used on occasion for GTA4. And the system ran fine.
Surprised, I set the FSB back to 'Auto' and after a reboot, Windows crashed twice upon loading. Back to 3ghz again, which is what I'm on right now, and it's plain sailing.
one of your sticks of memory may be faulty, try with only one at a time
PS if you have a PC Health tab in BIOS check what Volts the CPU are getting and what it should have. if its too many its going to run hot, If you have messed with Volts to Overclock this is most likely the problem
This thread is now locked and can not be replied to.