DJManuel Posted December 19, 2017 Share Posted December 19, 2017 On my PC at work I wanted to run synergy 2 because my PC isn't that good in specs. It has an Intel core duo (2 Cores / 2 Threads), 2Gigs of Ram and only the internal Graphics card. For some heavier workloads I decided on using my own Laptop besides my PC for work. Because I don't have Administrator privileges I can't reinstall Synergy or everything else. On my Laptop synergy 2 is working flawless but not on the PC. I wanted to ask if there are some minimal specs for Synergy 2 or if it should run on every machine? I just looked into the crashdump and there it says "Application_Fault_Null_Pointer_Read_Before_Call" and some other error codes. I put the crashdump at the end so somebody can probably help me. I would accept it if I just can't run Synergy 2 on my work PC but for now it's frustrating for me (because it's the first Installation and first try of Synergy 2) Thanks, Manuel Heres the Crashdump: Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 7 Version 7601 (23889) MP (2 procs) Free x86 compatible Product: WinNt kernel32.dll version: 6.1.7601.23889 (win7sp1_ldr.170810-1615) Machine Name: Debug session time: Tue Dec 19 02:46:12.000 2017 (UTC - 5:00) System Uptime: not available Process Uptime: 0 days 0:00:20.000 Kernel time: 0 days 0:00:01.000 User time: 0 days 0:00:01.000 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2 *** WARNING: Unable to verify checksum for ntdll.dll ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** WARNING: Unable to verify checksum for kernel32.dll TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2 *** WARNING: Unable to verify timestamp for Qt5Core.dll *** ERROR: Module load completed but symbols could not be loaded for Qt5Core.dll *** WARNING: Unable to verify checksum for ucrtbase.DLL *** WARNING: Unable to verify checksum for USER32.dll *** WARNING: Unable to verify timestamp for Qt5Qml.dll *** ERROR: Module load completed but symbols could not be loaded for Qt5Qml.dll *** WARNING: Unable to verify checksum for ole32.dll *** WARNING: Unable to verify timestamp for synergy-config.exe *** ERROR: Module load completed but symbols could not be loaded for synergy-config.exe *** WARNING: Unable to verify checksum for wlanapi.dll *** WARNING: Unable to verify checksum for RPCRT4.dll *** WARNING: Unable to verify checksum for SHELL32.dll TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 FAULTING_IP: ig4icd32+2095ed 031e95ed 8b01 mov eax,dword ptr [ecx] EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 031e95ed (ig4icd32+0x002095ed) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 00000000 Attempt to read from address 00000000 PROCESS_NAME: synergy-config.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 00000000 READ_ADDRESS: 00000000 FOLLOWUP_IP: ig4icd32+2095ed 031e95ed 8b01 mov eax,dword ptr [ecx] NTGLOBALFLAG: 0 FAULTING_THREAD: 00001e58 BUGCHECK_STR: APPLICATION_FAULT_NULL_POINTER_READ_BEFORE_CALL PRIMARY_PROBLEM_CLASS: NULL_POINTER_READ_BEFORE_CALL DEFAULT_BUCKET_ID: NULL_POINTER_READ_BEFORE_CALL LAST_CONTROL_TRANSFER: from 74c2c0fc to 031e95ed STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 05a6f370 74c2c0fc 000c0000 00100000 74c2c10d ig4icd32+0x2095ed 05a6f3bc 032778ca 00000000 06c4dba8 06c4dba8 KERNELBASE!GlobalAlloc+0x6e 05a6f4b4 77ca5f3c 05a6f97c 00000001 06c4c1c0 ig4icd32+0x2978ca 05a6f4b8 05a6f97c 00000001 06c4c1c0 00000000 ntdll!NtReleaseMutant+0xc 05a6f4c4 00000000 06afdeb0 06afdeb4 06afdeb4 0x5a6f97c SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ig4icd32+2095ed FOLLOWUP_NAME: MachineOwner MODULE_NAME: ig4icd32 IMAGE_NAME: ig4icd32.dll DEBUG_FLR_IMAGE_TIMESTAMP: 4aba6fc2 STACK_COMMAND: ~14s; .ecxr ; kb FAILURE_BUCKET_ID: NULL_POINTER_READ_BEFORE_CALL_c0000005_ig4icd32.dll!Unknown BUCKET_ID: APPLICATION_FAULT_NULL_POINTER_READ_BEFORE_CALL_ig4icd32+2095ed Followup: MachineOwner --------- Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.