I’m going to update this thread because the only thing worse than finding no solution to your problem on Google is finding a problem listed without a solution.

These machines can in with 8gb of RAM. Some came in with 4 2gb sticks of memory and some came with 1 4gb and 2 2gb sticks. The machines without the 4gb stick work perfectly. They will image just fine. If I image them and then add the 4gb stick back in, they blue screen. So Tom was correct, it was a RAM issue. The 4gb stick of RAM is causing the issue. Thanks for all the help!

@george1421 I changed EFI to rEFInd. I changed legacy to the GRUB_FIRST_HDD. So far every machine I have found is working! Thanks for the help. My Bootfile Name on the DHCP server is set to: undionly.kkpxe. I have seen others who use undionly.kpxe. Should I just leave it since it is working?

@george1421 Changed it to GRUB_FIRST_HDD. It is now working on the Hyper V virtual. Let me see what it does on the other physical machine that was giving me issues.

@george1421 I went into Fog System Settings -> Fog Boot Settings and changed it to SAN Boot. Now the machine is sitting at: “Booting from SAN device 0x80”

@george1421

#!ipxe
set fog-ip 10.25.8.68
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
cpuid --ext 29 && set arch x86_64 || set arch i386
goto get_console
:console_set
colour --rgb 0x00567a 1 ||
colour --rgb 0x00567a 2 ||
colour --rgb 0x00567a 4 ||
cpair --foreground 7 --background 2 2 ||
goto MENU
:alt_console
cpair --background 0 1 ||
cpair --background 1 2 ||
goto MENU
:get_console
console --picture http://10.25.8.68/fog/service/ipxe/bg.png --left 100 --right 80 && goto console_set || goto alt_console
:MENU
menu
colour --rgb 0xff0000 0 ||
cpair --foreground 1 1 ||
cpair --foreground 0 3 ||
cpair --foreground 4 4 ||
item --gap Host is NOT registered!
item --gap -- -------------------------------------
item fog.local Boot from hard disk
item fog.memtest Run Memtest86+
item fog.reginput Perform Full Host Registration and Inventory
item fog.reg Quick Registration and Inventory
item fog.deployimage Deploy Image
item fog.multijoin Join Multicast Session
item fog.sysinfo Client System Information (Compatibility)
choose --default fog.local --timeout 5000 target && goto ${target}
:fog.local
exit || goto MENU
:fog.memtest
kernel memdisk initrd=memtest.bin iso raw
initrd memtest.bin
boot || goto MENU
:fog.reginput
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.25.8.68/fog/ consoleblank=0 rootfstype=ext4 storage=10.25.8.68:/images/ storageip=10.25.8.68 loglevel=4 mode=manreg
imgfetch init_32.xz
boot || goto MENU
:fog.reg
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.25.8.68/fog/ consoleblank=0 rootfstype=ext4 storage=10.25.8.68:/images/ storageip=10.25.8.68 loglevel=4 mode=autoreg
imgfetch init_32.xz
boot || goto MENU
:fog.deployimage
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param qihost 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
param sysuuid ${uuid}
:fog.multijoin
login
params
param mac0 ${net0/mac}
param arch ${arch}
param username ${username}
param password ${password}
param sessionJoin 1
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme
param sysuuid ${uuid}
:fog.sysinfo
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=http://10.25.8.68/fog/ consoleblank=0 rootfstype=ext4 storage=10.25.8.68:/images/ storageip=10.25.8.68 loglevel=4 mode=sysinfo
imgfetch init_32.xz
boot || goto MENU
:bootme
chain -ar http://10.25.8.68/fog/service/ipxe/boot.php##params ||
goto MENU
autoboot

Link to pics: https://drive.google.com/open?id=1FKqzzshyMckBJWUW5Ty_0ooDn9nRjLbI

The pxe booting computer that I am using now is a Hyper V virtual machine. It is running in bios mode. I have tried it with physical machines that are also running in bios. (same result).

Pictures are attached. 

I am in the process of creating a new Fog Server for my School District. My current one is on version 1.4. using Ubuntu. I wanted to have a virtual one and try out CentOS 7 so I started from scratch. It is using Fog version 1.5.4. I created a virtual Windows 10 machine to test with. When it boots to the new Fog Server, it will load the Fog menu and if I wait it out, it tries to boot but gets the Chainloading failed message. It then gets stuck in a boot loop. If I switch DHCP back to the old Fog Server things work. I have tried all of the BOOT EXIT types and nothing seems to help. Trying a few kernals didn’t help.

I’m going to update this thread because the only thing worse than finding no solution to your problem on Google is finding a problem listed without a solution.

These machines can in with 8gb of RAM. Some came in with 4 2gb sticks of memory and some came with 1 4gb and 2 2gb sticks. The machines without the 4gb stick work perfectly. They will image just fine. If I image them and then add the 4gb stick back in, they blue screen. So Tom was correct, it was a RAM issue. The 4gb stick of RAM is causing the issue. Thanks for all the help!

@george1421 We have uefi turned off. We are using traditional 500gb hard drives. How do I run the compatibility test?

I forgot to specify. We have tried 3 machines with similar results.