Sign in with
Sign up | Sign in
Your question

How do i know if my northbridge needs an aftermarket heatsink?

Last response: in Overclocking
Share
November 7, 2010 5:10:24 PM

How do i know if my northbridge needs an aftermarket heatsink.

It is hot to touch and the heatsink that comes with the motherboard is compact.


Do i need to buy a special heatsink?

Nothing seemed to be going wrong in my system, but when I game I get some crashes, could the northbridge be causing that? (usually the error is, memory something error)
a b V Motherboard
a c 190 K Overclocking
November 7, 2010 5:35:29 PM

Northbridges do tend to get hot in use, not normally hot enough to cause issues though, (Sidenote, dont touch it)
if your error messages are mentioning memory, I'd be inclined to pursue that avenue of investigation first,
download memtest and run each of your sticks a couple of hours, see what that tells us
Moto
m
0
l
November 7, 2010 6:18:50 PM

i ran memtest for a weekend and got 2 errors in 38 passes, which I imagine is an acceptable rate.

ive looked at some NB heatsinks... are the mini towers with heatpipes over kill?
m
0
l
Related resources
a b V Motherboard
a c 190 K Overclocking
November 7, 2010 6:53:54 PM

depends how heavy your going with overclocking tbh, most people wont need them though,
and errors are errors Im afraid, any weakness in your sticks is bad, its just a case of when they fail, I'd look to getting some fresh ram for your rig, and I'm betting that will sort your random crashing,
how are your sticks configured? try playing with one stick of ram, see if either one causes the issue particularly
Moto
m
0
l
a c 330 K Overclocking
November 10, 2010 2:55:15 PM

^Agreed.

With RAM/memory errors, you typically have an issue with an unstable OC or you have bad memory. If you aren't overclocking, move on to focusing on RAM itself.

Try Memtest with each stick, one at a time, in each DIMM slot to see what results you get.

I'll be honest, I've actually had times where a bad NIC (prior to onboard LAN) or soundcard was causing the issues. So, that being said, pull as many components as possible that aren't required for your system to run, including DVD drive(s). This helps eliminate variables in testing that you might not be aware of.
m
0
l
!