|
|
Post by Ashley98 on Sept 16, 2019 9:21:14 GMT -5
Hi guys I got a brand new unopened nf3 250gb. Just recently got around to using it after sourcing a 3400+ and 3700+ however certain Nvidia cards don't send to work on it ...powers on for 3-5 seconds then powers off. Tried Geforce 6200 , 6600gt , 7800gs (2 of them). However all Radeon cards work fine but after driver install black screen .
Really have no explanation on why it is it doing it. Maybe you guys have experienced this problem before. I remember my MSI board with same chipset not playing ball with newer cards but nothing like this
|
|
|
|
Post by Mr.Scott on Sept 16, 2019 15:30:21 GMT -5
Nope. My NF3 250 runs everything I throw at it without an issue.
What PSU are you using on it?
|
|
|
|
Post by ShrimpBrime on Sept 16, 2019 15:40:41 GMT -5
Populate only the outer of the three memory slots. Or if one stick the one closest to the Cpu.
|
|
|
|
Post by Ashley98 on Sept 17, 2019 5:15:24 GMT -5
Nope. My NF3 250 runs everything I throw at it without an issue. What PSU are you using on it? 500w delta unit only 3 years old |
|
|
|
Post by Ashley98 on Sept 17, 2019 5:15:58 GMT -5
Populate only the outer of the three memory slots. Or if one stick the one closest to the Cpu. ruled that out too |
|
|
|
Post by Ashley98 on Sept 17, 2019 5:20:13 GMT -5
Radeon 9800 pro works and Installs Geforce 4 ti 4200 works and Installs Radeon x1950 pro boots but looks like this in device manger i.ibb.co/CtpvSvR/IMG-20190916-161530.jpgAll Nvidia 6-7 series cards act like there is a short and shut the system off after 5 seconds |
|
|
|
Post by Bones on Sept 17, 2019 6:29:55 GMT -5
Good question.
You did replace the CMOS battery if it had one sitting in it when received right?
Clean the goldfingers in the slot(s), they may have some crap on them from it just sitting all that time.
|
|
|
|
Post by Ashley98 on Sept 17, 2019 8:39:46 GMT -5
Good question. You did replace the CMOS battery if it had one sitting in it when received right? Clean the goldfingers in the slot(s), they may have some crap on them from it just sitting all that time. Yeah gave everything a clean it looks nice and shiny this thing was stored in an attic space for 14 years so I had to replace the CPU filter caps not if the rest are ok all the black caps looks fine all the kzg one were shot. Yeah gave it a new battery too |
|
|
|
Post by Bones on Sept 17, 2019 8:56:21 GMT -5
May be nothing more that you just need to run it awhile.
Sometimes when one has sat for a long time it will act out and just running it eventually solves the problem. Can't tell you how many times I've set one up that's been sitting around and it was doing some crazy stuff but eventually started acting right after some runtime was on it.
|
|
|
|
Post by george on Sept 17, 2019 11:04:10 GMT -5
Windows XP with all Service Packs and patches, before you install the card(s) that cause problem? BIOS 05/04/2005-NFORCE-CK8S-6A61CD49C-00 is latest for that board?
|
|
|
|
Post by Ashley98 on Sept 17, 2019 11:53:33 GMT -5
Windows XP with all Service Packs and patches, before you install the card(s) that cause problem? BIOS 05/04/2005-NFORCE-CK8S-6A61CD49C-00 is latest for that board?
My disc is latest patches and on latest bios too |
|
|
|
Post by Mr.Scott on Sept 17, 2019 15:33:48 GMT -5
That's not normal. You should be seeing only 2 x1950 entries, working or not. Your device manager is showing a working primary display x1950 and a half a dozen non working secondary displays. |
|
|
|
Post by ShrimpBrime on Sept 17, 2019 18:52:56 GMT -5
Yea, this is strange. Usually windows just doesnt see the card.
I would uninstall and run DDU once see what happens. Its almost like there is 6 different driver versions installed?
|
|
|
|
Post by george on Sept 18, 2019 11:51:55 GMT -5
phenomtoo, you probably know all this, but here is my 2 cents. While in BIOS menu do all voltages& temps look OK(when having the problem VGA card in)? Does it stay on while in BIOS or does it shut down while Windows boots, loading drivers? Could also try with a Linux live-CD to see if it keeps going or shuts down. If it keeps going with the Linux live-CD, then it is likely a software/driver issue. Could also try with various Nvidia chip set driver for the motherboard, before installing the problem card. Does GPU-Z show correct info for each card(if it stays going that long to get the info)? As a test, reduce AGP multiplier in BIOS, if such option exist.
Any capacitor running excessively hot?
Remove chip set heat sink, clean up the old glue and re-apply fresh paste.
|
|
|
|
Post by Ashley98 on Sept 19, 2019 18:11:49 GMT -5
Hi guys thanks for the posts. been busy with work
It could be the windows install my install CD is a bit messed up since it's burned onto a DVD-RW I have since purchased some CDRs and will burn a new one
With the x1950 pro in I can boot but 6x VGA Generic shows in device manager I installed the driver many times + DDU and it installs but after reboot it says 800x600 on my monitor flashes hangs for a bit then reboots. This card works and have had some weird behaviour on other boards (p4c800-e) where bios screen will be in 16 colours. But nothing on the extent of this.
Board seems fine after I got it full recap of KZG crap caps which did work but I wanted new rubycons on the primary filers for the CPU the rest of the board are nichicons but there is like 5 small KZG caps one near agp not sure if they filter agp. Board has had new past on chipset btw. Also bumped down the agp to 4x still no change.
What is strange the board doesn't turn off like it's a sudden short it comes on for about 3-4 seconds I've had boards that shut off within half a second not sure if it's even a short as it seems to be Nvidia cards only
|
|
|
|
Post by obscureparadox on Jul 20, 2020 6:07:42 GMT -5
Sorry to necro bump this thread, but have recently got my boards out to play with them and I'm having 2 issues, firstly I'm hitting some sort of artificial FSB limit of 270MHz on 2 different boards that I don't seem to be able to overcome at all, hangs on "detecting raid array" then loops on two different boards :/ Admittedly only tried Venice CPUs in them thus far so could be that?
Also is anyone aware of any modded Bios that provides the 05/04 ram divider for the Venice chips? I would rather not buy another motherboard just to get the feature :/
Many thanks!
|
|
|
|
Post by Mr.Scott on Jul 20, 2020 15:37:32 GMT -5
Don't use raid. Don't even use AHCI or the onboard SATA controller. Standard IDE or IDE to SATA adapter. Your FSB wall is bios related, along with your positive divider issue. Rebels Haven 623 bios is what I used to use. RH.zip (355.64 KB) |
|
|
|
Post by obscureparadox on Jul 20, 2020 16:47:19 GMT -5
Don't use raid. Don't even use AHCI or the onboard SATA controller. Standard IDE or IDE to SATA adapter. Your FSB wall is bios related, along with your positive divider issue. Rebels Haven 623 bios is what I used to use. View AttachmentI don't, it's a standard IDE drive, but it seems like it hangs there going through checks shows 49 or 4B on my poster when it hangs, I've tried a couple of different Bios and both wall at the same place on both boards, I'll give that a go tonight though. I was aware that the lack of 05/04 was a Bios issue but it's not available on the latest Bios on lejabeach but I will certainly try your Bios tonight and go from there. Appreciate the help as always  |
|
|
|
Post by Macsbeach98 on Jul 20, 2020 17:48:09 GMT -5
Either the board has an instability or the CPU is over its limit my NF4X does the same thing (Detecting Raid Array) if I overclock way over what its capable of.
I also have a 754 Lanparty that does that at stock settings (cant install) havent had a chance to figure that one out yet but its some sort of instability in the board.
I have seen it in other boards of that chipset I think the Gigabyte K8NSC-939 does it too.
|
|
|
|
Post by Bones on Jul 20, 2020 18:19:46 GMT -5
It's usually as said, when you reach the setup's limit is when it does that.
However, sometimes using a lower RAM divider helps a little with it.
Note I said sometimes, not that's it an actual solution/fix for it everytime because it's not.
|
|
