mnelson07
In Runtime
- Messages
- 349
- Location
- Denton, TX
So, whenever I leave my computer alone for a bit I lock it. I came back to find only the wallpapers shown and no login screen.
I reboot the computer manually to find the computer idling at the POST screen. It only reached reading the RAM. I restart it again and this time it gets to detecting IDE drives but never does. I reboot again and it finally gets to the Windows logo but idles at the blue loading bar. Once I restart from there it seems to repeat. Finally I decided to disconnect my secondary drive (the 250GB) and it booted to Windows again. However, it wanted to preform a check disk. And, given what has been happening, I let it run.
So far it has found and replaced a few things, but this kind of activity sounds like a dying hard drive to me. Which is a shame because I just bought the WD 750 about a week ago. I don't want to RMA for a new one already. We'll see what happens after CHKDSK runs, maybe it will fix the problem. But once again, why would errors in loading Windows affect the computer not booting completely through POST?
I reboot the computer manually to find the computer idling at the POST screen. It only reached reading the RAM. I restart it again and this time it gets to detecting IDE drives but never does. I reboot again and it finally gets to the Windows logo but idles at the blue loading bar. Once I restart from there it seems to repeat. Finally I decided to disconnect my secondary drive (the 250GB) and it booted to Windows again. However, it wanted to preform a check disk. And, given what has been happening, I let it run.
So far it has found and replaced a few things, but this kind of activity sounds like a dying hard drive to me. Which is a shame because I just bought the WD 750 about a week ago. I don't want to RMA for a new one already. We'll see what happens after CHKDSK runs, maybe it will fix the problem. But once again, why would errors in loading Windows affect the computer not booting completely through POST?