Recommended Posts

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.com/fwlink/?linkid=104288&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:

HWMonitor.png

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.

Although it sounds like an easy question Wave, Intel now sell a few different "stock" coolers and their new CPU's dont come with a cooler. Is he using the water cooled one? The really small air one or the large air one?

EDIT:// I'm guessing the mid sized air one by your latest post. In that case get a good aftermarket tower style air cooler.

It just seems like any other stock cooler I've had before, so I guess it's a "mid-sized" one. It's definitely air cooled.

I'm happy to replace the cooler but even the stock cooler shouldn't be seeing temps like this should it? If there's another problem causing the overheating I want to address that first - I can always get a better cooler later.

Well whilst the air coolers Intel ship with their processors aren't great you are right to say it shouldn't be this hot. I would expect the high load temperature to be around 70c not 90c - And based on the temperature of your Graphics Card I would take an educated guess and say your case has good air flow.

I assume you've already checked the heatsink for dust so it could be the cooler isn't locked down properly or the thermal paste is not making proper contact. The first thing I'd do is remove the cooler, clean its base and the top of the processor and apply some fresh thermal paste. Something like MX-4 is fine to use and affordable.

It could be a matter of:

A) The heatsink is covered in dust, preventing a decent transfer of heat when under load. Would need cleaning, which is usually an excellent point to check point B.

B) Thermal paste has run it's course, so would need cleaning off and re-applying some new paste. If the heatsink is detached from the CPU, you will need to clean and re-apply the paste anyway.

C) There is a lack of airflow around where the CPU fan draws air, so it isn't getting enough cool air to cope with the increased heat.

  • Like 2

I've only had it for a few months so I think it's unlikely to be dust or dry thermal paste. I guess it could be a lack of airflow but I did a pretty neat job of clearing wires etc when I installed it. I'll check it over when I get home just in case though, it's got to be worth checking.

I know absolutely nothing about voltages - is there any possibility that they're set incorrectly and could be causing this? How would I check?

If it's only a few months old, then I would check the heatsink seating to the CPU as it may have come loose and so will not be making a proper connection.

I wouldn't say it's the voltages, as I've got exactly the same CPU and it's showing the same voltages.

Sounds like I've got the same idle temperatures as you too.

So from what I can figure (and I may be wrong), it could be either an improper seating so the heat transfer isn't good enough...or there was too little/too much paste used when it was put together, again causing a problem with the heat transfer.

Analysed your dump file with WhoCrashed and the details are below:

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.

So yeah definitely an issue with either the HSF (being clogged with dust or faulty) or insufficient thermal paste...or worse; the CPU! Also make sure your BIOS is up to date as well as the chipset drivers.

I would definitely recommend getting an aftermarket CPU cooler, especially if you are constantly stressing the CPU with video encoding etc.

Are you running a stock cooler on yours Aldur82?

I am, but I don't do anything nearly as intensive as video encoding so I don't know if my CPU would end up reaching the same temperatures.

I've been thinking about getting a new cooler (a heat pipe style) as my temperature jumps to about 60 degrees just with listening to music, and idles around 50-52 depending on the ambient temperature of the room.

Is the OP overclocking?

If not, I find it quite annoying the amount of tech heads that instantly say "oh, you have to fit an aftermarket cooler" - which is clearly rubbish. If you're not overclocking, the stock coolers are more than enough to cool it properly, regardless of what you're doing.

If that wasn't the case, don't you think there would have been a massive uproar, and thousands upon thousands of complaints about them over heating?

It's much more likely that there's an issue with dust or thermal paste here.

Is the OP overclocking?

If not, I find it quite annoying the amount of tech heads that instantly say "oh, you have to fit an aftermarket cooler" - which is clearly rubbish. If you're not overclocking, the stock coolers are more than enough to cool it properly, regardless of what you're doing.

If that wasn't the case, don't you think there would have been a massive uproar, and thousands upon thousands of complaints about them over heating?

It's much more likely that there's an issue with dust or thermal paste here.

No one here said "oh, you have to fit an aftermarket cooler".

Is the OP overclocking?

If not, I find it quite annoying the amount of tech heads that instantly say "oh, you have to fit an aftermarket cooler" - which is clearly rubbish. If you're not overclocking, the stock coolers are more than enough to cool it properly, regardless of what you're doing.

If that wasn't the case, don't you think there would have been a massive uproar, and thousands upon thousands of complaints about them over heating?

It's much more likely that there's an issue with dust or thermal paste here.

Actually, if you're constantly raising the temperature of your CPU you're causing degredation - ergo, It's advisable (quite rightly so) to recommend a better after-market cooling solution to maintain the lower temperatures for the longevity of the CPU in cases where high stress is placed on the CPU for long periods of time.

However that being said; yes it really shouldn't be hitting over 70-75c and so there quite probably is either a dust or thermal-paste issue occuring here too.

No one here said "oh, you have to fit an aftermarket cooler".

+1

Yes who are you actually quoting "Wakers"?!

Suggestions have merely been made here and not ultimatums; due to the OP running a lot of video encoding tasks that highly stresses the CPU.You are also assuming that he has not overclocked when in fact he stated in his first post that he does not know if he has or not (his motherboard may have applied an overclock profile to his system from the push of a button or through the use of software): "I think I'm running at standard speeds."

Do you think it's just a coincidence that my CPU is running hot then? I'll have to dig out my spare GPU from the loft and see if that makes any difference to the BSOD, though I still want to get my temps down!

Ok guys well the hot CPU *seems* to have been resolved. It turns out that the "optimised" mode was enabled in the BIOS. I disabled this, and now temps are running at an average of about 70C, peaking at 76C briefly, and I've been recoding files for about an hour. Certainly nowhere near the 90C I was getting this morning after 20 minutes.

I've got a few more files to go through tonight so I'll leave it on again and if it's not crashed by the morning I guess it's safe to say the problem has been resolved.

Thanks for all the help guys.

OK that makes sense! That's why I mentioned an overclock profile earlier. Seems as though the stock cooler couldn't handle the overclock then.

Glad you got it sorted, those temps are much better.

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!