MikroTik

Community discussions
https://forum.mikrotik.com/

WinBox 3.7 crashes on Win10 15002

https://forum.mikrotik.com/viewtopic.php?t=116678

Page 1 of 1

WinBox 3.7 crashes on Win10 15002

Posted: Tue Jan 10, 2017 1:36 am
by ptr727
WinBox 3.7 connect to RB2011UAS-2HnD crash on Windows 10 x64 Pro Insider Fast Ring build 15002.
Used to work in previous Win10 builds, crashed since updating to the 15002 build released today.
Tested on two different machines. both crash after updating to 15002.
Code: Select all
Microsoft (R) Windows Debugger Version 10.0.10586.567 X86
Copyright (c) Microsoft Corporation. All rights reserved.

CommandLine: D:\Downloads\winbox.exe
Symbol search path is: srv*
Executable search path is: 
ModLoad: 00400000 0058a000   winbox.exe
ModLoad: 77960000 77ae6000   ntdll.dll
ModLoad: 74dd0000 74ea0000   WOW64_IMAGE_SECTION
ModLoad: 74dd0000 74ea0000   C:\WINDOWS\SysWOW64\KERNEL32.DLL
ModLoad: 74950000 74b08000   C:\WINDOWS\SysWOW64\KERNELBASE.dll
ModLoad: 743e0000 74472000   C:\WINDOWS\SysWOW64\apphelp.dll
ModLoad: 755d0000 75647000   C:\WINDOWS\SysWOW64\ADVAPI32.DLL
ModLoad: 74b10000 74bcd000   C:\WINDOWS\SysWOW64\msvcrt.dll
ModLoad: 75e80000 75ec1000   C:\WINDOWS\SysWOW64\sechost.dll
ModLoad: 75680000 7573f000   C:\WINDOWS\SysWOW64\RPCRT4.dll
ModLoad: 74490000 744b0000   C:\WINDOWS\SysWOW64\SspiCli.dll
ModLoad: 74480000 7448a000   C:\WINDOWS\SysWOW64\CRYPTBASE.dll
ModLoad: 77590000 775e5000   C:\WINDOWS\SysWOW64\bcryptPrimitives.dll
ModLoad: 74860000 7494d000   C:\WINDOWS\SysWOW64\COMDLG32.DLL
ModLoad: 6e8b0000 6e93e000   C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.15002.1001_none_eaa1cc1389d7dfdb\COMCTL32.DLL
ModLoad: 776f0000 77910000   C:\WINDOWS\SysWOW64\combase.dll
ModLoad: 75740000 75761000   C:\WINDOWS\SysWOW64\GDI32.dll
ModLoad: 75490000 755a8000   C:\WINDOWS\SysWOW64\ucrtbase.dll
ModLoad: 772f0000 7744a000   C:\WINDOWS\SysWOW64\gdi32full.dll
ModLoad: 775f0000 77676000   C:\WINDOWS\SysWOW64\shcore.dll
ModLoad: 77450000 77586000   C:\WINDOWS\SysWOW64\USER32.dll
ModLoad: 77910000 77955000   C:\WINDOWS\SysWOW64\SHLWAPI.dll
ModLoad: 75f80000 75f95000   C:\WINDOWS\SysWOW64\win32u.dll
ModLoad: 75fa0000 772e9000   C:\WINDOWS\SysWOW64\SHELL32.dll
ModLoad: 757f0000 75824000   C:\WINDOWS\SysWOW64\cfgmgr32.dll
ModLoad: 75860000 75dc9000   C:\WINDOWS\SysWOW64\windows.storage.dll
ModLoad: 755b0000 755be000   C:\WINDOWS\SysWOW64\kernel.appcore.dll
ModLoad: 752c0000 75305000   C:\WINDOWS\SysWOW64\powrprof.dll
ModLoad: 75ed0000 75ee0000   C:\WINDOWS\SysWOW64\profapi.dll
ModLoad: 753a0000 7548f000   C:\WINDOWS\SysWOW64\OLE32.dll
ModLoad: 77680000 776e7000   C:\WINDOWS\SysWOW64\WS2_32.dll
ModLoad: 73710000 7373f000   C:\WINDOWS\SysWOW64\IPHLPAPI.DLL
ModLoad: 72af0000 72d64000   C:\WINDOWS\SysWOW64\WININET.DLL
(35fc.3600): Break instruction exception - code 80000003 (first chance)
eax=00000000 ebx=0033e000 ecx=1de70000 edx=00000000 esi=007b25e8 edi=77966a34
eip=77a0a065 esp=0078fa24 ebp=0078fa50 iopl=0         nv up ei pl zr na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
ntdll!LdrpDoDebuggerBreak+0x2b:
77a0a065 cc              int     3
0:000> g
ModLoad: 75650000 75675000   C:\WINDOWS\SysWOW64\IMM32.DLL
ModLoad: 73bd0000 73c44000   C:\WINDOWS\SysWOW64\uxtheme.dll
ModLoad: 744b0000 745f1000   C:\WINDOWS\SysWOW64\MSCTF.dll
ModLoad: 75ee0000 75f76000   C:\WINDOWS\SysWOW64\OLEAUT32.dll
ModLoad: 75770000 757e8000   C:\WINDOWS\SysWOW64\msvcp_win.dll
ModLoad: 736b0000 736d3000   C:\WINDOWS\SysWOW64\dwmapi.dll
ModLoad: 73dc0000 73fc5000   C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.15002.1001_none_88bf45bd232301a6\comctl32.DLL
ModLoad: 73890000 738de000   C:\WINDOWS\SysWOW64\mswsock.dll
ModLoad: 74dc0000 74dc7000   C:\WINDOWS\SysWOW64\NSI.dll
ModLoad: 72a00000 72a13000   C:\WINDOWS\SysWOW64\dhcpcsvc6.DLL
ModLoad: 737d0000 737e4000   C:\WINDOWS\SysWOW64\dhcpcsvc.DLL
ModLoad: 730b0000 7310e000   C:\WINDOWS\SysWOW64\textinputframework.dll
ModLoad: 6f3c0000 6f44f000   C:\WINDOWS\SysWOW64\CoreMessaging.dll
ModLoad: 6f1a0000 6f3be000   C:\WINDOWS\SysWOW64\CoreUIComponents.dll
ModLoad: 74310000 74338000   C:\WINDOWS\SysWOW64\ntmarta.dll
ModLoad: 733a0000 7346f000   C:\WINDOWS\SysWOW64\wintypes.dll
ModLoad: 05410000 054df000   C:\WINDOWS\SysWOW64\wintypes.dll
HEAP[winbox.exe]: HEAP: Free Heap block 04DEDF08 modified at 04DEDF28 after it was freed
(35fc.3600): Break instruction exception - code 80000003 (first chance)
eax=0033e000 ebx=04deddd0 ecx=77a72be0 edx=00000047 esi=04dedf08 edi=00fb0000
eip=779f1fd9 esp=0078e2d8 ebp=0078e430 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
ntdll!RtlpFreeHeap+0x50e39:
779f1fd9 cc              int     3
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for winbox.exe - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\WINDOWS\SysWOW64\USER32.dll - 

DUMP_CLASS: 2

DUMP_QUALIFIER: 0

FAULTING_IP: 
ntdll!RtlpFreeHeap+50e39
779f1fd9 cc              int     3

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 779f1fd9 (ntdll!RtlpFreeHeap+0x00050e39)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 00000000

FAULTING_THREAD:  00003600

DEFAULT_BUCKET_ID:  HEAP_CORRUPTION

PROCESS_NAME:  winbox.exe

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

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

EXCEPTION_CODE_STR:  80000003

EXCEPTION_PARAMETER1:  00000000

WATSON_BKT_PROCSTAMP:  382f3815

WATSON_BKT_MODULE:  ntdll.dll

WATSON_BKT_MODSTAMP:  170c4638

WATSON_BKT_MODOFFSET:  91fd9

WATSON_BKT_MODVER:  10.0.15002.1001

MODULE_VER_PRODUCT:  Microsoft® Windows® Operating System

BUILD_VERSION_STRING:  10.0.15002.1001 (WinBuild.160101.0800)

MODLIST_WITH_TSCHKSUM_HASH:  0c888cd5887bae3a064add545bed8e073fe8ae76

MODLIST_SHA1_HASH:  a8520b5d144bdadf4098269ab92151726f5deb04

NTGLOBALFLAG:  70

APPLICATION_VERIFIER_FLAGS:  0

PRODUCT_TYPE:  1

SUITE_MASK:  272

APP:  winbox.exe

ANALYSIS_SESSION_HOST:  DESKTOP-D4TCEVF

ANALYSIS_SESSION_TIME:  01-09-2017 15:32:13.0487

ANALYSIS_VERSION: 10.0.10586.567 x86fre

THREAD_ATTRIBUTES: 
ADDITIONAL_DEBUG_TEXT:  Enable Pageheap/AutoVerifer ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

LAST_CONTROL_TRANSFER:  from 779a0e61 to 779f1fd9

THREAD_SHA1_HASH_MOD_FUNC:  d3700d7694bbaf2892b55a428e66c1c86824c3af

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  4f19ffb264187d83e23a436df1595c04f3258103

OS_LOCALE:  ENU

PROBLEM_CLASSES: 



HEAP_CORRUPTION
    Tid    [0x3600]
    Frame  [0x00]: ntdll!RtlpFreeHeap



HEAP_CORRUPTION
    Tid    [0x3600]
    Frame  [0x00]: ntdll!RtlpFreeHeap


BUGCHECK_STR:  HEAP_CORRUPTION_HEAP_CORRUPTION

STACK_TEXT:  
00000000 00000000 heap_corruption!heap_corruption+0x0


THREAD_SHA1_HASH_MOD:  ca4e26064d24ef7512d2e94de5a93c38dbe82fe9

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  heap_corruption!heap_corruption

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: heap_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  ** Pseudo Context ** ; kb

FAILURE_BUCKET_ID:  HEAP_CORRUPTION_80000003_heap_corruption!heap_corruption

BUCKET_ID:  HEAP_CORRUPTION_HEAP_CORRUPTION_heap_corruption!heap_corruption

PRIMARY_PROBLEM_CLASS:  HEAP_CORRUPTION_HEAP_CORRUPTION_heap_corruption!heap_corruption

BUCKET_ID_OFFSET:  0

BUCKET_ID_MODULE_STR:  heap_corruption

IMAGE_NAME:  heap_corruption

BUCKET_ID_MODTIMEDATESTAMP:  0

BUCKET_ID_MODCHECKSUM:  0

BUCKET_ID_MODVER_STR:  

BUCKET_ID_PREFIX_STR:  

FAILURE_PROBLEM_CLASS:  HEAP_CORRUPTION

FAILURE_EXCEPTION_CODE:  80000003

FAILURE_IMAGE_NAME:  heap_corruption

FAILURE_FUNCTION_NAME:  heap_corruption

BUCKET_ID_FUNCTION_STR:  heap_corruption

FAILURE_SYMBOL_NAME:  heap_corruption!heap_corruption

TARGET_TIME:  2017-01-09T23:32:17.000Z

OSBUILD:  15002

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

OSPLATFORM_TYPE:  x86

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  1988-03-22 17:05:36

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.15002.1001

ANALYSIS_SESSION_ELAPSED_TIME: 13b1

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:heap_corruption_80000003_heap_corruption!heap_corruption

FAILURE_ID_HASH:  {48f9f6fc-a298-839e-3fe0-9c2032d3fe58}

Followup:     MachineOwner
---------

Re: WinBox 3.7 crashes on Win10 15002

Posted: Thu Jan 12, 2017 1:18 pm
by acron
Same problem with versions 3.4 and 3.7 (I tried only these versions)

Re: WinBox 3.7 crashes on Win10 15002

Posted: Thu Jan 12, 2017 3:10 pm
by raffav
+1 Here too
on event viewer i get the error on user32.dll

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 13, 2017 4:23 pm
by Alessio Garavano
I have same problem... is the only app and write to support with some screen captures...

I am having problems to connect with Winbox to any device, this occur after install the last update of Windows 10 Inside Preview 15002 at 3 days ago and yesterday was update to a new windows release 15007, but the problem continue...

I tested winbox 3.7 and 3.8 in all compatibility modes, cleared the cache, etc etc and not working. Even with a new option Override high DPI scaling behavior in all modes.

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 13, 2017 9:59 pm
by Ahmed1222
I'm having the same problem. Anyone manged to solve this ?

Re: WinBox 3.7 crashes on Win10 15002

Posted: Sat Jan 14, 2017 9:39 pm
by patryknawrocki
same here with win10 1007, both on 3.7 and 3.8

Re: WinBox 3.7 crashes on Win10 15002

Posted: Mon Jan 16, 2017 10:48 pm
by x7007
Same, started to happened after I updated RouterOS to 6.38.1 and Winbox 3.9 still happens with 3.8 but with Win 10 1607 1493.693

Re: WinBox 3.7 crashes on Win10 15002

Posted: Tue Jan 17, 2017 1:58 am
by Alessio Garavano
I test the same... now i see the Winbox 3.9 was removed...

I sended a supout.rif to support, they tell the me the winbox crashes is logged in the router.

I hope fix quickly.

Regards!

Re: WinBox 3.7 crashes on Win10 15002

Posted: Tue Jan 17, 2017 2:25 pm
by Alessio Garavano
Hi guys, this is the reply from support after send the supout.rif of my main router...

"Hello Alessio,

Thank you very much for this file. We will try to inspect it and find some solution for this issue.

However it is still possible, that this is Windows issue not Winbox issue.

Best regards,
Martins S.
MikroTik.com"

Re: WinBox 3.7 crashes on Win10 15002

Posted: Tue Jan 17, 2017 5:24 pm
by ptr727
I bet it is a WinBox issue, the crash report says it is heap corruption, i.e. memory being accessed after it was freed.
Regardless, any ISV that ships product on Windows and does NOT test with Insider builds, is not a good ISV.

Re: WinBox 3.7 crashes on Win10 15002

Posted: Thu Jan 19, 2017 2:46 pm
by Multik
same problem... :(

Re: WinBox 3.7 crashes on Win10 15002

Posted: Thu Jan 19, 2017 9:10 pm
by Alessio Garavano
My solution...

VirtualBox... WinXP.... Winbox working! :D

Waiting new Windows release!

Regards!

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 20, 2017 2:24 am
by Alessio Garavano
DOWNLOADING NEW RELEASE Windows 10 Insider Preview 15014 (rs_prerelease)!!!

I hope fix that problem!

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 20, 2017 9:37 pm
by Alessio Garavano
NOT SOLVED!!! the f*cking crash continue... the rare is now the Whatsapp app for Windows is running fine, when in the 15002 and 15007 it has too many lags and crashes...
Now i think the real problem is WINBOX

Re: WinBox 3.7 crashes on Win10 15002

Posted: Thu Jan 26, 2017 11:46 am
by acron
New Winbox 3.10 works! Thanks, Mikrotik.
(My version of Windows is 15002)

Re: WinBox 3.7 crashes on Win10 15002

Posted: Thu Jan 26, 2017 7:46 pm
by Alessio Garavano
Yes, with windows release 15014 is working fine too!

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 27, 2017 10:13 am
by umatrix
15017 works too

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 27, 2017 10:22 am
by normis
so in the end, it was Windows bug after all? Because Winbox was not upgraded since the last reports above.

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 27, 2017 10:38 am
by andriys
so in the end, it was Windows bug after all? Because Winbox was not upgraded since the last reports above.
Nope, that was a WinBox problem, which was fixed in 3.10. CheckOut the ChangeLog that your colleague posted.

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 27, 2017 10:39 am
by normis
so in the end, it was Windows bug after all? Because Winbox was not upgraded since the last reports above.
Nope, that was a WinBox problem, which was fixed in 3.10. CheckOut the ChangeLog that your colleague posted.
Alessio above posted that still is not fixed, even after 3.10. Then he said it is fixed after new Windows release.

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 27, 2017 2:38 pm
by Alessio Garavano
so in the end, it was Windows bug after all? Because Winbox was not upgraded since the last reports above.
Nope, that was a WinBox problem, which was fixed in 3.10. CheckOut the ChangeLog that your colleague posted.
Alessio above posted that still is not fixed, even after 3.10. Then he said it is fixed after new Windows release.
Hi Normis, i say "Yes, with windows release 15014 is working fine too!" after the new winbox 3.10

The bug was in Winbox and was fixed in this last release 3.10

Regards

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 27, 2017 2:45 pm
by Alessio Garavano
15017 works too
Release 15017 is not available yet in Argentina

Re: WinBox 3.7 crashes on Win10 15002

Posted: Fri Jan 27, 2017 3:02 pm
by normis
OK!

Re: WinBox 3.7 crashes on Win10 15002

Posted: Sat Jan 28, 2017 12:50 pm
by PiGeonCZ
I can confirm that the Winbox 3.10 is working even with the latest 15019 build.
Winbox 3.9 didn't work on this build.

PiGeon
All times are UTC+02:00
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/