AccountingRight 19.13 crashes

Partner Enrique
2 Posts
Partner
Australia
Enrique
Partner

2Posts

0Kudos

0Solutions

AccountingRight 19.13 crashes

AccountingRight is crashing with the error The instruction at Ox7758eb83 referenced memory at Ox7755fb8e. The memory could not be written, Click on 0K to terminate the program. Windows 7 64 bit.

 

The same machine has a lot of MYOB error in the reliability logs - I see a lot of these as we use AccountingRight 19.13 on about 20 machines see below for a sample of errors -

 

Description
Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0b04fcad
Faulting process id: 0x1a1c
Faulting application start time: 0x01d342e9c9713f81
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: unknown
Report Id: 5ecc3889-aedd-11e7-bcd1-a41f725415cc


12-10-2017 10:14
Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: ole32.dll, version: 6.1.7601.23889, time stamp: 0x598d4c89
Exception code: 0xc0000005
Fault offset: 0x000224a3
Faulting process id: 0x2dc
Faulting application start time: 0x01d342eed442298e
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: C:\windows\syswow64\ole32.dll
Report Id: 425a831d-aee2-11e7-bcd1-a41f725415cc

Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: ntdll.dll, version: 6.1.7601.23889, time stamp: 0x598d4c81
Exception code: 0xc0000029
Fault offset: 0x000904de
Faulting process id: 0x2dc
Faulting application start time: 0x01d342eed442298e
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: C:\windows\SysWOW64\ntdll.dll
Report Id: e83ba0cd-aee4-11e7-bcd1-a41f725415cc

Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x0b2efcb1
Faulting process id: 0x1154
Faulting application start time: 0x01d342f3c20b206c
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: unknown
Report Id: 56c51c87-aee7-11e7-bcd1-a41f725415cc


Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0b20fd26
Faulting process id: 0x1370
Faulting application start time: 0x01d342f6b622c8f0
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: unknown
Report Id: 3e80f892-aeea-11e7-bcd1-a41f725415cc


Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000001d
Fault offset: 0x0435fd35
Faulting process id: 0xb78
Faulting application start time: 0x01d342fff5d515cf
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: unknown
Report Id: 806c4f51-aef3-11e7-bcd1-a41f725

Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000096
Fault offset: 0x0ba8fd28
Faulting process id: 0xe8c
Faulting application start time: 0x01d34305cff1d75e
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: unknown
Report Id: 5d82a9cf-aef9-11e7-bcd1-a41f725415cc

from event viewer

Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0b04fcad
Faulting process id: 0x1a1c
Faulting application start time: 0x01d342e9c9713f81
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: unknown
Report Id: 5ecc3889-aedd-11e7-bcd1-a41f725415cc

10:14

Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: ole32.dll, version: 6.1.7601.23889, time stamp: 0x598d4c89
Exception code: 0xc0000005
Fault offset: 0x000224a3
Faulting process id: 0x2dc
Faulting application start time: 0x01d342eed442298e
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: C:\windows\syswow64\ole32.dll


Faulting application name: Myobp.exe, version: 19.13.0.0, time stamp: 0x57e0d9cc
Faulting module name: ntdll.dll, version: 6.1.7601.23889, time stamp: 0x598d4c81
Exception code: 0xc0000029
Fault offset: 0x000904de
Faulting process id: 0x2dc
Faulting application start time: 0x01d342eed442298e
Faulting application path: C:\Premier19.13\Myobp.exe
Faulting module path: C:\windows\SysWOW64\ntdll.dll
Report Id: e83ba0cd-aee4-11e7-bcd1-a41f725415cc


Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Myobp.exe because of this error.

Program: Myobp.exe
File:

The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance.

Additional Data
Error value: 0B2EFCB1

 

 

 

MemoryCantBeWritten.png
3 REPLIES
Ultimate User gavin12345
1,581 Posts
Ultimate User
Australia
gavin12345
Ultimate User

1581Posts

1319Kudos

244Solutions

Re: AccountingRight 19.13 crashes

Hi @Enrique

 

Most unusual - esp if as you say this is happening on multiple computers. Premier v19 is normally quite robust and these type of errors would be very rare, suggesting there might be something wrong on the computers, such as the installation, or interference with other software.

 

I would suggest 2 things, uninstall and re-install Premier v19.13, ensure computers are regularly re-started. Continuous use of sleep mode can cause memory related issues on some computers.

 

Regards

Gavin

Partner Enrique
2 Posts
Partner
Australia
Enrique
Partner

2Posts

0Kudos

0Solutions

Re: AccountingRight 19.13 crashes

Hi,

I regularly re-install AccountingRight 19.13 whenever errors are reported as well as perform a regular health check on Windows 7 64 bit. The machines are restarted every day. 

 

The SOE is quite basic and just includes Office 2010 and a few other essentials. 

 

Any ideas on how I can troubleshoot this further?

MYOB Moderator Neil_M
5,454 Posts
MYOB Moderator
New Zealand
Neil_M
MYOB Moderator

5454Posts

526Kudos

739Solutions

Re: AccountingRight 19.13 crashes

HI @Enrique

 

Welcome to the MYOB Community Forum, I hope you find it a great resource.

 

Reviewing that error log, I notice the error 0xc0000005 appears quite a bit. Unfortunately, this is one of those Windows errors that have a number of different possible causes so pinning its cause down might be tricky.

 

Some things you may want to try if you haven’t already done so, would be to disable your antivirus and run AccountRight with full Windows Administrator permissions to see if the errors persist. Additionally you may also want to have a read of this Computer tricks and tips blog post which does discuss some common causes and solutions to that error code, How to Fix 0xC0000005 Error



Kind regards,
Neil
MYOB Client Support
Didn't find your answer here?
Try using advanced search to find a post more easily Advanced Search
or
Get the conversation started and make a new post Start a Post