Thermal Paste needed for Slot 1 CPU?


Recommended Posts

I?ve ordered a Pentium 3 550mhz (SL3F7), minus heatsink. I already have a 600mhz (SL3JM) version siting around, that never worked properly, that has attached a large passive heatsink. I had to modify this h/s, cutting off the ends, so that CPU could be seated in the slot (it still only mounted adequately, not 100% securely). Anyway, question is: if I swap that h/s onto the 550, do I need then to use any thermal paste between CPU and sink? There?s a white plastic looking patch on the h/s where it mounts to the CPU.

Link to comment
https://www.neowin.net/forum/topic/847680-thermal-paste-needed-for-slot-1-cpu/
Share on other sites

Most of the people on this board are probably not old enough to remember the P3 :-p

The white plastic thermal pad should be cleaned off and new thermal paste applied between the CPU and the heat sink. I would probably recommend using a fan, as I'm not sure a passive HS is adequate for a P3 550. I had a room with two P3 1 GHz PCs and an Athlon 733 MHz at one point and remember it being quite a hot room.

Sounds like cotton swabs and alcohol is the ideal way to clean the old paste off:

http://www.overclock.net/amd-cpus/335074-b...-paste-off.html

Hope this helps!

Very helpful, cheers! I drew a blank from a local hardware store and chemist, for those cleaners mentioned in that link. I removed the white pad from the h/s using my thumbnail and Auto Glym Engine & Machine Cleaner ?basically a ?powerful water-based biodegradable degreaser?. I?m reluctant to try that on the CPU. I?ll try again for something more appropriate tomorrow, unless you think I can get away with the Auto Glym cleaner?

I?ve got some Arctic Ceramic, that would be okay to use as thermal paste?

Perhaps the 600MHz CPU never worked well because it was using just a passive heat sink.

Incidentally, back in the P3 days, I typically just used contact without any fancy thermal pastes to attach and active heat sink/fan to a slot1 P3.

These days, the thermal paste may cost more than the CPU.

The 600 booted up fine, and I could use various programmes, but FireFox crashed if you visited various web pages. FF had to be used as the browser, so I dumped the 600.

That just sounds to me like it needs a proper heatsink/fan combo. It's designed to be 600/100 but how well does it run at 400MHz (400/66). It should be locked at 6x.

Very helpful, cheers! I drew a blank from a local hardware store and chemist, for those cleaners mentioned in that link. I removed the white pad from the h/s using my thumbnail and Auto Glym Engine & Machine Cleaner ?basically a ?powerful water-based biodegradable degreaser?. I?m reluctant to try that on the CPU. I?ll try again for something more appropriate tomorrow, unless you think I can get away with the Auto Glym cleaner?

Honestly, I would avoid things like that altogether. You want something that is completely pure and that won't leave behind any sort of residue. Ideally something like isopropyl alcohol (but not things like nail-polish remover, because that has additives), although acetone will also work extremely well provided the surfaces are metal. Heat spreaders and sinks usually are, but going from memory I think most of the slot 1 boards expose the processor directly and don't have a heat spreader, and so could potentially be damaged by acetone. Go with isopropyl alcohol, and give the heat sink a going over as well, in case the automotive cleaner left anything behind.

Provided the heat sink and processor physically touch, any HTC compound should be fine. I don't know what that particular Arctic product is, but it'll probably be fine.

Thanks for everyones advice.

That just sounds to me like it needs a proper heatsink/fan combo. It's designed to be 600/100 but how well does it run at 400MHz (400/66). It should be locked at 6x.
But why didn't the whole system crash, if you're suggesting the CPU thermally shut down? It was just FF that crashed and only on certain web pages, always the same pages. I'll see if it runs at 400.

Well the 550 isn?t working either. Just like the 600, it boots fine, and no problem with other programs, and no problem with most sites FireFox visits, apart from a few where ?Doctor Watson for Windows NT? interrupts things with: ?an application error has occurred and an application error log is being generated. FireFox exe.?

It?s not overheating, I aimed a fan at it.

According to this site, these CPU's should work with my P2B rev 1.10:

http://homepage.hispeed.ch/rscheidegger/p2...pgrade_faq.html

I was thinking maybe one last chance and get the 400 version of the Celeron 333, that it?s already running.

Edited by Deisel Weisel

Isopropyl Alcohol works well to clean

Arctic MX-2/3 is great paste.. Its like Arctic silver 5 but without the set in time

Two different processors, but the same problem.... Sounds to me like you're barking up the wrong tree. I would re-think my diagnosis if I were you.

I'm thinking he should run Memtest and test his memory for defects.

Two different processors, but the same problem.... Sounds to me like you're barking up the wrong tree. I would re-think my diagnosis if I were you.

+1

If the only issue you're seeing is Firefox crashing on certain webpages, that would not suggest a processor issue. Sounds more like a software issue, but it's hard to say without getting the full picture (system specs, OS, Firefox version, etc).

I'm thinking he should run Memtest and test his memory for defects.
The current Celeron 333 works fine. Maybe Pentium uses the memory slightly differently. Maybe I'll try that Memtest when I have time. Thanks.
+1

If the only issue you're seeing is Firefox crashing on certain webpages, that would not suggest a processor issue. Sounds more like a software issue, but it's hard to say without getting the full picture (system specs, OS, Firefox version, etc).

Okay, I'll list the spec later.
I'm thinking he should run Memtest and test his memory for defects.

Memtest is a good idea, you should aim for 10 rounds without any errors.

I built a PIII 667 based computer & found that the processor + motherboard + RAM is finicky & originally led to many strange program crashes, etc. In that particular case I figured out that I had to clock down the bus from 133mhz to something like 119mhz in order to not get any memtest errors, which itself was sneaky b/c the memtest errors would only come up on the 6th or 7th round of memtest. System runs stable now.

This has got slightly off-topic, maybe I should start another thread, but re potential RAM probs: Not had a chance to use Memtest yet, but I did try each of the 3 RAM sticks individually and they all got Doc Watson coming up, on those web pages. 2 x Kingston 128mb and 1 x Crucial 64mb. My test makes it far less likely memory probs are the cause of Doc Watson, right? Unless all 3 sticks are faulty.

Aiming a fan at a heatsink isn't the same as a proper heatsink/fan combination. Celeron 333s didn't really need active fan combos but the 550 and 600MHz P3 were designed to use an active heatsink/fan combination.

Okay Fred, thanks.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • 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!