*Weird* computer slowdown, brand new build...

nray

Limp Gawd
Joined
Mar 20, 2006
Messages
316
I put together a new computer this week from the following parts that I know work great:

AMS 480W power supply
EVGA 7900GTO 512MB video card
Creative Audigy 2ZS sound card
Intel Pro 1000 PT PCI-E gigabit ethernet
WD 74GB Raptor SATA drive
Seagate 250GB SATA drive
Lite-On DVD+-RW DL drive
Pioneer DVD+-RW DL drive

And then I bought the following new parts:

MSI P6N SLI Platinum motherboard
Intel E4300 processor
Super Talent T6UB1GC5 (DDR2-667 5-5-5-15), four sticks

First I updated the BIOS to version 1.1. Then I ran Memtest 86+ 1.70 overnight, and made sure there were no errors. I left everything at it's default clock speed.

Then I installed my copy of Windows XP x64, which is where I first noticed something was up. Now I have installed XP x64 many other times, and it's running just great on my overlcocked Opteron 175 in my Biostar TForce 6100-939 system, and I've never seen the problems I'm about to describe.

The Windows install completed without errors, only it took much longer than it should have, and at times when it shouldn't have taken a long time, such as cleaning up temporary files near the final stage of installation. I didn't look at a clock at the time, but it was about five to ten times longer than it should have been.

Booting into the desktop was a slower than it should have been but not outrageous, however there was a very large pause of about 30 seconds to a minute after typing in the password before the desktop started to appear. I installed the drivers (which I had already downloaded on another computer) one by one, and each one took an extraordinarily long time to decompress, verify, and install, anywhere from 15-45 minutes *per driver*, which was far out of the ordinary. The drivers I installed were:

8.43_nforce_650i_winxp64_english.exe
93.71_forceware_winxp64_english_whql.exe
PROEM64T.EXE
WDM_R161.exe
SBAX_WBUP2_LB_2_09_0016.exe

Those are all release 64-bit WDM drivers, and they all installed without errors, and after rebooting, things are still very slow - and while things are running slowly, I notice near 100% CPU utilization of one of the cores the whole time. I.E. just bringing up Microsoft's web site takes a full minute and fully utilizes a CPU, after it's done, CPU usage drops back down to near zero on both cores and stays there.

What is going wrong? Is my motherboard/CPU to blame somehow? Could MSI have mis-designed the motherboard so it doesn't run properly in 64-bit? (The driver disk from MSI doesn't include any 64-bit drivers and their autorun program on the driver CD refuses to even launch in Windows XP x64, which leads me to believe MSI could care less about 64-bit).

The only other oddity I've noticed is that the BIOS is extremely unresponsive to keyboard navigation when my USB keyboard is being run through a hub, i.e. I have to plug my USB keyboard directly into the a motherboard USB port for BIOS navigation to be responsive. Also, the i8042prt driver service fails to load and generates an error in the System event logs, which isn't a total surprise since I have no PS/2 devices (my keyboard and mouse are USB only), so the i8042prt driver probably can't assign itself an IRQ with no devices attached, but I can't think how that would cause the entire system to run slowly.

I installed the 240MB XP x64 Service Pack 2 which came out yesterday, and while it downloaded in a few minutes, it basically took all night to install, and the system still runs slowly.

I think I'm out of ideas... anyone have any?
 
Check the cables on your drives, try swapping out the SATA cables and whatnot...and run a diagnostic on the hard-disk.

Run a memory diagnostic (preferably overnight), and after all that run orthos for a good long time.

If everything passes, i'd probably do a full format (0 the drive) and try installing again.
 
Check the cables on your drives, try swapping out the SATA cables and whatnot...and run a diagnostic on the hard-disk.

Run a memory diagnostic (preferably overnight), and after all that run orthos for a good long time.

If everything passes, i'd probably do a full format (0 the drive) and try installing again.

Thanks for the reply.

Swapped out SATA cables, didn't help.

Decided to use an entirely different (and also known good hard drive) and format and install on that, and that didn't help.

My next step will be to try swapping out the (again, known good) IDE cables to the DVD-RW drives for other known good IDE cables.

If that doesn't help, I'll try pulling the Audigy 2ZS and Intel Gigabit ethernet cards.

And if that doesn't help, I'm going to sit down with a big glass of vodka on the rocks and drink.
 
I would suggest disconnecting everything and only having the motherboard and processor (out of the case). Power it up. Error codes are good here. Then add the memory, should not hear anything after 1 minute. Add video card, error on "inaccessible boot disk" is good. Add a drive, hopefully everything works. Otherwise, I'm not sure at this point.
 
And if that doesn't help, I'm going to sit down with a big glass of vodka on the rocks and drink.

have two, go with protias idea, I think your new shiney Mb has bios issues with drives.
Now I havent looked it up to see what it uses to handle all the SATA etc. but google jmicron problem and see what you get.

disconnect all those other drives, rip out the sound card (there is a nightmare in itself occansionally, bare bones system, everything but one HD and one CD , and do a clean install onto the drive.

If its still doing it, you may leave the bottle on the table and throw away the cap.

WoW a service pack for XP- 64 sweet.
 
Is a windows installation disk sufficient for zeroing a drive?

Yes, choose the Repair existing Windows installation, and it'll take you to a prompt. This is how I reformat as I don't have a floppy, and I really should get one.

Type in format c:.

Edit: Also, make sure you have your CD-Rom first in the boot priority.
 
Yes, choose the Repair existing Windows installation, and it'll take you to a prompt. This is how I reformat as I don't have a floppy, and I really should get one.

Type in format c:.

Edit: Also, make sure you have your CD-Rom first in the boot priority.

Thank you. It's just, when i get my rig up and running, i plan to re-install Vista multiple times, trying to get the best configuration for pagefile, apps etc. and it would be far easier to use the Vista installtion disk rather than a 3rd party app.
 
FOUR STICKS OF RAM = REALLY SLOW
TWO STICKS OF RAM = FAST (i.e. as fast as it should be)

WTF?!?!?!?!?!?!?!?!!

Ok, anyone with an explanation? (And FYI, four sticks or two sticks = total 100% error free runs in Memtest 86+ 1.70)
 
FOUR STICKS OF RAM = REALLY SLOW
TWO STICKS OF RAM = FAST (i.e. as fast as it should be)

WTF?!?!?!?!?!?!?!?!!

Ok, anyone with an explanation? (And FYI, four sticks or two sticks = total 100% error free runs in Memtest 86+ 1.70)

Are all of the sticks the same brand, model and size (do they all have the same amount of memory)?
 
Are all of the sticks the same brand, model and size (do they all have the same amount of memory)?

I spent a few more hours on it, and figured it out.

Apparently it's possible to use a tiny voltage boost to mask a bad stick of memory.

All four sticks were only running error-free when at 1.85V exactly.

I thought they simply were finicky, but they are rated for 1.8V exactly.

On a hunch, I started testing each stick at 1.8V, discovered one of them throws tens of thousands of errors, the others are error-free.

VERY strange that 1.85V would mask those errors in the bad stick when combined with the other three good sticks, and so I made a post documenting this oddity in the Memory forum so other people could know.

Have I mentioned I've had the worse luck with DDR2 memory at home? At the builds I've done for work, it's been smooth sailing though.
 
I spent a few more hours on it, and figured it out.

Apparently it's possible to use a tiny voltage boost to mask a bad stick of memory.

All four sticks were only running error-free when at 1.85V exactly.

I thought they simply were finicky, but they are rated for 1.8V exactly.

On a hunch, I started testing each stick at 1.8V, discovered one of them throws tens of thousands of errors, the others are error-free.

VERY strange that 1.85V would mask those errors in the bad stick when combined with the other three good sticks, and so I made a post documenting this oddity in the Memory forum so other people could know.

Have I mentioned I've had the worse luck with DDR2 memory at home? At the builds I've done for work, it's been smooth sailing though.

So you've had to increase the memory voltage to compensate on their.... sucky-ness, i guess that doesn't seem too strange when you think that dud CPUs may require more voltage than the norm in order to reach stability. Is it all working fine now, then?
 
So you've had to increase the memory voltage to compensate on their.... sucky-ness, i guess that doesn't seem too strange when you think that dud CPUs may require more voltage than the norm in order to reach stability. Is it all working fine now, then?

Now that I'm running three sticks of RAM instead of four, yeah everything is fine (and I'll be RMAing the bad stick).

The only thing left now is to see if the beta BIOS for my board solves the problem with E4300 overclocking...
 
Back
Top