Xp Random file corruptions on new PC

[rdhansen]

Hi All,

I've just built a new PC, and am having random system file corruptions at random times. I've reformatted and re-installed XP Pro several (about 4) times, and the problem is still happening. I have used this Cd to install on another PC previously and experienced no trouble.

Sometimes as soon as XP installs, before the install is finished, it says a file is corrupt and it reboots and checkdisks, and seems to go OK, but then at other times (opening explorer, at shutdown, some other random time) it will come up and say a different file is corrupt (explorer, dtc.dll, other dlls, one time the system wouldn't even boot, currently starts to boot but then aborts with ntosldr.exe corrupt (I may have file name slightly wrong))

I haven't got the message about the SYSTEM file corruption, or the HIVE corruption that I've seen in microsoft's knowledgebase, it just appear to be random system files.

I've downloaded the latest drivers for all components I can find, and put the HIVE fix from microsoft in, but the problems still occur.

The only thing I can think of, is maybe there's a problem with the memory and the motehrboard being incompatible? Or being a relatively new MOBO, maybe there's a problem with it?

After the checkdisk runs, I can look at the supposedly corrupt file and it seems to be fine.

My PC specs are:-

Gigabyte 7N400-L1 Motherboard
512MB Generic PC2700 DDR ram (1 stick)
ATI Radeon 9600 Pro
Maxtor Diamondplus 40GB ATA133 HDD

Any advice would be greatly appreciated. Thanks.

Russell.

 

[Amorphus]

are you overclocking? first thing that popped into my head is PCI frequency over spec.

then again, your HDD could be fubar.

 

[rdhansen]

No overclocking, using all the standard BIOS settings and speeds.

Funny you mention HDD. Was just talking to a collegue who said he'd had the same drive replaced 3 times as it as faulty.

But I've low level reformatted twice, and scnaidsk/checkdisked probably a dozen times, and never had any bad spots reported.

 

[DieHardware]

I'd change the HDD IDE cable and memtest86 the RAM(you want 10+ passes with no errors).

 

[rdhansen]

IDE cable hey? Hmm, hope I got a spare somewhere.

I did run memtest86, didn't know how long for though - it only got to 4 passed tests when I stopped it.

After running memtest86 was the first time the system actually wouldn't boot. The BIOS detected the drive, but the screen just went blank after that, and I had to boot from CD and do an XP repair before it would boot into XP again.

Thanks for the tips so far. I see Maxtor has a drive testing program, but it says the current version doesn't work with Nvidia chipsets - and mine is an Nforce Mobo

 

[ironique]

I second the IDE suggestion. I had a friend who had the same problem as you. We later realized that one of his IDE cables had a tiny hole in it. Replace you IDE cable and see it it works out.

 

[rdhansen]

 

[rdhansen]

Oops, sorry about the blank - can't find an edit button either.

What I meant to say was, I ran memtest86 ten passes with no fail, so i guess it seems the RAM is OK.

Just installed XP from a different disk in case the first was screwy, so I'll give it a bit of a thrash. If problems come up again, I'll try the IDE cable - I'll have to pull my other PC apart to get one. It was a brand new cable that came with the mobo. I'll let you know what happens.

 

[rdhansen]

OK, swapped with an IDE cable from my currently running PC, still had a corruption.

Moved the Maxtor drive to this PC as well as a slave, and ran Maxtor's Powermax test software, and it certifies the drive as OK.

So IDE, HDD and Memory tested, and all report as being OK. This only seems to leave the Motherboard. Anyone else got a 7N400-L1 working OK? Are these types of random corruptions possible symptoms of a screwy motehrboard?

If memtest86 reported the RAM as OK, could it still possibly be a problem with the RAM interfacing with the MOBO?

Any other ideas - I'm fast running out

Thanks. Russell.

 

[dprocket]

I have had the same problem, only it has only happened once. I also have a Maxtor HD that I ran the Maxtor tools on and deemed "ok". I don't have this mobo, but I plan to do a complete rebuild in the next 1-2 days, I'll let you know if I experience problems again.

Do you have the updated BIOS for your board?

 

[rdhansen]

Yes, I do have the latest BIOS version - F4 - at least the the download Gigabyte current have available.

 

[kursplat]

try letting he maxtor utility write ones to the whole drive. i had a western digital do the same thing and that fixed it.
good luck

 

[GonzoDaGr8]

Originally posted by: DieHardware
I'd change the HDD IDE cable and memtest86 the RAM(you want 10+ passes with no errors).

Second that. What type of cables are you using? Rounded or standard ribbon?

 

[rdhansen]

Yes, I've done the IDE cable an memtest checks. How do you tell a round from flat cable? I would say it's flat, not knowing what round is like.

I'm really starting to suspect the motherboard. I've seen a few messages today about people experiencing strange problems with nforce drivers 2.41, although no problems exactly like mine.

When I get home, I'm going to start all over again and try the 2.03 drivers instead, as they are supposed to be stable. I hope the MOBO isn't faulty, as I've had no experience with removing CPU's/Heatsinks and re-applying thermal paste.

 

[rdhansen]

Well, I've just about pulled all my hair out now. I've tried the 2.03 drivers and the 3.44 drivers and I'm still getting file corruptions.

I tried something different and installed the Radeon display drivers 1st thing after windows (before the nvidia drivers) and when it rebooted after install, it said it couldn't run some setup program, which sounds suspect as well. is there a problem installing other software before the nvidia drivers?