Member Avatar for jasperanza

Yesterday I was using my Compaq v2030 laptop and I suddanly got the bluescreen error message "KERNAL_STACK_INPAGE_ERROR" it said some other stuff that I didn't quite catch...maybe something about deleting physical memory...and "STOP: 0x00000077" and then it froze up. When I tried restarting it this morning the computer began starting up before I got the following message on a black screen: "PXE-E61: Media test failure, check cable" then PXE-M0F: Exiting PXE ROM" this just loops over and over again. I did a Google search on the following errors. () and (http://www.nocrash.com/ncbbs/msgs/3576.shtml) and exhausted all of the recommendations. One thing to note that no body else seemed to mention is that when I tried to run a HARD DRIVE SELF TEST in BIOS it said "no IDE device" under "Test Status". I subsequently removed the hard drive thinking that my laptop might have just been banged around too much and it was knocked loose and reinstalled it twice with no luck. Any suggestions? I have hours and hours of work saved on there that I need to get at ASAP!

Thanks ahead of time to all takers.

  • 3 Contributors
  • 4 Replies
  • 190 Views
  • 3 Months Discussion Span
  • Latest Post Latest Post by Merlotcifer

Dani AI

Generated

Quick diagnosis and next steps

The BSOD KERNEL_STACK_INPAGE_ERROR (STOP 0x00000077) means Windows failed to read a kernel page from the paging file — commonly a disk I/O or controller problem (RAM can also cause it). The PXE‑E61 / PXE‑M0F messages appear because the BIOS fell through to a network boot after it could not find a local boot device. Together with your BIOS “no IDE device” result, the evidence points to the laptop’s storage (drive, connector, or controller) rather than Windows itself. (Microsoft bug check 0x77, Intel PXE note). (learn.microsoft.com)

Triage — what to do right now

  • If the drive makes clicking, grinding, or unusual noises: power off immediately and don’t power it on again. Every spin-up can worsen mechanical damage; at that point professional recovery is the safe option. (pitsdatarecovery.com)
  • If there are no strange noises: check BIOS boot order and that the drive is enabled, reset BIOS defaults, and confirm the drive still reads as “No device.” Those symptoms are covered in vendor HDD/BIOS troubleshooting. (seagate.com)

Safe data‑recovery workflow (if you want to try yourself)

As suggested, remove the drive and connect it to a working machine with the correct adapter/enclosure (confirm whether it’s 2.5" PATA/IDE or SATA before buying an adapter). If the drive mounts, create a sector‑level image (read‑only) and recover files from the image — do not run CHKDSK or repair utilities on the original disk first. Imaging preserves data and reduces the risk of further damage. (How to use an adapter / desktop swap guide, imaging-first guidance). (pcguide101.com)

When to stop and call a pro

If the drive is not detected, shows mechanical symptoms, or your data is irreplaceable, stop DIY attempts and contact a reputable data‑recovery lab (they have cleanrooms and specialized tools). Disabling PXE (as noted) will stop the network‑boot loop, but it won’t get your files back — treat that as a cosmetic step only. Professional services and pricing vary; ask about “no‑data, no‑charge” policies before sending the drive. (ontrack.com)

If recovery is critical, prioritize: 1) stop powering the drive if it sounds bad, 2) image if it’s readable, 3) call a recovery lab if it isn’t.

Recommended Answers

All 4 Replies

Member Avatar for DMR

If possible, try installing the laptop's drive in another computer as a slave drive. You'll need to purchase a 2.5"->3.5" adapter for the cabling, but unless the drive is severely damaged, you have a good chance of at least being able to pull your valuable data off of it.

Member Avatar for Merlotcifer

Yesterday I was using my Compaq v2030 laptop and I suddanly got the bluescreen error message "KERNAL_STACK_INPAGE_ERROR" it said some other stuff that I didn't quite catch...maybe something about deleting physical memory...and "STOP: 0x00000077" and then it froze up. When I tried restarting it this morning the computer began starting up before I got the following message on a black screen: "PXE-E61: Media test failure, check cable" then PXE-M0F: Exiting PXE ROM" this just loops over and over again. I did a Google search on the following errors. () and (http://www.nocrash.com/ncbbs/msgs/3576.shtml) and exhausted all of the recommendations. One thing to note that no body else seemed to mention is that when I tried to run a HARD DRIVE SELF TEST in BIOS it said "no IDE device" under "Test Status". I subsequently removed the hard drive thinking that my laptop might have just been banged around too much and it was knocked loose and reinstalled it twice with no luck. Any suggestions? I have hours and hours of work saved on there that I need to get at ASAP!

Thanks ahead of time to all takers.

PXE has to do with your LAN. I would disable this option in the bios. If you've already reseated your harddrive and it still gives you an err saying no IDE found, I would look into replacing harddrive.

Member Avatar for DMR

PXE has to do with your LAN. I would disable this option in the bios.

But please note that this will have no effect on the problem itself; it will just keep the computer from trying to use the network as a boot option. The reason the computer attempted the network boot in the first place is because it failed to find bootable media using the other methods in the BIOS' boot device options list. Booting from a network device, by default, usually the last option attempted; you only get to that point if all other methods (floppy, CD, add-in controller card, etc.) fail.

Member Avatar for Merlotcifer

Correct.. Not finding other boot devices and giving IDE error..

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.