Contribute
Register

Gigabyte Z390 M Gaming build with working NVRAM

That message is saying something's wrong with NVRAM. Have you disabled CFG Lock? Have you tried clearing NVRAM? Did you add boot-arg, "agdpmod=pikera"?
Thanks! I also upgraded bios and forgot to set some stuff, but now everything is working!
 
After much fiddling with the USB kexts and all that
Funny tracking-down-the-problem story. Around the time I did this, I also updated a few other things.

I started around then having a persistent issue that after the ZMac had been screen off but not asleep for several hours (overnight typically), I'd unlock it normally, and then it would choke, freeze a little, spinning rainbow for a while, and then it would either reboot (or possibly just the windowing part of Macos requiring a login) or (if I was in a rush) I'd hard reboot. Really this was only a minor inconvenience but since my system had been stable without such troubles for ages, puzzling and annoying.

I could find absolutely no sign of cause of this in console or crash reports or anything.

Fast forward a couple weeks: I've had a project (severla projects) ongoing for a while that meant that I had WAY too many pages open in browsers, mostly firefox and a bit in safari - like dozens and dozens and dozens. Some windows had another dozen tabs or so open. This system has a ton of memory (32gb) and plenty of other extra space. Not really any performance issues for my uses in this project. None of the pages were heavy or showed any obvious signs of memory leaks or hammering the CPUs.

Yes, it's stupid to have so many pages open. And I'd like to argue it was working for me, but not really - it was just some serious procrastination.

So a few days ago, I undertook to get this sh!t organized, bookmark and save the links where necessary, make some notes, and close a lot of these pages.

So finally, I'm back to a 'normal' number of pages open, and most without tabs.

Since I did this: not a single delay on unlock screen, not a single crash.

No idea why, whether it was a particular page, tab, combination, or whatever. Probably should have started process ot narrow things down earlier and get this straigtened out.

Of course, there's no real reason that - in these conditions - this should have led to system crashes, that's still bad. (Note: I didn't have thousands of pages open, this wasn't some absurd stress test)

But sometimes the cause of a problem doesn't make outright sense.
 
Funny tracking-down-the-problem story. Around the time I did this, I also updated a few other things.

I started around then having a persistent issue that after the ZMac had been screen off but not asleep for several hours (overnight typically), I'd unlock it normally, and then it would choke, freeze a little, spinning rainbow for a while, and then it would either reboot (or possibly just the windowing part of Macos requiring a login) or (if I was in a rush) I'd hard reboot. Really this was only a minor inconvenience but since my system had been stable without such troubles for ages, puzzling and annoying.

I could find absolutely no sign of cause of this in console or crash reports or anything.

Fast forward a couple weeks: I've had a project (severla projects) ongoing for a while that meant that I had WAY too many pages open in browsers, mostly firefox and a bit in safari - like dozens and dozens and dozens. Some windows had another dozen tabs or so open. This system has a ton of memory (32gb) and plenty of other extra space. Not really any performance issues for my uses in this project. None of the pages were heavy or showed any obvious signs of memory leaks or hammering the CPUs.

Yes, it's stupid to have so many pages open. And I'd like to argue it was working for me, but not really - it was just some serious procrastination.

So a few days ago, I undertook to get this sh!t organized, bookmark and save the links where necessary, make some notes, and close a lot of these pages.

So finally, I'm back to a 'normal' number of pages open, and most without tabs.

Since I did this: not a single delay on unlock screen, not a single crash.

No idea why, whether it was a particular page, tab, combination, or whatever. Probably should have started process ot narrow things down earlier and get this straigtened out.

Of course, there's no real reason that - in these conditions - this should have led to system crashes, that's still bad. (Note: I didn't have thousands of pages open, this wasn't some absurd stress test)

But sometimes the cause of a problem doesn't make outright sense.

Hmm... Interesting...

Do you know how much, if any, memory swap was being used? Memory pressure?

Were you using Chrome?
 
Hmm... Interesting...

Do you know how much, if any, memory swap was being used? Memory pressure?

Were you using Chrome?

Memory pressure never, ever got out of green, and well into the lower part of the green. Swap - I recall having looked many times and there might be often a couple gig of swap, but not actively swapping (in normal use - I can't say at these points when it crashed after 'waking.') Note, that swap used / amount might be at end of day - call it cruft. Also usually I'd see several (many) gigs of cached files, which I would think available to be dumped at any moment if needed.

I normally have chrome open as well (yes, I use three browsers), but I use chrome the least - there might be 2-5 tabs open but not generally more. I actually quit out of chrome quite often, but still tend to use if for a few specific things (google related).

I'm still putting this in the 'really snouldn't have been the cause but was.'
 
We had a power glitch last night while my computer was asleep. It was off this morning. It took a long time to post when I turned it back on. Now every time I login, it tells my that my computer shut down because of a problem. I have tried cold booting, restarting, etc., but I get the same message every time I login. Any ideas how to fix it? It seems to be working OK.
 
We had a power glitch last night while my computer was asleep. It was off this morning. It took a long time to post when I turned it back on. Now every time I login, it tells my that my computer shut down because of a problem. I have tried cold booting, restarting, etc., but I get the same message every time I login. Any ideas how to fix it? It seems to be working OK.
navigate to Library -> Logs -> DiagnosticReports then remove any files relating to sleep / shutdown, empty trash, reboot
 
Easy update from Monterey to Ventura :headbang:

Ventura.jpg


Thanks @pastrychef for your OC EFI (the latest 0.8.5 works with no problems :clap:)
 
Back
Top