Start-up times out after mobo replacement

[Dnk_Productions]

The CPU temps were out of control so I replaced the motherboard. CPU temps are normal and stable but the system will not boot (it goes to the apple screen, startup wheel turns for 3 seconds and then the monitor (plasma TV) goes black (ie time's out).

Everything was kept the same. Made sure bios was f8, AHCI mode, etc. I have tried npci=0x2000 and npci=0x3000, PCIRootUID=0 (and =1), GraphicsEnabler=No, -x, -v, -f and nothing works.

If I don't enter npci=0x3000 then there is no wheel and it automatically goes from apple screen to blank screen (ie times-out). I assumed that everything would just startup with the new mobo since nothing else had changed. Only clue that I have is that verbose hangs at "PCI configuration begin" and then the screen goes black. This is the same thing with my pro hack build (that's right, I had two working now none of the hacks are working...)

gigabyte H61-USB3 (rev 1)
intel i5 2500k
8GB RAM
nvidia GT640

 

[TheTVMan]

As you know getting stuck at "PCI configuration begin" is usually a combination or npci=0x3000 and PCIRootUID=1/0 so maybe boot in -s and clear contents of; /System/Library/Caches/com.apple.kext.caches

 

[Dnk_Productions]

As you know getting stuck at "PCI configuration begin" is usually a combination or npci=0x3000 and PCIRootUID=1/0 so maybe boot in -s and clear contents of; /System/Library/Caches/com.apple.kext.caches

Thanks for the reply and yep that is what I thought but I am just not able to boot with any of the flags (even in safe or single user mode). I have attached some kernel Backtrace errors that I have received (attached). I have seen these before but not sure what to do with them.

I have tried UseKernelCache=No as well as -f to clear cache for boot but I am running into the same problem; which is the black screen (timed out monitor)

 

[Dnk_Productions]

Anyone else have any ideas? I am going to manually go into S/L/caches/com.apple.kext.caches and delete everything in here. This probably won't work because I can't even get unibeast to launch for a fresh install. The same issue occurs which is that the apple logo appears for about 3 seconds and then it goes to a black screen.

I am in f8; the only real change I made to the bios otherwise was change the boot order enable HTEP, 64 bit mode. I am probably missing something easy. Anyone? This is extremely frustrating as this is a super easy build that I have had working for 8 months.

Not a RAM issue: replaced RAM sticks one by one and same issue
Not a mobo issue: just replaced the mobo (although it is the same mobo there are additional settings that weren't in my last mobo such as Azalia audio (in the bios)
Not a graphics card issue: tried onboard (with GraphicsEnabler=Yes) and same issue
CPU: could be a CPU issue. Could the computer stop booting up because of a CPU issue. Everything seems find in terms of the CPU being read in the bios and the temps are stable

 

[TheTVMan]

A little random but is the onboard sound turned on in the BIOS Integrated Peripherals?

Also add a debug command to your boot up arguments, debug=0x100 this helped me when I was having issues with my 690 as it would dump the error msg on the screen when the screen blanked.

 

[TheTVMan]

SoundFlower is a program right? Try deleting it.

 

[Dnk_Productions]

A little random but is the onboard sound turned on in the BIOS Integrated Peripherals?

Also add a debug command to your boot up arguments, debug=0x100 this helped me when I was having issues with my 690 as it would dump the error msg on the screen when the screen blanked.

The only onboard audio that I see is Azalia. I went ahead and disabled this then trying booting with debug=0x100 npci=0x3000 PCIRootUID=0 -v. I saw the following error message and then the screen went black again.

Unable to open /var/db/BootCache.playlist [Mountain Lion]. This error message quickly disappears

SoundFlower is a program right? Try deleting it.

I went into the SSD and deleted this application as well; same issue. Verified and repaired the disk as well.

Could this be a hardware issue? It doesn't seem like one, but I am starting to think it could be