It's been running fine...until the next time it does this. lol I took the calculated risk of being the early adopter of an unknown budget card just so I could get my Athlon 64 and PCI express. Since it was only 100 bucks I'm not too concerned it it turns out to be junk. If it were a $280 Asus sli card I certinylu would be. This chaintech board actually seems to be doing fine- no stability problems or anything.
haha- same exact thing just happened 5 minutes ago while i was downloading somethin else. I guess I will have to put my motherboard in the corner for on a 5 minute power-deprived timeout. bad motherboard, bad...
Well, according to a search I did on AT forums and also on xtremesystems.org, people seem to report issues with the Chaintech board, while the none-ultra version that the Gigabyte K8NF-9 is based upon, seems trouble-free so far - not to mention it also has firewire 'b' and it's a better overclocker, but this has no concern to me as I don't intend to overclock ATM.
I think i'll be getting myself a K8NF-9 along with Gigabyte GF6600GT PCI-e instead of a K8NS-939 along with Leadtek GF6600GT AGP: the K8NF-9 sports 2 more S.ATA ports, Firewire 1394b (800MB/s) and most importantly: PCI-e. also, the memory on the 6600GT PCI-e is clocked higher than the AGP version and also is cheaper since there is no need for conversion 'PCI-e to AGP' on the card, that is why the chip that does this is missing and that translates into a lower MSRP.
I have not seen this issue on my VNF4 at all. I have been running it for 10 days now without any hitch, and I have not seen my network connectivity drop out ever. Must be a problem with some boards, but not others. Too bad too, since the board is a great board otherwise.Originally posted by: Trente
Well, according to a search I did on AT forums and also on xtremesystems.org, people seem to report issues with the Chaintech board, while the none-ultra version that the Gigabyte K8NF-9 is based upon, seems trouble-free so far - not to mention it also has firewire 'b' and it's a better overclocker, but this has no concern to me as I don't intend to overclock ATM.
I think i'll be getting myself a K8NF-9 along with Gigabyte GF6600GT PCI-e instead of a K8NS-939 along with Leadtek GF6600GT AGP: the K8NF-9 sports 2 more S.ATA ports, Firewire 1394b (800MB/s) and most importantly: PCI-e. also, the memory on the 6600GT PCI-e is clocked higher than the AGP version and also is cheaper since there is no need for conversion 'PCI-e to AGP' on the card, that is why the chip that does this is missing and that translates into a lower MSRP.
Hey guys,
Was having this exact same problem with my Chaintech board. I noticed that there were consistent collisions for traffic on this NIC as reported through my LinkSys BEFSR41 router. Tired of trying to fix it, I resolved it by having to add a third-party NIC instead of using the onboard one.
HOWEVER, the updated BIOS drivers from Chaintech's website (recent as of a couple of weeks, I think) seem to have done the trick. I'm back to using the onboard NIC and have freed up that precious PCI slot for my soundcard now.
Please note : this was after a clean install of Windows XP Pro using ONLY the drivers found on the Chaintech website - NOT the drivers that came on the CD with the 'board itself.
Hope this helps.
Cheers,
LankaBoy
Was having this exact same problem with my Chaintech board. I noticed that there were consistent collisions for traffic on this NIC as reported through my LinkSys BEFSR41 router. Tired of trying to fix it, I resolved it by having to add a third-party NIC instead of using the onboard one.
HOWEVER, the updated BIOS drivers from Chaintech's website (recent as of a couple of weeks, I think) seem to have done the trick. I'm back to using the onboard NIC and have freed up that precious PCI slot for my soundcard now.
Please note : this was after a clean install of Windows XP Pro using ONLY the drivers found on the Chaintech website - NOT the drivers that came on the CD with the 'board itself.
Hope this helps.
Cheers,
LankaBoy
I tried the power cord thing it only seemed like a temporary solution for me.
However from this thread I downloaded / installed the ethernet drivers from the MSI K8N nForce4 chipset driver package and everything's working fine now.
Before I've been using the Chaintech drivers off the CD.
Edit: I spoke too soon. It seemed to be another temporary fix and now my onboard Gigabit ethernet has crapped out completely. :| I've resorted to using a PCI ethernet card since I can't afford a 2 week downtime to get my motherboard RMA'ed.
However from this thread I downloaded / installed the ethernet drivers from the MSI K8N nForce4 chipset driver package and everything's working fine now.
Before I've been using the Chaintech drivers off the CD.
Edit: I spoke too soon. It seemed to be another temporary fix and now my onboard Gigabit ethernet has crapped out completely. :| I've resorted to using a PCI ethernet card since I can't afford a 2 week downtime to get my motherboard RMA'ed.
try this:
1 go to Control Panel -> System -> "Hardware" tab -> Device Manager.
2. Find the nForce networking controller, right-click to properties.
3 Click on the "Advanced" tab
4. Set "Checksum Offload" to Disable.
1 go to Control Panel -> System -> "Hardware" tab -> Device Manager.
2. Find the nForce networking controller, right-click to properties.
3 Click on the "Advanced" tab
4. Set "Checksum Offload" to Disable.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter