Back to the NBOS Home Page
›

Program errors on launch

jbclaypooljjbclaypool
edited November 2023 in Fractal Mapper General

When I launch Mapper 9 it gives three errors:
1. Access violation at address 0000000000F69A93 in module 'Mapper9.exe'. Read of address 0000000000000010.
2. Out of system resources
3. Out of system resources

After clicking Ok to each of them the program launches, but I'm seeing quirks in it like objects being sent to the back layer and any attempt to bring them to the front layer either causes everything else to disappear or has no effect at all.

I've re-installed, downloaded again and re-installed, tried installing on different hard drive: nothing is changing this. I have version 9.01a

Comments

  • Ed_NBOSEd_NBOS

    Do you still have FM8 installed? Open FM8, set the map to something like 100x100 feet with no grid, and close the program. I'm wondering if something in the registry settings is causing FM9 to have problems on startup. If you know how to use regedit, you can delete the FM section:

    Computer\HKEY_CURRENT_USER\SOFTWARE\NBOS Software\The Fractal Mapper\CurrentVersion

  • jbclaypooljjbclaypool

    FM8 is not installed.

  • jbclaypooljjbclaypool

    Ok, apparently FM8 was still installed, but not showing up in Win10 apps settings. I uninstalled it using the uninstall routine in the app folder, but FM9 is still erroring out.

  • jbclaypooljjbclaypool

    I deleted the CurrentVersion in the registry along with the Mapper 8 and Mapper 9 folders. No effect. Uninstalled and reinstalled FM9: it's still giving the first error but not 2 & 3.

  • Ed_NBOSEd_NBOS

    Try without anti-virus in case that is trying to do something to the executable or prevent it from creating app data directories.

  • jbclaypooljjbclaypool

    Uninstalled, turned off anti-virus and reinstalled--still happening. I should make clear, FM9 runs after the error happens, it just is concerning that this is persistent.

  • Ed_NBOSEd_NBOS

    Try launching it once as admin in case its not able to create or access a resource.

    If that doesnt work you can try the next update to see if it fixes it. In File -> Program Preferences set the update channel to "Special4" and then check for updates with Help -> Check for Updates.

  • jbclaypooljjbclaypool

    Launched as admin--no effect. Did update--no effect. Ran sfc/scannow--said it found and fixed issues--no effect. Tried running in compatibility mode for win 8, win 7--no effect. Ran an hour long RAM check--no errors. Have checked the C:drive (NVME) for errors--none found. At this stage I'm at a loss for what's going on. The program runs after clicking ok on the error. It's possible I may have some form of hidden malware issue that is protecting this particular memory location, but don't know why FM9 would be the only program affected. Or this may be related to the Webroot Internet Security problem I originally had--maybe an update to that has caused this to start happening.

  • Ed_NBOSEd_NBOS

    I honestly have no idea what this is related to. I can make a build with some debugging output that could help us narrow down the problem. That may take a couple rounds. Send me an email.

  • John_FosterJJohn_Foster

    I had the same error. I fixed by adjusting the High DPI settings on the executable's Properties/Compatibilities tab. Clicked on Change High DPI settings, then checked both Program and High DPI Override.

  • jbclaypooljjbclaypool

    I tried changing High DPI settings; no effect.

  • Ed_NBOSEd_NBOS

    As I said, I'd have to make special builds for you so we can try to isolate what the problem is. Send me an email so we can coordinate it.

  • jbclaypooljjbclaypool

    I messaged you via the private messaging on this forum. FYI since this problem began I built a new computer in February that runs Win11--previous was Win10. But the problem persists. I just used the Special 4 update channel to get version 9.04d of the program. It has the same error but the address location changed from 0000000000F69A93 to 0000000000F91F93. I've again ran Windows Memory Diagnostic and no errors there, nor any disk errors. Also turned off anti-virus. Error persists. Now that I realized the effects menu is disabled this error is more serious. Previously just an annoyance at startup, but this takes out a big part of program functionality.

  • jbclaypooljjbclaypool

    My Win10 computer had 32Gb of RAM, current computer has 64Gb. Could this be affecting the program?

  • Ed_NBOSEd_NBOS

    Whats the same between the systems? Any same hardware?

    I got you message but I can't start making those builds until the next update is out.

  • jbclaypooljjbclaypool
    edited September 13

    Both use gigabyte mb, ryzen cpu, nvidia video card, but nothing is common between the systems, except a western digital nvme.

  • jbclaypooljjbclaypool
    edited September 13

    I think the WD nvme may be the culprit: FM9 runs fine on my laptop, which has a ryzen cpu.

  • Ed_NBOSEd_NBOS

    I doubt its the nvme itself, but its certainly possible something in the file system on it is throwing FM for a loop. On rare occasions a directory or file will have some unexpected attributes, causing FM problems accessing it. If something is failing to load that it thinks is there (like not able to access a directory), that could certainly throw an av like that.

    I'm almost done getting the update ready for release. Once that's settled I'll make a build you can run to try to isolate where in the startup specifically its having a problem.

  • jbclaypooljjbclaypool

    Just for information: I've done the following to mitigate this issue--in roughly this order.
    Reinstalled FM9 several times
    Ran it as administrator
    Malware scans
    Quick SMART drive scan using WD software
    Tried changing the High DPI settings
    Run in compatibility mode all the way back to win7
    Upgraded FM9 to 9.04d on Special4 channel--changed the memory violation address
    Unchecked Read Only mode on the shortcuts and exe
    Ran Windows Memory Diagnostic standard mode
    Turned off all antimalware
    Deep malware scans for 24+hrs on RAM, all drives, etc.
    Tried to disable DEP on FM9--Windows 11 said it couldn't be done on 64bit programs
    Disabled UAC
    Ran Hardware and Devices Troubleshooter
    Scan using SFC
    Scan using DISM
    Updated drivers on motherboard
    Updated BIOS of motherboard
    Used Windows Update to repair Win 11
    Extended SMART drive scan using WD software

  • jbclaypooljjbclaypool

    I uninstalled FM9 and reinstalled to another hard drive. This did not get rid of the startup error but it did allow me to access the effects menus and fill patterns.

Leave a Comment