Sorry for another random reboot thread, couldn't find any help in the previous threads
My wife's computer started random rebooting Saturday. It's been doing it non-stop. She hasn't run any of the windows updates from MS, but now it won't stay running long enough to d/l the files needed for that. She's running a non-overclocked Duron, on a ECS5s7a board... a setup that has been running good for almost a year without any problems. I haven't added anything to her computer since I installed the mobo about 9 months ago. Sometimes the computer will load up only to crash in the middle of d/ling, other times, it won't even make it to the desktop before rebooting.
When the computer restarts, it goes to a blue MS screen. There it tells me my file system is FAT32, and says "one of your disks needs to be checked for consistency".. While searching the drive, it will find files and list the file along with "first allocation unit is not valid. The entry will be truncated." Other times it will say it will fix it by copying. The system has rebooted over 12 times just while I was trying to figure it out. I thought maybe it just needed to clean itself out, but 1 time it will find nothing wrong, the next time, it will find 1-2 mistakes, then it will find 8 mistakes... no clear pattern.
Any suggestions?
Thanks,
Gary
My wife's computer started random rebooting Saturday. It's been doing it non-stop. She hasn't run any of the windows updates from MS, but now it won't stay running long enough to d/l the files needed for that. She's running a non-overclocked Duron, on a ECS5s7a board... a setup that has been running good for almost a year without any problems. I haven't added anything to her computer since I installed the mobo about 9 months ago. Sometimes the computer will load up only to crash in the middle of d/ling, other times, it won't even make it to the desktop before rebooting.
When the computer restarts, it goes to a blue MS screen. There it tells me my file system is FAT32, and says "one of your disks needs to be checked for consistency".. While searching the drive, it will find files and list the file along with "first allocation unit is not valid. The entry will be truncated." Other times it will say it will fix it by copying. The system has rebooted over 12 times just while I was trying to figure it out. I thought maybe it just needed to clean itself out, but 1 time it will find nothing wrong, the next time, it will find 1-2 mistakes, then it will find 8 mistakes... no clear pattern.
Any suggestions?
Thanks,
Gary