To find that answer you would need to enable boot logging in the bios of the system you are operating with. To do this process a step by step can be found at: http://www.watchingthenet.com/how-to-enable-boot-logging-for-fixing-startup-problems-in-windows.html
Typically the issues lay with the file AFTER the one that was previously loaded in the log as the system has already loaded the file in the log and crashes loading the one following.
It's ntldr.exe
compact
False.
Ntbtlog.txt path= C:\Windows\Ntbtlog.txt page 701
no it can also use FAT32 or FAT16
1.5 times the amount of RAM
To use the utility to scan all Windows 2000/XP system files and verify them, first close all applications and then enter the command sfc /scannow in the Run dialog box. Click OK. The Windows File Protection window opens.
NTBOOTDD.sys
Enable Boot Logging
Windows 2000
It supports the New Technology File System (NTFS) which was used in Windows NT, 2000, XP, Server editions, Vista and Windows 7. It has changed from the File Allocation Table (FAT) file system which was used in earlier versions (and is still used in many removable devices). The reason for this is that NTFS uses access control lists (ACL) to track files and prevent less fragmentation, extra security protocols and a technology so that hard drive space can be utilized more efficiently.
Windows 2000
In A+ Guide to Managing & Maintaining Your PC Sixth Edition, Page 59 of Chapter 2 "What an Operating System Does" You will find it says: "The data is stored in a file on the hard drive called a SWAP file or PAGE file. The Windows 2000/XP swap file is Pagefile.sys, and the Windows 9x/Me swap file is Win386.swp."