NF7-s v2.0 problems!!!!!!!!!!!

thewizard1785

Banned
Sep 7, 2004
193
0
0
NF7-s v2.0
AMD 2600+ mobile & slk 900u
Corsair Ram
fortron PSU
9700 pro
Seagate 40GB

So I get all my hardware into my case hooked up properly and I turn on the system. I realize that I forgot to hook up a floppy and so I turn off the system and add the floppy drive. I tried to boot the system again and the mobo would start beeping like an ambulance. I remove the floppy drive and try again and the same problem. So I make a checklist to make sure each and every single wire is attached properly. I do that and try again but no success. It sounds exactly like an ambulance.

What do you suggest I should do?
 

Interitus

Platinum Member
Jan 28, 2004
2,143
9
81
mine did that when i used to tinker in the case and forget to plug the extra molex plug into my vidcard.

i'm pretty sure the ambulance sound is AGP error.
 
Mar 19, 2003
18,289
2
71
Originally posted by: Interitus
mine did that when i used to tinker in the case and forget to plug the extra molex plug into my vidcard.

i'm pretty sure the ambulance sound is AGP error.

Not necessarily. Every time I've had the "ambulance sound", it's been because of overheating.
 

thewizard1785

Banned
Sep 7, 2004
193
0
0
Originally posted by: SynthDude2001
Originally posted by: Interitus
mine did that when i used to tinker in the case and forget to plug the extra molex plug into my vidcard.

i'm pretty sure the ambulance sound is AGP error.

Not necessarily. Every time I've had the "ambulance sound", it's been because of overheating.


Well, I checked the heatsink fan and heatsink. I don't any problems with them. AGP is hooked up properly.
The ambulance siren is freaking me out.
 

itshondo

Junior Member
Dec 31, 2004
13
0
0
the 2 tone siren was found to be caused (most of the time) by a lack of contact between the CPU temp thermister in the CPU socket and the CPU- if you remove the CPU and bend the thermister up a bit (so it definitely touches the cpu bottom) it will probably fix the siren.

You might also want to clear your cmos -
 

thewizard1785

Banned
Sep 7, 2004
193
0
0
I will try that. I am trying to collect as much info as I can because I only one AGP video card rite now and switching video card back and forth is just painful.
 

thewizard1785

Banned
Sep 7, 2004
193
0
0
Latest shot:
Removed the heatsink and applied a new layer of Artic silver on the CPU..... nailed the heatsink firmly..... discharged the power supply....then cleared the CMOS.... tried to turn on the computer while holding insert key and still no luck....I tried one stick of Corsair XMS 3500.... also tried corsair XMS 3000 seperately....
The siren is non-stop. It sounds like that police car in the movie Bourne Identity...
 

Jeff7

Lifer
Jan 4, 2001
41,596
20
81
Reset the BIOS, and try to boot again.
It boots to 600MHz because the motherboard can't identify the mobile CPU. You'll need to either manually set the CPU speed, or else get a modified BIOS. Just know, modded BIOSes are made by users, not by the company. The usual void-your-warranty disclaimer applies here.
 

thewizard1785

Banned
Sep 7, 2004
193
0
0
Originally posted by: Jeff7
Reset the BIOS, and try to boot again.
It boots to 600MHz because the motherboard can't identify the mobile CPU. You'll need to either manually set the CPU speed, or else get a modified BIOS. Just know, modded BIOSes are made by users, not by the company. The usual void-your-warranty disclaimer applies here.

No the computer won't boot at all. Forget 600MHz. Plus I don't know what version of bios I have. At the moment I am not gonna try any modded BIOS. Plus I tried different RAM. Corsair pc3500 bh5 256mb, Corsair pc3000 BH6 seperately without any luck. The core of the CPU looks good but the surrounding area about 1 cm from all the sides looks little bit grey. I bought it used from someone and it came just like that.
Could it be a bad CPU.
 

DAPUNISHER

Super Moderator CPU Forum Mod and Elite Member
Super Moderator
Aug 22, 2001
31,941
32,257
146
Originally posted by: thewizard1785

could it be a bad CPU.
Absolutely, but have you tried the thermistor advice, making certaing the cooler is properly seated, that the fan is pluged into the CPU header, and that the fan is spinning? Tha alarm almost always means overheat but on some boards can indicate a bad psu too. I have the NF7-s v2.0 but it is running like a scolded dog so I can't say for certain what the problem is.
 

thewizard1785

Banned
Sep 7, 2004
193
0
0
Yes I tried lifting the thermistor little bit so that its in proper contact with the CPU. The previous user had it at 2400MHz all the time and I am guessing it looks grey because of the overclocking...
PSU is fortron. I tried it in my old system and it works properly so I am guessing its CPU.
I don't know much if ram has anything to do with it.
 

Interitus

Platinum Member
Jan 28, 2004
2,143
9
81
start pulling everything out one by one until you have the bare minimum to post the machine. do 1 stick of ram at a time. I just unplugged the vidcard power and it did the ambulance sound, so whether or not it's specific, I don't know.
 

Noid

Platinum Member
Sep 20, 2000
2,390
193
106
Helps if make an effort to search...

Try this First

let us know how it goes...

Theres a wealth of info and users at Abit willing to help.
 

freshspace

Senior member
Mar 23, 2002
617
0
0
Take out your memory modules, put it back, then reset the bios. I have a Soltek nforce2 board and it does that sometimes if my overclocking fails. Usually happens when I up the fsb too high. Try it.
 

k1114

Golden Member
Nov 15, 2002
1,153
0
76
I am the seller of the processor, and I also ran MotherboardFAQs.com for about a year and a half, about a third of that time specializing exclusively in the NF7-S. First off i'll say that the processor is working (unless damaged during the install or handling somehow), there's no doubt about that. The two tone siren you are experiencing is generally the result of one of the following:

1. An overclock past the limits of a certain peice of hardware
2. A bad stick of ram (less likely) or a bad ram setting (somewhat less likely).
3. Overheating
4. Bios dosen't support processor (not sure how likely, should boot as 600mhz/6x100 with any newer bios)

A two tone siren is not the error you should be receiving with a dead processor. That would yeild nothing (lights come on, fans spin, nothing happens)

What bios is the motherboard running? Any idea? My guess would be either you need to fiddle with the cmos and a single stick of ram (I've brought back "dead" NF7 series boards to life by doing this - the original owners thought they had killed them by overclocking) or get your hands on a non mobile and update the bios.

Also, how many of the other system components have you tested in other systems? I just can't see any scenario (aside from damage) in which the processor wouldn't work.

Edit:

Originally posted by: thewizard1785I am guessing it looks grey because of the overclocking...

This concerns me, can you describe this more? It wasn't burnt or anything, and it was not overheated at any time when I owned it. In fact here's a screenshot of what I ran it at (2.4/1.65v)