Repeated problems with blue screens.

MollygizerMollygizer New York, NY
edited December 2005 in Science & Tech
I have an earlier thread in the same vein; I thought I had fixed it, but it all began reccurring this week thricefold.

A few days ago, the system halted WindowsXP with an error message related to Hal.dll. When I restarted, CHKDSK utility began, and deleted the corrupted file... but this is obviously a necessary file for Windows to operate. Thanks, CHKDSK.

Ran a repair installation to rewrite over the drivers. Computer started normally. Ran Memtest 86 for good measure, no problems there.

Beginning yesterday, I'm getting random blue screens accompanied by physical memory dumps. CHKDSK always begins once the computer restarts, and always seems to find a slew of orphaned files and problems in $I30.

The last bluescreen finally had a message with it:

Kernel_data_inpage_error
0x0000007A
ftdisk.sys

The one before that was 0x0000008E, classpnp.sys.

I also went through my system event viewer, and although nothing has occurred in the last 3 days, from the 4-7 I have an overwhelming number of stops all relating to disk, atapi, ntfs.

Any suggestions? It also seems to especially, though not exclusively, occur when I wake the computer from standby.

Comments

  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited December 2005
    FTDISK.SYS (The Fault-Tolerant Subsystem Driver) is a component of the NTFS subsystem architecture. A problem referencing that could indicate a problem with your HD, or perhaps the partition on it. I remember your previous troubles and can only imagine how thrilled you must be to hear that... :rolleyes:

    The fact that it seems happen most often when coming out out of standby is another tipoff. In standby, everything loaded in memory is stashed away on the HD until you need it again, at which point it is loaded back into your RAM. The fact that you passed Memtest86 would indicate that it's not the RAM, so...we're back to the HD.

    Run the HD diagnostic test from the manufacturer. There may be no problem with it at all, but it would pay us to get that out of the way before going too much further.

    Good luck. :)
  • MollygizerMollygizer New York, NY
    edited December 2005
    And since you remember my past woes... yes, this is just dandy. Rrrrrrgh. :P

    And to be honest... I haven't a clue what brand of HD is in here. I was so frantic to get it back last time during finals, I shoved it at them, gave them money, and got it back working -- all I wanted, basically. Hindsight is 20/20.

    Any way for me to figure out what's living beneath this keyboard?
Sign In or Register to comment.