| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 61768 | 2005-09-15 23:07:00 | Computer with odd booting problems (as usual) | Agent_24 (57) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 388612 | 2005-09-15 23:07:00 | Just got a friend's computer in, was told it had been running slow and was suspected of viruses etc. Fired it up to be greeted with a nice windows xp bootscreen, which then after seeming to load windows, and blanking the screen as it does just before the welcome screen appears, I got a nice BSOD with UNMOUNTABLE_BOOT_VOLUME on it, which is odd as the PC appears to have finished booting before the error comes up, but maybe I'm wrong. Tried safe mode and everything else and I got the same error hunted around on gigabyte's site to find the SATA drivers so I could get recovery console to recognise the harddrive, ran CHKDSK, it said it fixed a few errors, I also did FIXBOOT too, restarted and windows loaded all fine. Then I ran spyware checks and deleted a ton of stuff, some of which was in memory so I was asked to restart to remove it fully. Now windows refuses to boot in normal mode. It just sits there at the bootscreen (doesn't freeze) but won't finish. Went back into recovery console, ran CHKDSK /R this time, took ages, said it had fixed errors but boot problem still there. Tried safe mode again and voila it works! so apart from only being able to use safe mode at 640x480 which is really annoying everything's fine.... :illogical Anyone have any suggestions? |
Agent_24 (57) | ||
| 388613 | 2005-09-15 23:36:00 | If you can get in to Windows in Safe Mode, run msconfig and start by disabling all startup items and try booting in normal mode. If that doesn't work try disabling all non microsoft services. |
CYaBro (73) | ||
| 388614 | 2005-09-15 23:41:00 | Whats the stop error code on the BSOD?? | Speedy Gonzales (78) | ||
| 388615 | 2005-09-15 23:59:00 | the BSOD error code (which now no longer appears) was: UNMOUNTABLE_BOOT_VOLUME STOP: 0x000000ED (0x Random numbers/letters - different each time, 0x0000185, 0x00000000, 0x00000000) |
Agent_24 (57) | ||
| 388616 | 2005-09-16 00:17:00 | OK. Here's a bit of info about the 0x000000ED bit. support.microsoft.com support.microsoft.com www.microsoft.com |
Speedy Gonzales (78) | ||
| 388617 | 2005-09-16 00:33:00 | all those pages seem to say it's a problem with the IDE cable, only problem is It's using SATA and as far as I know there is only one type of cable. If the second parameter (0xbbbbbbbb) of the Stop error is 0xC0000032, then the file system is damaged. but of course it wasn't that. although CHKDSK did find errors.... I also tried disabling everything in msconfig - apart from windows itself - but no luck. |
Agent_24 (57) | ||
| 388618 | 2005-09-16 00:37:00 | True, there is only one cable for SATA . (well 2 actually, power and data) . Altho, they'll be easier to bend than IDE, since theyre thinner . You could try changing the SATA cable . See if it makes a diff . I would also check the SATA power cable . . . . |
Speedy Gonzales (78) | ||
| 388619 | 2005-09-16 01:58:00 | Tried new SATA cable and checked the power cable but no change. I've just read also that the problem could be a virus (but then that's not hard to believe), but of course norton doesn't function in safe mode and when I boot from the norton CD it can't scan the harddrive for viruses. (even though it's the 2005 version) |
Agent_24 (57) | ||
| 388620 | 2005-09-16 02:21:00 | This is a fun error. All that MS stuff about cables is rubbish. Well maybe not but I've had it plenty of times where the cbale has been fine and 80 channel. I had one instance where it turned out to be a motherboard fault. Seeing as you can get into safe mode, I would do a complete virus check too. Yes Nortons sucks - get AVG or similar and run that. |
pctek (84) | ||
| 388621 | 2005-09-16 03:11:00 | Also, just ran the seatools desktop diagnostic program, which returned this error: File Structure Test Result: Partition 1 (NTFS (120 GB) SATA) Result: Failed with critical Errors The following errors were found while scanning the volume: - One or more errors were found in the index - One or more errors were found in metadata file records - Other errors were found Although the controller, cable and harddrive were physically fine according to the program . I was going to try FIXMBR but it told me that the partition tables were of non-standard confiiguration and writing a new MBR may render them inaccessable . . . think I should give it a go anyway? I'm downloading AVG free at the moment so I'll try that too when It's finished . |
Agent_24 (57) | ||
| 1 2 | |||||