View Single Post
11 Jul 2012  

Windows 7 Home Premium 64 Bit

BugCheck 0x7A
Quote   Quote: Originally Posted by Windows Dev Center - Hardware

Frequently, you can determine the cause of the KERNEL_DATA_INPAGE_ERROR bug check from the error status (Parameter 2). Some common status codes include the following:
  • 0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.

  • 0xC000009C, or STATUS_DEVICE_DATA_ERROR, typically indicates bad blocks (sectors) on the hard disk.

  • 0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose cabling, termination, or that the controller does not see the hard disk.

  • 0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.

  • 0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination or defective cabling on SCSI devices or that two devices are trying to use the same IRQ.

These status codes are the most common ones that have specific causes. For more information about other possible status codes that can be returned, see the Ntstatus.h file in the Microsoft Windows Driver Kit (WDK).

Another common cause of this error message is defective hardware or failing RAM.

A virus infection can also cause this bug check.


Resolving a bad block problem: An I/O status code of 0xC000009C or 0xC000016A typically indicates that the data could not be read from the disk because of a bad block (sector). If you can restart the computer after the error, Autochk runs automatically and attempts to map the bad sector to prevent it from being used anymore.

If Autochk does not scan the hard disk for errors, you can manually start the disk scanner. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.

Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.

Resolving a defective hardware problem: If the I/O status is C0000185 and the paging file is on an SCSI disk, check the disk cabling and SCSI termination for problems.

Resolving a failing RAM problem: Run the hardware diagnostics that the system manufacturer supplies, especially the memory scanner. For more information about these procedures, see the owner's manual for your computer.

Check that all the adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

Check the System Log in Event Viewer for additional error messages that might help identify the device that is causing the error. You can also disable memory caching of the BIOS to try to resolve this error.

Make sure that the latest Windows Service Pack is installed.

If the preceding steps do not 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 cause this error.

Resolving a virus infection: Check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.
The above was taken from Bug Check 0x7A: KERNEL_DATA_INPAGE_ERROR.

SSD Troubleshooting:
The crashes you are receiving are common with SSDs when there are incompatible drivers, hardware, BIOS, or firmware issues. Proceed with SSD troubleshooting:
  • Make sure the following are up to date:
    • SSD firmware
    • BIOS Version
    • Chipset Drivers
    • Hard disk controller drivers/SATA drivers
    • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.

  • Try doing a power cycle of the SSD. The following steps should be carried out and take ~1 hour to complete.
    1. Power off the system.
    2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
    3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
    4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
    5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
    6. Let the computer remain in the BIOS for 20 minutes.
    7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
    8. Leave the drive disconnected for 30 seconds to let all power drain from it.
    9. Replace the drive connection(s) and then do steps 4-8 again.
    10. Repeat steps 1-4.
    11. Start your computer normally and run Windows.

    The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community

    While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.
My System SpecsSystem Spec