Seekermeister
Golden Member
Last night, while playing an audio CD, MediaSource Player froze up and didn't restore by simply restarting it. So I rebooted and it delay forever doing the auto detection. I checked the bios and saw that the CD player wasn't listed and it was being powered, so I disconnected it.
That solved that issue, but then the progress bar on the logo screen froze several times abnormally long and was followed by a black screen. I noticed that the HD LED was remaining steadily lit, so I shutdown and checked connections, but that changed nothing. So I switched temporarily to another drive, but that one has some configurations problems, so I switched back. This time it struggled to the desktop, but the HD LED still remained lit. I had been planning to replace that drive, because of some SMART errors, but I guess that I delayed too long.
Trying to resume the audio CD, using the DVD player, when I opened the MediaSource player, it gave a couple of errors...one said something about the playlist being corrupt, and the second said that the database was corrupt and said to install MS's Jet Engine Database 3.0. I closed that player and used Nero's, which worked, but occassionally gave a pop in the audio.
I'm guessing that the HD caused all of this, but I'm wondering if it could cause the problem with the CD player also. If it were simply a matter of the OS recognizing it, it should have been functional during the bios run, before Windows started loading...shouldn't it?
The reason that I'm still thinking about this, instead of trying to fix anything, is that I'm wondering if the HD is really the source of the problems, or if the motherboard might really be the origin? I suppose that the answer is to be found by process of elimination, but I would like to have any input possible before commencing.
That solved that issue, but then the progress bar on the logo screen froze several times abnormally long and was followed by a black screen. I noticed that the HD LED was remaining steadily lit, so I shutdown and checked connections, but that changed nothing. So I switched temporarily to another drive, but that one has some configurations problems, so I switched back. This time it struggled to the desktop, but the HD LED still remained lit. I had been planning to replace that drive, because of some SMART errors, but I guess that I delayed too long.
Trying to resume the audio CD, using the DVD player, when I opened the MediaSource player, it gave a couple of errors...one said something about the playlist being corrupt, and the second said that the database was corrupt and said to install MS's Jet Engine Database 3.0. I closed that player and used Nero's, which worked, but occassionally gave a pop in the audio.
I'm guessing that the HD caused all of this, but I'm wondering if it could cause the problem with the CD player also. If it were simply a matter of the OS recognizing it, it should have been functional during the bios run, before Windows started loading...shouldn't it?
The reason that I'm still thinking about this, instead of trying to fix anything, is that I'm wondering if the HD is really the source of the problems, or if the motherboard might really be the origin? I suppose that the answer is to be found by process of elimination, but I would like to have any input possible before commencing.
