Slow Boot-up time with XP (32) on a 64 bit mobo?

[KWW]

I have just gotten a replacement system up and running. Did a repair install
on the existing hard drive when my daughter's Soyo Dragon+ mobo suddenly
died. Now, on bootup it takes an extra minute or two just sitting there at
the Windows screen. Granted, when the system died with the old mobo, she had
tried restarting it a time or two and first it got to the bootup screen and
blue-screened. Then it got only to the splash screen and then died, and
finally fairly quickly died. It was giving some OS-related errors. Maybe
it messed up some OS files on the disk (but the repair install should have
helped).

It can get out onto the internet, however it freezes the explorer window
before loading the Windows Update page, and Zone Alarm's built-in AV SW
cannot connect to update definitions. I was able to update and scan for
spyware with MS' Antispy.

Also, the memory check only registers 256MB on memory test.

During the repair install it did register a few errors, but after clicking
OK it went on.
1) COM + setup error "Subcomponent Com+ raised an exception while processing
the OC_COMPLETE_INSTALLATION setup message.
d:\nt\com\com1x\src\complussetup\comsetup\csetuputil.cpp (line 3406) Error
code = 0x8007007f The specific procedure could not be found. Failed to
load the library 'C:\WINDOWS\system32\catsrv.dll

(2) and (3) occurred in immediate succession while "registering components"
2) An error occurred loading "C:\Windows\System32\inetcomm.dll" the file nay
not have been installed or it has been corrupted.

3) An error occurred loading "C:\Program Files\Outlookexpress\msoe.dll" the
file nay not have been installed or it has been corrupted.

DFI LanParty nF4 Ultra-D
AMD Athlon64 3200+
XFX gForce 6600 DDR 256 (PCI+) video
2- 512Mb PC3200 CL3 Kingston DIMMs (KVR400X64C3A/512) (in sockets DDR1 &
DDR2 of Channel A)
Existing EIDE 120 Gb SD Drive.
CDR/W & CD drives.
Iomega Zip 100 Internal.
FDD.

TIA

 

[Richard Urban]

Please check your bios settings and make certain that the RAM timings are
correct. I just went through this with a customer using the same RAM. It
turned out that he had the bios set for "aggressive" RAM timings, which the
RAM wouldn't run at. I changed the RAM timing to optimal and everything was
sorted out. The Kingston PC3200, clock 3 RAM can not run at the aggressive
setting.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[KWW]

I take it that there are a number of timing things that you set. I basically
took the settings provided right out of the box.
Well, on the DRAM Configuration menu, most things are set to "Auto" with the
exception of the following:
02 Bus Clocks for: Row to Row delay (Trrd), Write redovery time (Twr), Write
to Read delay (Twtr);
03 Bus Clocks for: Read to Write delay (Trwt)
07 Bus Clocks for Row cycle time (Trc)
3120 cycles: Refresh period *(Tref)

Do these sound "aggressive"? When I select "F7" to automatically change the
settings to "Optimized" it selects all of these settings (again).

There is one curious feature that is not in the manual, DRAM Bank
interleaving, that defaults to "Enabled". Disabling it does not change the
amount of memory that shows up.

Does it sound right?
--
KWW

Please check your bios settings and make certain that the RAM timings are
correct. I just went through this with a customer using the same RAM. It
turned out that he had the bios set for "aggressive" RAM timings, which
the RAM wouldn't run at. I changed the RAM timing to optimal and
everything was sorted out. The Kingston PC3200, clock 3 RAM can not run at
the aggressive setting.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

 

[KWW]

Memory showing up incorrectly: Still not sure why the memory shows up as
"256MB" when I have two 512MB sticks of PC3200 in slots 1 & 2. (Does 64 bit
use 2x the memory for an equivalent size, and maybe it is trying to treat
these as a "matched pair" for interleaving?) Maybe I should move the memory
to slots 2 and 4 (or 1 & 3)?

Running faster: Windows explorer would not get to the update site, but the
file explorer could by a round-about route. After getting nearly all of the
updates, things started to work better. Maybe some of the formerly corrupted
OS files were replaced/repaired in the process (patches from pre-SP2 to the
present).

I take it that there are a number of timing things that you set. I basically
took the settings provided right out of the box.
Well, on the DRAM Configuration menu, most things are set to "Auto" with the
exception of the following:
02 Bus Clocks for: Row to Row delay (Trrd), Write redovery time (Twr), Write
to Read delay (Twtr);
03 Bus Clocks for: Read to Write delay (Trwt)
07 Bus Clocks for Row cycle time (Trc)
3120 cycles: Refresh period *(Tref)

Do these sound "aggressive"? When I select "F7" to automatically change the
settings to "Optimized" it selects all of these settings (again).

There is one curious feature that is not in the manual, DRAM Bank
interleaving, that defaults to "Enabled". Disabling it does not change the
amount of memory that shows up.

Does it sound right?

 

[KWW]

The problem that was not there.......
Brain dead or something..... finally noticed that the memory showing up was
right after the video card designation.... for some reason the "memory test"
did not show.... 256MB is the amount of memory on the video card....
duh....--

So that isn't a problem after all.
KWW