It's a different error this time KERNEL_DATA_IPAGE_ERROR (0x7A) as opposed to the original (0x77).
STOP: 0x0000007A
0xE1B804A8 - pte. not too interesting without the dump.
0xC000000E - ntstatus.h error code.
0xBF91AC5A - not defined for the pte case in the first parameter, might be the process id.
0x1689A860 - virtual address that couldn't be paged. - odd that it's low but the dump would probably explain it.
I'm at home so I'll need to rummage about to find out what the status code is, as it's not one of the ones listed on:-
http://www.microsoft.com/resources/...Windows/XP/all/reskit/en-us/prmd_stp_fvlq.asp
... <more searching>
It's one of the errors on the original link I posted...
If this is the case, the cause of this issue may be determined from the second parameter (the I/O status code) by using the following information that is listed in a "value of second parameter" followed by "general cause" format:
0xC000000E, or STATUS_NO_SUCH_DEVICE: the drive went unavailable, possibly a bad hard drive, disk array, and/or controller card.
That ties up with the clunk noise, it is the disk giving up the ghost and going away, right at the point windows is loading something. I can't explain easily why safe mode runs a bit better though, unless you have some odd virus or real mode loads up a bad driver for the disk.
If it's merrily making this noise all the time it's not happy. To avoid losing any data off it you might want I think you need to stop booting it now.
Get a new disk and re-install windows.
Temporarily mount this one as a slave.
Copy all the stuff you want off it.
or
Find a local who can do this stuff.
I'm not kidding about the booting thing either, if you lose an important bit of metadata for the filesystem on one of these failures it'll be byebye time to all the pictures etc. on the disk.
