Winbox 3.8 released!

Fri Jan 13, 2017 11:45 am

What's new in v3.8:

*) support RouterOS v6.39;
*) fixed problem when table header was hidden if filters were activated;
*) after Log window was opened second time, updates were not displayed automatically;

If you experience version related issues, then please report them to support@mikrotik.com.

Winbox is available here:
http://www.mikrotik.com/download

If you try to upgrade directly from Winbox loader and version is not available, then you might need to wait for a while until cache in path between your device and our servers is refreshed.

Fri Jan 13, 2017 1:32 pm

maisonmdsgreen - In Winbox loader please try to do "Tools/Clear Cache". Does issue persist? I am running Winbox 3.8 on Windows 10 without any problems.

raffav · Fri Jan 13, 2017 1:37 pm

yeah
this is still not fixing 3.8 dont fixed the problem,
maybe is windows bug related,

i will try some workaround

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

*** wait with pending attach
Symbol search path is: srv*
Executable search path is: 
ModLoad: 00000000`00400000 00000000`0058b000   C:\Users\raffaello\Downloads\winbox(1).exe
ModLoad: 00007ff9`e3290000 00007ff9`e3472000   C:\WINDOWS\SYSTEM32\ntdll.dll
ModLoad: 00000000`777f0000 00000000`77976000   ntdll.dll
ModLoad: 00000000`6ffd0000 00000000`70021000   C:\WINDOWS\System32\wow64.dll
ModLoad: 00000000`70040000 00000000`700b3000   C:\WINDOWS\System32\wow64win.dll
ModLoad: 00000000`70030000 00000000`7003a000   C:\WINDOWS\System32\wow64cpu.dll
ModLoad: 00000000`775d0000 00000000`776a0000   KERNEL32.dll
ModLoad: 00000000`76850000 00000000`76a08000   KERNELBASE.dll
ModLoad: 00000000`76740000 00000000`767b7000   ADVAPI32.dll
ModLoad: 00000000`75d60000 00000000`75e1d000   msvcrt.dll
ModLoad: 00000000`76e90000 00000000`76ed1000   SECHOST.dll
ModLoad: 00000000`76600000 00000000`766bf000   RPCRT4.dll
ModLoad: 00000000`74320000 00000000`74340000   SspiCli.dll
ModLoad: 00000000`74310000 00000000`7431a000   CRYPTBASE.dll
ModLoad: 00000000`776a0000 00000000`776f5000   bcryptPrimitives.dll
ModLoad: 00000000`75b20000 00000000`75c0d000   COMDLG32.dll
ModLoad: 00000000`76a40000 00000000`76c60000   combase.dll
ModLoad: 00000000`743a0000 00000000`744b8000   ucrtbase.dll
ModLoad: 00000000`77400000 00000000`77486000   SHCORE.dll
ModLoad: 00000000`76ce0000 00000000`76e16000   USER32.dll
ModLoad: 00000000`775b0000 00000000`775c5000   win32u.dll
ModLoad: 00000000`767c0000 00000000`767e1000   GDI32.dll
ModLoad: 00000000`764a0000 00000000`765fa000   gdi32full.dll
ModLoad: 00000000`763f0000 00000000`76435000   SHLWAPI.dll
ModLoad: 00000000`74660000 00000000`759a9000   SHELL32.dll
ModLoad: 00000000`76e20000 00000000`76e54000   CFGMGR32.dll
ModLoad: 00000000`75e80000 00000000`763e9000   Windows.Storage.dll
ModLoad: 00000000`744c0000 00000000`744ce000   AppCore.dll
ModLoad: 00000000`75e30000 00000000`75e75000   POWRPROF.dll
ModLoad: 00000000`74390000 00000000`743a0000   profapi.dll
ModLoad: 00000000`77700000 00000000`777ef000   ole32.dll
ModLoad: 00000000`76c60000 00000000`76cc7000   WS2_32.dll
ModLoad: 00000000`50d10000 00000000`50d9e000   COMCTL32.dll
ModLoad: 00000000`72d00000 00000000`72d2f000   IPHLPAPI.DLL
ModLoad: 00000000`72500000 00000000`72774000   WININET.dll
ModLoad: 00000000`76a10000 00000000`76a35000   IMM32.dll
ModLoad: 00000000`50fb0000 00000000`510d1000   GbpInj.dll
ModLoad: 00000000`76ee0000 00000000`76f76000   OLEAUT32.dll
ModLoad: 00000000`766c0000 00000000`76738000   msvcp_win.dll
ModLoad: 00000000`742d0000 00000000`742f8000   NTMARTA.dll
ModLoad: 00000000`71ca0000 00000000`71d14000   UxTheme.dll
ModLoad: 00000000`75c10000 00000000`75d51000   MSCTF.dll
ModLoad: 00000000`71970000 00000000`71993000   dwmapi.dll
ModLoad: 00000000`72d80000 00000000`72f85000   COMCTL32.dll
ModLoad: 00000000`6ce70000 00000000`6cece000   TextInputFramework.dll
ModLoad: 00000000`579d0000 00000000`57bee000   CoreUIComponents.dll
ModLoad: 00000000`6c470000 00000000`6c4ff000   CoreMessaging.dll
ModLoad: 00000000`60860000 00000000`6092f000   WinTypes.dll
ModLoad: 00000000`73d00000 00000000`74226000   GBIEH.DLL
ModLoad: 00000000`731a0000 00000000`73cf3000   IEFRAME.dll
ModLoad: 00000000`742b0000 00000000`742c3000   NETAPI32.dll
ModLoad: 00000000`72f90000 00000000`73197000   iertutil.dll
ModLoad: 00000000`742a0000 00000000`742a8000   VERSION.dll
ModLoad: 00000000`74290000 00000000`7429b000   netutils.dll
ModLoad: 00000000`74280000 00000000`74290000   wkscli.dll
ModLoad: 00000000`74230000 00000000`74248000   bcrypt.dll
ModLoad: 00000000`76cd0000 00000000`76cd6000   PSAPI.DLL
ModLoad: 00000000`77490000 00000000`77513000   CLBCatQ.DLL
ModLoad: 00000000`62900000 00000000`6290d000   wbemprox.dll
ModLoad: 00000000`62910000 00000000`62977000   wbemcomn.dll
ModLoad: 00000000`628d0000 00000000`628e0000   WBEMSVC.dll
ModLoad: 00000000`62810000 00000000`628d0000   FastProx.dll
ModLoad: 00000000`6fe70000 00000000`6ffce000   PROPSYS.dll
ModLoad: 00000000`621f0000 00000000`621fd000   LINKINFO.dll
ModLoad: 00000000`722d0000 00000000`72362000   apphelp.dll
ModLoad: 00000000`624e0000 00000000`62604000   NetworkExplorer.dll
ModLoad: 00000000`6fd50000 00000000`6fd66000   MPR.dll 
ModLoad: 00000000`72260000 00000000`72269000   drprov.dll
ModLoad: 00000000`72d30000 00000000`72d73000   WINSTA.dll
ModLoad: 00000000`721e0000 00000000`721f2000   NTLANMAN.dll
ModLoad: 00000000`721c0000 00000000`721da000   davclnt.dll
ModLoad: 00000000`72250000 00000000`7225a000   DAVHLPR.dll
ModLoad: 00000000`03450000 00000000`0349e000   MSWSOCK.dll
ModLoad: 00000000`62c40000 00000000`62c47000   WSHTCPIP.dll
ModLoad: 00000000`62c30000 00000000`62c37000   WSHTCPIP.dll
ModLoad: 00000000`62c20000 00000000`62c27000   WSHIP6.dll
ModLoad: 00000000`6cb20000 00000000`6cc8f000   WindowsCodecs.dll
ModLoad: 00000000`6ca00000 00000000`6ca43000   DataExchange.dll
ModLoad: 00000000`68560000 00000000`6879c000   d3d11.dll
ModLoad: 00000000`687a0000 00000000`68887000   dcomp.dll
ModLoad: 00000000`6c950000 00000000`6c9d6000   dxgi.dll
ModLoad: 00000000`679e0000 00000000`67b0a000   twinapi.appcore.dll
(27f0.3358): Unknown exception - code c000041d (!!! second chance !!!)
wow64!Wow64NotifyDebugger+0x1d:
00000000`6ffdccd9 65488b042530000000 mov   rax,qword ptr gs:[30h] gs:00000000`00000030=????????????????
0:000> .sympath cache*c:\sym;srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: cache*c:\sym;srv*https://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: cache*c:\sym;srv*https://msdl.microsoft.com/download/symbols

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       cache*c:\sym
Deferred                                       srv*https://msdl.microsoft.com/download/symbols
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for USER32.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Users\raffaello\Downloads\winbox(1).exe - 
*** ERROR: Module load completed but symbols could not be loaded for GbpInj.dll

DUMP_CLASS: 2

DUMP_QUALIFIER: 0

FAULTING_IP: 
USER32!DefFrameProcW+81
00000000`76d42ae1 8b7808          mov     edi,dword ptr [rax+8]

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000076d42ae1 (USER32!DefFrameProcW+0x0000000000000081)
   ExceptionCode: c000041d
  ExceptionFlags: 00000001
NumberParameters: 0

FAULTING_THREAD:  00003358

DEFAULT_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

PROCESS_NAME:  winbox(1).exe

ERROR_CODE: (NTSTATUS) 0xc000041d - An unhandled exception was encountered during a user callback.

EXCEPTION_CODE: (NTSTATUS) 0xc000041d - An unhandled exception was encountered during a user callback.

EXCEPTION_CODE_STR:  c000041d

WATSON_BKT_PROCSTAMP:  382f3815

WATSON_BKT_MODULE:  USER32.dll

WATSON_BKT_MODSTAMP:  7d5c570a

WATSON_BKT_MODOFFSET:  62ae1

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:  0f046f45b2e3884083c911f4e23f4459313b3909

MODLIST_SHA1_HASH:  7814add188d48f2dc44b94e2fae09d764aedfa2d

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

CHKIMG_EXTENSION: !chkimg -lo 50 -d !ntdll
    7ff9e3291010-7ff9e3291018  9 bytes - ntdll!RtlReportException
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32910a8-7ff9e32910b0  9 bytes - ntdll!WerpBreakIntoDebuggerIfPresent (+0x98)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32910e4-7ff9e32910ec  9 bytes - ntdll!WerpIsDebugPortPresent (+0x3c)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3291134-7ff9e329113c  9 bytes - ntdll!RtlReportExceptionHelper (+0x50)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3291590-7ff9e3291598  9 bytes - ntdll!WerpGetProcessSnapshot (+0x45c)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3291640-7ff9e3291648  9 bytes - ntdll!PssNtDuplicateSnapshot (+0xb0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32916c4-7ff9e32916cc  9 bytes - ntdll!PsspDuplicateSnapshotLocalToRemote (+0x84)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3291a70-7ff9e3291a78  9 bytes - ntdll!PsspDuplicateSnapshotRemoteToRemote (+0x3ac)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3291f44-7ff9e3291f4c  9 bytes - ntdll!PsspCaptureHandleInformation (+0x4d4)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32921a0-7ff9e32921a8  9 bytes - ntdll!PssNtCaptureSnapshot (+0x25c)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3292668-7ff9e3292670  9 bytes - ntdll!PsspSampleCounters (+0x4c8)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32926d8-7ff9e32926e0  9 bytes - ntdll!PsspCaptureThreadInformation (+0x70)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32929f0-7ff9e32929f8  9 bytes - ntdll!PsspDumpThread (+0x318)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3292bf0-7ff9e3292bf8  9 bytes - ntdll!PsspWalkHandleTable (+0x200)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3292ea0-7ff9e3292ea8  9 bytes - ntdll!PsspHandleDumper (+0x2b0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293170-7ff9e3293178  9 bytes - ntdll!PsspCaptureVaSpaceInformation (+0x2d0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293778-7ff9e3293780  9 bytes - ntdll!PsspCaptureImageInformation (+0x608)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293880-7ff9e3293888  9 bytes - ntdll!PsspDumpObject_Event (+0x108)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32938c0-7ff9e32938c8  9 bytes - ntdll!PsspDumpObject_Section (+0x40)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293930-7ff9e3293938  9 bytes - ntdll!PsspDumpObject_Thread (+0x70)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32939c0-7ff9e32939c8  9 bytes - ntdll!PsspDumpObject_Semaphore (+0x90)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293a00-7ff9e3293a08  9 bytes - ntdll!PsspDumpObject_Mutant (+0x40)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293a88-7ff9e3293a90  9 bytes - ntdll!PsspCaptureAuxiliaryPages (+0x88)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293d00-7ff9e3293d08  9 bytes - ntdll!PsspCaptureProcessInformation (+0x278)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293eb0-7ff9e3293eb8  9 bytes - ntdll!PsspCaptureHandleTrace (+0x1b0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3293f70-7ff9e3293f78  9 bytes - ntdll!PssNtQuerySnapshot (+0xc0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294020-7ff9e3294028  9 bytes - ntdll!PssNtFreeSnapshot (+0xb0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294190-7ff9e3294198  9 bytes - ntdll!PssNtValidateDescriptor (+0x170)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294240-7ff9e3294248  9 bytes - ntdll!PsspDumpObject_Process (+0xb0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294280-7ff9e3294288  9 bytes - ntdll!PsspFreeLinkedHandleList (+0x40)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32943c4-7ff9e32943cc  9 bytes - ntdll!WerpWaitForCrashReporting (+0x144)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294498-7ff9e32944a0  9 bytes - ntdll!ReportExceptionInternal (+0xd4)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32945cc-7ff9e32945d4  9 bytes - ntdll!SendMessageToWERService (+0x134)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32947cc-7ff9e32947d4  9 bytes - ntdll!WerpFreeSid (+0x200)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294814-7ff9e329481c  9 bytes - ntdll!WerpAllocateAndInitializeSid (+0x48)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32948fc-7ff9e3294904  9 bytes - ntdll!WaitForWerSvc (+0xe8)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32949a8-7ff9e32949b0  9 bytes - ntdll!SignalStartWerSvc (+0xac)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294a60-7ff9e3294a68  9 bytes - ntdll!WerpThreadId (+0xb8)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294a9c-7ff9e3294aa4  9 bytes - ntdll!WerpCreateCrashDataSection (+0x3c)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294bfc-7ff9e3294c04  9 bytes - ntdll!WerpCreateCompletionEvent (+0x160)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294c7c-7ff9e3294c84  9 bytes - ntdll!WerpSetProcessFaultInformation (+0x80)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294cc4-7ff9e3294ccc  9 bytes - ntdll!WerpIsProcessNative (+0x48)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294d10-7ff9e3294d18  9 bytes - ntdll!RtlGetAppContainerParent (+0x4c)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294de0-7ff9e3294de8  9 bytes - ntdll!RtlIsNormalizedString (+0xd0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294e70-7ff9e3294e78  9 bytes - ntdll!Normalization__IsNormalized (+0x90)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294f18-7ff9e3294f20  9 bytes - ntdll!RtlpTpETWCallbackStart (+0xa8)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3294f98-7ff9e3294fa0  9 bytes - ntdll!RtlpTpETWCallbackStop (+0x80)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e3295020-7ff9e3295028  9 bytes - ntdll!RtlLargeIntegerToChar (+0x88)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e32950fc-7ff9e3295104  9 bytes - ntdll!RtlpTpETWCallbackEnqueue (+0xdc)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e329517c-7ff9e3295184  9 bytes - ntdll!TppETWCallbackDequeue (+0x80)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
    7ff9e33a6010-7ff9e33a6018  9 bytes - ntdll!RtlAllocateMemoryBlockLookaside
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e33a6100-7ff9e33a6108  9 bytes - ntdll!RtlAllocateMemoryZone (+0xf0)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
    7ff9e33a6170-7ff9e33a6178  9 bytes - ntdll!RtlFreeMemoryBlockLookaside (+0x70)
	[ 66 90 0f 1f 80 00 00 00:48 8b 04 24 64 48 89 04 ]
8219 errors : !ntdll (7ff9e3291010-7ff9e33a6178)

PRODUCT_TYPE:  1

SUITE_MASK:  272

ANALYSIS_SESSION_HOST:  PC-50

ANALYSIS_SESSION_TIME:  01-13-2017 09:24:16.0233

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from 000000006ffdc234 to 000000006ffdccd9

THREAD_ATTRIBUTES: 
THREAD_SHA1_HASH_MOD_FUNC:  80a6ba8ae322bdf0ed6878bf116a143cf28e1800

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5ee532fe121f75fd0c73707e23bfaef06f0e234c

ADDITIONAL_DEBUG_TEXT:  Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

OS_LOCALE:  PTB

PROBLEM_CLASSES: 



MEMORY_CORRUPTION
    Tid    [0x3358]
    Failure Bucketing



LARGE
    Tid    [0x3358]
    Failure Bucketing


BUGCHECK_STR:  MEMORY_CORRUPTION_LARGE

STACK_TEXT:  
00000000`00000000 00000000`00000000 memory_corruption!ntdll+0x0


STACK_COMMAND:  .ecxr ; kb ; dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ** Pseudo Context ** ; kb

THREAD_SHA1_HASH_MOD:  7da7fbec386ce361a40d03d69a994bc4836f03e8

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  memory_corruption!ntdll

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_memory_corruption!ntdll

PRIMARY_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE_memory_corruption!ntdll

FAILURE_EXCEPTION_CODE:  c000041d

IMAGE_NAME:  memory_corruption

FAILURE_IMAGE_NAME:  memory_corruption

BUCKET_ID_IMAGE_STR:  memory_corruption

FAILURE_MODULE_NAME:  memory_corruption

BUCKET_ID_MODULE_STR:  memory_corruption

FAILURE_FUNCTION_NAME:  ntdll

BUCKET_ID_FUNCTION_STR:  ntdll

BUCKET_ID_OFFSET:  0

BUCKET_ID_MODTIMEDATESTAMP:  0

BUCKET_ID_MODCHECKSUM:  0

BUCKET_ID_MODVER_STR:  0.0.0.0

BUCKET_ID_PREFIX_STR:  

FAILURE_PROBLEM_CLASS:  MEMORY_CORRUPTION_LARGE

FAILURE_SYMBOL_NAME:  memory_corruption!ntdll

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_c000041d_memory_corruption!ntdll

TARGET_TIME:  2017-01-13T11:24:39.000Z

OSBUILD:  15002

OSSERVICEPACK:  1001

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

USER_LCID:  0

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

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.15002.1001

ANALYSIS_SESSION_ELAPSED_TIME: 5936

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:memory_corruption_large_c000041d_memory_corruption!ntdll

FAILURE_ID_HASH:  {efbbe75e-0ad6-12bb-31c1-28e31d3149a8}

Followup:     MachineOwner

raffav · Fri Jan 13, 2017 1:39 pm

maisonmdsgreen - In Winbox loader please try to do "Tools/Clear Cache". Does issue persist? I am running Winbox 3.8 on Windows 10 without any problems.

@strods
need to be on windows 10 insider fast ring on build 15002.1001

For everyone having this problem
Windows 10 Insider Preview 15007 (rs_prerelease) is available for download let see if this fix the problem

radpi · Fri Jan 13, 2017 2:27 pm

maisonmdsgreen - In Winbox loader please try to do "Tools/Clear Cache". Does issue persist? I am running Winbox 3.8 on Windows 10 without any problems.
@strods
need to be on windows 10 insider fast ring on build 15002.1001

For everyone having this problem
Windows 10 Insider Preview 15007 (rs_prerelease) is available for download let see if this fix the problem

with 15007 same problem winbox is crashing down.

raffav · Fri Jan 13, 2017 2:30 pm

maisonmdsgreen - In Winbox loader please try to do "Tools/Clear Cache". Does issue persist? I am running Winbox 3.8 on Windows 10 without any problems.
@strods
need to be on windows 10 insider fast ring on build 15002.1001

For everyone having this problem
Windows 10 Insider Preview 15007 (rs_prerelease) is available for download let see if this fix the problem
with 15007 same problem winbox is crashing down.

sh**t
that is very annoying

amokkatmt · Fri Jan 13, 2017 3:20 pm

Winbox 3.8, RB750GL 6.39rc12 - can not change/set firewall NAT rule's dst-port, src-port by winbox. Fields are grayed out/disabled whatever I do. On existing NAT rules and new ones as well. Already reported to support@mikrotik.com

Fri Jan 13, 2017 3:22 pm

Winbox 3.8, RB750GL 6.39rc12 - can not change/set firewall NAT rule's dst-port, src-port by winbox. Fields are grayed out/disabled whatever I do. On existing NAT rules and new ones as well. Already reported to support@mikrotik.com

did you specified a protocol??

I upgraded Winbox on 3 Win10 Home (up to date with patches) all working without any issues.

amokkatmt · Fri Jan 13, 2017 3:29 pm

Winbox 3.8, RB750GL 6.39rc12 - can not change/set firewall NAT rule's dst-port, src-port by winbox. Fields are grayed out/disabled whatever I do. On existing NAT rules and new ones as well. Already reported to support@mikrotik.com
did you specified a protocol??

I upgraded Winbox on 3 Win10 Home (up to date with patches) all working without any issues.

Yes, tried protocol, src/dst addresses, interfaces, anything - grayed out, on existing and new.

Copied 3.8 .exe to another machine (so I have windows 7 and win2008r2) - same thing.

Hmm. Tried Winbox 2.2.18 on win2008r2 on that RB with 6.39rc12 - same behavior, fields disabled.

Added new rule in console with "/ip firewall nat add dst-port=9999 in-interface=ether2 chain=dst-nat protocol=tcp action=log" succesfully, but when opened rule with winbox - fields are set but disabled.

So that's not winbox issue, but 6.39rc12. My fail was upgrading both same time because of "winbox - minimal required version is v3.8 (because of new quickset);" in changelog.

Phaere · Fri Jan 13, 2017 4:04 pm

Winbox 3.8, RB750GL 6.39rc12 - can not change/set firewall NAT rule's dst-port, src-port by winbox. Fields are grayed out/disabled whatever I do. On existing NAT rules and new ones as well. Already reported to support@mikrotik.com
did you specified a protocol??

I upgraded Winbox on 3 Win10 Home (up to date with patches) all working without any issues.
Yes, tried protocol, src/dst addresses, interfaces, anything - grayed out, on existing and new.

Copied 3.8 .exe to another machine (so I have windows 7 and win2008r2) - same thing.

Hmm. Tried Winbox 2.2.18 on win2008r2 on that RB with 6.39rc12 - same behavior, fields disabled.

Added new rule in console with "/ip firewall nat add dst-port=9999 in-interface=ether2 chain=dst-nat protocol=tcp action=log" succesfully, but when opened rule with winbox - fields are set but disabled.

So that's not winbox issue, but 6.39rc12. My fail was upgrading both same time because of "winbox - minimal required version is v3.8 (because of new quickset);" in changelog.

This is totally winbox issue. Same behavoir on winbox 3.7 and ROS 6.36.3 - fields with src\dst port are grayed out.
With winbox 3.7 - all fine;

pietroscherer · Fri Jan 13, 2017 4:10 pm

Winbox 3.8, RB750GL 6.39rc12 - can not change/set firewall NAT rule's dst-port, src-port by winbox. Fields are grayed out/disabled whatever I do. On existing NAT rules and new ones as well. Already reported to support@mikrotik.com
did you specified a protocol??

I upgraded Winbox on 3 Win10 Home (up to date with patches) all working without any issues.
Yes, tried protocol, src/dst addresses, interfaces, anything - grayed out, on existing and new.

Copied 3.8 .exe to another machine (so I have windows 7 and win2008r2) - same thing.

Hmm. Tried Winbox 2.2.18 on win2008r2 on that RB with 6.39rc12 - same behavior, fields disabled.

Added new rule in console with "/ip firewall nat add dst-port=9999 in-interface=ether2 chain=dst-nat protocol=tcp action=log" succesfully, but when opened rule with winbox - fields are set but disabled.

So that's not winbox issue, but 6.39rc12. My fail was upgrading both same time because of "winbox - minimal required version is v3.8 (because of new quickset);" in changelog.

Same issue here, running MS Windows 7, x64. Tested Winbox 3.8 on rOS 6.29.1 and the same problem. Using Winbox 3.7 on 6.29.1, works perfectly. It seems to be something in Winbox.

mpreissner · Fri Jan 13, 2017 7:13 pm

Mac version doesn't appear to be available yet. Started Winbox 3.7 on my Mac, hit Check for Updates, came back No new updates available.

the9quad · Sat Jan 14, 2017 2:16 am

Winbox 3.8, RB750GL 6.39rc12 - can not change/set firewall NAT rule's dst-port, src-port by winbox. Fields are grayed out/disabled whatever I do. On existing NAT rules and new ones as well. Already reported to support@mikrotik.com
did you specified a protocol??

I upgraded Winbox on 3 Win10 Home (up to date with patches) all working without any issues.
Yes, tried protocol, src/dst addresses, interfaces, anything - grayed out, on existing and new.

Copied 3.8 .exe to another machine (so I have windows 7 and win2008r2) - same thing.

Hmm. Tried Winbox 2.2.18 on win2008r2 on that RB with 6.39rc12 - same behavior, fields disabled.

Added new rule in console with "/ip firewall nat add dst-port=9999 in-interface=ether2 chain=dst-nat protocol=tcp action=log" succesfully, but when opened rule with winbox - fields are set but disabled.

So that's not winbox issue, but 6.39rc12. My fail was upgrading both same time because of "winbox - minimal required version is v3.8 (because of new quickset);" in changelog.

Same issue, winbox 3.8 ROS and ROS 6.38 cant change port in NAT. Was working in 6.3.7
Windows 10, hEX r3

shahbazian · Sat Jan 14, 2017 2:27 pm

Wireless snooper don't indented in winbox v3.0+

I previously shared this with Uldis in Dubai MUM.
So, I was waiting to be correct in version 3.8

Sent from my SM-G928C using Tapatalk

w0lt · Sat Jan 14, 2017 4:51 pm

I've been using "Crossover" for MacOS for quite a few years. This is a paid (supported) variation of "Wine". While version 3.8 of WinBox seems to run just fine, it doesn't seem to exit as gracefully as 3.7 as it leaves a Winbox session hanging in the menu bar. Exiting or quitting the app, same results. So something has changed in the way the Winbox closes that leaves it hanging in Crossover. The only way to remove the hanging Winbox sessions is to completely close Crossover. Can someone please take a look at it?

Thanks,

-tp

w0lt · Sat Jan 14, 2017 7:48 pm

Also from the CAPSMAN Access-List menu, disable doesn't seem to work. Please confirm.

Thanks,

-tp

Bigfoot · Sat Jan 14, 2017 8:12 pm

Also from the Web Proxy Access List menu, disable & enable buttons doesn't work. Please confirm.
Thanks,
Bigfoot

w0lt · Sat Jan 14, 2017 8:56 pm

Also from the Web Proxy Access List menu, disable & enable buttons doesn't work. Please confirm.
Thanks,
Bigfoot

Confirmed, doesn't work for me either.

-tp

ErfanDL · Sat Jan 14, 2017 9:20 pm

hAP Lite some times crashing when login to router

buzzdee · Sat Jan 14, 2017 11:09 pm

I'm a little puzzled...changelog for 6.39rc12 states

ike2 - include identity in peer address info

so does this mean it's just displayed somewhere or that we now can set a "peer ID", like we are already able to set "My ID" in the Advanced-Tab of peer configuration? A little more details on this changelog line would be nice. If it's already written somewhere, I gladly take hints to the source so I can RTFM myself

websun · Sun Jan 15, 2017 2:59 am

Messy layout on windows classic theme ( https://s24.postimg.org/pf9wqfapx/winboxerror.png )
Crap misspelling in pci device (if you go to system > resources > pci and then click on any device you will see catagory instead of category)
Crashes on disconnect for windows 8.1

Loads of issues with HAP lite (cannot disable services for one) too many to even bother.

troykelly · Sun Jan 15, 2017 8:05 am

While version 3.8 of WinBox seems to run just fine, it doesn't seem to exit as gracefully as 3.7 as it leaves a Winbox session hanging in the menu bar. Exiting or quitting the app, same results.

This seems to be occurring for Winbox 3.8 under any Wine instance (not just commercial versions)

vitaly2016 · Sun Jan 15, 2017 10:54 am

Also from the CAPSMAN Access-List menu, disable doesn't seem to work. Please confirm.

Yes, I confirm this bug of 3.8 at RB3011:
CAPsMAN -> Access List
Two buttons at header panel for quick enabling/disabling access entry do not work. Nothing happens clicking at them.
Of course, I still can change enabling some entry opening it and using inner button disable/enable.

There is no bug at Winbox 3.7

alfonzz · Sun Jan 15, 2017 1:05 pm

BUG in new winbox: not working enable/disable in ip-services and system-LEDs (maybe somewhere else)

gilester · Sun Jan 15, 2017 1:50 pm

I confirm that Winbox 3.8 is unreliable (and unusable!) when it comes to adjusting Sce or Dst ports in both NAT rules and Firewall rules.

Another: Unable to disable IP Neighbor Discovery in Winbox 3.8.

All of this works fine in Winbox 3.7.

Using RB2011 with RouterOS 6.37.3.

Thanks
Giles.

Abdock · Sun Jan 15, 2017 6:44 pm

Hello,

There is problem with disabling routing/ bgp, i cannot disable the peers with 3.8

Thanks,

baragoon · Sun Jan 15, 2017 7:19 pm

Winbox 3.8 is totally lol release. Waiting to 3.8.1 or so.

Отправлено с моего iPhone используя Tapatalk

WalidMorsi · Sun Jan 15, 2017 7:42 pm

+1

maisonmdsgreen - In Winbox loader please try to do "Tools/Clear Cache". Does issue persist? I am running Winbox 3.8 on Windows 10 without any problems.
@strods
need to be on windows 10 insider fast ring on build 15002.1001

For everyone having this problem
Windows 10 Insider Preview 15007 (rs_prerelease) is available for download let see if this fix the problem
with 15007 same problem winbox is crashing down.
sh**t
that is very annoying

HeadCraft · Mon Jan 16, 2017 12:37 am

Have anyone faced with bridge flood in wireless and vlan interfaces when traffic have to go to ethernet interface with this 6.38 version?
P.S.: Sorry for wrong topic, noticed to late..

macsrwe · Mon Jan 16, 2017 4:52 am

In 3.8, the "disable" (X) button in system schedule does nothing. Writearound: If one double-clicks the desired schedule, the "Disable" box works.

infused · Mon Jan 16, 2017 5:54 am

Do the function keys work now? disable/enable/comment etc? seriously not upgrading until those are there.

ErfanDL · Mon Jan 16, 2017 10:12 am

Can not disable and enable hotspot servers

lukaszkubat · Mon Jan 16, 2017 11:37 am

HI - in winbox 3.8 I am unable to set ports in firewall rules (the src port dst port and any port) are greyed out.
In winbox 3.7 it works (the fields are editable).

I have routers and APS all on ROS v6.38

regards
Lukasz

LaRP · Mon Jan 16, 2017 1:40 pm

HI - in winbox 3.8 I am unable to set ports in firewall rules (the src port dst port and any port) are greyed out.
In winbox 3.7 it works (the fields are editable).

Me too

Chupaka · Mon Jan 16, 2017 2:35 pm

I like friday releases

Friday, 13th...

raffav · Mon Jan 16, 2017 2:37 pm

For the nat problem I found a workaround
If something related to the (protocol number)

The problem
Just type the protocol and the port field is enabled again

The solution

Enviado de meu XT1580 usando Tapatalk

expert · Mon Jan 16, 2017 2:52 pm

I like friday releases

Friday, 13th...

But today is Monday and broken Winbox 3.8 is still on download site...

raffav · Mon Jan 16, 2017 2:57 pm

I like friday releases

Friday, 13th...
But today is Monday and broken Winbox 3.8 is still on download site...

it was a joke man !

Tambakti · Mon Jan 16, 2017 4:06 pm

I can't use the disable button and the enable button using Winbox 3.8

Chupaka · Mon Jan 16, 2017 4:13 pm

But today is Monday and broken Winbox 3.8 is still on download site...

the only reason to worry for me is the absence of official answer from MT...

Mon Jan 16, 2017 4:15 pm

3.9 coming soon

raffav · Mon Jan 16, 2017 4:36 pm

3.9 coming soon

maybe fix the windows insider preview bug ?

Mon Jan 16, 2017 4:38 pm

why are so many of you using this windows insider preview

?

raffav · Mon Jan 16, 2017 4:44 pm

why are so many of you using this windows insider preview ?

i like to live on risk and test new features, and fix bugs and find new on

Windows 10 is getting better thanks to the program, and thanks the insider that report bugs and suggestion to it

Chupaka · Mon Jan 16, 2017 4:57 pm

why are so many of you using this windows insider preview ?

you mean, "why are so many of you using RouterOS Release Candidate?" ? xD

Mon Jan 16, 2017 5:05 pm

Winbox 3.9 has been released:
http://forum.mikrotik.com/viewtopic.php?f=21&t=116947

Who is online