Does our crash log indicate MBP freeze due to bad RAM or other?

Question

Hello,
Our 13-inch MBP, mid-2010, has recently begun to freeze intermittently.
Trying to determine if the cause is faultry RAM (recently upgraded) or our install of ML. Running on second set of RAM modules from the vendor. An overnight memtest did not reveal fault, but will be running it again this evening to double check.
Can you glean anything from the following, copied from the most recent crash log?
Many thanks,
JLS
Build Info:      WebKit2-7536026017000000~1
Code Type:       X86-64 (Native)
Parent Process:  Safari [3107]
User ID:         502
Date/Time:       2012-12-09 15:45:19.825 -0500
OS Version:      Mac OS X 10.8.2 (12C60)
Report Version:  10
Crashed Thread:  0  Dispatch queue: com.apple.main-thread
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
    __TEXT                 000000010d33f000-000000010d340000 [    4K] r-x/rwx SM=COW  /System/Library/StagedFrameworks/Safari/WebKit2.framework/PluginProcess.app/Con tents/MacOS/PluginProcess
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x00007fff91688d16 kevent + 10
1   libdispatch.dylib                       0x00007fff9481edea _dispatch_mgr_invoke + 883
2   libdispatch.dylib                       0x00007fff9481e9ee _dispatch_mgr_thread + 54
Thread 2:
0   libsystem_kernel.dylib                  0x00007fff916886d6 __workq_kernreturn + 10
1   libsystem_c.dylib                       0x00007fff90aadeec _pthread_workq_return + 25
2   libsystem_c.dylib                       0x00007fff90aadcb3 _pthread_wqthread + 412
3   libsystem_c.dylib                       0x00007fff90a98171 start_wqthread + 13
Thread 3:
0   libsystem_kernel.dylib                  0x00007fff916886d6 __workq_kernreturn + 10
1   libsystem_c.dylib                       0x00007fff90aadeec _pthread_workq_return + 25
2   libsystem_c.dylib                       0x00007fff90aadcb3 _pthread_wqthread + 412
3   libsystem_c.dylib                       0x00007fff90a98171 start_wqthread + 13
Thread 4:
0   libsystem_kernel.dylib                  0x00007fff916886d6 __workq_kernreturn + 10
1   libsystem_c.dylib                       0x00007fff90aadeec _pthread_workq_return + 25
2   libsystem_c.dylib                       0x00007fff90aadcb3 _pthread_wqthread + 412
3   libsystem_c.dylib                       0x00007fff90a98171 start_wqthread + 13
Thread 5:
0   libsystem_kernel.dylib                  0x00007fff916886d6 __workq_kernreturn + 10
1   libsystem_c.dylib                       0x00007fff90aadeec _pthread_workq_return + 25
2   libsystem_c.dylib                       0x00007fff90aadcb3 _pthread_wqthread + 412
3   libsystem_c.dylib                       0x00007fff90a98171 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000001  rbx: 0x0000000000000000  rcx: 0x00007fff9168853e  rdx: 0x0000000000000000
  rdi: 0x00000001139d790c  rsi: 0x0000000000000001  rbp: 0x0000000000000000  rsp: 0x138a5fb000000000
   r8: 0x000000010f317940   r9: 0x0000000000000000  r10: 0x00007fff91689342  r11: 0x0000000000000246
  r12: 0x0000000000000001  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x4d55545800000000
  rip: 0x0000000000000000  rfl: 0x0000000000010202  cr2: 0x0000000000000000
Logical CPU: 1

Answer 1

The backup you used is too old. That is why your clients are experiencing trust relationship failures: the computer passwords are no longer matching so they are failing to connect to AD. You need to disjoin and join them again.
I understand that this is the only DC you have so please make sure that the DC is not multihomed, that it points to its private IP address as primary DNS server and 127.0.0.1 as secondary one. Also, you might need to rebuild your SYSVOL folder if you keep
getting the SYSVOL errors: https://support.microsoft.com/kb/315457?wa=wsignin1.0
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile