*FIXED*

[NOX]

The MOBO in question is the MSI K7T Turbo2 (a.k.a. MS-6330 V5.0).

The problem started when we upgraded the memory from PC100 128MB to PC133 512MB. Everything regarding the CPU/Memory/HD was working fine before this.

After the upgrade, the first thing to happen was rebooting upon starting Windows (Win2k). Once it would get to desktop (just before it displayed the login screen) it would reset/reboot itself, it would do this over and over until an ACPI blue screen would appear stating that our bios wasn?t fully ACPI complaint (which is strange because its been using the same bios for over two months now without any problems).

I also tried reformatting, however 25% through the install it will give me a stop error (which has never happened to me before) that some files are not being copied correctly. I tried using another HD, but same error. I also tried changing all IDE cables, RAM (tried using old RAM), and tried another CD-ROM to perform the install of Win2k, but I always get that stop error.

Right now I will try and revert back to an older bios version like 3.3 (currently using 3.6). I really hope that works, because this is the second mobo in less then a year for this system. Previous mobo was K7T Pro (which we did not RMA because it probably would have been a waist of time).

If you have any suggestions please let me know here. I?ll post with an on what happend with the bios update, though I don?t think it?ll work because I have a feeling it?s the bios or rather the mobo that has gone bad.

System info:
MSI K7T Turbo2
AMD 2000+
ATI 9500 Pro
512MB PC133
WD 20GB ATA66 HD
Sony CD-ROM
TDK Burner
Linksys 10/100 NIC
Antec 430w True Power PS
SBLive Value

EDIT: Bios v3.3, no go! I also wanted to mention that when installing Win2k, it will also state that the bios (v3.3 & v3.6) is not fully ACPI supported. The only way it will let me get past it is by hitting F7, but then that will fail too, when it stops at 25% when it states files are not being copied correctly.

 

[DieHardware]

Have you tried disabling power management in the MBs BIOS?

 

[PCMarine]

Hmmm I have that same motherboard and the 512 stick SHOULD work. My only thought is that you picked up faulty RAM as that results in symptoms like yours.

 

[billyjak]

I just bought that motherboard for a friend, I was planning on putting a stick of 512k Crucial ram in there.
Did you set the jumper pin to 133mz, it's at 100mz by default. You must change it to run stable. What ram are you using?

 

[nweaver]

Win2K copy errors are almost always ram related. Had the same problem (right after 2K came out) that was resolved by replacing ram. Once it was up and running, I could put the ram back in, and it was just fine. Same thing happened a week or so ago with a 256 stick of PNY and WinXP, stopped at 10% every time. I swapped sticks, and then it worked fine.
1. What brand of ram?
2. Slow ram timings down as far as you can.....see if that helps.

 

[PCMarine]

Originally posted by: billyjak
I just bought that motherboard for a friend, I was planning on putting a stick of 512k Crucial ram in there.
Did you set the jumper pin to 133mz, it's at 100mz by default. You must change it to run stable. What ram are you using?

Yes this is almost a high likelyhood of being your error

 

[NOX]

Ok, Ram is Kingston PC133 that you can pick-up from CompUSA.

The FSB jumper (J17) has been removed.

The problem here, is that I went back and used the same Ram (going back to the old settings) and that too didn't work anymore.

I'm really stumped here. I hardly post when I?m having a problem, because soon after I do I fix it, however this time I?m really not making any progress, and I?m getting very frustrated.

Here is a link to the actual Ram.

 

[NOX]

 

[NOX]

Fixed!!! Ram was to blame.

 

[Adul]

i was going to say try another stick of ram

 

[DieHardware]

NOX wrote;

Fixed!!! Ram was to blame.

Both the new and the old sticks went bad at exactly the same time?

You wrote in your first post...

The problem started when we upgraded the memory from PC100 128MB to PC133 512MB. Everything regarding the CPU/Memory/HD was working fine before this.

and further on...

I also tried changing all IDE cables, RAM (tried using old RAM), and tried another CD-ROM to perform the install of Win2k, but I always get that stop error.

 

[NOX]

Originally posted by: DieHardware
NOX wrote;

Fixed!!! Ram was to blame.

Both the new and the old sticks went bad at exactly the same time?

You wrote in your first post...

The problem started when we upgraded the memory from PC100 128MB to PC133 512MB. Everything regarding the CPU/Memory/HD was working fine before this.

and further on...

I also tried changing all IDE cables, RAM (tried using old RAM), and tried another CD-ROM to perform the install of Win2k, but I always get that stop error.

Yes Detective, for some strange reason the old ram also displayed same symptoms as the newer defective ram.

 

[magomago]

an u tried blaming it on yuor chipset

 

[NOX]

Originally posted by: magomago
an u tried blaming it on yuor chipset

LOL! You got me there... VIA, I blame them for everything!