there are two modules able to produce this error message NTLOADER and
NTKERNEL, next time you get this message, look for source module
identification somewhere on this blue screen of death. It is important
information to know

The cause of this error message is, that actual disk driver is unable to
access critical files under WINNT folder specified by operating system
descriptor inside boot.ini, usually kernel module itself, system registry or
runtime disk driver file (it can produce different message saying that
specific file is corrupted or missing, it depends on situation). Possible
causes on previously running machine:
* reset of BIOS setting - sometimes happen when CMOS battery is weak or on
some faults (peaks or leaks) of computer electrical power. Especially if you
are using SATA or SCSI disks, it is possible your BIOSes (both motherboard
and disk controller) should be set accordingly to disk driver settings. To
repair this, you need either to set BIOS back to functional settings or
replace manually disk driver file or settings in unfunctional OS instance
(not recommended for unexperienced users!)
* previous change made to disk or partions system. - Adding or removing of
disk, disk controller, adding or deleting of partition on system disk. All
this can change physical order of disks and partitions and can make
operating system descriptor in boot.ini to point to inexistant location. It
is probably not your case, as your descriptors seems to be the same. To
repair this, "just" change OS descritptor in bott.ini to point to correct
disk and partition.
* corrupted or missing file or filesystem - make deep check of filesystem
using other OS instance, eventually apply the same SP and critical system
updates to your temporary instance and try to replace the same files in
SYSTEM32 and system32/drivers folders.

ALWAYS backup original files before making any changes!