A PROBLEM HAS BEEN DETECTED.
geting an occasional blue screen of death. this is what it says
a problem has been detected & windows has been shut down to prevent damage to your computer.
***STOP: 0X00000077 (0XC000000E, 0XC000000E, 0X00000000, 0X003E5000)
BEGINNING DUMP OF PHYSICAL MEMORY.
It also says to uninstall any new software that was recently installed. even though that is not the case. also, hearing a clicking sound.
now, i say it is the HDD going out.
what do you think??
Stark Raving MOD
first things first. do a hard drive diag. If this is the same Dell server, then it's probably a bad drive.
You can Google the stop code or search Microsoft's website with it to see what their take is on the cause.
Run CHKDSK /R from the command prompt.
Start > Run > type in cmd > type in chkdsk /r
Mod w/ an attitude
If the second code inside the ( ) is the following:
0xC000000E, or STATUS_NO_SUCH_DEVICE: the drive went unavailable, possibly a bad hard drive, disk array, and/or controller card.
Replace the hard drive.
KERNEL_STACK_INPAGE_ERROR (symbolic name) (Stop 0x00000077 or Stop 0x77 (Stop error code)) (Parameter codes: 0xC000009A (or STATUS_INSUFFICIENT_RESOURSES - lack of non-paged pool resources due to a driver bug in the storage stack, since the storage stack should always be able to retrieve data, regardless, of software resource availability), 0xC000009C (or STATUS_DEVICE_DATA_ERROR – typically relates to bad blocks (sectors) on the hard disk drive), 0xC000009D (or STATUS_DEVICE_NOT_CONNECTED - defective or loose cabling, or improper controller or disk configuration/termination: unable to see hard disk drive), 0xC000016A (or STATUS_DISK_OPERATIONS_FAILED – again, typically relates to bad blocks (sectors) on the hard disk drive), 0xC0000185 (or STATUS_IO_DEVICE_ERROR - improper SCSI termination or defective cabling, or two devices attempting to use the same resources (IRQ)):
(Cause: Similar to those of the Stop error message KERNEL_DATA_INPAGE_ERROR. This bug check indicates a requested page of kernel data could not be read from the paging file into memory; the Master Boot Record (MBR) is infected with a virus: a boot sector virus; bad sectors or blocks, cable connection problems or failing physical memory (RAM). These are the most common causes to invoke Stop error 0x77. The master boot code (the boot sector’s executable code or boot code) runs automatically when an x86-based computer starts up, creating a vulnerability that can be exploited by virus writers as the location of the MBR is constant (unused in cylinder 0, head 0, sectors 2...n). Boot sector viruses can activate before an operating system is loaded and run when the boot code in the MBR identifies the active primary partition, activating the executable boot code for the volume. For this reason, it is unwise to use the undocumented FDISK /MBR command or even the Recover Console (RC) fixmbr command. The reason being is that although these commands will only rewrite a new boot code in the first 446 bytes (boot loader code) of the MBR, leaving the 64-byte table (starting at offset 0x1BE (1BEh = 446)) intact, if the partition table is damaged or changed restoring the boot code to an original boot code using the commands mentioned, may result in vital information stored elsewhere by the virus becoming compromised, undermining access to this vital information too. Many viruses update the boot sector with their own code and move the original boot sector to another location on the hard disk drive. After the virus is activated, it stays in memory and passes the execution to the original boot sector so that the startup appears normal. Some viruses do not relocate the original boot sector, making the volume available but inaccessible. If the affected volume is the primary active partition, the system cannot start. Other viruses relocate the boot sector to the last sector of the hard disk drive or to an unused sector. If the virus does not protect the altered boot sector, normal use of the computer might overwrite it, rendering the volume available but inaccessible or preventing the system from restarting. Newer viruses have the power to make restoring an uninfected MBR more intractable. Also check for faulty hardware installed (in particular memory, e.g., physical RAM, L2 RAM cache, video RAM, and cracks and scratched traces, or defective components on the motherboard). (Solution: Firstly, use the Event Viewer, Control Panel > Administrative Tools > Event Viewer and check for SCSI or FASTFAT error messages in the System Log. Check for error messages from Autochk in the Application Log. Error messages may identify whether a device or a device driver is causing the Stop error. 1) Increase the quantity of non-paged pool memory available to the kernel by adding more physical RAM. 2) Boot sector viruses can activate before an operating system is loaded and run when the master boot code in the MBR identifies the active primary partition, activating the executable boot code for the volume. In this case the first port of call is to run a pre-Windows commercial anti-virus program or one that is free for non-commercial use, i.e., F-Prot Antivirus for DOS (Definition files) or avast! 7 for MS DOS (Definition file). There is no guarantee that full or partial boot file disinfection will be possible. Many computer viruses exploit a hard disk drive and/or filesystem’s critical structures that a computer uses to start up by replacing, redirecting or corrupting the code and the data that starts the operating system. Always scan for viruses using an up-to-date anti-virus program and definition database regularly. Use it to guide repairs. 3) Run the chkdsk /r especially for parameters 0xC000009C and 0xC000016A (locates bad sectors and recovers readable information (implies /f) and to resolve any file structure corruption). If Chkdsk.exe cannot lock the volume, it offers to check it the next time the computer restarts. Because NTFS also identifies and remaps bad sectors during the course of normal operations, it is usually not necessary to use the /f parameter useless there is a suspicion that a hard disk drive has bad sectors) to detect and correct filesystem damage, if any. Refer to the entry RC and run chkdsk /r if booting into Windows is not possible. If on booting, run Windows Setup or the RC, it will not be possible to determine the cause of the problems using the solutions aforementioned and 4) Faulty hardware: Remove any recently installed hardware and determine whether this resolves the error. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics utilities downloadable from the manufacturer’s support webpage and seek further advice. Check cables are undamaged and connectedly correctly. Replace if necessary.