This machine has been up and running for months. Just over the last week or so I noticed some slight strange behavior. Then this last Saturday, whaile trying to load a 3 level demo of a game that will remain nameless, I started getting BSOD. This particular demo has to be loaded from the console and involves a large read/write to get going and the BSOD references the file system. What happened last nite is after checking and re-writing the boot sector and mbr (just to make sure) all computer activity was normal. I then tried to run said demo again but same result, BSOD. Turned machine off and it has not come back on since. I am leaning to it being a bad stick of ram at the moment, for 2 reasons. 1. I had a stick of Crucial go bad in this same m/b this summer. I started getting same kind of errors with large read/write activity. Normal load stuff was fine. Had 2 sticks in box so it would get past the mem check and boot up completely. 2. When I got the first stick of Corsair, it was DOA and box did exactly what it does now, wake the monitor up but POST no further.
Nothing has been changed, nothing unhooked. The first post in this thread did not tell the whole story as I was dictating it to my daughter over long-distane land line, hence I tried to be brief. Sorry for that. I will know late tonite when I get home as a buddy is loaning me a stick of my old Crucial and I will see if it is the ram. I don't know what the led's on the m/b mean since they are not referenced in the manual. In fact, I don't remember what they should when all was working.