So I stopped by a computer store yesterday -- I needed to get some thermal grease since the stuff I had put on the system I was trying to build had used the little bit that I had gotten. So I went ahead and stopped by this store and picked some up.

On my way out, I noticed that they had the motherboard that I had gotten (and had problems with). So I took a look, and sure enough, the revision on the motherboard was version 2.0. This version was known to have most of the problems fixed -- problems with the memory that I got and other minor problems.

I decided (spur of the moment) today that I should go pick it up. Missy had been talking about upgrading her system for some time now, and I figured she could have the motherboard that I get back from Asus (the one going in for an RMA) and I could make sure the problem was in the motherboard and not in the CPU (the only other item that I couldn't just "replace").

So I set it up tonight and sure enough....
It works beutifully.

So I had it run the burn-in-util for 2 hours without everything plugged in and set up the way that I want it. It's now re-installing Windows (only the second time -- I think probably three or four times before I'm happy with it). I'll run the burn-in-util for another 12 hours tonight.

In other news, I'm going to go do a 50 mile ride tomorrow morning with the bike store peoples that I normally go to (Cambria Bicycle). I stopped by there today as well to pick up some chain grease. Biking in the rain makes chains go squeeeeeeeeeeek! So I stopped by the bike store and there on their counter was an announcement that they were holding a 50 mile bike ride starting tomorrow morning.

So I'm gonna finnish this episode of Stargate SG1 and then head off to bed.

Nighty-night!
--B--

So yesterday I'm at home -- not feeling well -- so I'm watching TeeVee. After watching it for about 2 hours, suddenly our stereo receiver starts kicking in and out. It'll completely shut the sound off for 20 seconds (or more) and then come back on for a couple minutes, then shut off again.

Now we saw this behavior before, lucked out that the receiver was under warranty, and supposedly had it fixed. This was probably just over a month ago. Now the same shit is happening again. Only now the receiver is out of warranty. So I've got to call up the place that fixed it, bitch them out, and hopefully be able to take my receiver back to them to get it fixed for *real* this time.

Our temporary receiver was also crapping out -- it was our old system that I've had for ... well 9 years. So I went ahead and tossed it. There was an entire channel that wasnt getting sent (the left channel) and it wasn't surround sound or anything fancy. Just an old deck. So it got tossed.

Now what does that have to do with our current problems? Well last time we took in our receiver that cuts in and out, the shop had it for just around a month. Since we no longer have a "back up" receiver, that means one month without sound in our house. Not accetable in my opinion.

So last night we went out and purchased a new receiver. Instead of going with the cheaper/more features brand, we went with the tried & true brand. We are now the proud owners of a Harmon Kardon receiver. I'd tell you the model# but I've already forgotten it. I'll update this post later when I'm at home with the model#.

I think it already sounds slightly better then our old one. It doesn't have the same wattage (sound level) for output but it does seem to make things sound a lot better.

I've got to get some new speaker wire to run to the surround right speaker as the old stuff we had was like 22guage -- way too thin for the new receiver's big plugs. Small price to pay for better sound tho.

I'll still get the old one fixed and then take it upstairs and set it up as my receiver for my computer. For the computer that doesn't have a working motherboard yet. But thats another challenge for another day.

*sigh*
--B--

So how did installing the new system go you ask?
Putting it together was easy and quite enjoyable.
Then the troubles started.

I'm getting funny errors that I thought were memory related but now I'm not sure...
First thing I ran into was that the memory, sold as "the best memory for the chipset" was not 100% compatable with the motherboard. Well okay -- it was compatable, but the standard for the super fast PC3200 memory isn't finalized. The memory uses one set of defaults, the motherboard a second set. I finally found settings that seemed to fix the problem for me (yay!) and the little app, memtest86 returned flying colors for both dimms.

"Great," I thought to myself, "Now I can install windows and be all ready to rock and roll!" Only it wasn't to be. Windows XP Install gets right to the point where it says "Start Windows" (right before you format/partition the drives) and blue screens with IRQL_NOT_LESS_OR_EQUAL errors. Whatever *that* means.

And thats where I've been for two days now. I've replaced the following to eliminate wierd errors:
Graphics Card
Memory Dimms (tried slower PC2700 and PC2100 memory)
Floppy Drive (installed and not installed)
CD Drive

Since everything else is on board, that leaves...
CPU
Motherboard

*ugh*
So now I've got to figure out which one to try to replace. I've never run into problems like this. And after reading up online about IRQL_NOT_LESS_OR_EQUAL errors, it looks like thats almost a catch-all for Microsoft. People say to fix it try:
Replacing Graphics card (tried)
Replace HD (I guess I could try that...)
Install a better heatsync (CPU temp is under 50c -- don't think thats it)
Don't overclock (wasn't going to try)
Slow down the memory/replace memory (tried both)
Install latest BIOS (tried that -- in fact I tried older versions of the bios as well just to be safe)
Get latest device drivers (shouldn't matter as I'm not actually in Windows yet and the IDE controller is a standard one supported on the Microsoft HCL).
Replace motherboard
Replace CPU

So you can see where I'm at...
*ugh*
Anyone have any ideas before I go through the hastle of trying to return the motherboard?

--B--