6 replies to this topic

[hendo72]

Autopatcher crashed when started after finishing downloading updates.

Quote

What Autopatcher was trying to do
It appears that the error occured while Autopatcher was trying to get commandline arguments.

Where: mdInitialization.Main()
Error Code:0x7: Out of memory

Here is the log:

Quote

Attempting to initialize common controls.
Accessing filesystem...
AutoPatcher 5.6 loaded the filesystem.

Detected English (1033) Windows XP Professional Service Pack 2

System Components:
Internet Explorer: 8.0.6001.18812
Windows Media Player: 11.0.5721.5145
.NET Framework: 1.1.4322|1.1SP1|2.0.50727.3053|2.0SP2|3.2.30729.01|3.2SP2|3.5|3.5SP1
Windows Installer: 4.5.6001.22159
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
Microsoft Word: 12.0.6504.5000
Microsoft Excel: 12.0.6504.5001
Microsoft PowerPoint: 12.0.6500.5000
Microsoft Outlook:
Microsoft Access:
Microsoft Project:
Microsoft Publisher:
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath:
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:

[_def_x_]

Quote

Autopatcher crashed when started after finishing downloading updates.

AutoPatcher doesn't download, did you mean APUP (apup.exe), or are you saying that after apup.exe downloaded the release for you,
that when you attempted to load the release in AutoPatcher - AutoPatcher crashed?

Can you elaborate on exactly the steps you were following and in what order the errors occurred, and, who exactly are you quoting?

Since you have only one post I'm going to assume you are new to AutoPatcher and APUP so we will need more clarity about your setup,
meaning, did you download a complete release and so on.

[hendo72]

gUiTaR_mIkE, on 24 October 2009 - 09:03 PM, said:

AutoPatcher doesn't download, did you mean APUP (apup.exe), or are you saying that after apup.exe downloaded the release for you,
that when you attempted to load the release in AutoPatcher - AutoPatcher crashed?

Can you elaborate on exactly the steps you were following and in what order the errors occurred, and, who exactly are you quoting?

Since you have only one post I'm going to assume you are new to AutoPatcher and APUP so we will need more clarity about your setup,
meaning, did you download a complete release and so on.

I'm not new to Autopatcher - just new to the forums. I've been using it since before it was re-incarnated.

I was quoting the Crash Handler window.

I ran apup.exe to update it from 1.0.0.5 to the new version. I ran Autopatcher after apup was done updating the files.

It was at this point that it crashed. As soon as I start Autopatcher, it crashes. The issue is with Autopatcher, not APUP.

I downloaded the complete 1.0.0.6 release, just in case there was a problem with update.

I ended up with the exact same result.

I've done nothing different than I do every other time that I do this.

This is the first time I've had a problem with Autopatcher that I haven't been able to fix or work around.

[Cristiano]

please, how much free RAM & Virtual memory do you have when you're trying to run AutoPatcher? have you tried check for errors in the memory? free tools like memtest86+ may help a lot, because it can pinpoint if the issue is related to your ram or windows install

[]s

[_def_x_]

@hendo72

I feel I may have insulted you by assuming you were new around here, that wasn't my intention, anyway...

The only application updated was apup.exe, nothing was done to autopatcher.exe, and if you have been using it for as long as you mention and
just now having memory issues it must be something at your end. You should also look at your drives, are they getting full, how about the pagefile?

Possibly there is an issue with another program using up memory, or a leak and when autopatcher.exe seeks memory none is available.

Also, have a look at these 2 freeware utilities that are great for hunting down strange behavior within the operating system, registry, accounts, running
applications, and more. Finally, the whole Sysinternals Suite (all free) might be worth the download but here are 2 of the more widely used tools,

...Process Monitor

...Process Explorer

[hendo72]

Cristiano, on 25 October 2009 - 12:53 AM, said:

please, how much free RAM & Virtual memory do you have when you're trying to run AutoPatcher? have you tried check for errors in the memory? free tools like memtest86+ may help a lot, because it can pinpoint if the issue is related to your ram or windows install

[]s

At it's peak, I'm only using 425MB of my 6GB pagefile. Only using 18-20% of my virtual memory (11980MB).
I have plenty of free RAM. 2 x 2GB DDR3 1066 OCZ DC installed and I have to really task the system just to get it to use 2 of it. I'll check for memory errors. But, this is the only program that is having a 'memory' problem. I can play WoW, listen to music and surf the web all at the same time without a single problem.

I'm using XP Pro, if that makes a difference.

[Cristiano]

> I'm using XP Pro, if that makes a difference.
no. booth of my machines are running windows xp pro oem. but i still have one license for xp home (also oem) and another pro license (also oem) on ice. impressive. i have that since 5 or more years and those never was activated, except for the ones that i'm currently running

as for your issue, this error is an common place for vb6 based software. the only one thing that i've found about it is related to damages into windows installation or errors in memory

as for your virtual memory, hit's huge. but still, memory errors may be tricky. sometimes, only a few software are affected. also, you may try install vbrun60sp6.exe, that is at autopatcher folder, but i really doubt that this will make any difference

[]s