Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Mac Mini restarted during sleep/hibernate at night

S

saha-med

macrumors regular
Original poster
Dec 2, 2012
193
5
Hi,

I own a late 2012 base model mac mini, running OSX 10.8.3. It was running fine all the while, and i would always sleep my mac mini instead of shutting it off at night. However recently i noticed, several times when i woke it up in the morning it had actually gone through a restart during the night.

Is it due to software updates or anything like that? Because ive heard the Mac mini can update itself while in sleep mode.


Thanks for the help
 
I recommend checking the system logs to see if any updates were applied. Otherwise, you could have either a hack booting your system, power, or a hardware issue.
 
I was looking at the system logs and i had a hard time deciphering it...

Is there any message in the system logs that signify a restart??
 
Sorry for the delay, had a crash today and managed to find out its caused by WindowServer.

Below is the diagnostics report

Process: WindowServer [98]
Path: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/WindowServer
Identifier: WindowServer
Version: 331.0.4
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 88

Date/Time: 2013-04-06 17:42:23.151 +0800
OS Version: Mac OS X 10.8.3 (12D78)
Report Version: 10

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000010c

VM Regions Near 0x10c:
-->
__TEXT 0000000100c44000-0000000100c45000 [ 4K] r-x/rwx SM=COW /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/Resources/WindowServer

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreGraphics 0x00007fff8d0b48f2 CGXLGetMainDisplay + 69
1 com.apple.CoreGraphics 0x00007fff8d0b49e4 CGXLCorrectDisplays + 62
2 com.apple.CoreGraphics 0x00007fff8d058a67 CGXRestoreDisplayConfiguration + 778
3 com.apple.CoreGraphics 0x00007fff8d05b978 restoreNewDeviceSet + 172
4 com.apple.CoreGraphics 0x00007fff8cde5c46 run_timer_pass + 381
5 com.apple.CoreGraphics 0x00007fff8ced0a6e CGXRunOneServicesPass + 198
6 com.apple.CoreGraphics 0x00007fff8ced122e CGXServer + 1000
7 WindowServer 0x0000000100c44f41 main + 9
8 libdyld.dylib 0x00007fff8d8777e1 start + 1

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff97aefd16 kevent + 10
1 libdispatch.dylib 0x00007fff9201edea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff9201e9ee _dispatch_mgr_thread + 54

Thread 2:
0 libsystem_kernel.dylib 0x00007fff97aed686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff97aecc42 mach_msg + 70
2 com.apple.CoreFoundation 0x00007fff96704233 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation 0x00007fff96709916 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation 0x00007fff967090e2 CFRunLoopRunSpecific + 290
5 com.apple.CoreFoundation 0x00007fff96717dd1 CFRunLoopRun + 97
6 com.apple.CoreGraphics 0x00007fff8d04819f eventThread + 379
7 libsystem_c.dylib 0x00007fff8c1847a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8c1711e1 thread_start + 13

Thread 3:: com.apple.CoreAnimation.render-server
0 libsystem_kernel.dylib 0x00007fff97aed686 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff97aecc42 mach_msg + 70
2 com.apple.QuartzCore 0x00007fff965e217b CA::Render::Server::server_thread(void*) + 403
3 com.apple.QuartzCore 0x00007fff96666dc6 thread_fun + 25
4 libsystem_c.dylib 0x00007fff8c1847a2 _pthread_start + 327
5 libsystem_c.dylib 0x00007fff8c1711e1 thread_start + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000005 rcx: 0x0000000000000004 rdx: 0x0000000000000000
rdi: 0x0000000100d30480 rsi: 0x0000000000000005 rbp: 0x00007fff5efb2ae0 rsp: 0x00007fff5efb2ae0
r8: 0x0000000000000004 r9: 0x0000000000000005 r10: 0x00007fdecb458ae0 r11: 0x0000000100d30470
r12: 0x00000000000003f3 r13: 0x0000000100d30480 r14: 0x0000000000000001 r15: 0x0000000000000000
rip: 0x00007fff8d0b48f2 rfl: 0x0000000000010202 cr2: 0x000000000000010c
Logical CPU: 0

Binary Images:
0x100c44000 - 0x100c44fff WindowServer (331.0.4) <22E1AB9C-F0FF-39FC-9116-378F03039FF7> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphics.framework/Resources/WindowServer
0x100dcb000 - 0x100f89fff GLEngine (8.7.25) <8398B57C-EE2D-3006-940C-CECE8E719D3B> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x100fc0000 - 0x101130fff libGLProgrammability.dylib (8.7.25) <EE2DD8AF-C6C3-303D-976E-87B4AABF8371> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib
0x101198000 - 0x101620fff com.apple.driver.AppleIntelHD4000GraphicsGLDriver (8.10.44 - 8.1.0) <6C433F44-4BDD-357F-8D15-3573B8363C10> /System/Library/Extensions/AppleIntelHD4000GraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHD4000GraphicsGLDriver
0x101794000 - 0x101798fff com.apple.IOAccelerator (30.14 - 30.14) <9AE086BC-46F6-38A3-9456-0841D7BD48E4> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator
0x10179f000 - 0x1017abfff libGPUSupportMercury.dylib (8.7.25) <1207928C-DFD1-315B-BAD6-BCDBEB03FC0D> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib
0x112a61000 - 0x112a62fff com.apple.driver.IOAccelerator2D (30.14 - 30.14) <562F8DFC-CEAB-3018-B592-ADC4A9E45496> /System/Library/Extensions/IOAccelerator2D.plugin/Contents/MacOS/IOAccelerator2D
Click to expand...

Ive researched and saw some actually recommend a logicboard replacement... is that neccessary at this stage?
 
saha-med said:
Sorry for the delay, had a crash today and managed to find out its caused by WindowServer.

Below is the diagnostics report



Ive researched and saw some actually recommend a logicboard replacement... is that neccessary at this stage?
Click to expand...

Don' know if this had to do anything with your former problem, was the time of this report during sleep/at night time?

This Crashlog is almost sure Graphic related, you can find CoreGraphics-IntelHD4000-GLEngine amongst others all GPU/IGP related.

And no, I don't think the Logic board is the problem, I think bad drivers causes this.
 
justperry said:
Don' know if this had to do anything with your former problem, was the time of this report during sleep/at night time?

This Crashlog is almost sure Graphic related, you can find CoreGraphics-IntelHD4000-GLEngine amongst others all GPU/IGP related.

And no, I don't think the Logic board is the problem, I think bad drivers causes this.
Click to expand...

Sorta, i had to go off for like few minutes and i set the mini to sleep. Came back, logged back in and can see that it had restarted as my startup scripts were run
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back