apianti

This is caused by an ACPI table's code execution causing an exception, or being corrupted so the structure is messed up and makes no sense or a needed device is missing. EDIT: Boot into windows from your firmware boot menu directly. You can get the log from the blue screen from event viewer, or there are some raw dumps somewhere in the windows folder. EDIT2: The log should tell you all the information about what ACPI issue was and where/why.

I understand what you said before perfectly fine. I think you're not understanding, the system is booting. It went into a power state that turned off devices to save energy, it has to boot again but slightly differently as I said. This is actually pretty quick most the times and you probably don't really realize it unless something is causing a delay, like the screen needing to be initialized because this wasn't done during boot because it was not a full boot, it just woke the graphics device. I don't understand what this means. What do you mean wasn't at sleep before? It only sleeps one time when it sleeps and wakes, then never again? Never wakes again? Or the problem only happens the first time it sleeps? Or it's only happening after sleep? I suspect the last. And it seems to me that it is causing resolution negotiation on the external displays because they also went to sleep (from loss of signal, which is why you get a screen saying this, it is actually already out of being able to work with the graphics cards until it is reinitialized) and are also being woken up. Do you have macOS set to never sleep or hibernate? Because you are not simply just locking your screen, that keyboard shortcut is a power management function as well. https://support.apple.com/en-us/HT201236#sleep

Yeah, I'm cool. I tore my abdomen from my right groin up into rib cage, I had to have a mesh inserted to fix the herniation. Surgery wasn't anything compared to having to deal with that this entire year since it happened in january... Yeah, I keep hearing others say that they are having issues with some time delay but I don't see any commonality among them at all. I am trying to think about what else could be causing it but ACPI issues... I don't even have a guess at another answer currently actually. EDIT: Actually, seeing that the problem is that image codec driver but the code base for that driver was integrated into OC guessing the driver is missing something... I'm unsure what parts. Funny, that's the reason they used to take control of AptioFix, because it was integrated into clover, it couldn't be used or contributed by others (except it could)... then they integrated all this stuff into OC, and now it can't be used by others, lol...... Yeah I want to switch to an NVIDIA because CUDA processing, I had a class and it really sucked having to do it over ssh to a massive gpu rig at the school. Plus I realized how much you can optimize data experiments with a gpu, it's crazy. I've had this RX 580 nitro+ since launch because it was one of the models that macOS specifically supported from sapphire in that external thunderbolt enclosure. Nah, I wouldn't be using that for macOS. But it is a newer revision of the 970evo, basically just has faster transfer rates. I will actually use my 960evo for macOS, I just made this only windows so I can clone it then install macOS back onto it. I just got ahead of myself since I use windows a lot more because of certain software and I'm like stuck where I am...

Weird... Is that disabled EFI entry the same disk as arch or a different one? I wonder what the load options variables actually look like, maybe there is a mistake or something else. The ScanPolicy is not affecting what is being shown? That seems to contradict the documentation. I think I linked you previously how to change the entries, did I not? You can also just find it in the documentations. The documentation says how to rename with .contentDetails, etc: 2. How to customise boot entries? OpenCore follows standard Apple Bless model and extracts the entry name from .contentDetails and .disk_label.contentDetails files in the booter directory if present. These files contain an ASCII string with an entry title, which may then be customised by the user.

Hi @Pene! I am not using it currently. I actually don't even have macOS on my main machine at the current moment, I was thinking about getting a new SSD and cleaned this one because I can't really do much recovering from a surgery.... again, lol. Weird thing is I was not having any issues with my old machine (z77 extreme4, 2500k) or this one with clover or OC. But someone else just asked me about it happening the reverse for them, they're having good quick boot in clover but not in OC. We always seem to have fairly similar hardware, I currently have the asrock Z390 Extreme4, 9700K, was about to buy a 970evoplus 1tb (have a 960evo). Do you still have a rx580? That's what I have, and the other user, they have a skylake though. I also have other computers though I don't want to mess with them because they are used by others or for something. I am in the process of recommissioning my old main machine since I moved some parts into this one, so it is currently out of action.... I can look through what's going on though and see if I see anything plus I guess in the next few days here I will end up trying to get macOS going again, and I do normally use filevault.

Oh yeah, then I'm betting someone can indeed add that with relative ease...

I think the theme just needs updated with the newer changes that exist now. Seems like mostly the sizing is just off on everything.

Does the patch not work if you just create it in patches as well? EDIT: Sorry, I don't know if I was clear enough. I mean, does the patch work from config if you just copy the patch properties from the source you linked? EDIT2: Starting here, https://github.com/acidanthera/OpenCorePkg/commit/462a831d02da70a1c72d2c472a1d3fc9b2ef750e#diff-321493a74690c4f5eede8a18cce0eae0R883 until line 911 should be what you need. Just wondering if clover will allow an empty find.

Yes, I was saying your statement was non-sense because why do you think there are only 127 characters? You can put any character in any encoding in there............ I really don't understand you.

Call it like I see it. No, the bits at the beginning of each UTF-8 code point are referred to as leading/trailing bits. It is a common term. I found plenty of results with that google search but ok... Byte order absolutely matters check it out. The copyright character in windows codepage 1252 (western language default) is 0xA9. In UTF-8, this character is 0xA9C2, 0xA9 alone is invalid in UTF-8. It contains the highest bit set because it is larger than 127...

Oh, I just realized that as well. I never noticed that before, lol. The cyrillic one is more tall and open where the latin one is shorter and more closed. In GCC 10, they added a non-standard extended identifiers extension, enabled by default. Because this is not a problem in the other compilers since they accept extended character sets for some reason by default... What is wrong with the theme? What needs to be done to fix it? It's just missing that file, can you not just grab it from another theme or make it? Why not try to convert the old theme to svg?

I don't even know what this means, it's complete non-sense. There was literally this in the general discussion. I don't know if you know this but if there are more than 127 characters (every character set besides ASCII), then the trailer bit is set because it is the 128 bit. So every single code page in windows uses the trailer bit but does not know whether or not it is actually a trailer bit for UTF-8 unless it has a byte order mark or the locale is set to UTF-8. This is what I was explaining to slice (also this is a reason why strings are not coming out correctly - they appear to be encoded wrong in source). The reason it doesn't compile is because the template types can't be deduced, I am pretty sure I said this was a problem a while ago..... Cool. Yeah, it can't determine the type of the template arguments, so then it can't determine the type of the overloaded function arguments when used in the template...

Does ScanPolicy change how your options are shown? The default is like 0x10f0103, I think. Did you somehow not continue through the next stage and now you can't get back...?

Yeah, you don't need that driver if you have an nvme m.2 slot in your motherboard, it has to have an nvme driver. It wouldn't really make sense otherwise. You need to fix something in macOS that is causing a kernel panic during boot. EDIT: Did you happen to rebuild your kernelcache? Just noticed you cloned it, you probably got some wrong stuff in there. Maybe try booting into the recovery and try fixing your kernelcache from your install.

No you need the fixes for the NVMe drivers for macOS. That is for the preboot, which you probably don't need if the disk is recognized to begin in your firmware. EDIT: You can also have the boot stop on panic with the verbose output so you can see exactly where it is crashing, I'm just guessing that is the issue. But it would be better to know by looking at the panic.