Check disk consistency after power failure, freezes Freezes at desktop
#1
Posted 30 July 2009 - 06:34 PM
#2
Posted 30 July 2009 - 07:10 PM
If successful, then initiate a chkdsk /r on the boot drive.
Start/Run...type chkdsk /r (with space between k and /) and hit Enter.
Type Y in response to onscreen message and hit Enter.
Reboot the system. The chkdsk /r will run before the system boots to the desktop. After the chkdsk /r has completed, the system will boot into XP automatically.
Louis
#3
Posted 31 July 2009 - 08:31 AM
I tried that, and it did the complete check, but it still freezes once the desktop screen appears. Further, before it freezes, the computer says drive D needs to be checked for file consistency, but the chkdsk /r only checks the C drive. Any other suggestions would be most appreciated.
#4
Posted 31 July 2009 - 09:41 AM
FWIW: D: is usually the optical drive and that's what I assumed, not paying attention to what you previously posted.
You might also check Event Viewer for any errors referring to Disk0, Disk1, etc. and post the details of such.
How To Use Event Viewer - http://www.bleepingcomputer.com/forums/topic40108.html
Louis
#5
Posted 31 July 2009 - 11:51 AM
I looked at the event viewer, and the following errors came up under the "system" sub menu:
The DHCP Client service depends on the NetBios over Tcpip service whick failed to start because of the following error: A device attached to the system is not functioning.
The DNS client service depends on the TCP/IP Protocol Driver service....the rest of the sentence is the same as above.
The TCP/IP NetBIOS Helper service depends on the AFD service....same as above.
The IPSEC Services service depends on the IPSEC driver service...same as above.
The following boot-start or system-start driver(s) failed to load:
AFD
BHDrvx86
ccHP
eeCtrl
ElbyCDIO
Fips
IDSxpx86
IPSec
MRxSmb
NetBIOS
NetBT
Processor
RasAcd
Rdbss
SRTSPX
SYMTDI
Tcpip
WS2IFSL
That's all that came up. Any thoughts?
Thanks,
Steve
#6
Posted 31 July 2009 - 01:31 PM
Take a read here: http://windowsxp.mvps.org/dhcp.htm
FWIW: It's always a good idea to allow yourself to see full filenames in XP. Otherwise, it makes it difficult to really track files. So I suggest that, if you haven't already done so, you enable the viewing of all files, including system and hidden.
You can do this by following the directions for XP at http://www.bleepingcomputer.com/tutorials/how-to-see-hidden-files-in-windows/
Something is wrong with your networking setup and the failure of drivers to load may be contributing to your situation. Or...the driver situation may be the result of something else. It won't hurt to try to correct this, following the guidance in the links provided.
Louis
#7
Posted 31 July 2009 - 03:23 PM
#8
Posted 31 July 2009 - 04:05 PM
But...I would do a clean install before pursuing that line of thought. It makes it a lot easier to determine if it's an O/S or hardware issue.
I've gone through power failures with my systems before...I even had a laptop get it's dialup modem zapped by a nearby lightning strike. But I never had any problems with my system or the O/S afterwards...so I'm lost.
Which forces me to lean in the direction of a clean install.
Let's see if others have better ideas
Louis
A hard drive diagnostic may be called for now, in spiite of the fact that chkdsk /r ran to fruition.
This post has been edited by hamluis: 31 July 2009 - 04:11 PM
#9
Posted 02 August 2009 - 02:45 PM
#10
Posted 03 August 2009 - 05:14 AM
1. Remove/un-plug all external devices from the computer and this includes all USB devices, and internet connection devices in particular .... leaving only the keyboard, mouse and monitor connected.
Attempt to start your system. What happens?
2. Inside the box, remove/un-plug all un-necessary devices ... and this includes any extra CD-ROM drives, expansion cards (including the graphics card if you are able to use onboard graphics?), network/internet connection devices, extra USB connections, hard drives ... etc Strip the system bare for the purposes of trouble-shooting.
Attempt to start your system. What happens?
----------------
If that does not allow Windows to load and function normally .... try disabling the on-board LAN in BIOS ... if that is what you are using ?
What happens when you try loading Windows?
Google is my friend. Make Google your friend too.
#11
Posted 03 August 2009 - 11:57 AM
#12
Posted 03 August 2009 - 01:27 PM
Hard Drive Installation and Diagnostic Tools - http://www.bleepingcomputer.com/forums/topic28744.html
Louis
#13
Posted 03 August 2009 - 03:14 PM
#14
Posted 03 August 2009 - 04:02 PM
Most diagnostics operate from either a bootable floppy or a bootable CD (since the user often cannot boot into Windows).
The system admin doesn't come into play on such.
If you are trying to use SeaTools for Windows...try SeaTools for DOS instead.
Louis
#15
Posted 03 August 2009 - 04:09 PM

Help

Back to top









