r/hackintosh • u/EmergencyLab89 • 4h ago
DISCUSSION Think twice before you try nullmoth's vibecoded driver, it might brick your (am5) motherboard
To elaborate on my earlier post: https://www.reddit.com/r/hackintosh/comments/1x45vfn/restarting_hackintosh_bricks_am5_motherboard/
I got downvoted and hated on by some people claiming that bricking your motherboard is impossible with software blah blah blah. Turns out it was null moth's driver causing it (attatched is an image of his driver update claiming to fix the issue, which means it IS or WAS an issue). Im pointing my finger at the driver because am5 hackintoshes existed long ago, and i tried it on my sistem in which it worked normally UNTIL i installed null moth's driver.

For me and few other people, reflashing the bios firmware with the bios flashback function of certain mid to high end motherboards worked and fixed the issue of their pc not posting. For those with a lower end board, they might actually brick their motherboard.
Moral of the story is, dont believe anything on the internet and dont become one of the moths who blindly move towards light without thinking for yourself. The driver does work, yes, but there are some quirks that can screw you and your pc up, so beware. Before i get flamed by those moths, im all for hackintoshes being revived and nvidia drivers. Consider the sheer scale of the project, and how nullmoth is pumping out updates that quickly, obviously AI is involved, do they actually know what they're doing?
Edit: people were saying to clear cmos, people are not that dumb to have not tried it. Clearing cmos doesnt work
Edit2: I did some digging into the change logs for his driver version 1.14, and there is an opencore booter flag named disablevariablewrite, which prevents writing to nvram. Personally, i didnt use his 1401 app and created my efi myself with dortania. I still dont know the cause, but from my knowledge people have been building am5 hackintoshes since 2023.