Click to See Complete Forum and Search --> : XP unstable


panhead
November 2nd, 2008, 06:11 AM
Since about a week my PC with XP (SP3) has become very unstable and crashes now and then.
I don't know if it is related, but I think it occurred after the installation of the critical MS update, combined with the .net framework SP1. I uninstalled both, but that did not work.
I also did the Trend Micro housecall and checked with HijackThis, but no viruses/malware etc.
What can I do more to find and solve this problem?

BTW, also Firefox crashes often, can there be a relation?

Matridom
November 2nd, 2008, 06:50 AM
would you be able to give us any of the error messages that you obtain when windows and/or apps crash?

panhead
November 2nd, 2008, 08:29 AM
Most of the times it just shuts down and restarts. This is in the event viewer:

Error code 00000024, parameter1 001902fe, parameter2 b58a6a10, parameter3 b58a670c, parameter4 f7b556f5.

According to MS this is ER_KRNLCRASH_LOG (category 102, event id 1003).

NooNoo
November 2nd, 2008, 10:24 AM
Turn off automatically restart in the advanced options of the properties in my computer. (right click my computer, properties, advanced tab, settings button near the bottom, uncheck the box automatically restart). Then you can post the full BSOD message which should have the name of the offending .sys file.

You should start by checking your RAM -www.memtest86.com has a bootable iso you can download and burn to a cd.

panhead
November 2nd, 2008, 11:31 AM
Thank you, will do that.
The size of the pagefile.sys is now managed by Windows. Is it better to do the settings manually (I have 2.5 Gb memory)?

NooNoo
November 2nd, 2008, 11:34 AM
Leave it managed by windows and see what the general usage range is... then set it to the same size so that the pagefile.sys is not constantly resizing.

panhead
November 2nd, 2008, 11:41 AM
And initial size and maximum size the same value?

panhead
November 2nd, 2008, 12:05 PM
BSOD:

STOP: 0x00000024 (0x001902FE, 0xBA79CFB0, 0xBA79CCAC, 0xF7B556F5)

NTF.SYS - address F7B556F5

- BASE AT F7B52000
- DATASTAMP 48025be5

NooNoo
November 2nd, 2008, 12:28 PM
Ouch, damaged NTFS file system or damaged drivers.

Back up, update your drivers and run chkdsk /f

Cross fingers!

NooNoo
November 2nd, 2008, 12:28 PM
And initial size and maximum size the same value?

Yes

panhead
November 2nd, 2008, 12:31 PM
And again:

BAD_POOL_HEADER

STOP 0x00000019

NooNoo
November 2nd, 2008, 12:35 PM
Same... bad driver or bad hardware...

panhead
November 2nd, 2008, 01:07 PM
Did chkdsk /f, so let's see how things are going. I also have Partition Manager, which has functionality to check the system.

NooNoo
November 2nd, 2008, 01:09 PM
I hoped you backed up!

panhead
November 2nd, 2008, 01:17 PM
Yes, I do a daily backup of data.
BTW, thanks for the input!

panhead
November 2nd, 2008, 05:52 PM
If the NTFS file system is corrupted, would it be possible (and help) to convert to FAT32 and then back to NTFS?

NooNoo
November 2nd, 2008, 07:05 PM
NO!! on both counts....

panhead
November 3rd, 2008, 03:11 PM
No crashes this far......

panhead
November 10th, 2008, 02:53 PM
NooNoo,

Probably a stupid question, but if ntfs.sys is corrupt, can it be replaced by another one?

BTW, I upgraded my memory, could that be the cause?

NooNoo
November 10th, 2008, 03:22 PM
Yes memory mismatch could easily be the cause

how to replace ntfs.sys (http://support.microsoft.com/kb/822800)

panhead
November 10th, 2008, 03:42 PM
Thank you!

panhead
November 10th, 2008, 03:51 PM
Still another question: On the XP installation I can see ntfs.sys. Can't I copy it directly from cd to the windows directory?

NooNoo
November 10th, 2008, 04:00 PM
Err did you read the instructions? It tells you to copy from the cd.

panhead
November 10th, 2008, 05:10 PM
Yes I did, but that method is the long way and I thought I could that a shortcut...

NooNoo
November 11th, 2008, 03:51 AM
You rename the old file, you copy the new... what's long about that?

panhead
November 11th, 2008, 11:49 AM
Not long, but I skip starting from the CD :)
Thanks again!