Author Topic: Dcuppdater.exe crashes multiple times daily in W7... (Read 38826 times)

alias · « **on:** October 15, 2009, 04:18 PM »

I was looking at my Reliability Monitor today, just out of curiosity, and noticed that it says that DcUppdater.exe crashes multiple times every day. This is typical of the problem report:

Description
Faulting Application Path:   C:\Program Files\DcUpdater\DcUppdater.exe

Problem signature
Problem Event Name:   APPCRASH
Application Name:   DcUppdater.exe
Application Version:   1.0.0.0
Application Timestamp:   00000000
Fault Module Name:   KERNELBASE.dll
Fault Module Version:   6.1.7100.0
Fault Module Timestamp:   49eea60f
Exception Code:   0eedfade
Exception Offset:   0000b4f4
OS Version:   6.1.7100.2.0.0.256.1
Locale ID:   1033
Additional Information 1:   84b3
Additional Information 2:   84b3678162dd6817be25351f87fdbaf6
Additional Information 3:   2b84
Additional Information 4:   2b8441d5a089892b85e6f2ef429b1336

Extra information about the problem
Bucket ID:   1248410852

I'm running v1.23.01, according to the app itself. Any ideas as to why this might be happening? Most days, it happens twice at around 2:30 AM, and twice at around 2:30 PM. It also leaves an icon in my system tray each time it happens, which disappears, of course, as soon as I mouse over it.

mouser · « **Reply #1 on:** October 15, 2009, 04:43 PM »

going to work on this this weekend (along with catching up on all my other promissed dc software updates!)

alias · « **Reply #2 on:** October 15, 2009, 05:11 PM »

Awesome - very exciting times! (You don't know how hard it's been on my scanty store of patience to not keep bugging you about the FARR updates...)

bigloudjeff · « **Reply #3 on:** November 17, 2009, 01:28 AM »

Any update on this. DCUpdater is such a key component for the DonationCoder software it is frustrating that it crashes on Windows 7. If there is anything I can do to help test or debug please let me know.

AEngineer · « **Reply #4 on:** December 09, 2009, 09:09 AM »

I just discovered the same problem on my W7 machine. It works if I start it individually and then use it, but I'm getting the same multiple crash warning that forces my "reliability" index to 1.

mouser · « **Reply #5 on:** December 09, 2009, 09:15 AM »

ahh!!!!!!!!!!

i should have read the initial post more carefully -- this must be why i had a hard time reproducing the problem -- because it doesn't happen if you run it manually!

can i verify that everyone with this problem is using my Find and Run Robot program? If so, go into the Find and Run Robot options and disable Check automatically from the Plugins and Updates tab. If not, then first step is to figure out what is telling dcupdater to run.

Deozaan · « **Reply #6 on:** December 09, 2009, 04:15 PM »

I just ran it manually and it worked fine until I closed it. Upon exit it crashed. Oddly enough it brought up the "This program has stopped working" window twice.

katykaty · « **Reply #7 on:** December 13, 2009, 11:20 AM »

For me DcUpdater crashes after use regardless of whether I start it manually or from the FARR automatic check.

It appears to actually work fine, except for the 2 "This program has stopped working" windows when it tries to close itself.

J-Mac · « **Reply #8 on:** December 15, 2009, 02:37 PM »

mouser,

I don't know if this could be causal, but I find multiple messages in the Event Viewer: some reference DcUpdater, while others reference DcUppdater.

I remember that at one time the app was simply named DcUpdater - with one "p"; at some point you changed that to two "p"s - DcUppdater. I think at the time you were trying to isolate a problem. Anyway now as I said, there are references to both spellings throughout.

Could that be part of the problem?

Just wonderin'

Thanks!

Jim

PS - I'm seeing this also; a whole lot!

easye · « **Reply #9 on:** December 19, 2009, 10:56 AM »

I've been having the same issue - DcUpdater crashes multiple times per day.

Not sure if this will help, but I used ProcDump from Sysinternals to get a dump file when it crashed. I'm not familiar with Windows debugging too much, but was able to get the following summary report of the dump file. If I can provide you with any other info on this let me know.

FYI I am running the latest version of the most excellent FARR

. These crashes are happening when FARR automatically runs DcUpdater as well as when I manually run it.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Eric\Documents\My Dropbox\Apps - portable\wscc\DcUppdater_121709_125306PM.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Version 7100 MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Machine Name:
Debug session time: Thu Dec 17 12:53:07.000 2009 (GMT-5)
System Uptime: not available
Process Uptime: 0 days 17:31:01.000
................................................................
........
eax=0012faf4 ebx=00000057 ecx=00000007 edx=00000000 esi=01991194 edi=00000000
eip=75c8b4f4 esp=0012faf4 ebp=0012fb44 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000212
KERNELBASE!RaiseException+0x58:
75c8b4f4 c9 leave
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

*** ERROR: Symbol file could not be found. Defaulted to export symbols for guard32.dll -
*** WARNING: Unable to verify checksum for focus.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for focus.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for PATROLPRO.DLL -
*** WARNING: Unable to verify checksum for DropboxExt.3.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for DropboxExt.3.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for SugarSyncShellExt.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for libcurl.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for slc.dll -
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

FAULTING_IP:
+5f4d952f043fda44
00000000 ?? ???

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

FAULTING_THREAD: 00001778

DEFAULT_BUCKET_ID: STATUS_BREAKPOINT

PROCESS_NAME: DcUppdater.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 004f15ba to 75c8b4f4

STACK_TEXT:
0012fb44 004f15ba 0eedfade 00000001 00000007 KERNELBASE!RaiseException+0x58
WARNING: Stack unwind information not available. Following frames may be wrong.
0012fb9c 0054022d 0012fd68 00540283 0012fc78 DcUppdater!Nxclassesinitialization$qqrv+0x1a88a
0012fc78 0054f1c3 0199a4e4 01991194 005405c8 DcUppdater!Nxclassesinitialization$qqrv+0x694fd
0012fcd4 7628c6c2 000d1512 00000082 00000000 DcUppdater!Nxclassesinitialization$qqrv+0x78493
0012fd00 76286101 00380b29 000d1512 00000082 user32!InternalCallWinProc+0x23
0012fd78 7628502c 00000000 00380b29 000d1512 user32!UserCallWinProcCheckWow+0xe0
0012fdd4 7627c628 00a54338 00000082 00000000 user32!DispatchClientMessage+0xda
0012fe04 77ac817e 0012fe1c 00000018 0012fe40 user32!__fnNCDESTROY+0x26
0012fe30 7627c661 0054052d 000f14a6 0012fe60 ntdll!KiUserCallbackDispatcher+0x2e
0012fe34 0054052d 000f14a6 0012fe60 0054054d user32!NtUserDestroyWindow+0xc
0012fe50 00529854 00000000 00527594 0012fe80 DcUppdater!Nxclassesinitialization$qqrv+0x697fd
0012fe74 0040340a 01973d01 0012feb8 005675a3 DcUppdater!Nxclassesinitialization$qqrv+0x52b24
0012fea8 00403254 01971e20 01972200 0012ff78 DcUppdater!UnStopAppWindowFromAppearingOnTaskbar$qqrv+0x1512
0012fedc 004e60b9 004013d8 004ebae0 005254a0 DcUppdater!UnStopAppWindowFromAppearingOnTaskbar$qqrv+0x135c
0012ff0c 0056fa2b 00000000 005b1034 00000000 DcUppdater!Nxclassesinitialization$qqrv+0xf389
0012ff34 0056fa7a 005e6af0 00000001 00000000 DcUppdater!Nxclassesinitialization$qqrv+0x98cfb
0012ff58 0056e4ec 00000000 00000000 00000000 DcUppdater!Nxclassesinitialization$qqrv+0x98d4a
0012ff6c 0056fc50 00000000 0012ffc4 0056827c DcUppdater!Nxclassesinitialization$qqrv+0x977bc
0012ff88 765c10dc 7ffd9000 0012ffd4 77ae1e9e DcUppdater!Nxclassesinitialization$qqrv+0x98f20
0012ff94 77ae1e9e 7ffd9000 727e97d8 00000000 kernel32!BaseThreadInitThunk+0xe
0012ffd4 77ae1e71 00401758 7ffd9000 00000000 ntdll!__RtlUserThreadStart+0x70
0012ffec 00000000 00401758 7ffd9000 00000000 ntdll!_RtlUserThreadStart+0x1b

STACK_COMMAND: ~0s; .ecxr ; kb

FOLLOWUP_IP:
DcUppdater!Nxclassesinitialization$qqrv+1a88a
004f15ba 33c0 xor eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: DcUppdater!Nxclassesinitialization$qqrv+1a88a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: DcUppdater

IMAGE_NAME: DcUppdater.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 46c97c4c

FAILURE_BUCKET_ID: STATUS_BREAKPOINT_80000003_DcUppdater.exe!Nxclassesinitialization$qqrv

BUCKET_ID: APPLICATION_FAULT_STATUS_BREAKPOINT_DcUppdater!Nxclassesinitialization$qqrv+1a88a

WATSON_STAGEONE_URL: http://watson.micros...00000.htm?Retriage=1

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

mouser · « **Reply #10 on:** December 19, 2009, 10:59 AM »

i apologize to everyone for taking so long to get to this -- i will try to get it solved this weekend.

J-Mac · « **Reply #11 on:** December 19, 2009, 02:52 PM »

i apologize to everyone for taking so long to get to this -- i will try to get it solved this weekend.
-mouser (December 19, 2009, 10:59 AM)

Hi Jesse - In the meantime, is there a way to disable it? I have it set not to start with Windows, and I also deselected it in the Plugins section of FARR's options as you suggested above, but dcuppdater still manages to start at some point. I am guessing that one of the programs I have from you is calling it and causing it to start.

Any way to disable it without causing problems with my other DC apps?

Thanks!

Jim

mouser · « **Reply #12 on:** December 19, 2009, 03:10 PM »

once disabled in farr and not starting with windows, i do not think it should be launching.

mouser · « **Reply #13 on:** December 20, 2009, 12:06 AM »

i'm having the hardest time getting trying to get my windows 7 virtual machine to have any problems with the updater.. any ideas why this might be happening to you guys and not to me?

mouser · « **Reply #14 on:** December 20, 2009, 04:07 PM »

can you guys try my experimental new version, and let me know if it does any better:
https://www.donation...a/DcUpdaterSetup.exe

easye · « **Reply #15 on:** December 20, 2009, 07:26 PM »

. Just tried it, and for me it caused the same issue. Again, the program runs and checks all the installed software. But when I exit DcUpdater. I get a message that it has stopped working. The problem details are as follows:

Problem signature:
Problem Event Name:   APPCRASH
Application Name:   DcUppdater.exe
Application Version:   1.0.0.0
Application Timestamp:   00000000
Fault Module Name:   KERNELBASE.dll
Fault Module Version:   6.1.7100.0
Fault Module Timestamp:   49eea60f
Exception Code:   0eedfade
Exception Offset:   0000b4f4
OS Version:   6.1.7100.2.0.0.256.1
Locale ID:   1033
Additional Information 1:   84b3
Additional Information 2:   84b3678162dd6817be25351f87fdbaf6
Additional Information 3:   45f5
Additional Information 4:   45f5d7257a5e5af74d9ee127e8d651ce

I wish I could track down what is causing the issue on my side. However, I haven't found anything. It does seem that Windows 7 has some odd issues like this. I recently had another beta application (Evernote) that wouldn't even install on Windows 7. On those forums half the people were able to get it to install correctly and the other half couldn't even get the install to do anything. The developers have not found a solution for that yet.

If there's anything to run on my side that might help you find a pointer to the issue, let me know and I'll be glad to help.

mouser · « **Reply #16 on:** December 20, 2009, 08:14 PM »

ok well someone willing to help test who gets the error reliably is a big aid -- do you mind emailing me ([email protected]) and testing a few versions for me as i try to pin down the cause?

J-Mac · « **Reply #17 on:** December 20, 2009, 11:04 PM »

Same AppCrash issue here too. However I do have the Evernote beta installed - that gave me no problems. (Other than the beta being so poorly designed that I might drop Evernote altogether). But the E-Note installer worked anyway.

I don't know what is different on my box here. Windows 7 Home Premium, clean install on a box that was running XP Pro before. 2.3 GHz AMD Athlon, 4 GB RAM, 2+ TB hard disk space.

Thank you.

Jim

mouser · « **Reply #18 on:** December 22, 2009, 06:53 PM »

is it possible you are all using the same antivirus or some common security application?

J-Mac · « **Reply #19 on:** December 23, 2009, 02:02 AM »

Eset's NOD32 V.4.0.474.0 (Latest build). I also run Malwarebytes scans but not the real-time active scanner. Windows 7 Firewall behind a hardware firewall. I have not logged any events, notifications, etc. with any of those regarding any of my DC apps.

Thank you.

Jim

katykaty · « **Reply #20 on:** December 27, 2009, 03:13 PM »

Using Comodo antivirus and Zonealarm fierewall, new version doesn't change the error.

mouser · « **Reply #21 on:** December 27, 2009, 05:21 PM »

easye has had great patience with me and we are making good progress tracking down the bug, slowly and steadily. it shall be fixed soon.

mouser · « **Reply #22 on:** December 29, 2009, 05:26 PM »

DC members easye and katykaty have tested dozens of versions of the code to help me try to locate the problem.. not fun for anyone i assure you.

I have a new candidate version, let's see how this works for the rest of you:
https://www.donation...a/DcUpdaterSetup.exe

katykaty · « **Reply #23 on:** December 29, 2009, 05:48 PM »

to Mouser for all the work he's put into this in the last couple of days

f0dder · « **Reply #24 on:** December 29, 2009, 06:23 PM »

Let us know what the problem was once you nail it down