Windows 2000 blue error screen

[terryleaman]

Can somebody please help. I have w2K sp4.
Three times today, I have had a blue screen, twice the machine has restarted itself but then says it doesn't recognise my 2nd hard drive. Once it did not restart, so I had to do it, on restart it failed to recognise either hard drive. so I switched off and left it for a while, came back to it and it restarted normally. I managed to get one of the error messages down:-

STOP: 0X0000077 (0xC00000E, 0xC00000e, 0x00000, 0x0027A000)
Kernel_stack_inpage_error
beginning dump of physical memory.

I may have got the wrong number of zeros in some of these

Part of a previous error started
STOP: 0x0000007A, 0XC02FFFD4- couldn't get the rest down before it restarted.

Every one of these events started with the screen locking up first, then going to blue

After the last restart it checked Drive C for consistency and came up with a whole list of file errors.

Anyone any idea what is happening please?

[Digitalic]

This is from the Error and Event Messaging Help


"Error Message:
KERNEL_STACK_INPAGE_ERROR

Explanation:
This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. It might have been caused by a bad block (sector) in a paging file, a disk controller error, a defective motherboard, failing RAM, or because the stack signature in the kernel stack was not found. In extremely rare cases, it is caused when nonpaged pool resources run out.

User Action:
If the stack signature in the kernel stack is not found, the likely cause is defective hardware. Check the disk cabling and SCSI termination for problems. In addition, check your computer for viruses using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. Another cause of the Stop message might be that the data could not be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map the bad sector to prevent its further use. If Autochk does not scan the hard disk for errors, you can manually launch the disk scanner. Run Chkdsk /f /ron the system partition. Restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r. Caution: If your system partition is formatted with the FAT file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOS–based hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks. Another common cause of this Stop message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner’s manual for your computer. Check that all the network adapters in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure network adapter contacts are clean. In addition, check the System Log in Event Viewer for additional error messages that might help pinpoint the device causing the error. Disabling memory caching of the BIOS might also resolve this error. Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support. "

[terryleaman]

Many thanks for this posting.
I think I may have discovered what the problem was (or it may be a coincidence) When it happened again and restarted, my monitor went blank! absolutely nothing there at all. Switched off and checked my video card, wiped the connections of with a medical alcohol wipe put it back in, and hey presto everything seems to be working OK. I guess time will tell.