New NForce Driver out tommorow

J-Mag said:
These new drivers DO allow me to use NCQ (it was enabled by default after I installed them) and I have been running for a couple days now with zero corruption problems...

I am not sure if it also allows me to see my DiamondMax 10's with all BIOSes yet but they do detect fine in 1002 and 1004.001 (through all reboots).

I will test on 1003 this evening to see if there is any effect.


Hey, good luck. Perhaps 1004.001 was the BIOS that did fix the compatability issues as long as a decent driver was also implimented.
 
Hmmm... This is interesting..... Does this only apply to the SATA Diamondmax 10's or the ATA As well? I'm usung a Ultra ATA 133/ Diamondmax 10 250Gb Drive and windows keeps hanging on startup..... Freezes at the spash screen) Boots into Safe Mode just fine... But hands whenever I try to fully load windows..... Repaired XP, and then even did a Re-nstall and still the same..

Really strange thing is that it worked for a couple hours before locking up at boot....
 
Impaqt said:
Hmmm... This is interesting..... Does this only apply to the SATA Diamondmax 10's or the ATA As well? I'm usung a Ultra ATA 133/ Diamondmax 10 250Gb Drive and windows keeps hanging on startup..... Freezes at the spash screen) Boots into Safe Mode just fine... But hands whenever I try to fully load windows..... Repaired XP, and then even did a Re-nstall and still the same..

Really strange thing is that it worked for a couple hours before locking up at boot....

And you have an NForce 4 motherboard I assume? Well, the IDE controller would be in the chipset just like the SATA controller. I've never looked up what the IDE Diamond Max 10's have for features, but if they are NCQ drives, then I suppose they would, since the issue is if the drives are NCQ basically. The Seagate NCQ's weren't as bad, but some people had problems with them too.
 
DFI-Ultra-D.......

Gonna give this one more shot onthis drive, Re-install all my drivers again and see what happends....
 
Impaqt said:
DFI-Ultra-D.......

Gonna give this one more shot onthis drive, Re-install all my drivers again and see what happends....

Good luck. Just to ask, does it drop the drive right from the start, or does it take a couple reboots?

And just to get the "n00b" type questions out of the way, have you checked the jumpers on the hard drive just to be sure. Not trying to treat you like a n00b, just figured I'd ask the obvious, everyone sometimes forgets the basic things once in a while. :)
 
Arvig said:
And you have an NForce 4 motherboard I assume? Well, the IDE controller would be in the chipset just like the SATA controller. I've never looked up what the IDE Diamond Max 10's have for features, but if they are NCQ drives, then I suppose they would, since the issue is if the drives are NCQ basically. The Seagate NCQ's weren't as bad, but some people had problems with them too.

I don't think you can have NCQ on an IDE drive, it is only a SATA command method.

It probably just boils down to that point that nforce4 drivers hadn't really been released... The 5.10's were technically from nforce3. So with teh combination of NEW drives and a NEW chipset with OLD drivers is what gave us problems...

I read over on anandtech that man people have problems with the 6.39 updates ethernet driver... I can ovutch for this as well cause I wa sgetting booted from games with regularity, until I switch NICs...
 
Turns out my issue was a Dead NVidia Ethernet port.... Had drive is perfect... and Yes.. Jumpers were correct....

I may be a noob here, but I've been around a while.... EOCF is my primary stomping grounds, but this forum seems pretty cool as well....
 
Impaqt said:
Turns out my issue was a Dead NVidia Ethernet port.... Had drive is perfect... and Yes.. Jumpers were correct....

I may be a noob here, but I've been around a while.... EOCF is my primary stomping grounds, but this forum seems pretty cool as well....


Wasn't trying to say you were a n00b in general, or assuming you were because it says "n00bie" in your title, I know the title is just an abstrat way of indicating post count, something I ignore on any message board. Just suggesting you try some of the obvious stuff, everyone overlooks the obvious once in a while because well...it seems so obvious. ;) Or at least I have once or twice.

Was going to reply to j_mag in this post too, but i'll do a new post to avoid confusion.
 
J-Mag said:
I don't think you can have NCQ on an IDE drive, it is only a SATA command method.

It probably just boils down to that point that nforce4 drivers hadn't really been released... The 5.10's were technically from nforce3. So with teh combination of NEW drives and a NEW chipset with OLD drivers is what gave us problems...

I read over on anandtech that man people have problems with the 6.39 updates ethernet driver... I can ovutch for this as well cause I wa sgetting booted from games with regularity, until I switch NICs...

I HAD to use a beta, either the motherboard cd's drivers or a beta I found at www.guru3d.com, beta 6.14 to get my board going, 5.10 wouldn't even attempt to install. So for what it's worth, I had all the NCQ hard drive problems with drivers newer then 5.10, albeit all beta drivers, I heard all the motherboard CD ones were betas too.

I MAY have had problems with my 6.39 chipset ethernet drivers too then, I got punted a couple times myself, but at the time I attributed it to the cable service just being a bit iffy that day, since it's only happened during one day. Haven't tried the Marvel lan port at all.
 
I can confirm that the ethernet driver in the 6.39 release is borked...

I did a roll back to the previous driver on the nvidia lan, and I was having zero problems last night (all problems I had previously attributed to overclocking.... heh...) and yes I did switch form the marvell port to the nvidia port....

It is really annoying actually because I hate it when drivers or software cause instability... THATS MY JOB DAMNIT!!!!!!! :eek: And I am normally doing osmething that might cause instability, so I ended up dorking around with BIOS settings for a day or two before I realised that I was getting droped out of network games due to the stupid driver...

I am currently using both the older LAN driver and the older NAM/Firewall and everything else is from the 6.39 package... (still haven't bothered to upgrade video drivers yet...)
 
J-Mag said:
I can confirm that the ethernet driver in the 6.39 release is borked...

I did a roll back to the previous driver on the nvidia lan, and I was having zero problems last night (all problems I had previously attributed to overclocking.... heh...) and yes I did switch form the marvell port to the nvidia port....

It is really annoying actually because I hate it when drivers or software cause instability... THATS MY JOB DAMNIT!!!!!!! :eek: And I am normally doing osmething that might cause instability, so I ended up dorking around with BIOS settings for a day or two before I realised that I was getting droped out of network games due to the stupid driver...

I am currently using both the older LAN driver and the older NAM/Firewall and everything else is from the 6.39 package... (still haven't bothered to upgrade video drivers yet...)

Oh fun. Oh well, guess I get to dig out my motherboard's CD...or actually go to Marvel's site and pull down their drivers. C'est la poop I guess. Or I can do what you did and just roll back the ethernet port driver...think I'll do that, still like the idea of using the chipset LAN port if I can.
 
Tips on installing this new driver? Should I uninstall first? If so, which drivers? All but display? And should I use driver cleaner?
 
I can't remember where I read this, maybe PCStats, you really want to use the chipset Ethernet port anyway, with Active Armor turned on. Form what I recall the CPU utilization was less and the throughput greater than whatever other ethernet chip was onboard and better than when Active Armor was off (as hard as that is to believe.) Does anyone else remember seeing that?
 
Dr. X said:
Tips on installing this new driver? Should I uninstall first? If so, which drivers? All but display? And should I use driver cleaner?


Driver cleaner is nice but I wouldn't worry about it unless you're really cluttered IMO. Really, I'd pull the whole mess, or at least chipset and display at the same time (or if you're using an ATI card, display first then chipset). Reinstall chipset FIRST, then your display driver.

I usually don't bother with pulling the sound driver or anything else, but I'm possibly being lazy...if a PC is in bad shape (my best friend's systems tend to get really cluttered really fast...with all due respect to him he knows enough to be really dangerous, and thinks he knows more then he does), I'll yank the whole mess and start over.
 
WheresWaldo said:
I can't remember where I read this, maybe PCStats, you really want to use the chipset Ethernet port anyway, with Active Armor turned on. Form what I recall the CPU utilization was less and the throughput greater than whatever other ethernet chip was onboard and better than when Active Armor was off (as hard as that is to believe.) Does anyone else remember seeing that?

Well all of the Nvidia security apps only work with the Nvidia Port anyway... The marvel port is unprotected unless you get a seperate firewall app...

I am not quite sure what to be worried about though... I should just hook up my router between my roomates switch and my computer ( I honestly think he has about 100 times the chance to get hacked, zombied, or whatever... ) then I shouldn't have any problems unless I am stupid and run files form unknown places...

ANyway supposedly the marvel GB Lan has slightly greater throughput. Also, I saw someoene who did a test on the Nvidia Firewall vs MS firewall and the Nvidia firewall added slightly more latency to the ping times (howeer, he did not show any CPU utilization graphs)
 
Works fine for me on my MSI NF4, but for some reason my external drive isn't showing up in explorer.
 
Back
Top