problem after restart

Joined
Jan 1, 2009
Messages
16,379
Reaction score
4,735
Points
113
Location
Winchester, VA
Your Mac's Specs
MBP 16" 2023 (M3 Pro), iPhone 16 Pro, plus ATVs, AWatch, MacMinis (multiple)
Post #15 has paths to some. You can use EasyFind or Find Any File to find the valvesoftware one. You may have to boot in Safe mode to delete them from where you find them, then reboot normally.
 
OP
jasongoldworthy
Joined
Aug 28, 2017
Messages
535
Reaction score
30
Points
28
Location
Wales, UK
Your Mac's Specs
iMac 27" 32GB i7 3TB & 1TB NVME OSX 13,5,1 late 2013
I don’t think SIP should be off unless this is a T2 chip model requiring external boot access.

The other thing I’d like to ask is what do you do with the notice option when you receive it? Do you send the error report to Apple or just ignore it?
To be honest there is no option to report the error it just says that.
 

Attachments

  • 967E6020-7C44-4399-81AA-3CF82469134C.jpeg
    967E6020-7C44-4399-81AA-3CF82469134C.jpeg
    174 KB · Views: 2
OP
jasongoldworthy
Joined
Aug 28, 2017
Messages
535
Reaction score
30
Points
28
Location
Wales, UK
Your Mac's Specs
iMac 27" 32GB i7 3TB & 1TB NVME OSX 13,5,1 late 2013
Thanks guys I’ll try the steps you mention :)
 
OP
jasongoldworthy
Joined
Aug 28, 2017
Messages
535
Reaction score
30
Points
28
Location
Wales, UK
Your Mac's Specs
iMac 27" 32GB i7 3TB & 1TB NVME OSX 13,5,1 late 2013
Here's an older solution that may help your problem:




If that doesn't work there seem to be some other solutions posted here that might provide a solution or fix:

At least you are not alone with the problem... 😉

Hope you find one of the fixes there works for you and stops the annoying message.


- Patrick
=======
hi patrick

your suggestion worked wonders so far.

I have several sleep failure logs in there also.
 
Joined
Oct 16, 2010
Messages
18,169
Reaction score
1,914
Points
113
Location
Brentwood Bay, BC, Canada
Your Mac's Specs
2020 27" i9 5K nano iMac, 1TB(partitioned) SSD, GB, macOS 15.3.1 Sequoia
hi patrick
your suggestion worked wonders so far.

Thanks for your feedback Jason, and it's nice to know that an old fix still works works when the OS screws up. I guess it's just a matter of knowing where to look and what to do. 😉


- Patrick
=======
 
OP
jasongoldworthy
Joined
Aug 28, 2017
Messages
535
Reaction score
30
Points
28
Location
Wales, UK
Your Mac's Specs
iMac 27" 32GB i7 3TB & 1TB NVME OSX 13,5,1 late 2013
Thanks for your feedback Jason, and it's nice to know that an old fix still works works when the OS screws up. I guess it's just a matter of knowing where to look and what to do. 😉


- Patrick
=======
Yeah it sure is but it makes you think why a log would cause an issue lol

but thanks again :)
 
Joined
Oct 16, 2010
Messages
18,169
Reaction score
1,914
Points
113
Location
Brentwood Bay, BC, Canada
Your Mac's Specs
2020 27" i9 5K nano iMac, 1TB(partitioned) SSD, GB, macOS 15.3.1 Sequoia
Yeah it sure is but it makes you think why a log would cause an issue lol

What is even stranger is my El Capitan 2011 iMac suddenly started producing the same notification shortly after I had posted the suggested solution.

There were three log files existing at the suggested path, two with the same date but different times and the notification disappeared after trashing them and restarting.

I had had no problems restarting or whatever. Strange, but at least the fixed worked again.


- Patrick
=======
 
OP
jasongoldworthy
Joined
Aug 28, 2017
Messages
535
Reaction score
30
Points
28
Location
Wales, UK
Your Mac's Specs
iMac 27" 32GB i7 3TB & 1TB NVME OSX 13,5,1 late 2013
What is even stranger is my El Capitan 2011 iMac suddenly started producing the same notification shortly after I had posted the suggested solution.

There were three log files existing at the suggested path, two with the same date but different times and the notification disappeared after trashing them and restarting.

I had had no problems restarting or whatever. Strange, but at least the fixed worked again.


- Patrick
=======
Oh god that is strange to say the least I must have jinxed it :-D

but atleast the fix helped you also :)
 
Joined
Feb 1, 2011
Messages
4,904
Reaction score
2,908
Points
113
Location
Sacramento, California
I'm late coming into this thread, but it seems obvious to me that your Mac is experiencing a kernel panic when you sleep or shutdown. You *might* find a good clue as to what the culprit is by reading your panic log.

However, I see that you have the TechTool Pro kext installed. That's been known to cause kernel panics. The first thing that I would do is use TTP's uninstaller to completely remove all TTP components, and see if that fixes things.
 
OP
jasongoldworthy
Joined
Aug 28, 2017
Messages
535
Reaction score
30
Points
28
Location
Wales, UK
Your Mac's Specs
iMac 27" 32GB i7 3TB & 1TB NVME OSX 13,5,1 late 2013
I'm late coming into this thread, but it seems obvious to me that your Mac is experiencing a kernel panic when you sleep or shutdown. You *might* find a good clue as to what the culprit is by reading your panic log.

However, I see that you have the TechTool Pro kext installed. That's been known to cause kernel panics. The first thing that I would do is use TTP's uninstaller to completely remove all TTP components, and see if that fixes things.
hi Randy Thanks for the reply

believe it or not ive always had the tech tool pro installed and had no issues before.

in fact I have no issues now either since deleting the log.

how do I read a panic log ?
 
Joined
Feb 1, 2011
Messages
4,904
Reaction score
2,908
Points
113
Location
Sacramento, California
how do I read a panic log ?
You can find your Panic log file in your system directory at:

[Your Hard Drive}/Library/Logs/Panic.log.

Use the Console program, found in your Utilities folder (inside your Applications folder), to open any log file and see what it says.
 
Joined
Oct 16, 2010
Messages
18,169
Reaction score
1,914
Points
113
Location
Brentwood Bay, BC, Canada
Your Mac's Specs
2020 27" i9 5K nano iMac, 1TB(partitioned) SSD, GB, macOS 15.3.1 Sequoia
You can find your Panic log file in your system directory at:

[Your Hard Drive}/Library/Logs/Panic.log.

Use the Console program, found in your Utilities folder (inside your Applications folder), to open any log file and see what it says.

Maybe the question should have been - how do you translate what the Panic log says into something actually logical or meaningful or understandable to someone who isn't a computer Guru genius...??? 😉


- Patrick
=======
 
Joined
Feb 1, 2011
Messages
4,904
Reaction score
2,908
Points
113
Location
Sacramento, California
Maybe the question should have been - how do you translate what the Panic log says into something actually logical or meaningful or understandable to someone who isn't a computer Guru genius...??? 😉

Sometimes you can't. But since it is a free, quick, and easy thing to do it's worth taking a look when you are experiencing kernel panics and you are trying to tack them down.

You should be looking at entries that were generated recently in time, or if your kernel panic just occurred, the most recent entry. See if the entry refers to a specific application or utility. If it does, try uninstalling it, restarting, and seeing if things are better.

There are a limited number of things that tend to cause kernel panics, and they are mostly all known. Usually kernel panics are hardware related, or, more rarely, they are related to software that installs deep within, or modifies the OS itself. I, personally, would almost always look for or test these known things first.
 

Shop Amazon


Shop for your Apple, Mac, iPhone and other computer products on Amazon.
We are a participant in the Amazon Services LLC Associates Program, an affiliate program designed to provide a means for us to earn fees by linking to Amazon and affiliated sites.
Top