Currently Being ModeratedJan 21, 2013 10:03 AM (in response to spds.montrose)
Hello, you can post a certain amount here, but hundreds of lines won't likely be looked at, nor needed, is there a Thread such & such # crashed section in the log?
When you say it's been checked, what does that mean exactly, by you or someone else?
Currently Being ModeratedJan 21, 2013 10:17 AM (in response to spds.montrose)
What is a Kernel Panic?
More details here:
Useful article on how to avoid and eliminate kernel panics here:
Currently Being ModeratedJan 23, 2013 8:04 AM (in response to BDAqua)
"checked" = personally looking internally at the RAM to make sure it is seeded correctly and installed to spec in pairs and not loose... there are no third-party peripherals in external ports...
As far as everything else, what you see on the log is everything for that particular crash.
Currently Being ModeratedJan 24, 2013 10:34 AM (in response to spds.montrose)
Not much to go on in that, but what Audio stuff mught you be using?
Any more innfo in the system log for date/time of that crash?
Currently Being ModeratedJan 29, 2013 8:22 PM (in response to spds.montrose)
The original crash was happening while being executed in the context of the windowserver process and it caused a data access violoation. It tried to access Data access DAR=0x0000000000000018 which of course has to fail. You are a bit unlucky as the back trace terminated prematurely. However it printed the following backtrace addresses:
0x0001C2C0 0x00025860 0x00025844 0x000B45CC 0x20494452
The next steps are to:
- figure out to which modules these addresses maps and
- which functions.
Generally the full panic dump shows the module addresses. To figure out to which symbols the addresses maps you need to download the kernel debug kit as explained in http://developer.apple.com/library/mac/#technotes/tn2063/_index.html and determine the function names. If you need further help from there, you would need to provide the stacktrace with the symbols.