Is this a sign of trouble ahead

I came in to the BSOD this morning

KERNEL_STACK_INPAGE_ERROR

I rebooted and am using the computer now.

Is there someting I should/can do, or just play ostrich?

XP (updated to SP3 or whatever is most recent - I let it do all the updates), Dell precision 380, anything else I should be telling you?

 

I would boot from your XP CD and run a chkdsk /r ... ASAP

 

Thanks Drizzles.

I ran chkdsk /f /r and hit restart. I didn't watch, but when it finished it returned to the welcome screen. I'm assuming that if there were uncorrectable error, it would have left that message up until I acknowledged it.

I dont know how to boot from the CD. Should I still do this?

My XP CD is a Dell reinstallation CD with SP2. If I reboot from this CD will I have to add all the updates again?

 

chkdsk /r implies /f so you don't need to add /f but no if its completed you need to check you logs to find out its result ... right click on My Computer and select Manage, select Event Viewer and go to Application ... find the most recent entry with the title winlogon ... this should be the results of your chkdsk ... double click on the entry and post the results.

 

Thanks again,

I walked in today and saw the BSOD again.

I ran chkdsk /r and got the following message in the event code:

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

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 12 unused index entries from index $SII of file 0x9.
Cleaning up 12 unused index entries from index $SDH of file 0x9.
Cleaning up 12 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc00000b5 at offset 0xb2100e000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0xb21018000 for 0x1000 bytes.
Read failure with status 0xc00000b5 at offset 0xb4d789000 for 0x10000 bytes.
Read failure with status 0xc00000b5 at offset 0xb4d796000 for 0x1000 bytes.
Windows replaced bad clusters in file 12206
of name \pagefile.sys.
Read failure with status 0xc00000b5 at offset 0xbc2d96000 for 0x1000 bytes.
Read failure with status 0xc00000b5 at offset 0xbc2d96000 for 0x1000 bytes.
Windows replaced bad clusters in file 69495
of name \DOCUME~1\Eddie\Desktop\TEMPFO~1\ATPDIL~1.DOC.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 3 bad clusters to the Bad Clusters File.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

156199994 KB total disk space.
24390576 KB in 70574 files.
25976 KB in 7317 indexes.
24 KB in bad sectors.
166430 KB in use by the system.
65536 KB occupied by the log file.
131616988 KB available on disk.

4096 bytes in each allocation unit.
39049998 total allocation units on disk.
32904247 allocation units available on disk.

Internal Info:
90 6b 01 00 4e 30 01 00 e0 b7 01 00 00 00 00 00 .k..N0..........
26 07 00 00 01 00 00 00 c3 04 00 00 00 00 00 00 &...............
78 c8 5e 06 00 00 00 00 90 34 43 4d 00 00 00 00 x.^......4CM....
58 74 29 0f 00 00 00 00 0c 26 c8 88 04 00 00 00 Xt)......&......
8e 62 c6 91 07 00 00 00 9e 9b 57 85 0c 00 00 00 .b........W.....
80 46 43 be 00 00 00 00 a0 38 07 00 ae 13 01 00 .FC......8......
00 00 00 00 00 c0 ae d0 05 00 00 00 95 1c 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
__________________________________________________________

 

The computer does not restart:

I came in and saw the blue screen

I wrote down what I thought might be critical info.

KERNEL_STACK_INPAGE_ERROR

(I think it was) ***STOP: followed by the following codes: 0x00000077, 0xC00000B5, 0xC00000B5, 0x00000000, 0x014AB000

I will check out your link to see if I can figure out which tools I'll need - Thanks.

 

I downloaded and ran the Freeware version of MemTest for about an hour today and found no errors.

Hopefully the chkdsk /r solved my problems.

Thank you

 

Well your chkdsk found bad sectors also so I would definetly start putting away some money to replace that Hard Drive soon ... and I would back up any important information so there is no risk of loosing it ...

 

That is what I wanted to know.

I am backing up more frequently now, and was wondering if I should replace the hard drive because this is a sign that it is failing.

Would you keep using your hard drive if it were behaving like this, or would you preemptively swap it out? Presumably, the hard drive could last a few years like this. I assume my only risk is that I lose all data that has not been backed up.

 

It's definitely not a sign, it IS failing it just hasn't completely yet ...


You could keep using it for now as 24kbs is not a large amount, but it is definitely an indicator to be prepared for a change soon. The more kbs of BS' the more data will end up being corrupted which is why we backup. Generally, when A HDD gets some BS' the number of them will steadily continue to rise.

And yes your assumption is correct. You loose everything not backed up including your OS, which will need to be reinstalled. Mind you your HDD still has a fair way to go before it completely fails, but in the meantime, you will experience documents, images, etc you cannot access, you will experience OS errors and when the BS' get in the right spots, massive decreases in speed. I had a laptop the other day that timed it took 1 hour and 40 minutes to boot as a result of 240 BS' (from power on to a [sort of] useable desktop state).

The thing I tell everyone is to avoid losing data, have at least 3 HDDs. One for your OS, another for your personal data and documents and the last for backup.