Assertion Failed Error #4703

issue rifaterdemsahin opened this issue on August 15, 2014
  1. rifaterdemsahin commented at 11:02 AM on August 15, 2014: none

    I get the assertion failed error.

    Steps

    Install brand new Windows Server 2012 machine. I installed Bitcoin Qt I loaded my wallet.dat It ran ok for 8 hours.

    Thank you for all your efforts.

    Good work keep up

  2. sipa commented at 11:07 AM on August 15, 2014: member

    which assertion error?

  3. rifaterdemsahin commented at 1:23 PM on August 15, 2014: none

    I got the memory dump.

    I think this is the relevant part. ( the part that got hang )

    72 0f85c3080000 jne bitcoin_qt+0xa34c3b (0000000000e34c3b) 0000000000e34378 488b542438 mov rdx,qword ptr [rsp+38h] 0000000000e3437d c68424f100000000 mov byte ptr [rsp+0F1h],0 0000000000e34385 807a7c00 cmp byte ptr [rdx+7Ch],0 0000000000e34389 0f854d010000 jne bitcoin_qt+0xa344dc (0000000000e344dc) 0000000000e3438f 0fb68424f0000000 movzx eax,byte ptr [rsp+0F0h] 0000000000e34397 f644245404 test byte ptr [rsp+54h],4 0000000000e3439c 888424f1000000 mov byte ptr [rsp+0F1h],al 0000000000e343a3 0f8433010000 je bitcoin_qt+0xa344dc (0000000000e344dc) 0000000000e343a9 488b82c8000000 mov rax,qword ptr [rdx+0C8h] 00000000`00e343b0 8b5008 mov edx,dword ptr [rax+8]

  4. laanwj commented at 1:49 PM on August 15, 2014: member
    • What is the assertion message itself?
    • What version of bitcoin-qt are you using?
    • What's at the end of debug.log in your data directory?
    • Does it keep happening every restart or was it a one-time thing?
  5. rifaterdemsahin commented at 2:37 PM on August 15, 2014: none

    What is the assertion message itself?

    bitcoind only write "Assertion Failed!"

    What version of bitcoin-qt are you using?

    Latest one (bitcoin-0.9.2.1-win64-setup)

    What's at the end of debug.log in your data directory?

    here it is 2014-08-15 07:48:01 ProcessBlock: ACCEPTED 2014-08-15 07:48:09 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:48:09 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:48:09 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:48:09 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:48:09 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:48:09 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:48:09 ERROR: AcceptToMemoryPool : nonstandard transaction: scriptsig-non-canonical-push 2014-08-15 07:48:21 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:54:12 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:54:42 UpdateTip: new best=00000000000000000xxxxxxxxxxxxxxxxxxxxxce height=315711 log2_work=80.198269 tx=44596887 date=2014-08-15 07:51:39 progress=0.999994 2014-08-15 07:54:42 ProcessBlock: ACCEPTED 2014-08-15 07:58:26 ResendWalletTransactions() 2014-08-15 07:59:23 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:59:25 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:59:26 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:59:26 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:59:30 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:59:36 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:59:36 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:59:36 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 07:59:41 UpdateTip: new best=000000000000000009d0xxxxxxxxxxxxxxx4a87 height=315712 log2_work=80.198357 tx=44597100 date=2014-08-15 07:59:15 progress=0.999999 2014-08-15 07:59:41 ProcessBlock: ACCEPTED 2014-08-15 08:00:45 ERROR: AcceptToMemoryPool : nonstandard transaction: dust 2014-08-15 08:07:18 ResendWalletTransactions() 2014-08-15 08:13:01

    Does it keep happening every restart or was it a one-time thing?

    Yes this is the 4 th time failing. I tried it in brand new installed windows machines with clean block-chain downloads.

    > > > > > > > > Also Dump Analysis <<<<<<<<<<<<<<<<<<< > > > > > > > > FAULTING_THREAD: 0000000000000d18

    DEFAULT_BUCKET_ID: STATUS_BREAKPOINT

    PROCESS_NAME: bitcoin-qt.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

    APP: bitcoin-qt.exe

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    PRIMARY_PROBLEM_CLASS: STATUS_BREAKPOINT

    BUGCHECK_STR: APPLICATION_FAULT_STATUS_BREAKPOINT

    LAST_CONTROL_TRANSFER: from 00007ffb470013ad to 00007ffb4992b13a

    STACK_TEXT:
    000000000023bde8 00007ffb470013ad : 0000000000000113 0000000000000002 0000000000000001 0000000000000102 : ntdll!NtWaitForMultipleObjects+0xa 000000000023bdf0 00007ffb4788336f : 0000000000000006 00007ff5ffff6000 0000000000000000 0000000000000001 : KERNELBASE!WaitForMultipleObjectsEx+0xe1 000000000023c0d0 0000000000e34475 : 0000000000000024 0000000000000002 0000000000000000 0000000000000000 : user32!MsgWaitForMultipleObjectsEx+0x13f 000000000023c180 00000000006ba898 : 0000000001f70980 0000000000000024 000000000023f710 0000000000000001 : bitcoin_qt+0xa34475 000000000023f5c0 0000000000e409ad : 000000000023fa80 0000000000000014 00000000016ca010 00000000016f375e : bitcoin_qt+0x2ba898 000000000023f690 0000000000d015f1 : 000000000023f8c0 0000000000000000 0000000000b3d7f0 000000000023fa80 : bitcoin_qt+0xa409ad 000000000023f7e0 00000000016cb7cb : 0000000000000002 0000000001f71200 0000000000000003 0000000000000000 : bitcoin_qt+0x9015f1 000000000023f8e0 00000000004013ce : 0000000000000001 00000000020d1660 0000000000000000 0000000000000000 : bitcoin_qt+0x12cb7cb 000000000023fe70 00000000004014c8 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : bitcoin_qt+0x13ce 000000000023ff30 00007ffb472216ad : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : bitcoin_qt+0x14c8 000000000023ff60 00007ffb49904629 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0xd 000000000023ff90 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x1d

    STACK_COMMAND: ~0s; .ecxr ; kb

    FOLLOWUP_IP: bitcoin_qt+a34475 00000000`00e34475 488b8c24d8000000 mov rcx,qword ptr [rsp+0D8h]

    SYMBOL_STACK_INDEX: 3

    SYMBOL_NAME: bitcoin_qt+a34475

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: bitcoin_qt

    IMAGE_NAME: bitcoin-qt.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 51a93980

    FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_bitcoin-qt.exe!Unknown

    BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_bitcoin_qt+a34475

    ANALYSIS_SOURCE: UM

    FAILURE_ID_HASH_STRING: um:status_breakpoint_80000003_bitcoin-qt.exe!unknown

    FAILURE_ID_HASH: {b82eeeaa-0ef8-36be-b31c-e9e88544a173}

    Followup: MachineOwner

  6. MaDeRkAn commented at 2:56 PM on August 15, 2014: none

    I have also faced with this error.

  7. mohamedfarrag commented at 2:57 PM on August 15, 2014: none

    +1

  8. laanwj commented at 5:16 PM on August 15, 2014: member

    I've run that stack trace through addr2line:

    Address Function Line
    0xa34475 QEventDispatcherWin32::processEvents(QFlagsQEventLoop::ProcessEventsFlag) qabstracteventdispatcher.cpp:?
    0x2ba898 QWindowsGuiEventDispatcher::processEvents(QFlagsQEventLoop::ProcessEventsFlag) qwindowsguieventdispatcher.cpp:?
    0xa409ad QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)> qlibrary.cpp:?
    0x9015f1 QCoreApplication::exec() qobject.cpp:?
    0x12cb7cb main https://github.com/bitcoin/bitcoin/blob/v0.9.2.1/src/qt/bitcoin.cpp#L603

    It appears that it happens deep inside the windows kernel, invoked by the Qt library, after requestShutdown. However I see nothing about a requested shutdown in your debug log. I suppose this happens after closing the client window?

    BTW this error code is extremely strange. Or is this because you're running it in a debugger?

    ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

    There's nothing further here that can help me debug this issue, sorry.

  9. rifaterdemsahin commented at 10:23 AM on August 18, 2014: none

    BTW this error code is extremely strange. Or is this because you're running it in a debugger?

    I opened the memory dump in Visual Studio and tried to set a breakpoint.

    It appears that it happens deep inside the windows kernel, invoked by the Qt library, after requestShutdown. However I see nothing about a requested shutdown in your debug log. I suppose this happens after closing the client window?

    That is my main problem.

    when I look at the log I constantly get these errors: A.ERROR: AcceptToMemoryPool : inputs already spent B.ERROR: CheckTransaction() : vin empty C.ERROR: AcceptToMemoryPool: : CheckTransaction failed

  10. laanwj commented at 10:38 AM on August 18, 2014: member

    That logging is normal. That's just people sending you invalid transactions, happens all the time.

  11. rifaterdemsahin commented at 10:55 AM on August 18, 2014: none

    sorry panicked and opened a new issue.

    What could I do now ? The core gets shutdown every 4 hours. I installed a brand new windows 2012 server. Still shutdown happens. There is no software on that machine other than bitcoin-qt. Is there a verbose debugging feature that I could understand the error better ?

    When I ran CMD > netstat -an I see that 8332 and 8333 is running but rpc server is not responding. listening but rpc not responding

    PS: RPC server goes down between two and four hours.

  12. MaDeRkAn commented at 11:49 AM on August 18, 2014: none

    Any update on this issue ?

  13. rifaterdemsahin commented at 12:21 PM on August 18, 2014: none

    Normal state of the bitcoin qt on my server normal state

    Memory profile on the working state

    WaitForMultipleObjects,75.832578,75.832578,71.149441,71.149441,KERNEL32,[unknown],0 GetQueuedCompletionStatus,15.987317,15.987317,15.000000,15.000000,KERNELBASE,[unknown],0 NtWaitForSingleObject,9.433113,9.433113,8.850559,8.850559,ntdll,[unknown],0 WaitForSingleObjectEx,5.329106,5.329106,5.000000,5.000000,KERNELBASE,[unknown],0 Tcpip4_WSHStringToAddress,0.000000,5.329106,0.000000,5.000000,MSWSOCK,[unknown],0 [00000000004610B7],0.000000,4.104007,0.000000,3.850559,bitcoind,,0 WSARecv,0.000000,5.329106,0.000000,5.000000,WS2_32,[unknown],0 Tcpip6_WSHAddressToString,0.000000,4.104007,0.000000,3.850559,MSWSOCK,[unknown],0 Tcpip4_WSHOpenSocket2,0.000000,5.329106,0.000000,5.000000,MSWSOCK,[unknown],0 [00000000008BD64F],0.000000,5.329106,0.000000,5.000000,bitcoind,,0 select,0.000000,4.104007,0.000000,3.850559,WS2_32,[unknown],0 [00000000005F374F],0.000000,75.832578,0.000000,71.149441,bitcoind,,0 [00000000008C21AC],0.000000,15.987317,0.000000,15.000000,bitcoind,,0 [00000000008BD280],0.000000,5.329106,0.000000,5.000000,bitcoind,,0 Tcpip6_WSHGetWildcardSockaddr,0.000000,4.104007,0.000000,3.850559,MSWSOCK,[unknown],0

  14. TurgutKanceltik commented at 12:43 PM on August 18, 2014: none

    me too please help mee :(

  15. rifaterdemsahin commented at 1:39 PM on August 18, 2014: none

    At the time of failure 2014-08-18 16_40_25-btc-developer - btc-developer cloudapp net_56982 - remote desktop connection

    WaitForMultipleObjects,151.326786,151.326786,70.840752,70.840752,KERNEL32,[unknown],0 NtWaitForSingleObject,51.579601,51.579601,24.146008,24.146008,ntdll,[unknown],0 WaitForSingleObjectEx,10.680772,10.680772,5.000000,5.000000,KERNELBASE,[unknown],0 [0000000000460B92],0.028283,0.028283,0.013240,0.013240,bitcoind,,0 Tcpip4_WSHStringToAddress,0.000000,42.723088,0.000000,20.000000,MSWSOCK,[unknown],0 [00000000008BD280],0.000000,42.723088,0.000000,20.000000,bitcoind,,0 select,0.000000,8.856513,0.000000,4.146008,WS2_32,[unknown],0 Tcpip6_WSHGetWildcardSockaddr,0.000000,8.856513,0.000000,4.146008,MSWSOCK,[unknown],0 Tcpip6_WSHAddressToString,0.000000,8.856513,0.000000,4.146008,MSWSOCK,[unknown],0 [00000000008BD64F],0.000000,10.680772,0.000000,5.000000,bitcoind,,0 [00000000005F374F],0.000000,151.326786,0.000000,70.840752,bitcoind,,0 Tcpip4_WSHOpenSocket2,0.000000,42.723088,0.000000,20.000000,MSWSOCK,[unknown],0 [00000000004610B7],0.000000,8.856513,0.000000,4.146008,bitcoind,,0 WSARecv,0.000000,42.723088,0.000000,20.000000,WS2_32,[unknown],0

  16. rifaterdemsahin commented at 2:10 PM on August 18, 2014: none

    I am so desperate right now. I will write a program to watch the Rpc and shutdown bitcoin.core if it does not respond and restart bitcoin.qt.

    I am waiting for good ideas.

  17. mohamedfarrag commented at 2:23 PM on August 18, 2014: none

    you can call it bitcoin restarter :)

  18. cozz commented at 3:00 PM on August 18, 2014: contributor

    If you only need rpc, you can use bitcoind instead of bitcoin-qt.

  19. rifaterdemsahin commented at 7:19 AM on August 19, 2014: none

    They both failed in bitcoin-qt and bitcoind.

  20. rifaterdemsahin commented at 7:40 AM on August 19, 2014: none

    I am ready to pay 0.1 BTC for the person who fixes the bug. Please Help

  21. rifaterdemsahin commented at 12:56 PM on August 21, 2014: none

    I am ready to pay 0.3 BTC for the person who fixes the bug.

  22. laanwj commented at 1:28 PM on August 21, 2014: member

    Can you try the 32-bit version to compare?

  23. TheBlueMatt commented at 3:25 AM on August 22, 2014: member

    Also, if they are the same, have you tried any previous Bitcoin versions?

  24. laanwj commented at 10:21 AM on September 1, 2014: member

    Yes, can you try with at least the 0.9.1 release? Reason: there is a similar problem with a nondescript crash after 48 hours being reported here, which started at release 0.9.2: https://bitcointalk.org/index.php?topic=760225.0

  25. rifaterdemsahin commented at 11:02 AM on September 1, 2014: none

    Thank you laanwj. I will try it and let you know the status.

  26. laanwj commented at 11:45 AM on December 5, 2014: member

    Closing due to inactivity of OP.

  27. laanwj closed this on Dec 5, 2014
  28. MarcoFalke locked this on Sep 8, 2021
Contributors
rifaterdemsahinsipalaanwjMaDeRkAnmohamedfarragTurgutKanceltikcozzTheBlueMatt
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-29 03:16 UTC
This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me