0x00000ba0 error

re: 0x00000ba0 error

Drew32 — Sun, 07 Sep 2008 23:38:49 GMT

Had same problem for months with "The memory could not be read error"

I have tried everything I could find to eliminate the issue with no success.

I finally uninstalled the Bytemoble Acceleration client for my ATT laptop connect card and the problem is GONE!!!!

Thank God.

If you have an ATT card, go to the Tools tab, settings, accelerration and select uninstall. Reboot and the error is gone.

Hope this helps someone out.

re: 0x00000ba0 error

soxsince67 — Thu, 20 Dec 2007 21:38:38 GMT

Bingo! I had an issue where EVERY program got the 0x00000ba0 error when closed.

I removed Venturi and Verizon Access Manager which were no longer being use, and problem solved. Thanks for the help, this error was all over the net, with not a lot of specific cause and effect or solutions.

re: 0x00000ba0 error

Tom Jones — Fri, 27 Jul 2007 18:39:20 GMT

Thanks for your blog. I had the same issue and uninstalling Verizon VzAccess fixed it.

re: 0x00000ba0 error

kwsupport — Thu, 19 Jul 2007 23:56:32 GMT

Vernon, the Venturi compression comes with the Verizon VZ Access software that Verizon supplies with their Verizon wireless broadband cards.

re: 0x00000ba0 error

vernon — Wed, 18 Jul 2007 22:47:57 GMT

Is the Venturi Compression program only for ACER LAPTOPs? I have a DELL Latitude PII 266 version running perfectly fine except for the crappy memory problems that have accured recently. I will be trying the two solutions you have posted.

thanks

re: 0x00000ba0 error

Hank Tate — Wed, 24 Jan 2007 15:34:25 GMT

I had a similar problem. After upgrading my harddisk and cloning it to a larger harddisk I started getting the error message.

Application Error : The instruction at

"9999999999" referenced memory at "0x00000ba0". The memory could not be "read". (the calling number sometimes varied but the referenced number was always the same)

The programs all ran fine, but when I closed them I would get the popup of the error message.

I searched .. and followed all the suggestions

Tested Memory .. NO PROBLEM

I figured out that it was an operating system issue the way it came up. Finally fixed it by:

1. Ran a Registry Clean-Up Program and cleaned out the Registry.

2. Deleted the pagefile (turned it off)

3. Defragmented the harddisk

4. Turned the pagefile back on

No more error message!!