Freeze again, I think I found HUGE REASON


Recommended Posts

I have Windows XP SP1 alright, and lately I told you my computer freeze up quite often, and for a long time it went away. I thought it was fixed, yesterday played Simcity 3-4 hours without frozen up.

Most times, I use computer for like 8 hour straight without frozen up, but again, I got frozen up again.

It drives me crazy, and confused, so I run Chkdsk

Here is the output:

C:\windows>chkdsk

The type of the file system is NTFS.

Volume label is xxxx xxxxx.

WARNING!? F parameter not specified.

Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...

File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...

Deleting index entry INDEX.MAP in index $I30 of file 5095.

Deleting index entry OBJECTS.MAP in index $I30 of file 5095.

Deleting index entry 00105286.MAP in index $I30 of file 11106.

Deleting index entry 00105287.MAP in index $I30 of file 11106.

Deleting index entry 00105288.MAP in index $I30 of file 11106.

Deleting index entry 00105289.MAP in index $I30 of file 11106.

Index verification completed.

Errors found.? CHKDSK cannot continue in read-only mode

So, there is a problem. I run chkdsk/f and reboot the system, and run chkdsk again to check.

Here it goes again, it keeps saying "Deletinblah blah blahi> in index $I30 of filblahi>."

Thblahi> represents a different name.

And, I run it again and again, it does the SAME thing!!!

My computer seems to have NO problems, afraid it would goto hell by now, but it runs pretty smooth SO FA:):)!

So, the next thing I did is to check http://support.microsoft.com for issues, and unfortunately all I found was Windows 2000 issues, it looked similar and Microsoft said, the issue will be fixed with a service pack. Jeez, there was NO answers for Windows XP OS though.

I ran a search on google, and http://groups.google.com for NEWSGROUPS discussion relating to this.

And, seems other people are talking about this too.

One guy seem to say, he had the same problem, but unless I misread. He even reformated his drive and reinstalled Windows XP & SP1, He still have the same problem.

What the hell???

Any of you have this going on?

Link to comment
Share on other sites

I was experiencing something similar and found it was related to how your drives are setup on their IDE channels. Data would often become corrupted. Check that they are configured correctly. I played around with their configurations and the problem went away. Weird... :unsure:

Link to comment
Share on other sites

I have Windows XP SP1 alright, and lately I told you my computer freeze up quite often, and for a long time it went away. I thought it was fixed, yesterday played Simcity 3-4 hours without frozen up. [More......]

How about CHKDSK /R Did you try that? :yes:

Link to comment
Share on other sites

Ran it again

CHKDSK is verifying files (stage 1 of 3)...

File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...

Deleting index entry INDEX.MAP in index $I30 of file 5095.

Deleting index entry OBJECTS.MAP in index $I30 of file 5095.

Deleting index entry OBJECTS.MAP.NEW in index $I30 of file 5095.

Deleting index entry OBJECT~1.NEW in index $I30 of file 5095.

Deleting index entry 00106121.MAP in index $I30 of file 11106.

Deleting index entry 00106122.MAP in index $I30 of file 11106.

Deleting index entry 00106123.edb in index $I30 of file 11106.

Deleting index entry 00106125.MAP in index $I30 of file 11106.

Deleting index entry 00106126.MAP in index $I30 of file 11106.

Deleting index entry 00106127.MAP in index $I30 of file 11106.

Deleting index entry 00106128.MAP in index $I30 of file 11106.

98 percent completed.

:cry: :cry:

Link to comment
Share on other sites

Do you have a radeon?

I heard a while back that if you had a radeon, XP and had set the control panel/System/Advanced/Performance Settings/Advanced and under where it says "memory usage" if it IS set to "system cache" then it may cause data corruption. This was a while back ,and I'm not sure if there was a fix for it, but i"d check out the setting if you have a radeon just to be sure.

Link to comment
Share on other sites

And, I have also heard from the newsgroups that even if you reformat the drive and reinstall won't fix this, so why bother reformat it? I won't anyway until the drive completely stops working.

I am telling you, if my computer can up for 4-5 hours each day, without freezing up. It's ok would not worry about it.

I heard of the hardware (HardDrive issue) too, but I think the warrant is good for another year anyways.

I am letting it be this way, for now, I do not want to risk to all files & partitions just because of this issue.

When Windows .NET (2003) comes that's when I'll do a reformat & extensive testing I think, unless this thing tries die on me before Win2003.

Edited by JediXAngel
Link to comment
Share on other sites

I just found this, have a read!

Chkdsk is prone to falsely reporting errors when in read-only mode and might

report that a volume is corrupted even when no corruption is present. For

example, Chkdsk might report corruption if NTFS modifies an area of the disk

on behalf of a program at the same time Chkdsk is examining the same area.

You can find out if there is any corruption by typing the following at the

command prompt:

fsutil dirty query c: (substitute your drive letter for c:)

If it says the volume is not dirty, then you do not need to run Chkdsk

because there are no file system errors on the disk.

If you scheduled Chkdsk to run at startup (which you said you did but could

not read the results quickly enough), a version of Chkdsk known as Autochk

runs. You can review the Autochk report in the application log of the Event

Viewer snap-in. Autochk information is logged by the Winlogon service, so

look for entries with Winlogon listed as the source of the entry.

Also, there is no version of Scandisk in Windows XP or Windows 2000. There

are, however, two ways to run Chkdsk--one from the command line and other

from the user interface as Dave pointed out. Both do pretty much the same

thing, although the command-line version has more options.

The Windows XP Resource Kit has a lot of information on Chkdsk, including

all the issues I described above. The link below will take you to the RK.

You want to use the Troubleshooting Disks and File Systems chapter in Part

VI: Troubleshooting.

http://www.microsoft.com/technet/treeview/....asp?frame=true

Hop e this helps!

Hmmmm

Looks like MS is Lazy to fix the Chkdsk problem here... :unsure:

Edited by JediXAngel
Link to comment
Share on other sites

Ran it again

CHKDSK is verifying files (stage 1 of 3)...

File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...

Deleting index entry INDEX.MAP in index $I30 of file 5095.

Deleting index entry OBJECTS.MAP in index $I30 of file 5095.

Deleting index entry OBJECTS.MAP.NEW in index $I30 of file 5095.

Deleting index entry OBJECT~1.NEW in index $I30 of file 5095.

Deleting index entry 00106121.MAP in index $I30 of file 11106.

Deleting index entry 00106122.MAP in index $I30 of file 11106.

Deleting index entry 00106123.edb in index $I30 of file 11106.

Deleting index entry 00106125.MAP in index $I30 of file 11106.

Deleting index entry 00106126.MAP in index $I30 of file 11106.

Deleting index entry 00106127.MAP in index $I30 of file 11106.

Deleting index entry 00106128.MAP in index $I30 of file 11106.

98 percent completed.

:cry: :cry:

Assuming that you are using NTFS (as is prudent), you should

be running 'chkdsk C: /X /R'

chkdsk parameters are:

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/i] [/C] [/L[:size]]

volume Specifies the drive letter (followed by a colon),

mount point, or volume name.

filename FAT only: Specifies the files to check for fragmentation.

/F Fixes errors on the disk.

/V On FAT/FAT32: Displays the full path and name of every file

on the disk.

On NTFS: Displays cleanup messages if any.

/R Locates bad sectors and recovers readable information

(implies /F).

/L:size NTFS only: Changes the log file size to the specified number

of kilobytes. If size is not specified, displays current

size.

/X Forces the volume to dismount first if necessary.

All opened handles to the volume would then be invalid

(implies /F).

/I NTFS only: Performs a less vigorous check of index entries.

/C NTFS only: Skips checking of cycles within the folder

structure.

The /I or /C switch reduces the amount of time required to run Chkdsk by skipping certain checks of the volume.

Link to comment
Share on other sites

I have Windows XP SP1 alright, and lately I told you my computer freeze up quite often, and for a long time it went away. I thought it was fixed, yesterday played Simcity 3-4 hours without frozen up.

Most times, I use computer for like 8 hour straight without frozen up, but again, I got frozen up again.

Any of you have this going on?

Did it crash when playing SimCity?

Because this can happen for a lot of reasons. If you were playing while it froze, then it probably just needed to sync the NTFS

journal with the backup. No need to worry. It could be corruption, try to not overclock (if you are doing this now) and see what happens.

You see:

CHKDSK is verifying files (stage 1 of 3)...

File verification completed.

CHKDSK is verifying indexes (stage 2 of 3)...

Deleting index entry INDEX.MAP in index $I30 of file 5095.

...meaning that the FILES are okay. It is just NTFS that need to fix itself up a little. Nothing bad.

Link to comment
Share on other sites

Then, I went to do check in Safe Mode, it says difference messages, but not the same junk anymore.

It says like

Correcting errors in the master file table's (MFT) DATA attribute.

Correcting errors in the Volume Bitmap.

Windows found problems with the file system.

The newsgroups results I got, seems people are also confused about it as well.

The only MS rep/tech help responder is the one I quoted, saying Chkdsk is prune to errors (I am starting to believe that more than my computer/HD really has disk problems).

Go figure!

And, Everytime Simcity 4 froze when I tried to save! :no:

Edited by JediXAngel
Link to comment
Share on other sites

So, after all I read & learned, I have reached a Conclusion.

There IS something WRONG with Windows XP's CHKDSK = My Final verdict!

Don't believe what CHKDSK says, or you'll go format & return your hard disk for the WRONG reasons!

And, Microsoft NEEDS to put out a patch to fix this Stupid BUG causing all this confusion!

Link to comment
Share on other sites

try disabling the disk cache option. I am at work and have to go now but I will post the exact how to do it when I get home. It is under either IDE or Hard Drive settings in Device Manager. Have a little look for it, I think it is under the Advanced tab. Sorted all the issues instantly for a friend of mine.

Link to comment
Share on other sites

Hey, I have run this at Safe mode a second time. And, it DOES NOT show any errors at all.

So, yes, that perhaps confirms Chkdsk is prune to errors sometimes.

Besides, I am using Partitions created using PM7, maybe that's what cause confusions. And, I have heard from some people saying that certain Windows XP services will do this too.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.