Search results

Any ideas ?

No crashes on windows, but windows is not installed on the same ssd. The windows os is installed on the default xiaomi ssd, I put a second ssd for the mac os Yes I tried to install high sierra first on a Samsung 970 Evo and now on a 960 Evo, but no changes, I still have crashes.

Hi everyone, I still have big issues with my high sierra install, I tried a lots of different things though. It’s been four months since my firsts messages on this forum but nobody seems to have the answer for my problem I followed the guide in page one of this thread : I install clover on...

Well I thought maybe it was because of my BIOS version so I changed to 300 and also 502 version, but I still have these random crashes. So now I am still in 502 and I am going to install high sierra one more time to check if it changes something.

Hey everyone, Does someone managed to have something stable with the 602 bios version ? I am experiencing random crashes but maybe it's because of something else. My panic report indicate a Nvme related issue, when I look for other post with similar issues on High Sierra it seemed to be linked...

does someone have a clue about this ?

Hello, @telepati I think I have the same issue than you about SystemMemory issue and Nvme kernel Panic I'm trying to understand the thing I have to fix on my DSDT.dsl but I am quite unsure about it, even when I read this thread ...

And this is what I get when I open my origin DSDT.dsl on Maciasl : Firmware Error (ACPI): Failure looking up [^GFX0.CLID], AE_NOT_FOUND (20180427/dswload-498) // Invalid external declaration at AML offset 0x3c2 (see bz1397). Firmware Error (ACPI): Failure looking up [^^UBTC.MGI0], AE_NOT_FOUND...

I might have the same problem as you guys, I got random crashes and the report indicate it's due to my ssd drive which is a 970 evo too.

Hello again ! So I fixed the prohibitory sign issue, I still have the random crashes, each report seems to indicate a problem linked to my ssd drive. I couldn’t understand what was wrong about the drive but I tried several things : -injecting Sata-unsupported kext but I still got crashes...

oupsy, alright I'll try this

My Injectkext seemed to be "Yes", I should have checked this before trying to install FakeSMC.kext and VoodooPS2 on system. So I guess there is a conflict between my kext in systems and those on my EFI partition ?

I just installed SATA-unsupported.kext via my bootable usb key, still the same issue at start-up. So I tried to uninstall both FakeSMC.kext and VoodooPS2 controller from L/E but I have the same problem. I am not sure if I can delete kexts using "rm -Rf" from the bootable key because I still can...

I am now stuck on prohibitory sign at booting... it happened just after installing VoodooPS2Controller and FakeSMC kexts on system volume. I tried to uninstalled both of them from my usb boot key with terminal targeting my drive but apparently nothing changed. This is my verbose mode attached.

Okay, I just fixed the trackpad problem, I had to Ctrl+F9 in Windows 10 to activate it, I don't how I ended up like this. But I still have this crashes problems.

Hi everyone, I’m having troubles with trackpad in High Sierra but also in Windows 10, it isn’t detected at all. It was working fine a few hours ago and nothing has changed though. I noticed however the trackpad was working in the xiaomi boot manager. On top of this I am experiencing crash...