Let's start with some specs of things that could be relevant to this:
Athlon 64 3400+
1024 RAM
150GB Harddrive set as master
250GB Harddrive set as slave
DVD-ROM
CD-RW
Ok, so here we go.
I bought a new hard drive for my computer. 250GB. The one I have now is 150GB.
So I get it, install it, and all is well. Sort of. I actually broke two ribbon cables while trying to plug them in. Those things are so crappy, and awkward to plug in. I've run out of spare ribbon cables, but as long as the last one doesn't break...
Also, when they broke, the actual part that plugs into the harddrive got stuck both times, so I had fun trying to pry it off with pliers. It didn't want to come out.
So I set the 250GB to slave, and boot up Windows XP.
The first thing I notice is that Windows is taking about 2x longer than usual to boot up, but I don't think twice about it. I put on some victory music in celebration as soon as it's done, and I notice that the music starts stuttering from time to time. Only, though, when my computer's loading something. Now, it has to be semi-CPU intensive to make it stutter, but I'm doing things like loading Firefox that's making it stutter, and that's nowhere near what should lag any sound.
So not only does the sound lag, but my mouse will also kind of get choppy for a few seconds while this is happening. My CPU usage seems to spike up to 100% also, which is kind of normal, but not as randomly as it's doing, and not for such long periods.
So I try removing the 250GB and booting again from the 150GB. It's still doing it. I format the 250GB, boot from that hard drive, load XP on it, then try it on a fresh XP install. That should, by all means, solve any software problems. It still does it.
I flash my BIOS and update it, the only thing I could possibly think of left to do. It's still doing it.
Now, just a little earlier my computer stopped detecting my CD and DVD-ROM. I opened up my computer. I figured it might be the slot that it's plugged into, so I tried plugging the ribbon cable from the hard drive into the I/O card on the motherboard where the DVD and CD-ROM plug in...and it didn't detect it. I plug the ribbon from the CD and DVD-ROM into the I/O card where the hard drive was working, and it detects the CD and DVD-ROM.
So, one of the I/O cards on my motherboard seems broken, I guess. If one is broken, what's saying the other one isn't damaged to the point where, say, it has trouble loading data in from the harddrive? This might cause the stuttering, and would also kind of explain why it's taking longer to boot up XP.
Basically, I'm thinking that I'm going to have to buy a new motherboard.
So, my question is, what do you think? Is it logical to conclude that it's the motherboard causing the problem? Is it just a coincidence that one of the slots on my motherboard isn't working, and that fact's not related to the stuttering?
Any insight would be greatly appreciated. I'd really rather not have to buy and install another motherboard unless I absolutely have to. I also don't want to buy a motherboard then realize after that that wasn't the problem.
Thanks in advance.
Athlon 64 3400+
1024 RAM
150GB Harddrive set as master
250GB Harddrive set as slave
DVD-ROM
CD-RW
Ok, so here we go.
I bought a new hard drive for my computer. 250GB. The one I have now is 150GB.
So I get it, install it, and all is well. Sort of. I actually broke two ribbon cables while trying to plug them in. Those things are so crappy, and awkward to plug in. I've run out of spare ribbon cables, but as long as the last one doesn't break...
Also, when they broke, the actual part that plugs into the harddrive got stuck both times, so I had fun trying to pry it off with pliers. It didn't want to come out.
So I set the 250GB to slave, and boot up Windows XP.
The first thing I notice is that Windows is taking about 2x longer than usual to boot up, but I don't think twice about it. I put on some victory music in celebration as soon as it's done, and I notice that the music starts stuttering from time to time. Only, though, when my computer's loading something. Now, it has to be semi-CPU intensive to make it stutter, but I'm doing things like loading Firefox that's making it stutter, and that's nowhere near what should lag any sound.
So not only does the sound lag, but my mouse will also kind of get choppy for a few seconds while this is happening. My CPU usage seems to spike up to 100% also, which is kind of normal, but not as randomly as it's doing, and not for such long periods.
So I try removing the 250GB and booting again from the 150GB. It's still doing it. I format the 250GB, boot from that hard drive, load XP on it, then try it on a fresh XP install. That should, by all means, solve any software problems. It still does it.
I flash my BIOS and update it, the only thing I could possibly think of left to do. It's still doing it.
Now, just a little earlier my computer stopped detecting my CD and DVD-ROM. I opened up my computer. I figured it might be the slot that it's plugged into, so I tried plugging the ribbon cable from the hard drive into the I/O card on the motherboard where the DVD and CD-ROM plug in...and it didn't detect it. I plug the ribbon from the CD and DVD-ROM into the I/O card where the hard drive was working, and it detects the CD and DVD-ROM.
So, one of the I/O cards on my motherboard seems broken, I guess. If one is broken, what's saying the other one isn't damaged to the point where, say, it has trouble loading data in from the harddrive? This might cause the stuttering, and would also kind of explain why it's taking longer to boot up XP.
Basically, I'm thinking that I'm going to have to buy a new motherboard.
So, my question is, what do you think? Is it logical to conclude that it's the motherboard causing the problem? Is it just a coincidence that one of the slots on my motherboard isn't working, and that fact's not related to the stuttering?
Any insight would be greatly appreciated. I'd really rather not have to buy and install another motherboard unless I absolutely have to. I also don't want to buy a motherboard then realize after that that wasn't the problem.
Thanks in advance.