6 replies
by cmiller5400 Accepted solution
by Former member Accepted solution
by cmiller5400 Accepted solution
Sounds like the installation is corrupted. Is there any data worth worrying about? If so I would boot up to a linux cd such as knoppix and get the data off. Or use a utility such as Acronis True Image to image the drive. (this is the method I use. I just extract the data from the image) Then do an in place install to see if that helps. http://www.informationweek.com/windows/showArticle.jhtml?articleID=189400897
Good Luck!
by Former member Accepted solution
by zuben347 Accepted solution
Have you checked to make sure the CPU fan (unless passively cooled) is working properly? It takes only seconds for a CPU to overheat if not properly cooled and provoke a reboot cycle.
Have you unplugged every internal and external device? Take out every PCI card and unplug the power and data cables from every optical drive, floppy, zip, and hard drive--except the primary boot disk that has the OS that keeps rebooting.
Leave just one module of RAM and test each slot with it. Try the others the same way unless you've uncovered the culprit by now.
Is the Northbridge fan (again, unless it has a heatsink alone) working? Does the case have sufficient air flow from the front and out the back? Dust bunnies teaming up with obstructive IDE ribbons, and oily dust residue slowing down fan blades could be to blame.
Can you hit 'tab' for verbose mode while BIOS runs the POST? Either way, what beep code are you getting?
Can you run TuffTest or some other hardware diagnostic to non-destructively test for bad sectors on your HDD, and verify its MBR?
BartPE has lots of add-ons you can use to troubleshoot, and also can read NTFS partitions. Even if she says there's nothing important on there--next week she might remember her .wab, .dbx's, .pst, or perhaps even a sacred music collection!
How about F8 and "Boot to Last Known Good" restore point?
Take the drive out if all else fails. Slave it if it's an IDE. Run a battery of tests on it AFTER you've pulled any data you might think she may need after all.
Check to make sure the System account has Full Control in the root ACL. Apply to all files and folders. Try it again in her box by itself after RAM and CPU vindication (POST beep should be enough).
Rebuilds take hours, and all of the above should take about an hour or two to determine if it's a hardware issue before you nuke the site from orbit!
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending