dpkg crashed with SIGSEGV in __libc_start_main()

[Anton Turnwald]

when my system starts up, sometimes the error-msg comes up, so I have no idea what happens.
but it comes only at the start up. I installed the file twice, but the error comes sometimes again and again

cu Toni

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: dpkg 1.18.4ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
Date: Fri Feb 12 21:45:11 2016
ExecutablePath: /usr/bin/dpkg
InstallationDate: Installed on 2015-11-03 (101 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027)
SegvAnalysis:
 Segfault happened at: 0x40be90: movl $0x0,0x28(%rax)
 PC (0x0040be90) ok
 source "$0x0" ok
 destination "0x28(%rax)" (0x182000007e95ac8) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: dpkg
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x4033f0, argc=34, argv=0x7ffe838f0648, init=<optimised out>, fini=<optimised out>, rtld_fini=<optimised out>, stack_end=0x7ffe838f0638) at libc-start.c:289
Title: dpkg crashed with SIGSEGV in __libc_start_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #359127, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.