Well, I "upgarded" my BIOS to v1.8 without bothering to check these forums... just hoping that MSI would have fixed the bugs by now. Big mistake. Now my computer won't even shutdown and I have to manually hold down my power button just to power off my computer. I've finally had enough of...
spidey07,
Yea, 200-500 Mb/s is kind of what I expected. The gigabit cards are onboard. I ran these tests on recently purchased commonplace Dell servers. I'm wary of making registry changes on servers, so I will try changing the MTU on test workstations.
The server sending the data and the server receiving the data both have similar hardware. Both running RAID 5... both recently purchased commonplace Dell servers. I believe the RAID card is the only card in the PCI slot. The gigabit cards are onboard. Onboard devices don't share the PCI...
The specs are just standard Dell servers.
Raid card is Dell Perc 4di running on Seagate Cheetah 10k RPM, SCSI-3 hard drives on RAID 5.
These are relatively new Dell servers that were put in recently. I know there are overheads and such... but my problem is... we're not even getting close...
I got similar results on my home computer which I recently put together. I tried transferring from one Hitachi SATA hard drive to another identical hard drive. I don't have have any PCI cards installed and my video card is PCI-e.
I have one. It is SWEEEEET. I have THREE 120mm Panaflo fans with fan speed controller. One at back, one in front, and one on CPU. DAMN quiet. Only bad part is that the top of the case collects dust FAST and you can tell because the case is black. I especially like the silent Power supply...
MCrusty and Chaotic, thanks for the quick reply. I would actually be thrilled to even have 25MB/s(200Mbits/s) transfer speed.
The specs are just standard Dell servers.
Raid card is Dell Perc 4di running on Seagate Cheetah 10k RPM, SCSI-3 hard drives on RAID 5.
These are relatively new...
Yes, the SCSI RAID card is on a PCI slot. Heck, we've even tried going server to server and skip the switch altogether by using a cross-over cable and the results were the same. We've tried testing on multiple servers and the results were the same. I've had a friend at a different company run...
I've been doing some tests recently here at work on our gigabit network and I've noticed something peculiar. When I do large file transfers between servers, I noticed that I don't get anywhere near what I should be getting for a gigabit network. Heck, I don't even maximize a 100 baseT network...
I've been doing some tests recently here at work on our gigabit network and I've noticed something peculiar. When I do large file transfers between servers, I noticed that I don't get anywhere near what I should be getting for a gigabit network. Heck, I don't even maximize a 100 baseT network...
Really?? Hmm.... When I installed the new drivers I just installed everything there. I wasn't using a IDE hard drive so I didn't think it would affect me. Right now, I just live with it. About half the time when I turn on my computer, it blue screeens. It works fine once I restart it...
Just got back from a long weekend... turned on my computer... and it kept restarting and blue screening after reaching the Windows XP screen. This thing is really pissing me off. Brand new computer... doesn't work like it's supposed to. I thought everything was finally figured out, but there...
If you read the earlier posts in this thread, you'll see that the problem is most likely because of the bad ethernet card driver that is installed. I think the file that is causing it to crash is like... nvtcp.sys or something like that. The reason why it looks like your computer reboots...
Dude, your computer is probably blue screening. Windows XP defaults it to reboot when you get a BSOD so to you, it seems like the computer just restarted on its own when you actually got a BSOD. Read the earlier part in this thread. You probably just need to install the latest ethernet card...
My driver version is 4.6.8 made on 1/13/2005. If I remember correctly, this version of the driver doesn't even use the nvtcp.sys file. When I do a search on my computer for that file, nothing comes up now. You may have to install the driver manually. I remember when I tried to install it...
I had the same exact problem. Go to www.nvidia.com and download the nForce 4 STANDALONE drivers. It has a different set of ethernet card drivers than the unified one. I haven't had a problem since replacing the ethernet card driver.
hmm, I noticed some static noise on my MSI nForce onboard sound as well. I seem to hear it only when I'm not playing anything and I'm trying to access stuff from my hard drive.
For some reason, the ethernet card driver for the nForce4 standalone uses Ethernet driver 4.68 (WHQL) (which I'm currently using) and the unified nForce drivers uses Ethernet driver 4.42 (WHQL) (which was causing my BSODs).
Make sure you have the latest ethernet card drivers. Mine would randomly BSOD and restart on me too. Figured out it was a file related to the ethernet card called nvtcp.sys. After installing the latest nForce 4 ethernet card driver, I haven't had a BSOD since.
Bukka,
Are you able to get into the BIOS? If nothing comes up, it may be the video card. Do you get any beep codes when the computer starts up? If you are able to get into BIOS, try turning off dynamic overclocking until you get your system up and stable. I noticed it was turned on by...
Broken Visage,
Yes it does. I have that same exact memory working perfectly fine on mine. I haven't overclocked it yet, so I can't tell you anything about that.
yup. nvtcp.sys was the file that was causing the BSODs. I went to nVIDIA's website and turns out there is a newer driver that MSI Live Update didn't have and installed that one. Since then, no problems at all. I ran stress tests on my computer for 20 hours straight with no BSODs. All this...
OK... turns out my computer was rebooting on its own because of IRQL_not_less_or_equal blue screen of death. I just bought this MSI Neo4 board about a week ago. Sometimes, this BSOD happens 10 minutes after I boot up... sometimes a few hours later. Since I just put together all the parts for...
I got my Neo4 mobo last week. The computer has crashed on me a few times... and restarted itself a few times as well. Right now, the only thing I can hear from my computer is my stock CPU fan and NB fan. Any ideas why my computer would restart randomly? I'm thinking its the stock CPU fan and...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.