Windows 7: Core i5 2500K running hot, causing BSOD 124?

Hi guys,

I think my Core i5 2500K is running too hot and causing a BSOD in Handbrake when encoding large files. I've been leaving my PC on overnight to recode some MKVs for my Plex server, but every couple of nights it will turn itself off or reboot after what is apparently a BSOD error.

The main error report I see when logging back into Windows says:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8009AE3028
BCP3: 00000000BE200000
BCP4: 000000000005110A
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\051112-12698-01.dmp
C:\Users\Ray\AppData\Local\Temp\WER-62572-0.sysdata.xml
Read our privacy statement online:
http://go.microsoft....88&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I started another file encoding on Handbrake and then ran HWMonitor to check the temps. The CPU is running at over 90C, which seems pretty bad to me. I turned off Handbrake and the temps immediately dropped to 50C. You can see what HWMonitor was showing under load here:


I have uploaded the full HWMonitor.txt report here.

I think I'm running at standard speeds, but to be honest I can't remember whether my Asus motherboard's "optimised O/C mode" is running and I didn't have time to check before I left for work this morning. I'm running a stock cooler in a well ventilated Coolermaster case that has, until now, provided decent cooling even under sustained heavy loads. I've not had chance to double check the CPU cooler but I'm usually very careful to make sure they're fitted properly.

The Windows crash report files are below but I don't know how to open the .dmp file without it turning into gibberish:

WER-62572-0.sysdata

051112-12698-01.dmp

Do you think the CPU is causing the BSOD error?

Any tips/advice would be much appreciated. Thanks.

No readable DMP included.
Do it this way...


We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

Quote:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

Quote:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Sorry that's my mistake. I've corrected the URL in my original post but here it is again for convenience: 051112-12698-01.dmp

Again not readable...
Please try again the way I listed in Post 2.
Pay particular attention to the parts in colour.

What version of Handbrake do you have?

It's the lastest version of Handbrake, I can't remember the exact number though.

Strange that the file's not readable again - the first time I just mistyped the URL, but now that it's working I don't understand why the file is not readable. How should I be able to open the file?

I'm at work at the moment so unfortunately I can't get access to the original file again until this evening.

Understood.
We await the DMP's as per Post 2 asap.

No need to compress (zip the files) Why arent you uploading them here?

This is what they look like now

Sorry, I didn't realise I could upload stuff directly here. I've attached it to this message. Thanks!

Does this mean anything?

crash dump file: C:\Windows\Minidump\051112-12698-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8009AE3028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

hello playxray. Your temperatures on your CPU are extremely out of range and need to be handled immediately. If you do not, you will fry your processor. If your processor has been already reaching these temps for an extended period, then there may already be damage that has shortened the expected life of your CPU. First, under your post is a tab that reads "My System Specs". Please select it and then select edit and accurately fill out the information there. If you are unsure of what you have. please use Speccy to get the information. Also, please let us know what type of cooling you have. Are you using the factory heat sink fan or aftermarket, if aftermarket what make and model. Be sure to give us the make and model of the case.

Also, to start, open up your case and see if there is an excess, or any amount for that matter, of dust. If so, using a can of compressed air, clean it out thoroughly.

Thanks,

James