Bootloop after login

[cadash]

Hi guys,

 

For some reason I started getting a boot loop right after login, I am not sure why but it happens after a few seconds. Once it reboots. if I choose to resume the crashed session it reboots right away. If I click the Cancel button it starts and then after a few seconds it boots again.

OSX is installed on a second drive.

First drive has Windows 10, inside it I run a Wmware machine that uses the Physical disk where OS X is installed and I am able to use if just fine and it doesnt have the boot loop problem.

I didn't change anything in the bios or hardware. The only problem I had is that I accidentally  wiped the first HDD where Win10 is instead of a USB drive as the install location. I didn't realize they had the same volume names and the HDD took the priority, yeah!! lucky me.

 

 I know its not a hardware problem,  I checked the BIOS and it looks just fine as always however I am never to stay in OS X long enough to do anything it just reboots.

 

I also tried making a USB installer to install El Capitan/Sierra/High Sierra all of them several times on a second machine within VMWare on Win10 booting the HDD, for some reason it won't boot. I guess it is because VMWare Player 14 is handling the USB operations. No matter which Clover version I try to put in the USB installer, I get an incompatibility warning. (tried from clover versions 3544 onwards till the latest 4300 something) The installer says everything was installed, I can see the files in the drive but the drive never boots after a power cycle.

 

I have a third 128mb USB drive with just clover, I know this clover works just fine because I can use it to boot the drive with the bootloop problems. But when I use it in the second machine, the USB installer with the non working clove would boot but then will give me an HPET error halfway the OS load up.

 

I am pretty sure that if I could make everything work properly if I could at least have one disk to load the OS. Then I should be able to create an installer with no issues the same way I always did. 

 

I know this whole thing sounds weird. But I have been pulling my hair over 2 days trying to figure this one out. Any pointers, ideas, suggestions are highly appreciated. Haven't felt this clueless for a long time.

 

[cadash]

Ok, solved, I figured out that that the no HPETs available error is actually a kernel panic and its easily fixed using the nullcpupowermanagement.kext

 

The weird thing is that I never had to use that kext till now. My second machine has the exact some motherboard and I am not getting this issue either. 

 

Being able to boot into my first computer I could create the USB installer and make it boot without issues.