Let's talk about Broadwell's uknown(?) GPU hang/KP issue...

[fivos1996]

I don't know what you mean by "changed every value". To which kext?
Such experimentation must be done carefully. One value at a time.

And don't forget about the need to rebuild kernel cache (best to make changes outside /S/L/E, then install kext, then rebuild cache).

If you expect to solve this, it will require a certain effort to proceed carefully, verify everything...
I'm here just to suggest things to try.
Your responsibility to pursue the ideas.

AppleIntelBDWGraphics.kext/Contents/Info.plist. But why would someone tweak Apple's graphics drivers?

 

[RehabMan]

AppleIntelBDWGraphics.kext/Contents/Info.plist. But why would someone tweak Apple's graphics drivers?

Also see options in AppleIntelBDWGraphicsFramebuffer.kext.

For the case some feature causes an issue with non-Apple hardware. Apple designs/tests their drivers for Apple hardware only.

 

[fivos1996]

Just to keep this post updated, here's what happens if you try Yosemite 10.10.5 on the same hardware.

 

[RehabMan]

Just to keep this post updated, here's what happens if you try Yosemite 10.10.5 on the same hardware.

Not useful without "Problem Reporting" files.

 

[fivos1996]

Not useful without "Problem Reporting" files.

"Problem reporting" files in this case not useful either. It's clear from the verbose output that the GPU is "hanging". Broadwell drivers seem to be different on Yosemite.

 

[RehabMan]

"Problem reporting" files in this case not useful either. It's clear from the verbose output that the GPU is "hanging". Broadwell drivers seem to be different on Yosemite.

You provided the "output".
Useless without the "input".

 

[fivos1996]

You provided the "output".
Useless without the "input".

I hope the files in ACPI/origin aren't old enough to be useless.

 

[RehabMan]

I hope the files in ACPI/origin aren't old enough to be useless.

They are too old to compare against ACPI/patched.
Must be current.
It is the only way I can know that you didn't change BIOS rev, BIOS options, or hardware.

Also, is this a fresh install with everything on the system volume vanilla?
Why is ACPIBatteryManager.kext in EFI/Clover/kexts/Other? (it is not an essential kext).

config.plist/SMBIOS/Memory/Channels=0 is nonsense. Two memory modules implies dual-channel.
Note: You would be best off with matched memory modules (best practice).

Is the panic the same every time or does it change?

 

[fivos1996]

They are too old to compare against ACPI/patched.
Must be current.
It is the only way I can know that you didn't change BIOS rev, BIOS options, or hardware.

Also, is this a fresh install with everything on the system volume vanilla?
Why is ACPIBatteryManager.kext in EFI/Clover/kexts/Other? (it is not an essential kext).

config.plist/SMBIOS/Memory/Channels=0 is nonsense. Two memory modules implies dual-channel.
Note: You would be best off with matched memory modules (best practice).

Is the panic the same every time or does it change?

Updated the files. That Yosemite installation was 100% vanilla and clean installation. About the memory, I figured out that this motherboard doesn't support dual channel at all. So if I set dual channel in config.plist, I will get 3 memory slots on System Information. I removed the battery kext as you suggested. The panic, of course, is random.

 

[RehabMan]

Updated the files. That Yosemite installation was 100% vanilla and clean installation. About the memory, I figured out that this motherboard doesn't support dual channel at all. So if I set dual channel in config.plist, I will get 3 memory slots on System Information. I removed the battery kext as you suggested. The panic, of course, is random.

Something is going wrong with your memory information.
Suggestion you focus on that.