Welcome Guest ( Log In | Click here to Register a free account now! )
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.| Important Announcement: The winners of the BC Million Post contest have been announced. You can read who the winners are at this post. - BleepingComputer Management |
![]() ![]() |
Jan 4 2005, 05:07 PM
Post
#1
|
|
|
New Member ![]() Group: Members Posts: 3 Joined: 23-November 04 Member No.: 5,730 |
I understand what this means - that the memory address that the particular program is trying to write the particular instruction is probably being used by other software. My question is: What do I do to solve the conflict. Reinstalling the program doesn't work. Is there a utility, within or separate from WIN XP to re-direct the instruction to a vacant memory address and, if so, how is this done? Anyone? |
|
|
|
Jan 6 2005, 09:19 PM
Post
#2
|
|
![]() Bleep Bleep! ![]() ![]() ![]() ![]() ![]() ![]() Group: Admin Posts: 29,367 Joined: 24-January 04 From: USA Member No.: 3 |
This is usually caused by incompatbilities in hard drivers and/or shoddy programming in an application. Does the error tend to happen wtih a certain app?
You may want to try updating all the drivers for the hardware on your machine and see if that helps -------------------- Lawrence
|
|
|
|
![]() ![]() |
| Lo-Fi Version | Time is now: 21st November 2008 - 08:38 PM |