<< Solved >> Radeon VII - Repeated KP's - 10.14.6

EpicNUFO said:

EveryMac identified mine as a 2017 iMacPro also, but this was on the surface. Hackintool showed deeper analysis with model iMac7,1 and validity says "unlikely". Use Hackintool to check your current serial, first post of the thread I linked you to has 2nd big red arrow pointing to it. Also in the thread above I liked you to, Hackintool developer said this bug was in all (Hackintool, Clover Configurator, etc) because everyone references the same serial generation script in their backend. Here it is again:

View attachment 424758

Also, you'll notice on that screenshot ROM and Board Serial are ??? and this was due to not yet using EmuVariable with the Designare Board. Native NVRAM has tons of holes.

Click to expand...

I don't recall ever seeing the question marks for ROM and Board Serial. Native NVRAM is very important and I hate that Z390 users have no choice but to use emulated NVRAM.

The following screenshot was taken while booted using OsxAptioFix3Drv + EmuVariableUefi:

@EpicNUFO Just update to the last version of hackintool, there was a little bug in that version...

pastrychef said:

I don't recall ever seeing the question marks for ROM and Board Serial. Native NVRAM is very important and I hate that Z390 users have no choice but to use emulated NVRAM.

The following screenshot was taken while booted using OsxAptioFix3Drv + EmuVariableUefi:

Click to expand...

Yours looks good. I may change mine, I haven't decided. I have so much software on here which authorizes via machine serial, it's a lot of work and some of it requires email to deauthorize because I've gone back and forth so many times already I've exceeded the amount of times I'm allowed to do it. I've already had to go back and forth from iMac to the Pro and back and then back to the Pro then back to normal iMac again in the past month with a mobo/cpu upgrade and buggy Radeon Vii troubleshooting; I have a sour taste in my mouth about changing SMBIOS right now...it's also hard to be motivated to change it when the system has had no problems using the Free2000 driver I'm not supposed to be as is the case for many other people. Heck, @CaseySJ's guide for this mobo details using that driver and he is a site mod. Think about how many people used his guide, you don't think if it was causing issues we'd be seeing that flooding in on here?

I get it, a Clover developer made a post saying this can break things. Where is all the breakage, though? I would feel more motivated if someone could actually show examples of problems directly related to using this driver, and on what systems those problems occurred...

Juhne said:

@EpicNUFO Just update to the last version of hackintool, there was a little bug in that version...

Click to expand...

It was not a bug in Hackintool, it was a bug in the serial generation script which affected all app which utilized it. See the Hackintool thread I had linked above.

EpicNUFO said:

It was not a bug in Hackintool, it was a bug in the serial generation script which affected all app which utilized it. See the Hackintool thread I had linked above.

Click to expand...

Hello EpicNUFO! Are you still here?
Have the radeon vii and random freezing system. I cant find the reason.
After more that a year can you confirm the problem is the AppleGFXHDA?
Thank you!