I lost my ability to get into Win2K. I have a dual boot setup, with Windows 98 on C (IDE disk) and Win 2K on my RAID. An onboard Highpoint controller runs the RAID setup on an Abit KX7 Raid Motherboard.
Right before I lost ‘contact’, I ran chkdsk /f on the Win2K boot drive (E). The chkdsk seemed to fail, rebooting midway, but I rebooted in OK and ran fine. The next time I re-booted, I was unable to get in. My blue screen read:
Stop 0x000000D1 (0x00000004, 0x000000010, 0x00000000, 0xEB432843)
Driver IRQL_NOT_LESS_OR_EQUAL
Address EB43284 base at EB430000
Datestamp 3ba834fb – HPT3xxNT.sys.
Here is what I know from that, thanks to MS TechNet. The system attempted to access pageable memory using kernel process IRQL that wastoo high. Drivers that have used improper addresses typically cause this problem.
The 0x0 part (the third number string) says this was a read operation.
And as far as I can tell, this is a High Point driver. It doesn’t seem to be supplied by the disk that comes with my motherboard, though. Perhaps it is a Service pack file? The RAID must be working as Windows 2K boots, or else how could it be loading drivers (from the RAID disk) before it blue screens?
But more importantly, how Ican I get to my files? I can use recovery console to see them. I even found the HPT3xxNT.sys file in system32\drivers. Renaming it won’t work-that just blue screens with an “Inaccessible boot device”. I tried replacing the file with one I found off the net (don?t try this at home!), and I get the same inaccessible device screen. I did rerun chkdsk /p from here to fix the drive.
Will I ever see my files again?? This sucks. I use RAID 0,1 just so I have automatic backup (I am using 4 disks), and now I have no way to get to the files (NTFS of course)!
PS I disabled all memory shadowing and caching just in case.
