Setup problem with XP

[DCFife]

I am in the process of building a new system for a friend. I got all of the parts from Newegg and they are as follows:

Enlight 7237 case w/ 300W Enlight PSU
IWill KK266+ motherboard
AMD Duron 1.0Ghz CPU
Globalwin WBK38 HSF
Maxtor D740X 40GB 7200RPM HD
Lite-On 52x CD-ROM
Lite-On 16x10x40 CD/RW
Gainward GeForce2 MX 400 video card
256MB Kingston ValueRam PC133

I threw it all together and attempted to install XP. During the initial setup (during the blue screen with the white bar across the bottom telling you what is being loaded) it gets done loading what it needs then says "Setup is starting Windows" then it just stops. Nothing happens...apparently ever! I have two systems of my own, both with XP and they worked just fine when I set them up this way. In fact, my wifes computer is almost identical except she has the Gainward GeForce 2 Pro, KK266+R and the Lite-On 24x10x40 burner. Just for the heck of it I pulled out my old Windows 98 SE disc and it installed just fine.

Any ideas???

Dave

 

[DARRIN]

Since you have 98SE on it now just try to do an update instead of a fresh install.

 

[DCFife]

Thanks to Kaieye for the solution to this one. Turns out to be a problem with the GeForce2 MX400 video card! Here's a link for anybody else who ever happens to have this problem...

Link

Happy New Year!

- Dave

 

[Frodolives]

<< Thanks to Kaieye for the solution to this one. Turns out to be a problem with the GeForce2 MX400 video card! Here's a link for anybody else who ever happens to have this problem...

Link

Happy New Year!

- Dave >>



I'm keenly interested in this since I have a copy of xp pro that I should probably be using, and I do have a gf2 also, but I'm a little confused by the thread you linked. Didn't see a response by "Kaieye" and not sure I see a clear solution amongst all of that.

Could you please cut and paste the solution that worked for you? Thanks! 🙂

 

[Frodolives]

Update: for whom it may help or inform. I hope it's permitted to paste this since I seem unable to link this information posted at my card maker's member's site. I trust all parties concerned are glad to spread information on the issue.



<< There is some talk going around regarding the notorious "Infinite Loop" or NV Loop/BSOD error that have been plaguing many people using later versions of the Detonator XP drivers. Apparently, the problem can occur with different results when running games or applications that utilize the OpenGL or Direct3D API's.

Common error symptoms that have become evident in OpenGL or Direct3D include spontaneous reboots, hardware lockups, insufficient virtual memory error (Windows XP) or Blue Screen of Death (BSOD) describing an "infinite loop" error with an NVIDIA driver, more notably with the nv4_disp.dll file. A sample error message reads as follows:

"Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER -
A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver."

This problem has been reported to occur when using the Detonator XP drivers version 23.11 in Windows XP and in some cases, Windows 2000. Therefore, revert to using an earlier version of the driver, anywhere from 12.41 and above with the 21.83 driver version being preferred. There is no definite answer as to whether or not this issue is more of a hardware vendor or software related issue, but a safe bet to say that it is a combination of both. It turns out that the video drivers were allocating too many system resources, more notably RAM to the video card, putting too much load on the memory timing procedure. This problem seems to occur more frequently with a certain driver set, version 23.11, more so in a few motherboard chipsets ranging anywhere from Intel to VIA.

Both motherboard chipset manufactures, Microsoft and NVIDIA are currently working together to alleviate the problem. Please check with chipset manufactures regarding any new patches or updates made for your particular motherboard model. One of these chipset manufactures, VIA, has come out with a BETA version of the patch that has reportedly corrected the issue for some and is available here. VIA's latest revision of their "4in1" chipset driver suite, version 4.37, includes the new patch and is readily available on their driver download page.

If the problem persists, the problem may lie with lower quality motherboard memory or aggressive memory settings found in the motherboard BIOS that must be set to factory defaults or lower. Please check with your motherboard manufacture for preferred BIOS settings.The following are BIOS memory settings for the VIA chipset:

DDR266 motherboards (Recommended settings):

SDRAM Cycle Lenth: Cas setting of 2.5
Bank Interleave: Enable or Disable (only if 1 DIMM is installed)
Precharge to Active (Trp): 3T
Active to Precharge (Tras): 6T
Active to CMD (Tras): 2T
DRAM Burst Length: 4
DRAM Drive Length: Auto
CPU to DRAM: Slow or medium

PC133 motherboards (Recommended settings):


DRAM Timing by SPD: Disabled
DRAM Clock: HCLK at 100FSB if 133FSB fails
SDRAM Cycle Length: 3
Bank Interleave: Enable or Disable (only if 1 DIMM is installed)
DRAM Drive Strength: Auto
Memory Hole: Disabled or Enable at 15M-16M
Q]