Mem bad pointer ошибка

The MEM_BAD_POINTER error is a challenging problem to wrap one’s head around. It usually comes up at startup in a dialog window and goes away when you click on the OK button, only to show up again on your next reboot.

The error is associated with the SmartHeap Library, which manages system memory, and indicates that something has gone wrong with an application that depends on the Library. The error is also a symptom of OS incompatibility.

What Is the SmartHeap Library?

SmartHeap is an old technology used to optimize system memory. It was used in older operating systems that couldn’t maximize memory allocation in a multiprocessor and multi-threaded environment. Many old programs used the tool to compile files and modules.

Today, there’s hardly any program that relies on the memory management tool. If you see the error, it is because you have installed a legacy version of Adobe Acrobat, AutoCAD, or CorelDraw.

What Causes the MEM_BAD_POINTER Error?

You now know that if you see the error, it means you have an old program installed on your system. The cause of the error can be traced to that particular program. Here are brief explanations of the root problems:

Program incompatibility

Modern operating systems do not always agree with legacy applications. While newer versions of Windows should have no problems running old apps, support for those apps might have been abandoned by Microsoft and the app developers, resulting in minor issues between the programs and your OS.

Corrupt installation

It’s one thing to have a legacy application that might not be in sync with the operating system, but it’s another to have installed it wrongly. Apart from that, the program’s files might have been compromised by malware or any other system glitch, causing the SmartHeap Library error to occur.

System changes

Suppose you’ve been using the legacy application for a while. In that case, a recent change, such as a new software installation, a new update, or even a new driver installation, might be causing the error. Upgrades are not so kind to legacy applications, as they might introduce certain setups that were not baked into the apps’ code.

Application conflicts

Other applications on your system, especially startup programs and services, might be clashing with the legacy program. You can find out which app is causing the conflict and rectify the problem. You’ll find out how to do that later on.

Problematic registry keys

Certain programs leave registry keys behind after they’ve been uninstalled. The error occurs whenever a registry key attempts to call up a program that is no longer available. Clearing bad registry keys should fix the problem immediately.

How to Resolve the MEM_BAD_POINTER Issue

Now that you’ve acquainted yourself with the likely causes of the error, it’s time to resolve those problems and get rid of them for good.

Fix the legacy application or uninstall it

The MEM_BAD_POINTER error indicates that you have an old program that relies on the SmartHeap Library. It’s also a sign that the program is problematic or not compatible with your operating system. So, your first action is to repair the application.

Repairing the program is easy. You have to go through the Programs and Features window in the Control Panel. Follow these steps:

1. Press the Windows and R keyboard buttons together or right-click the Start button and select Run once the Power User menu opens.
2. After the Run dialog window opens, type “Control panel” into the text field and click on the OK button.
3. After the Control Panel window appears, click on Uninstall a Program under Programs.
4. The Programs and Features window will now appear.
5. Next, locate the program, right-click on it, and then click on Repair.
6. Follow the subsequent instructions on the wizard to complete the process.

If you don’t see the repair option, you have to uninstall the application and install it again. Better still, you can go for the latest version of the program that is developed to work with your current operating system.

Run the legacy application in compatibility mode

We mentioned that the error could be showing up due to compatibility issues. If you’re running the legacy application on a Windows 10 PC, that could be the problem, as the OS might not fully support the app. That said, Windows 10 comes with a feature that allows you to run apps in older Windows environments. Windows 8 or 7 should have better support for the app, so running it in compatibility mode for any of these versions could see the error disappear for good.

If you don’t know how to run the program in compatibility mode, follow these steps:

1. Right-click on the app’s desktop shortcut and click on Properties in the context menu.
2. If the app doesn’t have a desktop shortcut, follow these steps:

• Press the Windows and S keyboard buttons simultaneously to open the search function.
• Search for the program.
• Once it shows up in the search results, right-click it, select More, and click on Open File Location.
• You’ll see a folder containing the program’s shortcut.
• Right-click on the shortcut and click on Open File Location in the context menu.
• Once the app’s installation folder opens, head to its executable file (the file with the EXE extension) and right-click it.
• Select Properties once the context menu drops down.

1. After the Properties dialog window opens, switch to the Compatibility tab.
2. Next, mark the checkbox for “Run this program in compatibility mode for,” then select Windows 8 or Windows 7.
3. After that, click on the OK button.
4. Check if the problem surfaces again.

Clean up your system registry

Some leftover registry keys cause problems from time to time. If you had a legacy app but uninstalled it, some of its leftover registry keys may be causing the error. It’s also possible that another application’s registry key is clashing with the legacy app and triggering the MEM_BAD_POINTER issue.

In this case, you have to look for those registry keys and clear them out to fix the problem.

Note that the system registry is a sensitive and highly advanced section of your operating system. You can cause irreparable damage if you don’t have adequate knowledge and tamper with it.

We recommend that you go for a specialized application designed to find these problematic keys and get rid of them. Auslogics Registry Cleaner is highly recommended. The program is friendly to novices and experts alike. If you don’t know how to tweak the Windows registry, the tool will restrict its scope to only basic operations that are entirely safe.

That said, the first thing you should do is back up the entire registry. This way, you can quickly get your system back to normal if something goes wrong.

These steps will show you how to back up the registry:

1. Hit the Windows logo key and R key simultaneously or right-click on the Start button and select Run from the Power User menu.
2. After the Run dialog window opens, type “regedit” and click on OK.
3. Click Yes in the User Account Control dialog.
4. Once you see the Registry Editor window, click on File in the top-left corner.
5. Click on Export.
6. After the Export Registry File dialog window opens, navigate to the folder where you’d like to save the backup, choose a file name, and then select All under Export Range.
7. After that, click on the Save button.
8. Whenever you want to restore the registry, open the Registry Editor and click on File >> Import.
9. Next, head to the folder where you saved the backup file and load it.

Now that you’ve backed up your registry, head to Auslogics Registry Cleaner’s official webpage and download the program’s setup file. After the setup file is downloaded, run it. Click on Yes in the User Account Control dialog to allow the setup wizard to run.

Once the setup wizard appears, select your preferences, such as language and preferred installation location, then agree to the license. Once the wizard completes the installation, restart your system.

After your system restarts, launch the program, click on the Scan Now button and leave the Back Up Changes option checked. The process should now begin. The duration of the scan will depend on the contents of your registry and your system’s speed.

Once the scan is complete, the program will list the problems it found, with each problem’s severity level beside it. After that, click on the Repair option to allow the tool to resolve the issues it detected. You’ll see the repair process’s progress, and the program will let you know the status of those registry issues once it’s done. You might see advertisements about other products from the program’s developers.

Perform a system restore

If you have started experiencing issues with the legacy application only recently, it indicates that some recent changes made to your system are triggering the problem in question. It could be a new software program, driver, or system update.

You can resolve the problem by restoring your computer to a previous date. Note that there has to be a saved restore point before you can restore your system. Luckily, Windows typically creates automatic restore points when you make significant changes to your system.

The steps below will show you how to perform a system restore:

1. Right-click on the Windows logo in the taskbar and click on File Explorer or press the Windows and E keyboard buttons together.
2. After the File Explorer window opens, go to the left sidebar and right-click on This PC.
3. Select Properties from the context menu.
4. After the System window opens, click on System Protection on the left side.
5. The System Protection tab of the System Properties dialog window will now appear.

Tip: You can use the Start menu’s search function to summon the System Properties dialog. Just open Start and type “system restore,” then click on “Create a Restore Point.”

1. Click on the System Restore button.
2. Once the System Restore wizard opens, click on Next.
3. Select a restore point and click on Next again.
4. After that, click on the Finish button and allow Windows to restore your PC.
5. Check for the problem after the process completes.

Perform a clean boot

If none of the fixes above has worked, your next action should be checking for application interference. To do that, you have to perform a clean boot.

Performing a clean boot involves disabling applications and services that are designed to load whenever your system starts. This way, you get to find out whether there is a certain application that is triggering the error. You can also use the clean boot technique to identify the responsible app or service.

Follow these steps to perform a clean boot:

1. Go to the Start menu, search for Run, and then launch the program. You can also tap the Windows and R keyboard buttons to open Run.
2. After Run opens, type “msconfig” and then hit the Enter key.
3. Once the System Configuration dialog window opens, head to the Services tab.
4. Check the box that reads, “Hide All Microsoft Services.”
5. Next, click on the Disable All button.

1. After that, head to the Startup tab and click Open Task Manager.
2. Under the Startup tab of the Task Manager, select each program and click on Disable.
3. Once you’ve disabled every program under the Startup tab of the Task Manager, go back to the System Configuration dialog and click on OK.
4. Restart your system.

If the error doesn’t appear after your system starts, then you have to find the program that was causing it earlier. To do that, enable one service and restart your system to check if the error shows up. Keep going through the rest of the services until the problematic app triggers the error again.

You can follow these steps if going through the apps one by one is too much work:

1. Open the System Configuration window and switch to the Services tab.
2. Uncheck the first half of the services you disabled earlier, and then click on the Disable All button. The second half of the startup services will be prevented from loading after your next reboot.
3. If the error dialog doesn’t show up, then none of the services you unchecked is responsible. Uncheck the rest of the services, click on Disable, and then restart your system.
4. If the error shows up the first time you restart your system, then one of the services in the first half of the list is what you’re looking for. You don’t have to check other startup items anymore. However, in some cases, more than one app may trigger the error.

Once you find the responsible app, get rid of it or update it.

Conclusion

That’s how to fix the mem_bad_pointer error in Windows 10. You can use the comments section below to share your thoughts and questions if you’re confused about anything.

We recommend that you use a powerful antivirus program if you don’t have one. Issues like these can be the result of malware infection.

Обновлено March 2023: перестаньте получать сообщения об ошибках и замедлите работу вашей системы с помощью нашего инструмента оптимизации. Получить сейчас в эту ссылку

1. Скачайте и установите инструмент для ремонта здесь.
2. Пусть он просканирует ваш компьютер.
3. Затем инструмент почини свой компьютер.

Некоторые пользователи Home Windows сообщают, что ошибка библиотеки SmartHeap появляется каждый раз, когда они запускают свои персональные компьютеры. В каждом случае сообщение об ошибке в этом всплывающем окне — MEM_BAD_POINTER / MEM_BAD_POINTER (библиотека SmartHeap). Независимо от того, нажимает ли пользователь «ОК» или «Отмена», результат один: компьютер работает нормально, но сообщение об ошибке появляется при следующем запуске системы.

Поврежденные значения реестра: раздел реестра, который остался зависшим, также может быть причиной всплывающего окна, вызывающего библиотеку SmartHeap. В большинстве случаев это связано с тем, что инфраструктура, вызываемая ключом реестра при запуске, больше не существует. В таком случае, удаление оставшегося раздела реестра вручную или с помощью такой утилиты, как сторонний очиститель реестра, чтобы навсегда решить проблему.

Частично несовместимое устаревшее приложение: В зависимости от используемой версии Windows и версия устаревшего приложения вызывая проблему, вы можете полностью избежать всплывающего окна, настроив запуск основного исполняемого файла в режиме совместимости с версией Windows, которая его полностью поддерживает.

Непризнанный сторонний конфликт: Эта проблема связана со старыми приложениями Adobe, Corel и AutoCAD, но, вероятно, существуют и другие старые программы, использующие инфраструктуру библиотеки SmartHeap, которые могут вызывать аналогичные проблемы. В этом случае вам следует перезагрузить компьютер и найти определенный процесс или элемент запуска, который может вызывать проблему.

Последние системные изменения: Обновление инфраструктуры Windows или установка новых драйверов также могут вызвать эту проблему. В этом случае вам следует подумать об использовании восстановления системы, чтобы перезагрузить компьютер до точки, в которой скрипты, вызывающие проблему, не существовали.

Установка поврежденной устаревшей программы: Одна из наиболее частых причин этой проблемы — когда устаревшая программа, использующая библиотеку SmartHeap, была частично повреждена или была изменена для повреждения некоторых своих файлов. Несколько пользователей, столкнувшихся с той же проблемой, подтвердили, что смогли решить проблему, установив или удалив старое проблемное приложение.

Как исправить ошибку MEM_BAD_POINTER / MEM_BAD_POINTER (библиотека SmartHeap)

Выполните восстановление системы

Если проблемы со старыми приложениями возникли недавно, это означает, что причиной проблемы являются недавние изменения в вашей системе. Это может быть новое программное обеспечение, драйвер или обновление системы.

Вы можете решить эту проблему, сбросив настройки компьютера на более раннюю дату. Обратите внимание, что вам следует сохранить точку восстановления перед восстановлением вашей системы. К счастью, Windows обычно создает точки автоматического восстановления, когда вы вносите существенные изменения в свою систему.

1. Щелкните правой кнопкой мыши логотип Windows на панели задач и выберите Проводник или одновременно нажмите клавиши Windows и E на клавиатуре.
2. Когда окно проводника открыто, перейдите на левую боковую панель и щелкните правой кнопкой мыши «Этот компьютер».
3. Во всплывающем меню выберите «Свойства».
4. Когда откроется окно «Система», нажмите «Защита системы» слева.
5. Теперь отображается вкладка Защита системы диалогового окна Свойства системы.
6. Нажмите кнопку Восстановление системы.
7. Когда откроется Мастер восстановления системы, нажмите Далее.
8. Выберите точку восстановления и снова нажмите Далее.
9. По завершении нажмите «Готово» и позвольте Windows восстановить ваш компьютер.
10. Проверьте проблему после завершения процесса.

Восстановить или удалить устаревшее приложение

Ошибка MEM_BAD_POINTER указывает на то, что у вас есть старая программа, которая использует библиотеку SmartHeap. Это также признак того, что программа проблематична или несовместима с вашей операционной системой.

Ваше первое действие — восстановить приложение. Исправить программу очень просто. Вам нужно перейти в окно «Программы и компоненты» Панели управления. Сделайте следующее:

1. Одновременно нажмите клавиши Windows и R на клавиатуре или щелкните правой кнопкой мыши кнопку «Пуск» и выберите «Выполнить», когда откроется меню «Опытный пользователь».
2. После появления диалогового окна «Выполнить» введите «Панель управления» в текстовое поле и нажмите «ОК».
3. Когда появится окно Панели управления, щелкните Удалить программу в разделе Программы.
4. Откроется окно «Программы и компоненты».
5. Теперь найдите программу, щелкните ее правой кнопкой мыши и выберите «Восстановить».
6. Следуйте остальным указаниям мастера, чтобы завершить процесс.

Если вы не видите вариант восстановления, вам необходимо удалить и переустановить приложение. А еще лучше приобрести последнюю версию программы, предназначенную для работы с вашей текущей операционной системой.

Выполнение перезагрузки

Выполнение перезагрузки отключает приложения и службы, которые должны загружаться при запуске системы. Таким образом вы сможете узнать, является ли конкретное приложение причиной ошибки. Вы также можете использовать метод чистого запуска, чтобы определить ответственное приложение или службу.

1. Перейдите в меню «Пуск», найдите «Выполнить» и запустите программу.
2. Вы также можете нажать клавиши Windows и R на клавиатуре, чтобы открыть команду «Выполнить».
3. После открытия «Выполнить» введите «MSConfig» и нажмите Enter.
4. Когда откроется диалоговое окно «Конфигурация системы», щелкните вкладку «Службы».
5. Установите флажок «Скрыть все службы Microsoft».
6. Затем нажмите кнопку «Отключить все».
7. Затем перейдите на вкладку «Пуск» и нажмите «Открыть диспетчер задач».
8. На вкладке «Пуск» диспетчера задач выберите каждую программу и нажмите «Отключить».
9. После отключения всех программ на вкладке «Пуск» диспетчера задач вернитесь в диалоговое окно «Конфигурация системы» и нажмите «ОК».
10. Перезагрузка системы.

Совет экспертов: Этот инструмент восстановления сканирует репозитории и заменяет поврежденные или отсутствующие файлы, если ни один из этих методов не сработал. Это хорошо работает в большинстве случаев, когда проблема связана с повреждением системы. Этот инструмент также оптимизирует вашу систему, чтобы максимизировать производительность. Его можно скачать по Щелчок Здесь

Сообщение Просмотров: 322

Some Windows users are reporting that they are seeing a SmartHeap Library error at every computer startup. In every case, the error message inside there popup is either MEM_BAD_POINTER / MEM_BAD_POINTER. Whether the user clicks on Ok or Cancel, the end result is the same – The computer functions normally, but the error message returns at the next system startup.

SmartHeap Library Error MEM_BAD_POINTER / MEM_BAD_POINTER

What is SmartHeap Library?

Smartheap is an old infrastructure that was previously used as the primary memory management library when certain programs were compiled.

Nowadays, virtually no programs still rely on this memory management component, so most likely it found your way on your computer when you installed a legacy version for Corel Draw, Autocad, Adobe Acrobat, etc.

Now that you are more familiar with the underlying component that’s being responsible for this issue, here’s a list of scenarios that are known to cause the MEM_BAD_POINTER or MEM_BAD_POINTER error message inside a SmartHeap Library prompt:

• Corrupted installation of the legacy program – One of the most common causes that will cause this issue is an instance in which a legacy program that is using the SmartHeap library has become partially corrupted or has undergone some changes that corrupted some of its files. Several users facing the same issue have confirmed that they’ve managed to fix the issue by either repairing or uninstalling the problematic legacy application.
• Partially incompatible legacy app – Depending on the Windows version that you’re using and the version of the legacy app that’s causing these types of issues, you might be able to avoid the popup altogether by configuring the main program executable to run in Compatibility mode with a Windows version that fully supports it.
• Corrupted Registry Values – A remnant registry key can also be responsible for the pop-up that is calling for the SmartHeap Library. In most cases, this will occur because the infrastructure called by the startup registry key is no longer present. In this case, removing the remnant registry key manually or with a utility like CCleaner should fix the issue permanently.
• Recent System Change – An infrastructure Windows update or a new driver installation might also be responsible for this problem. In this case, you should consider using System Restore to revert your PC state back to a point in which the scenarios that are currently causing the problem were not present.
• Unidentified 3rd party conflict – This issue is linked with legacy applications of Adobe, Corel, and AutoCAD, but there are certainly other legacy programs that are using the SmartHeap Library infrastructure and might produce similar issues. In this case, you should clean boot your computer and investigate for the specific process or startup item that might be causing the issue.

Now that we’ve been through the list of potential culprits, here’s a rundown of the most effective methods that affected users have successfully used to prevent the apparition of the annoying startup pop-up:

Method 1: Repairing or Uninstall the Legacy Program (if applicable)

Keep in mind that in most documented cases, this issue is known to be caused by a corrupted installation of a legacy program that is actively using the SmartHeap Library memory management infrastructure. This issue is confirmed to occur on Windows 7, Windows 8.1, and Windows 10.

In most cases, this is reported to occur with legacy versions of Corel Draw and other Corel products, Adobe Acrobat Reader and Autocad. However, this is not a rule as you can also see the MEM_BAD_POINTER or MEM_BAD_POINTER error message due to a lesser-known legacy program.

If you find yourself in this particular scenario, you should start by trying to repair or uninstall the legacy program in order to prevent the pop-up from occurring.

Note: You probably have the right to upgrade to a newer version of the program, so there’s no reason to continue using legacy software that is no longer fully compatible with your Windows installation.

Follow the instructions below to attempt to repair or uninstall the legacy program that is producing the SmartHeap pop-ups at every system startup:

1. Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘appwiz.cpl‘ and press Enter to open up the Programs and Features menu.

   

   Type appwiz.cpl and Press Enter To Open Installed Programs Page

2. Once you’re inside the Programs and Features screen, scroll down through the list of installed programs and locate the legacy program that you suspect might be using the SmartHeap module.
3. Right-click on the legacy program and see if you have the option to Repair from the context menu that just appeared. If you have it, click on Repair and follow the on-screen instructions to complete the repair process, then restart your computer and see if the issue is fixed at the next startup.

   

   Uninstalling or repairing the legacy app

   Note: If repairing the legacy application is out of the question, the only thing you can do is uninstall it. In this case, choose Uninstall from the context menu.

4. Once you have enforced the change to the legacy program (repair or uninstall) reboot your computer and see if the error popup returns.

If you are still encountering the MEM_BAD_POINTER or MEM_BAD_POINTER error, move down to the next potential fix below.

Method 2: Running the Program in Compatibility Mode

Depending on the legacy program that you’re having issues with, you might be able to fix the problem by configuring the software to run in compatibility mode with a Windows version that fully supports it.

There are a lot of documented instances where affected users have managed to fix the problem after configuring a legacy version of AutoCAD to run in compatibility mode with Windows 7.

Important: This fix will only be effective in instances where the main executable of the legacy program is being called by a startup item at every system startup.

So whether you’re encountering this issue while having AutoCAD installed or a different program, follow the instructions below to configure the legacy program to run in compatibility mode:

1. Right-click on the main executable of the legacy program that you suspect for being responsible for this startup error and choose Properties from the context menu.

   

   Accessing the Properties screen of the legacy program

2. Once you’re inside the Properties screen of the legacy program, click on the Compatibility tab from the menu at the top.
3.  Next, check the box associated with Compatibility mode, then select Windows 7 or an even older Windows version if necessary before finally clicking Apply to save the changes.

   

   Running the Legacy program in compatibility mode

4. Restart your computer and see if their issue is fixed at the next computer startup.

In case you are still dealing with the MEM_BAD_POINTER or MEM_BAD_POINTER error, move down to the next potential fix below.

Method 3: Running a Registry Scan

If none of the methods above have allowed you to fix the issue, you should start considering the possibility that you might be dealing with a remnant registry key that is calling for the SmartHeap Library even though the infrastructure is no longer present.

If this scenario is applicable, the issue will only be fixed after you manage to identify the problematic Registry key and remove it from your computer. However, since the manual approach is not recommended since they are a lot of potential different scenarios that might spawn this error, you should use a 3rd party suite that is capable of automatically identify remnant registry keys and remove them from your computer.

In case you’re looking for step-by-step instructions, follow the instructions below to use CCleaner to clean your Registry of remnant entries that are no longer valid:

1. Open your default browser and visit the official download page of Ccleaner. Once you’re inside the download page, the download of the latest version of CCleaner should start on its own – In case this doesn’t happen, click on the download hyperlink to start the download manually.

   

   Downloading Ccleaner
2. Once the installer is successfully downloaded, double-click on it and hit Yes when prompted by the UAC (User Account Control) to grant admin access. Next, follow the on-screen prompts to complete the installation.

   

   Installing CCleaner

3. When the installation is finally complete, open CCleaner and move over to the left-hand side of the screen and click on Registry.
4. Inside the Registry screen, click on Scan for Issues, then wait for the operation to complete.

   

   Doing a Registry scan with CCleaner

   Note: This operation will ensure that every unused instance of your registry will be removed. This will not cause any damage to your system, as it will only deal with corrupted Registry values and paths that no longer point towards a viable location.

5. Once the Registry scan is complete, you can also do a standard clean by clicking on Clean, but this is entirely optional.
6. Restart your computer and see if this scan has managed to fix the MEM_BAD_POINTER or MEM_BAD_POINTER error.

If you’re still dealing with the same issue, move down to the next potential fix below.

Method 4: Using a System Restore Point

If you only started to deal with this error recently, chances are a recent OS change has contributed to the apparition of this error. Several affected users dealing with the same kind of issue have confirmed that they’ve managed to fix the issue by using System Restore to revert the computer state back to a state in which this issue was not occurring.

If you haven’t used System Restore before, keep in mind that this utility will allow you to revert your computer back to a healthy state (as long as you have an available system restore a snapshot to choose from)

Note: As long as you didn’t modify the default behavior of System Restore, you should have plenty of restore snapshots to choose from as the utility is configured to create new entries right before important system startups (such as the installation of a new program, a big Windows update, etc.)

If you understand how this tool works and what it can do for you, go ahead and use it to identify the best restore snapshot and deploy it in order to fix the pop up caused by the SmartHeap Library.

Using System Restore

Note: Keep in mind that once you go through with this operation, every change you have enforced since the creation of that restore snapshot will be lost.

Once the restore snapshot has been deployed, reboot one final time, and see if they pop up is fixed.

In case you are still seeing the same MEM_BAD_POINTER or MEM_BAD_POINTER startup error, move down to the final fix below.

Method 5: Clean Boot your Computer

If none of the methods above have worked in your case, you have to consider the possibility that some kind of 3rd party interference is causing this startup error. If you have no idea of which potential culprit might be causing the issue, a good place to start is to boot your computer in a clean boot mode and ensure that no 3rd party services and startup items are permitted to run.

This will allow you to confirm if the MEM_BAD_POINTER or MEM_BAD_POINTER startup error is being caused by a 3rd party application or not. If you confirm that a 3rd party app is causing the issue, it’s just a matter of identifying the culprit by systematically re-enable every disabled item until the error pop-up appears again.

Since this process is quite long, we’ve put together a step-by-step guide that will walk you through the whole process:

1. Press Windows key + R to open up a Run dialog box. Next, type ‘msconfig’ and press Enter to open up the System Configuration tool.

   

   Accessing the MsConfig utility
2. Once you’re inside the System Configuration tool, click on the Services tab from the menu at the top. Once you’re inside, enable the checkbox associated with Hide all Microsoft services. Note: Doing this will ensure that every native Microsoft Service that’s essential to your Windows installation will be hidden so you can’t disable it by mistake. 
3. Now that you’re only left with the 3rd party services, click on the Disable all button and click Apply to save the changes.

   

   Disabling every 3rd party service

4. Next, click on the Startup tab and click on Open Task Manager from the hyperlink below.

   

   Opening the Task Manager

5. Once you’re inside the Task Manager utility, go ahead and disable every Startup service that is not signed in by Microsoft Corporation by right-clicking on Disable from the newly appeared context menu.

   

   Disabling every 3rd party startup item

6. After you manage to disable every relevant 3rd party startup service, reboot your computer conventionally and wait for the next startup to complete.
7. At the next system startup, be on the lookout for the MEM_BAD_POINTER or MEM_BAD_POINTER error. If the issue doesn’t return, you’ve just confirmed that the issue is caused by a 3rd party component. At this point, it’s just a matter of pinpointing the program that’s causing the issue – To do this, go ahead and systematically re-enable every previously disabled startup item and process coupled with regular restarts until you see the error returning.
   Note: Once you discover the culprit, either uninstall the parent application or keep the problematic service/startup item disabled to prevent the error from returning.
8. Finally, if you manage to fix the issue, go ahead and re-enable every previously disabled item in order to prevent your computer from clean booting at every startup.

Archiv verlassen und diese Seite im Standarddesign anzeigen : Проблема Готика 1

В общем такое дело. Поставил я на днях опять первую Готу, чтобы поиграть. Лицензия от Снежков. До этого всё было нормально. Сейчас игра, при выходе из неё выдаёт ошибку: Smart Heap Library: MEM_BAD_POINTER. Каждый раз, когда я выхожу. Плюс к этому в игре какие-то проблемы с текстурами и она очень часто зависает, вешая при этом всю винду. Драйвера на мать, видео и звук я переустанавливал, регистр чистил, лишнего фуфла в трее при запуске нет (хотя раньше Гота и с этим фуфлом прекрасно пахала). Что это может быть? Погуглив, я внятного ответа на этот вопрос не нашёл.

А конфигурацию компьютера, версию драйверов и ОС религия не позволяет указать?

Сделал дефрагментацию, поставил новый директ и дрова. Не помогло от вылетов. Жаль… теперь не могу поиграть в мою самую любимую игру(((… Но всё равно спасибо ukur’у за помощь!

Kc-Gray
Внимательно прочитай соседнюю тему.
TEXHИЧECKИЙ FAQ для Гoтики 1 и Гoтики 2(Hoчь Bopoнa) (http://forum.worldofplayers.de/forum/showthread.php?t=874483)

Спасибо за подсказку, да только проблема в том, что не помогает… вобщем в той теме и распишу

Powered by vBulletin® Version 4.2.2 Copyright ©2023 Adduco Digital e.K. und vBulletin Solutions, Inc. Alle Rechte vorbehalten.

Данная проблема актуальна для всех модов использующих скриптовый расширитель IKARUS.

Решение:​

Открываем окно свойства Винды(комбинация клавиш: Win+Pause)​

В открывшемся окне переходишь во вкладку «Дополнительно», в ней выбираешь в блоке «Быстродействие» кнопу «Параметры».​

Откроется окно «Параметры быстродействия», в нем переходишь во вкладку «Предотвращение выполнения данных», в этом окне будет два радиобаттона:​

— Включить DEP только для основных программ и служб Windows;​

— Включить DEP для всех программ и служб, кроме выбранных ниже;​

​

Так вот, если Деп включен для второй строки, то в ней ждем кнопу «Добавить…», в открывшимся окно идешь в каталог установленной игры «..system»​

и из него добавляешь все ехе-шники(Gothic2.exe, GothicStarter.exe) в это окно..​

​

Как все добавил жмешь «Применить» и «Ок».​

​

Если включен для первой, ничего не делаешь.​

​

Далее идешь в каталог игры Г2НВ «..system»​

В свойствах ехе-шников проставляешь/ставишь галки, во вкладке «Совместимость», пункт «Режим совместимости»​

— Запустить программу в режиме совместимости WinXP SP3 *​

и​

— Запускать с правами администратора.​

Жмешь «Применить» и «Ок».​

Проверяешь в работе игру..​

​

* — если игра будет подтупливать с этим параметром запуска, то его можно отключить, такое бывает, но редко и не у всех..​

​

Игру всегда запускать с админ правами, если ОСь выше Вин ХР..​