SGTool and windows 7 64bit Problem - Crash Analysis

[unlock.mk]

We all know about SGTool problem with starting on windows 7 platform.

I want to open this thread in order to find solution. It is nice piece of software, so we all want to use it, no matter what kind of windows we have.

If someone have solution for this, please post here.
I made DMP file and i want to share results of that file, maybe, i say just maybe will be useful to programers to fix that bug, which is present in this software a while ago.

Crash Analysis
Windows 7 Version 7601 (Service Pack 1) MP (4 procs) Free x64
kernel32.dll version: 6.1.7601.17651 (win7sp1_gdr.110715-1504)

*** ERROR: Module load completed but symbols could not be loaded for sgtool.exe
*** WARNING: Unable to verify checksum for actskn43.ocx

EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD: 00000000000001ec

DEFAULT_BUCKET_ID: STATUS_BREAKPOINT

PROCESS_NAME: sgtool.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG: 0

APPLICATION_VERIFIER_FLAGS: 0

PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT

BUGCHECK_STR: APPLICATION_FAULT_STATUS_BREAKPOINT

LAST_CONTROL_TRANSFER: from 0000000074662cb4 to 0000000074662e09

STACK_TEXT:
00000000`0008ec08 00000000`74662cb4 : 00000000`747f8e63 00000000`746d0023 00000000`00200246 00000000`0018f41c : wow64cpu!CpupSyscallStub+0x9
00000000`0008ec10 00000000`746dd07e : 00000000`00000000 00000000`74661920 00000000`0008eea0 00000000`76e9ecd1 : wow64cpu!Thunk2ArgNSpNSpReloadState+0x2a
00000000`0008ecd0 00000000`746dc549 : 00000000`00000000 00000000`00000000 00000000`746d4ac8 00000000`7ffe0030 : wow64!RunCpuSimulation+0xa
00000000`0008ed20 00000000`76eb4956 : 00000000`002b3030 00000000`00000000 00000000`76fa2670 00000000`76f75978 : wow64!Wow64LdrpInitialize+0x429
00000000`0008f270 00000000`76eb1a17 : 00000000`00000000 00000000`76eb4061 00000000`0008f820 00000000`00000000 : ntdll!LdrpInitializeProcess+0x17e4
00000000`0008f760 00000000`76e9c32e : 00000000`0008f820 00000000`00000000 00000000`7efdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x29220
00000000`0008f7d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe


STACK_COMMAND: ~0s; .ecxr ; kb

FOLLOWUP_IP:
wow64cpu!CpupSyscallStub+9
00000000`74662e09 c3 ret

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: wow64cpu!CpupSyscallStub+9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: wow64cpu

IMAGE_NAME: wow64cpu.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4e212273

FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_wow64cpu.dll!CpupSyscal lStub

BUCKET_ID: X64_APPLICATION_FAULT_STATUS_BREAKPOINT_wow64cpu!C pupSyscallStub+9

WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne...htm?Retriage=1

"Helvetica CE row CE Light "Helvetica CE row CE Light "Helvetica CE row CE Light "Helvetica CE row CE Light "Helvetica CE row CE Light "Helvetica CE row CE Light "Helvetica CE row CE Light "Helvetica CE row CE Light Samsung Unlock Client Link to Support Forum Read UnlockCodes Advanced Options Select Language S_VERSION_INFO VarFileInfo Translation StringFileInfo 040904B0 Comments SGTool CompanyName SETOOL.NET FileDescription SETOOL Samsung Module LegalCopyright SETOOL.net ProductName SGTool FileVersion 1.00.0004 ProductVersion 1.00.0004 InternalName sgtool OriginalFilename sgtool.exe "Helvetica CE row CE Light "Helvetica CE row CE Light /13+R& zt)@FI

[universalunlocking]

i have same problem i can not open SGTool at all try all methods need help

[unlock.mk]

We all need sgtool to work on W7-64bit. But no such as update till now.

[daz72]

agreed we need sgtool update to work with win7 64bit.

br.

[Camecana]

Originally Posted by daz72

agreed we need sgtool update to work with win7 64bit.

br.

i have same problem on win7 32 bits
LGTool is OK
SETool is OK
SGTool not running (it was working before)