Welcome, Guest
Username: Password: Remember me

Search Micromat Forum

Keyword

TOPIC: TechToolPro10 another crash

TechToolPro10 another crash 14 Jun 2018 20:33 #9814

Again problems for a second time already. All this within an hour of buying and installing the new programme.
Running the 'check computer' suite of tests and crashed when finishing the sensor test (previous tests, memory, fans etc. ran ok). Don't think I am goin to be able to trust this new version 10 of the programme, version 9 was more stable and reliable.
iMac El Capitan 10.11.6
The administrator has disabled public write access.

TechToolPro10 another crash 14 Jun 2018 21:18 #9816

Please send a message to This email address is being protected from spambots. You need JavaScript enabled to view it. , including a link to this thread. You will receive a reply by email. The response time is unusually long at the moment. We appreciate your patience and cooperation.

Your posting will be moved to the TechTool Pro 10 forum, where your other posting has already appeared.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.

TechToolPro10 another crash 25 Jun 2018 15:49 #9890

I have almost daily maintenance to keep my Macintosh running ... the internet connection is not working well with the Mac OS software and I must use Techtool Pro to .. check the internet Devices and software .. and then tun a Download/Upload test and then I got my browsers like Safari or Firefox working ... and I get to be HERE and help you out a bit.

i just purchased TTP 10 just for the iPhone battery stuff and the new tools they have sharpened in the lab. I open TTP up and not a difference in the world on the face of it .. I plug in my iPhone 5s/32 and BANG ,.. appears the battery test in the lineup. IT works fine ... I do not have a lifestyle to Cycle my battery and after 3 years it is still at 97% capacity. Apparently i keep it FULL ... or close to it.

NOW ..to help you OUT.

Please consider doing some things after a download.

FIRST ... start up your computer on an external hard drive .. E drive ... flash drive ... another Mac platform that as TTP on it .. so you can fix up the Mac OS on your Startup Work computer ... that you like to do things with all the time. The only way you are going to optimize the data ducks and get them in a proper row in their proper files ... is to run TTP this way on the Macintosh OS.

If this is not a help .. you can always come back and rebuild the desktop folder and clean your cache folder .. small stuff that only ONCE has been an unusual change.

SECOND ... is when you are finished with the data ducks all in a row being done up. Then restart your Macintosh to Zap the PRAM. Hold down the Command + Option + P + R key on the keyboard ... throughout the startup. Your computer screen will start up normal .. then it will go black again with a second harmonic cord being struck a second time. You can hold those 4 keys down as long as you want to zap the PRAM as many times as you want .. but zapping it Once .. is good to go.

Let the computer start up ... and then see if TTP is sorted out correctly.

THIRD ..is another option to see what is diagnostically going on with your Macintosh .. and that is a SAFETY startup .. just hold down the shift key on start up ... this put Apple Self Diagnostic to work and the Computer will start up in a different configuration .. to see if TTP will run in that situation. Some time it does .. and offers up Crash reports to Apple or to Micromat as the case may be .. if there is something gong on.

Which you would like to know .. I am sure.

I am still testing TTP 10 .. but so far .. everything is working spot on correct.

Mac OS 10.13.3 on a 27 inch iMac that was made in 2013.

I understand that Apple Inc is doing work to destroy older versions of the iPhone and Macintosh .. that they admitted to in court .. as some Mac Users got pissed and took them to court over.

Since Steve Jobs died .. the management has really been fornicating with their customer base .. trying to sell them Jewelry .. Trendy colors like Pink ... and now the iPhone X ... people spend $1200 and bring the phone back in 72 hours as it is a headache to operate. There is no HOME button to fix things quickly and get on with business.

To get Home on the iPhone X .. apparently you have to press 3 buttons at the same time and do other stuff. I refuse to buy Apple now ... and waiting for my Macintosh to be obsolete and keep my iPhone as an iPod for road tunes.

Seem LENUX is the place for me .. as Microsoft is now a mandatory down load and there is no getting out of that extortion.

sumbuddie wear blind sea
The administrator has disabled public write access.

TechToolPro10 another crash 26 Jun 2018 15:50 #9897

Just upgrade to 10.0 (30 minutes ago) and app crashes every time i ask it to check machine. MacBook Pro (15-inch, 2016), running MacOS High Sierra.

Traceback:

Process: TechTool Pro 10 [68291]
Path: /Applications/TechTool Pro 10.app/Contents/MacOS/TechTool Pro 10
Identifier: com.micromat.techtoolpro10
Version: 10.0.1 (4121)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: TechTool Pro 10 [68291]
User ID: 501

Date/Time: 2018-06-26 11:40:57.303 -0400
OS Version: Mac OS X 10.13.5 (17F70a)
Report Version: 12
Bridge OS Version: 3.0 (14Y664)
Anonymous UUID: 3746BAA9-6E0A-3FCB-BCFD-0A13B1EF356F

Sleep/Wake UUID: C810A43F-669C-44AF-9BFE-BBEA2271C717

Time Awake Since Boot: 84000 seconds
Time Since Wake: 12000 seconds

System Integrity Protection: enabled

Crashed Thread: 9

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information:
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Bad value for mVideoMemoryPhysicalSize'
abort() called
terminating with uncaught exception of type NSException

Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff4f4e232b __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff76641c76 objc_exception_throw + 48
2 CoreFoundation 0x00007fff4f4e80c2 +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fff51611340 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 193
4 TechTool Pro 10 0x000000010038e01f -[MMVideoMemoryAgent performVideoMemoryTestOnDisplay:] + 767
5 TechTool Pro 10 0x000000010038ee39 -[MMVideoMemoryAgent executeVideoMemoryTest] + 585
6 TechTool Pro 10 0x000000010038da83 -[MMVideoMemoryAgent runThreadWithArguments:] + 659
7 TechTool Pro 10 0x00000001002ed7b4 -[MMThreadAgent threadEntry:] + 100
8 TechTool Pro 10 0x00000001002edbee -[MMDevThreadAgent threadEntry:] + 254
9 Foundation 0x00007fff515671f8 __NSThread__start__ + 1197
10 libsystem_pthread.dylib 0x00007fff77573661 _pthread_body + 340
11 libsystem_pthread.dylib 0x00007fff7757350d _pthread_body + 0
12 libsystem_pthread.dylib 0x00007fff77572bf9 thread_start + 13

Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff773a220a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff773a1724 mach_msg + 60
2 com.apple.SkyLight 0x00007fff711181a6 SLSGetWindowTags + 204
3 com.apple.AppKit 0x00007fff4cb1958d _NSWindowSetHasKeyAppearance + 72
4 com.apple.AppKit 0x00007fff4cb18356 -[NSWindow(NSWindow_Theme) acquireKeyAppearance] + 152
5 com.apple.AppKit 0x00007fff4cb178f0 -[NSWindow becomeKeyWindow] + 1357
6 com.apple.AppKit 0x00007fff4ccc7324 _NXShowKeyAndMain + 166
7 com.apple.AppKit 0x00007fff4ce0e0fa -[NSApplication _handleActivatedEvent:] + 1345
8 com.apple.AppKit 0x00007fff4d189236 -[NSApplication(NSEvent) sendEvent:] + 2462
9 com.apple.AppKit 0x00007fff4c9e98b5 -[NSApplication run] + 812
10 com.apple.AppKit 0x00007fff4c9b8a72 NSApplicationMain + 804
11 com.micromat.techtoolpro10 0x00000001001ee022 main + 34
12 libdyld.dylib 0x00007fff7725b015 start + 1

Thread 1:
0 libsystem_kernel.dylib 0x00007fff773abcfa __select + 10
1 com.micromat.techtoolpro10 0x000000010057d454 socket_check_fd + 259
2 com.micromat.techtoolpro10 0x000000010057d55c socket_receive_timeout + 36
3 com.micromat.techtoolpro10 0x00000001005b0ca2 receive_packet + 62
4 com.micromat.techtoolpro10 0x00000001005afdea device_monitor + 555
5 libsystem_pthread.dylib 0x00007fff77573661 _pthread_body + 340
6 libsystem_pthread.dylib 0x00007fff7757350d _pthread_start + 377
7 libsystem_pthread.dylib 0x00007fff77572bf9 thread_start + 13

Thread 2:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff773a220a mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff773a1724 mach_msg + 60
2 com.apple.CoreFoundation 0x00007fff4f45d7d5 __CFRunLoopServiceMachPort + 341
3 com.apple.CoreFoundation 0x00007fff4f45cb27 __CFRunLoopRun + 1783
4 com.apple.CoreFoundation 0x00007fff4f45c1a3 CFRunLoopRunSpecific + 483
5 com.apple.AppKit 0x00007fff4cb31fc4 _NSEventThread + 184
6 libsystem_pthread.dylib 0x00007fff77573661 _pthread_body + 340
7 libsystem_pthread.dylib 0x00007fff7757350d _pthread_start + 377
8 libsystem_pthread.dylib 0x00007fff77572bf9 thread_start + 13

Thread 3:
0 libsystem_kernel.dylib 0x00007fff773ac292 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff77573009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff77572be9 start_wqthread + 13

Thread 4:
0 libsystem_kernel.dylib 0x00007fff773ac292 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff77573009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff77572be9 start_wqthread + 13

Thread 5:
0 libsystem_kernel.dylib 0x00007fff773ac292 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff7757320e _pthread_wqthread + 1552
2 libsystem_pthread.dylib 0x00007fff77572be9 start_wqthread + 13

Thread 6:
0 libsystem_kernel.dylib 0x00007fff773ac292 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff77573009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff77572be9 start_wqthread + 13

Thread 7:
0 libsystem_kernel.dylib 0x00007fff773ac292 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff77573009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff77572be9 start_wqthread + 13

Thread 8:
0 libsystem_kernel.dylib 0x00007fff773ac292 __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff77573009 _pthread_wqthread + 1035
2 libsystem_pthread.dylib 0x00007fff77572be9 start_wqthread + 13

Thread 9 Crashed:
0 libsystem_kernel.dylib 0x00007fff773abb6e __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff77576080 pthread_kill + 333
2 libsystem_c.dylib 0x00007fff773071ae abort + 127
3 libc++abi.dylib 0x00007fff75202f8f abort_message + 245
4 libc++abi.dylib 0x00007fff7520312b default_terminate_handler() + 265
5 libobjc.A.dylib 0x00007fff76643ea3 _objc_terminate() + 97
6 libc++abi.dylib 0x00007fff7521e7c9 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x00007fff7521e26f __cxa_throw + 121
8 libobjc.A.dylib 0x00007fff76641da5 objc_exception_throw + 351
9 com.apple.CoreFoundation 0x00007fff4f4e80c2 +[NSException raise:format:arguments:] + 98
10 com.apple.Foundation 0x00007fff51611340 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 193
11 com.micromat.techtoolpro10 0x000000010038e01f -[MMVideoMemoryAgent performVideoMemoryTestOnDisplay:] + 767
12 com.micromat.techtoolpro10 0x000000010038ee39 -[MMVideoMemoryAgent executeVideoMemoryTest] + 585
13 com.micromat.techtoolpro10 0x000000010038da83 -[MMVideoMemoryAgent runThreadWithArguments:] + 659
14 com.micromat.techtoolpro10 0x00000001002ed7b4 -[MMThreadAgent threadEntry:] + 100
15 com.micromat.techtoolpro10 0x00000001002edbee -[MMDevThreadAgent threadEntry:] + 254
16 com.apple.Foundation 0x00007fff515671f8 __NSThread__start__ + 1197
17 libsystem_pthread.dylib 0x00007fff77573661 _pthread_body + 340
18 libsystem_pthread.dylib 0x00007fff7757350d _pthread_start + 377
19 libsystem_pthread.dylib 0x00007fff77572bf9 thread_start + 13

Thread 9 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x000070000d973000 rcx: 0x000070000d970f78 rdx: 0x0000000000000000
rdi: 0x000000000005610b rsi: 0x0000000000000006 rbp: 0x000070000d970fb0 rsp: 0x000070000d970f78
r8: 0x000070000d970e40 r9: 0x000070000d971010 r10: 0x0000000000000000 r11: 0x0000000000000206
r12: 0x000000000005610b r13: 0x0000000000000030 r14: 0x0000000000000006 r15: 0x000000000000002d
rip: 0x00007fff773abb6e rfl: 0x0000000000000206 cr2: 0x00007fffafd81168

Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133


Binary Images: [deleted]
removed binary images
Last Edit: 26 Jun 2018 16:49 by micromattech3.
The administrator has disabled public write access.

TechToolPro10 another crash 26 Jun 2018 16:48 #9899

Please send a message to This email address is being protected from spambots. You need JavaScript enabled to view it. , including a link to this thread. Thank you.

The forums are moderated. New postings do not appear until they are approved by a moderator. I deleted your duplicate posting.

I have edited your posting to remove the "binary images" data. I have been told that this is rarely useful to a programmer, but should be kept in case it is requested.

I suggest you change your screen name to something other than an email address. These forums are indexed by Google, and you might get a lot of spam. Use the My Account link at the top of the page, and then the Account Information link. Changing your screen name retroactively updates the screen name that appears in all of your postings.
MicroMat Inc
Makers of TechTool
Last Edit: 26 Jun 2018 16:51 by micromattech3.
The administrator has disabled public write access.

TechToolPro10 another crash 26 Jun 2018 17:32 #9900

When you contact This email address is being protected from spambots. You need JavaScript enabled to view it. , please send along, in addition to the crash report, an Apple System Information report. There is a chance that the problem is caused by the program not dealing correctly with a second monitor. Thanks for your cooperation.
MicroMat Inc
Makers of TechTool
The administrator has disabled public write access.
Time to create page: 0.327 seconds