EPoX "EP-9NPA+Ultra" NVIDIA nForce4 ULTRA Chipset Motherboard

[nerp]

Originally posted by: Mem

gfngfgf: I tried not to install SW IDE driver and the system is working fine but it will take 2 to 3 minutes to load windows. In Windows, everything seems to be normal. Is this really normal for this mobo to take 2 to 3 minutes to load Windows?

That is because of NCQ ,so go to Device Manager,select properties on Nvidia SATA Controller and deselect "Enable Command Queing" ,in the primary tab of the HD.

Great tip, I just resolved a long-standing issue with my roommates's computer by doing this. He's got an Abit AN8 and he was always wondering why it took forever to boot. I wasn't able to figure out and was frustrated I couldn't pinpoint the cause.

Thanks.

 

[kikis]

Thank you! I will try this.

 

[RideFree]

Originally posted by: tjpark1111
ok guys give me a VERY clear(yes/no)answer. Is the USB issue common and if so, only for X2 processors? thx.

TJ,
I would not hesitate to put this combo into motion.
I believe Mem would second the motion.
However, I believe it may depend on your level of expertise at some point.

Addendum: If your copy of XP is SP1, SP2 or slipstreamed, I am of the opinion that you will not encounter any problems.

 

[msftman19]

Have to disagree with you, RideFree. Folks with ABit & ECS NForce4 boards are having the same USB problems (I have both the Epox & ECS ones - same symptoms). I've installed 32-bit Windows XP SP2 (slipstreamed), and 64-bit Windows. No difference. So that would seem to eliminate drivers as being part of the issue. Hard lockups across the board...

 

[tjpark1111]

I don't want to cause a big argument in this thread again by my fault, so let me ask you guys this. What motherboard has no problems at all(nforce4 ultra), in which it can fit a scythe ninja and a zalman nb47j northbridge cooler?

 

[ingeborgdot]

I had a problem with a long load time of about 2.5 minutes at reboot. I rolled back the nvidia drivers to xp and now under 30seconds to boot.

 

[kikis]

Originally posted by: ingeborgdot
I had a problem with a long load time of about 2.5 minutes at reboot. I rolled back the nvidia drivers to xp and now under 30seconds to boot.

What do you mean??

 

[Mem]

What do you mean??

He means don't install the Nvidia SW IDE driver ,just use the default Mircosoft one,if you do install the SW IDE driver just untick "enable command queing",either way works for fast bootup.

 

[RideFree]

Originally posted by: tjpark1111
I don't want to cause a big argument in this thread again by my fault, so let me ask you guys this. What motherboard has no problems at all(nforce4 ultra), in which it can fit a scythe ninja and a zalman nb47j northbridge cooler?

A8N-SLI Premium

I just assembled this with a 165 OEM from Monarch and have achieved installation Nirvana. Perfect, smooth, flawless installation of XP & all upgrades.
Also, perfect upgrade of BIOS & all nVidia 6.70 drivers.
USB 2, Firewire 800, Gb Network - all work without fault. Also running nVidia Firewall.
All installations and upgrades were flawless i.e error-free.

 

[kikis]

Originally posted by: Mem

What do you mean??

He means don't install the Nvidia SW IDE driver ,just use the default Mircosoft one,if you do install the SW IDE driver just untick "enable command queing",either way works for fast bootup.

Thank you Mem for the clarification.

I'm a little confused. If the SW IDE driver is not installed, will the "Enable Command Queuing" still appears under device manager or not?

 

[RideFree]

Originally posted by: tjpark1111
...and a zalman nb47j northbridge cooler?

I forgot to mention that this won't be necessary. I have the XP-120 with the 120 x 120 x 38 mm Panaflow blowing down.
Coolness

Edited: Unless you would want to remove the northbridge heatpipe cooler???

 

[Mem]

I'm a little confused. If the SW IDE driver is not installed, will the "Enable Command Queuing" still appears under device manager or not?

I don't remember seeing it without the Nvidia SW IDE driver installed,far as I know you need the SW IDE installed to enable NCQ .

 

[kikis]

Originally posted by: Mem

I'm a little confused. If the SW IDE driver is not installed, will the "Enable Command Queuing" still appears under device manager or not?

I don't remember seeing it without the Nvidia SW IDE driver installed,far as I know you need the SW IDE installed to enable NCQ .

I did not install the SW IDE driver and still the system is taking 2 to 3 minutes to boot to Windows. But once it's inside Windows, everything seems to be fine.

Is there something wrong with the system??

 

[Mem]

kikis: Hard to say,guess you can try a defrag see if that improves startup time or download bootvis,link.

 

[kikis]

Originally posted by: Mem
kikis: Hard to say,guess you can try a defrag see if that improves startup time or download bootvis,link.

Tried reinstalling the OS a couple of times, no go. I've updated the BIOS version to the latest, no go. Used the latest chipset driver, no go. If I will install the SW IDE driver, the system will not boot to Windows but I've read something in this forum that it will take more than three minutes before the system will boot to Windows right after installing the chipset driver and the SW IDE driver. I never really waited that long. But the weird thing is while the system is in Windows, everything seems to be fine.

Any idea on what seems to be the problem?

 

[Mem]

kikis: Problem with the Nvidia SW IDE driver is a few people still get problems when they install it,sounds like you are one of those few.

I aways recommend you install and get everything stable first before you overclock your cpu to rule out any problems caused by overclocking the cpu.


Having the SW IDE driver not installed is not a big deal anyway.

 

[kikis]

MEM: My system was not overclocked while I'm reinstalling the OS and the drivers. BTW, this is my second mobo. The first mobo was replaced because the SATA controller failed.
The system is very stable while in Windows. The only problem is the very long boot time(2-3 mins) which is really not normal, I think.

 

[Mem]

The only problem is the very long boot time(2-3 mins) which is really not normal, I think.

Try Bootvis like I suggested,I'm sure that will help with bootup time.

 

[kikis]

Mem: I'll try that then. But I don't think that this is a software problem because I've reinstalled the OS multiple times and I've tried multiple Win XP CDs. (WinXPPro, WinXPHome, WinXPGold) and the problem still exists.

 

[RideFree]

Originally posted by: Mem
kikis: Problem with the Nvidia SW IDE driver is a few people still get problems when they install it,sounds like you are one of those few.

I aways recommend you install and get everything stable first before you overclock your cpu to rule out any problems caused by overclocking the cpu.


Having the SW IDE driver not installed is not a big deal anyway.

Mem,
Many times I have used the installation of XP to test an O/C.
XP install is one of the most exacting and demanding tests I know of.
But, that is not to criticise getting everything stable, first; then doing a Ghost-type backup, and throw caution to the winds. Nothing to lose that way.

 

[RideFree]

Originally posted by: kikis
...The only problem is the very long boot time(2-3 mins) which is really not normal, I think.

I remember having this problem on an installation quite some time back and many systems ago...can't for the life of me remember what the solution was.

Are all devices showing up as "OK" in the Device Manager window?

 

[sgtdic]

one of the main things that affect bootup time is your startup processes. go to run and type in msconfig. go to startup tab and deselect all of the noncritical processes. you can always restart them later when you need them.

 

[IlluminiX]

*** USB 2.0/ X2 Breakthrough!!! ***

Well I hope it is. After talking with Tony at Epox USA, he mentioned to me that only X2 3800+'s seem to be affected by the freezing issue, and then it occurred to me that AMD released the Manchester 3800+ and then the TOLEDO 3800+ with the disabled L2 cache (should be Rev JH-E6 in CPU-Z)! Before I get ahead of myself, I should ask, does anyone with something other than the X2 3800+ (Toledo) have this freezing issue?? Another way to put it is: does anyone WITH the X2 3800+ Toledo not have a freezing issue??

My theory is that the disabled L2 cache plays a large role in the freezing issue, but I need more data before I can make any conclusions. Like I know Mem has no freezing issues, but he has a 4400+ X2 I believe. This means he doesn't have that disabled L2 cache and would not have the freezing issues.

The AMD Errata 123 may have something to do with it as well since it fixes an L2 cache issue with X2 processors:

Errata 123 refers to the 123rd bug identified in AMD Athlon and Opteron processors. This bug affects the cache bypass feature in those processors.

These processors have an internal data path that allows the processor to bypass the L2 cache and initiate an early DRAM read for certain cache line fill requests, even before receiving the hit/miss status from the L2 cache.

However, at low core frequencies, the DRAM data read may reach the processor core before it is ready. This causes data corruption and/or the processor to hang.


Feel free to chime in with your thoughts, but as of now, I think I might be on to something!!!

IlluminiX

 

[Ultralight]

I want to thank you for posting this information. I have purchased this board but due to some serious health issues have yet to do my new build. Nevertheless I have been following this USB 2.0 issue for some time.

My AMD processor is the 3200+ Venice core an so I will be watching closely to see if indeed it is only the X2 3800+ cores that seem to have this issue. Again, thanks.

 

[msftman19]

Originally posted by: IlluminiX
*** USB 2.0/ X2 Breakthrough!!! ***

Feel free to chime in with your thoughts, but as of now, I think I might be on to something!!!

IlluminiX

Very interesting...I do have 3800's on both my systems, and they both hang (one Epox board, one ECS). A search around the net - looks like DFI & Tyan have BIOS updates that offer a workaround. Epox, ECS, let's go!