crashing

[disha14]

Subject: Repeated BSOD – KERNEL_DATA_INPAGE_ERROR and Disk 0 Hardware I/O Errors

I have an HP ProBook 640 G2 running Windows 10 Pro 64-bit. My laptop has been crashing repeatedly (around 7+ times) with the BSOD error KERNEL_DATA_INPAGE_ERROR.

I checked the system and the SSD is detected as a 256GB M.2 SATA SSD and Windows reports its health as "Healthy." RAM testing also passed.

However, Windows Event Viewer repeatedly shows Event ID 154 with the message:

"The IO operation at logical block address for Disk 0 failed due to a hardware error."

I also tried installing the Intel Rapid Storage Technology Driver from the HP support page, but the laptop crashed with KERNEL_DATA_INPAGE_ERROR during the driver installation.

My current storage controller is Standard SATA AHCI Controller, using Microsoft's driver.

Please advise whether this indicates an SSD failure, M.2/SATA connection issue, storage controller/driver problem, or a BIOS issue, and what HP diagnostic test or repair procedure you recommend.

BIOS: HP N76 Ver. 01.61 (10/03/2023)

I would prefer to diagnose the hardware before reinstalling Windows or replacing the SSD.

[Hawks_Eye]

Hi @disha14 

Welcome to the HP Support Community! We're here to help you get back up and running.

I understand the concern. Based on the information you've provided for your HP ProBook 640 G2, the combination of repeated KERNEL_DATA_INPAGE_ERROR BSODs and recurring Event ID 154 (Disk 0 hardware I/O errors) points more strongly toward a storage-related issue than a memory issue, especially since the RAM test has already passed.

As per the above details the following order of likelihood:

1. SSD Degradation or Intermittent SSD Failure

• Windows may still report the SSD as "Healthy" even when the drive is developing read/write faults.
• Event ID 154 indicates Windows attempted to access data from Disk 0 and received a hardware-level I/O failure.
• The fact that the system crashed during Intel Rapid Storage Technology driver installation further suggests instability while accessing storage.

2. M.2 SSD Connection Issue

• An improperly seated M.2 SSD, oxidation on contacts, or a loose connection can cause intermittent read failures.
• These failures can trigger both Event ID 154 entries and KERNEL_DATA_INPAGE_ERROR crashes.

3. Storage Controller or Driver Issue

• Less likely than hardware failure because the crashes continue while using Microsoft's Standard SATA AHCI Controller.
• However, controller communication problems cannot be ruled out until hardware diagnostics are completed.

4. System Board or BIOS Issue

• Possible, but lower probability.
• Your BIOS version (N76 Ver. 01.61 dated 10/03/2023) is already relatively current for this platform.
• BIOS-related issues typically do not generate repeated logical block I/O failures on their own.

 

Recommended HP Diagnostic Process

Before considering a Windows reinstall or SSD replacement:

Step 1: Run HP PC Hardware Diagnostics UEFI

1. Power off the notebook.
2. Turn it on and immediately tap F2 repeatedly.
3. Open HP PC Hardware Diagnostics UEFI.
4. Select Component Tests.
5. Run Storage → Quick Test.
6. If it passes, run Storage → Extensive Test.

The Storage Extensive Test is the most important test in this situation because it can identify sectors or communication issues not visible in Windows.

Step 2: Record Any Failure ID

• If the Storage test reports a failure, note the:
  • Failure ID
  • Product ID
  • Test Name

A storage failure code would strongly confirm the SSD as the source of the crashes.

Step 3: Check Physical SSD Connection If the storage tests pass:

1. Power off the system.
2. Remove AC power.
3. Access the M.2 SSD.
4. Remove and carefully reseat the SSD.
5. Ensure the retaining screw is secure.

This helps eliminate intermittent contact issues.

Step 4: Review Additional Diagnostics Within HP PC Hardware Diagnostics:

• Run System Board Test
• Run Power Test
• Run another Memory Extensive Test

Even though memory already passed, completing the full HP hardware validation helps confirm the issue is isolated to storage.

 

Note:

Because:

• Multiple BSODs occurred.
• Event Viewer repeatedly logs Disk 0 hardware I/O errors (Event ID 154).
• Crashes occur during storage-intensive activity.
• RAM tests passed.

The strongest working diagnosis is an intermittent SSD hardware problem or SSD-to-system connection issue rather than a Windows software problem.

For that reason, we recommend completing the HP UEFI Storage Extensive Test first before attempting a Windows reinstall. If the storage test fails, replacing the SSD would generally be the appropriate corrective action. If the storage test passes, the next focus should be reseating the M.2 SSD and further validating the storage controller path.

Please share the results of the HP UEFI Storage Quick Test and Extensive Test, including any Failure ID, and we can help interpret the findings and determine the next diagnostic step.

Take care, and have an amazing day!

Regards, 

Hawks_Eye