Windows Legacy OS forum

General discussion

Windows XP Professional freezes during boot screen.

by Dustmuffins / January 16, 2007 3:32 AM PST

Recently I was playing a game when my computer froze up, when I restarted it, it froze every time on the Windows XP bootscreen. It boots fine in Safe mode with networking. (I'm typing this post on this computer)

Have tried to fix:
-fixboot
-chkdsk /r
-system restore
-praying to the computer gods
-change IDE cable
-remove all overclocking.

Even after running the chkdsk /r, if I boot in safemode and run chkdsk (read only mode) in the cmd prompt, I get multiple errors.

I am 100% sure that I do not have spyware or viruses (they wouldn't even effect the boot screen anyway)

System stats
OS: Windows XP Professional SP2
CPU: Socket 939 AMD 64 3000+
GPU: Nvidia 6600GT PCIe
HD: 1 WD 40 gig(os is on this one)1 WD 80 gig (I can install vista on this one)
CD: 1 generic DVD combo drive and 1 crappy old CD drive.

Your help would be greatly appriciated, I need the computer for work so please post ASAP

Discussion is locked
You are posting a reply to: Windows XP Professional freezes during boot screen.
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: Windows XP Professional freezes during boot screen.
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
.
by Dustmuffins / January 16, 2007 11:20 AM PST

Bump? I really need help on this!

Collapse -
reply to: Windows XP Professional freezes during boot screen
by caktus / January 16, 2007 4:28 PM PST

While in Safe Mode, have you tried System Restore?

Also, what game? When it froze, did you receive any error messages?

When it refuses to boot can you go into Safe Mode and check the Event viewer for errors?

Charlie

Collapse -
(NT) Sorry, overlooked you tried Systen restore.
by caktus / January 16, 2007 4:30 PM PST
Collapse -
fd
by Dustmuffins / January 17, 2007 12:47 AM PST

I was playing Serious Sam, and the game just locked up.(sound skipped in half second intervals for a few seconds, then system restarted) Lately I was having problem with my second hd (without the os) loosing power. I determined it was because of a bent contact on the plug. I fixed that.

I'll search on google on how to check the event viewer and report back.

Thanks.

Collapse -
adf
by Dustmuffins / January 17, 2007 1:04 AM PST
In reply to: fd

This is the first entry in the "Application" menu of the even viewer after the crash:

11:38:37 AM

Checking file system on D:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Read failure with status 0xc000009c at offset 0x874a1d000 for 0x20000 bytes.
Read failure with status 0xc000009c at offset 0x874a29000 for 0x1000 bytes.
File record segment 81072 is unreadable.
Read failure with status 0xc000009c at offset 0x874a29000 for 0x1000 bytes.
File record segment 81073 is unreadable.
Read failure with status 0xc000009c at offset 0x874a29000 for 0x1000 bytes.
File record segment 81074 is unreadable.
Read failure with status 0xc000009c at offset 0x874a29000 for 0x1000 bytes.
File record segment 81075 is unreadable.
120992 file records processed. 754 large file records processed. Read failure with status 0xc000009c at offset 0x874a29000 for 0x400 bytes.
4 bad file records processed. 0 EA records processed. 1 reparse records processed. Index entry Images of index $I30 in file 0x13cad points to unused file 0x13cb0.
Deleting index entry Images in index $I30 of file 81069.
435820 index entries processed. CHKDSK is recovering lost files.
Recovering orphaned file inactive.bmp (94466) into directory file 81075.
17 unindexed files processed. 120992 security descriptors processed. Cleaning up 3 unused index entries from index $SII of file 0x9.
Cleaning up 3 unused index entries from index $SDH of file 0x9.
Cleaning up 3 unused security descriptors.
9002 data files processed. CHKDSK is verifying Usn Journal...
108063040 USN bytes processed. Usn Journal verification completed.
Adding 1 bad clusters to the Bad Clusters File.
Correcting errors in the master file table's (MFT) DATA attribute.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

39078080 KB total disk space.
33883176 KB in 104625 files.
42168 KB in 9005 indexes.
4 KB in bad sectors.
295200 KB in use by the system.
65536 KB occupied by the log file.
4857532 KB available on disk.

4096 bytes in each allocation unit.
9769520 total allocation units on disk.
1214383 allocation units available on disk.

Internal Info:
a0 d8 01 00 e7 bb 01 00 18 ba 02 00 00 00 00 00 ................
fc 06 00 00 01 00 00 00 f9 03 00 00 00 00 00 00 ................
8e 06 1f 10 00 00 00 00 c8 6a 0d 9c 00 00 00 00 .........j......
e2 3c 85 0b 00 00 00 00 00 00 00 00 00 00 00 00 .<..............
00 00 00 00 00 00 00 00 b6 be fa d0 00 00 00 00 ................
99 9e 36 00 00 00 00 00 00 00 00 00 00 00 00 00 ..6.............
28 22 32 ff 00 00 00 00 c0 23 19 00 00 00 00 00 ("2......#......


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

End file
_____________________________________________________________________

This looks just like a regular chkdsk to me.

Here's what System was reporting, I think the crash happened at aroudn 11:00 AM:

10:55:49 AM

Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Uniprocessor Free.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
______________________________________________________________________

10:55:49 AM

The Event log service was started.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
______________________________________________________________________

11:38:34 AM (about the time that application log was created)

Microsoft (R) Windows (R) 5.01. 2600 Service Pack 2 Uniprocessor Free.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

______________________________________________________________________

11:38:34 AM

The Event log service was started.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
______________________________________________________________________

11:38:02 AM

The description for Event ID ( 12 ) in Source ( sfsync02 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: .
______________________________________________________________________

And that's everything around the time of the crash.

Collapse -
Ouch. Test that drive and be prepared to replace it.
by R. Proffitt Forum moderator / January 17, 2007 1:11 AM PST
In reply to: adf
http://www.google.com/search?q=0xc000009c

Read other replies to this disk check failure but it's quite possible the OS is on parts of the drive and with read failures the OS will do a variety of blue screens and lockups.

Looks like a hardware error given the clues so far.

Bob
Collapse -
Good thing it's the crappiest drive I have.
by Dustmuffins / January 17, 2007 5:29 AM PST

Good thing it's my 40 gig 5 year old drive in that case. I'll move my files to my 80 gig, run vista RC2, and order a new HDD, stick vista home premium on it when it comes out.

Glad to finally nail down the problem. I was going to replace that drive anyway. Thanks all for input!

Collapse -
I fixed it!
by Dustmuffins / January 17, 2007 8:40 AM PST

Reinstalled Service pack 2. Have not tried to reboot again, but right now all is running correctly!

I'll keep my files and replace the harddrive just to be on the safe side though. Thanks all for help.

CASE CLOSED.

Popular Forums
icon
Computer Newbies 10,686 discussions
icon
Computer Help 54,365 discussions
icon
Laptops 21,181 discussions
icon
Networking & Wireless 16,313 discussions
icon
Phones 17,137 discussions
icon
Security 31,287 discussions
icon
TVs & Home Theaters 22,101 discussions
icon
Windows 7 8,164 discussions
icon
Windows 10 2,657 discussions

FALL TV PREMIERES

Your favorite shows are back!

Don’t miss your dramas, sitcoms and reality shows. Find out when and where they’re airing!