• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

The Official Sudden Northwood Death Syndrome (S.N.D.S.) Thread[Retired sticky]

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
[email protected] dead here. It was on water @ 30-35c 1.7v 3 months till SNDS set in. Will not boot past bios stable at any speed. R.I.P

Research and experience lead me to this hypothesis: many times extreme Speed kills Northwood’s even with a reasonable voltage (Less then 1.75) and temperature (Less then 40c). They just don’t like it.
 
Last edited:
Had a P4 2.4B, SL6EF C1 core running at 3ghz with 1.725V for a bloody week. Now it won't boot at 3ghz anymore, not even with 1.75V. I'm not going to try any higher, I don't want to totally mess this thing up....Back at default speeds now...bah.
It only got about 43degrees stressed...running an Albatron PX845PEV Pro motherboard.
 
Mine's fine

Running 1.8a @ 2.4 for six months @ 1.55 actual volts. No problems here....
 
I've been running my 1.6a rig since february @ 1.95 volts, and 2912mhz 24/7.

And have tried every p4 chip i've ever had probably 10 different one's at over 2 volts.

My 2.8 now doesnt go any faster whether @ 1.68 where i keep it at or over 2 volts.

Point is. If you cant afford to kill the chip, dont overclock it.

Banned by hard OCP for questioning their fake scores, looking for new home
 
Csybe said:


My first BD7II went out after a few days as well, but I don't know if it's in connection with overclocking.

It's funny this should happen to you. The exact samething happened to me after 2 days. After closer observation of the board I noticed that the MOFSETS were not all the same. I think Abit had some quality issues with a couple of BD7ii's as my friend bought the 1 from the exact same store as me and on the same day and his mofsets were all consistent (Same brand) and he has not had a problem. I am still waiting on the verdict of my board, I sent it into abit direct as my reseller does not want to have anything to do with me as I had reminants of dielectric grease in the socket.

At the time I was running the abit I was running my 1.8a @ 2.05 volts, 180FSB. The mofsets were so damm hot I could cook a turkey on them. It didn't make sense at all, as my new Asus board's mofsets do not get nearly as hot @ 180fsb. I have since had some sense knocked into me and I run a little conservative I run @ 1.7v , 3ghz, no more wire wrapping, and by default it seems that Asus boards overvolt in Idle conditions and the vcore drops underload.
 
SNDS

My hardworking P4nw 1.8A @2610 (with 1.70V paint trick) recently refused to work at 2610. A lot of instability problems such as game crash, BSOD, boot problem, etc. Anyway..... thanks to this forum and Rasputin Liver, I don't get shock when having this SNDS problem at first sight. I right away notice this kind of mysterious crash is something to do with SNDS.

I have to downspeed at 135fsb now, and is stable all right.

This is my comp. biodata:

P4nw 1.8A (SL68Q) @2.610GHz (145fsb & 1.70V paint trick)
512Mb Mushkin PC3200 @ CL 2 -3 -3 -6 -1 (2.70V)
Asus P4PE mobo
Temperatures and Voltages see below:
CPU temp: 46C idle & 56C max.loads
Mobo temp: 33C idle & 36 max.loads
12V : 11.712V
5V : 4.919V
3.3V : 3.200V
CPU Vcore: 1.584V
 
Sam, i cant resist, delete this if you like, or tell me to in the return PM, but:

With the exception of Skip and maybe 1 or 2 others, your overclocking very sloppily. I do not mean to be rude, but jumping from 35c to 47c from idle to load (1st or 2nd poster) is entirely unacceptable of a temp differential.

You guys NEED proper cooling, stock heatsinks do not cut it when doing 30%+ overclocks. I agree that there is something fishy going on, but you guys are being careless. Thats entirely your perrogative, but I'm just letting you know, you need to not just watch the temps but the differentials and changes as well. Also, loosing more than .2vcore when going under load is walking the line, im talking dangerously close. And be careful with the voltages.

I ran my old school XP1600+, which I still have now, at 2.3vcore 1.85ghz for almost 6 months, but it was kept at 40-43c with heavy custom watercooling. You guys are playing in dangerous waters (for the CPU's) and taking huge risk's with your chips. Overclocking isn't just pop a chip in with everything stock, crank the vcore mad high, and start bumping the FSB 10mhz at a time. Its about precision, thoroughly testing and burning the CPU for at least 12 hours per setting checking for errors, runing memtest86 for a couple hours each frequency bump to make sure you arent generating errors (which will often not crash the comp, but write erraneous data back to your disk and send it to the CPU), and use prime95 to test system calculation outputs.

Sorry for ranting and disobeying Sam's thread rules, but I had to post this.
 
i experienced identical problems to the ones listed here. i ended up going from 3ghz @ 1.65/1.58 vcore with my 2.26b chip after 4~5 months of use. idle/load temps were 21/28C with my water cooling on a BD7II-Raid. i used the vpin trick for a few weeks, but took it off because it DOES cause trouble.

after that i reseated everything in my system and cleaned the dust off and it all ran like new again just at random one day. it was down to stock speed and voltage barely stable but then one day i opened up a window and put it down to 8C ambient. ever since it has had no problems hitting the same speeds with sane room temperatures. it did not do that after reseating everything including heatsinks and nb heatsink. i still do not know why i could not pass 150fsb but now upwards of 180mhz fsb works again. i have even had the ambient up to 25~27C and been stable at 3ghz.

just something to keep in mind. also as soon as i took the vpin off i gained some stability back, but not all.
 
Id like to add here. I have a p3s 1.26ghz 512k chip that is .13 micron
Ive been running it at max voltage that my mobo supports (1.85v). for the past.... 8 months.
Not a single hicup. Ill also add that I have average cooling at best, my load temp is 49-52c But its completley silent :D

Never had a problem. I think this is just limited to northwoods, not the .13 micron tualatin line.
 
Re: The Official Sudden Northwood Death Syndrome (S.N.D.S.) Thread

Silversinksam said:
Lets make this thread more of a database of Northwoods that have died or degradated prematurely.

Please only post ONCE in this thread if your Northwood has suffered S.N.D.S

Please add the voltage that led to the chips demise(and/or Degradation factors) and roughly how long the chip performed before symptoms of S.N.D.S. appeared.

You can always edit your initial post if you have had more than one Northwood casualty.

AGAIN PLEASE ONLY POST IN THIS THREAD IF YOU HAD A NORTHWOOD CHIP THAT SUFFERED SUDDEN NORTHWOOD DEATH SYNDROME.



*credit to Rasputin'sLiver for aptly naming this Northwood disease


hmmm good time to go AMD!! hehehe
 
I would like to add evidence of the "Expected Athlon Death Syndrome" called "EADS", these are 4 of the 5 samples (the last one was a Palamino core) I damaged in 2001. Since then I am with a Pentium 4, have used maybe 8 of them within 1 year, running them at insane voltages (pin wire mod) and frequencies: 2.66@3700 Mhz with a vapochill. I haven't seen a dead Pentium 4 since then nore have I ever heard of any among all the 1000s of Pentium users at OCAU.

Cemetry.jpg
 
Don't you think...

Don't your think that if you are overvolting and/or overclocking your CPU that you are voiding the warrantee? I have overclocked before and have fond memories of my Celeron 300a @ 464, but I always knew that it was risky. Anyone that overclocks, destroys the CPU and then expects the CPU maker to replace that CPU should prolly rethink what they are doing and what they can reasonably expect from the manufacturer.
 
Unstable after 8+ months

I think I may be running in to SNDS.

I have a 1.6a that I've been running at 2.4Ghz ( 150FSB & 1.6v ) since March. Recently I've gotten BSOD during gaming several times. (not all of the time- just randomly sometimes)

Tried a few things to solve it....
Clean the dust out of case.... kept everything running cooler
Back down the OC on vid card.... nope not it
Fdisk, reinstalled OS.... put back all GOOD(some older) drivers
Still get it....

I'm thinking about getting a new mobo & a 2.4B

Current system: (since 3-24-02)
P4 1.6a @ 2.4Ghz with 1.6v
Asus P4S333 (sis645) mobo
256MB Corsair XMS3000 @ 2-3-3-6 - 5:4 ratio
GF4ti4600 @300/700
etc...
http://www.crowdcontrolusa.com/overclock
 
AMD sudden death ?

I am reading these posts about S.N.D.S with great interest because Ive been considering building my first Intel box in years. I feel for you guys (and girls) having box problems because nothing is worse than your toy being on the blink..

As far as AMD box's suffering this same fate I would only say that I dont understand why some people feel the need to post in this Intel thread about AMD processors that have failed. We all know about the fragile Athlon core and the special handling it requires. I have been using AMD cpu's since the Athlon first came out and have 3 of them running right now...all overclocked. Any CPU can fry if the person building the system makes a mistake or gets carried away with pushing the system. My best OC has been an Athlon Thunderbird AXIA 1G @ 1.4G solid for 2 years now. While im not suggesting AMD cpu's are any less likely to fail than Intel processors, this thread has given me second thoughts about that 1.6A box idea I was playing with. Also i think some people would like to turn this thread into a "mines better than yours" flame war. Please resist the urge and keep up the good posts about this growing? Northwood problem. Thanks guys for the great info on this issue.
 
Tedinde said:
Banned by hard OCP for questioning their fake scores, looking for new home

We at [H]ard|OCP do not post "fake" scores and never have. Did we post a benchmark that was wrong? Yes we did. We corrected it and all of this has been addressed directly with our readers on our front page with an apology to our readers for not acknowledging the change immediately. We made a mistake and we are sorry for it. If one mistake discounts five years of work, so be it.

Many folks that are claiming innocence were banned for posting pornography and making all sorts of statements insulting myself our site and threatening my family with violence. They do seem to leave that out though when relating their "banned story".
 
Can those of you who have permanently lost your P4 CPU's remove your heatspreader and investigate whether it looks like it had good contact with your die?

I have wondered just how good that heatspreader is; I know protecting the die's physical integrity is critical, but is that heatspreader a good thing when you are overclocking? That is one other possible difference between our P3 overclocks and the P4's that may account for these death syndromes.
 
Back