Condor 2 Error: Access Violation at 006F407B
-
- Posts: 6
- Joined: Thu Aug 27, 2020 1:47 pm
Condor 2 Error: Access Violation at 006F407B
Hi team!
I am getting an error from Condor 2 (2.1.3.0): "Access Violation at 006F407B in Module 'Condor.exe'. Read of address 00000000" whenever I try to launch a flight. Free flight, school flight... same error. Interestingly, after getting the error, condor doesn't fully shut down, because the next time I attempt to open the app, windows tells me that an instance of Condor is already running.
Steps I have tried:
--Updated Hangar to 14
--Deleted all scenery
--Reinstalled Condor 2 from scratch
--Updated Nvidia drivers
--Updated Windows OS and Drivers
--Turn it off, turn it back on again...
Machine: Razer Blade 15 with RTX 2080 SUPER and 10th gen intel
Any suggestions?
Thanks!
I am getting an error from Condor 2 (2.1.3.0): "Access Violation at 006F407B in Module 'Condor.exe'. Read of address 00000000" whenever I try to launch a flight. Free flight, school flight... same error. Interestingly, after getting the error, condor doesn't fully shut down, because the next time I attempt to open the app, windows tells me that an instance of Condor is already running.
Steps I have tried:
--Updated Hangar to 14
--Deleted all scenery
--Reinstalled Condor 2 from scratch
--Updated Nvidia drivers
--Updated Windows OS and Drivers
--Turn it off, turn it back on again...
Machine: Razer Blade 15 with RTX 2080 SUPER and 10th gen intel
Any suggestions?
Thanks!
Last edited by RaptorBoss on Thu Aug 27, 2020 2:17 pm, edited 1 time in total.
-
- Posts: 6
- Joined: Thu Aug 27, 2020 1:47 pm
Re: Condor 2 Error: Access Violation at 006F407B
Hi! It's installed directly to C://
Re: Condor 2 Error: Access Violation at 006F407B
The full path of install directory...
-
- Posts: 6
- Joined: Thu Aug 27, 2020 1:47 pm
Re: Condor 2 Error: Access Violation at 006F407B
Ah sorry, it's
This pc\C:\Condor2\Condor.exe
does that answer your question?
This pc\C:\Condor2\Condor.exe
does that answer your question?
Re: Condor 2 Error: Access Violation at 006F407B
yes, thank you. Did it work before?
-
- Posts: 6
- Joined: Thu Aug 27, 2020 1:47 pm
Re: Condor 2 Error: Access Violation at 006F407B
Yep, it did work before, and I'm not aware of any changes that would have triggered the issue. I did a windows cumulative update for windows on 8/12 (KB4566782), but I have used Condor between then and now.
Re: Condor 2 Error: Access Violation at 006F407B
Did you delete a landscape?
Re: Condor 2 Error: Access Violation at 006F407B
Look at logs (copy'n' paste them here), it can have useful data.
C:\Condor2\Logs\Logfile.txt
C:\Condor2\Logs\Logfile.txt
-
- Posts: 6
- Joined: Thu Aug 27, 2020 1:47 pm
Re: Condor 2 Error: Access Violation at 006F407B
Thanks!
It is possible that I deleted a landscape file using WinDirStat, but I think that a full reinstall would probably fix that issue, no?
Here is all I see in the log file:
CONDOR LOG STARTED AT 4:48:43 PM
Condor version: 2130
Creating splash screen.
Loading cursors.
Loading fonts.
Creating controlers.
Creating client.
Creating replay.
Creating flighttrack.
Loading GUI skins.
Loading skin hash list.
Checking skin hash list.
Saving skin hash list.
Reading language.
Writing installdir.
Reading lastplayer.
Reading defaultlandscape.
Loading Setup.
Destroying splash screen.
ENTERING FLIGHTPLANNER.
STARTING FREE FLIGHT SIMULATION AT 4:48:52 PM.
Debug mode: False, False.
Creating window.
0: NVIDIA GeForce RTX 2080 Super with Max-Q Design.
VIDEO RAM: 3072.0 Mb.
1: Intel(R) UHD Graphics.
VIDEO RAM: 128.0 Mb.
2: Microsoft Basic Render Driver.
VIDEO RAM: 0.0 Mb.
SELECTED: NVIDIA GeForce RTX 2080 Super with Max-Q Design.
VIDEO RAM: 3072.0 Mb.
Monitor: \\.\DISPLAY1.
Left: 0.
Right: 1536.
Top: 0.
Bottom: 864.
Attached to desktop: True.
Access violation at address 006F407B in module 'Condor.exe'. Read of address 00000000.
It is possible that I deleted a landscape file using WinDirStat, but I think that a full reinstall would probably fix that issue, no?
Here is all I see in the log file:
CONDOR LOG STARTED AT 4:48:43 PM
Condor version: 2130
Creating splash screen.
Loading cursors.
Loading fonts.
Creating controlers.
Creating client.
Creating replay.
Creating flighttrack.
Loading GUI skins.
Loading skin hash list.
Checking skin hash list.
Saving skin hash list.
Reading language.
Writing installdir.
Reading lastplayer.
Reading defaultlandscape.
Loading Setup.
Destroying splash screen.
ENTERING FLIGHTPLANNER.
STARTING FREE FLIGHT SIMULATION AT 4:48:52 PM.
Debug mode: False, False.
Creating window.
0: NVIDIA GeForce RTX 2080 Super with Max-Q Design.
VIDEO RAM: 3072.0 Mb.
1: Intel(R) UHD Graphics.
VIDEO RAM: 128.0 Mb.
2: Microsoft Basic Render Driver.
VIDEO RAM: 0.0 Mb.
SELECTED: NVIDIA GeForce RTX 2080 Super with Max-Q Design.
VIDEO RAM: 3072.0 Mb.
Monitor: \\.\DISPLAY1.
Left: 0.
Right: 1536.
Top: 0.
Bottom: 864.
Attached to desktop: True.
Access violation at address 006F407B in module 'Condor.exe'. Read of address 00000000.
Re: Condor 2 Error: Access Violation at 006F407B
No, because personal data & settings are kept in \Documents\Condor. Logs indicate Condor Crash while listing screens (if you have more than 1) or before initializing DirectX, so not very helpful :/
Try to backup then delete Documents\Condor directory and subdirectory, and check if it hangs again.
Try to backup then delete Documents\Condor directory and subdirectory, and check if it hangs again.
-
- Posts: 6
- Joined: Thu Aug 27, 2020 1:47 pm
Re: Condor 2 Error: Access Violation at 006F407B
Boom! Fixed! Thank you!
I will permanently delete the old Documents\Condor directory and re-download my scenery using the installer.
Thanks again!
I will permanently delete the old Documents\Condor directory and re-download my scenery using the installer.
Thanks again!
Re: Condor 2 Error: Access Violation at 006F407B
I experienced this issue today. The suggestion to clear c:\documents\Condor worked for me too so I dug a bit deeper...
I discovered that it was the c:\documents\Condor\Pilots\mypilot\Setup.ini that caused it.
I then worked out that the issue for me was that I had somehow deselected the monitor, so [0] monitors were enabled and that was the cause.
Once I realised this I was able to restore everything for c:\documents\Condor from a back up, then startup Condor and use the Setup->Graphics menu to identify and enable my monitor to get everything working again.
I discovered that it was the c:\documents\Condor\Pilots\mypilot\Setup.ini that caused it.
I then worked out that the issue for me was that I had somehow deselected the monitor, so [0] monitors were enabled and that was the cause.
Once I realised this I was able to restore everything for c:\documents\Condor from a back up, then startup Condor and use the Setup->Graphics menu to identify and enable my monitor to get everything working again.
Re: Condor 2 Error: Access Violation at 006F407B
I am also having an access code violation that results in a freeze up, with Condor2 not responding.
This started suddenly as I had no previous issues and had changed nothing.
It appears to only occur when I am using the North Texas landscape. I had been using this landscape for a year with no problems.
I have deleted all condor documents, and files, have uninstalled and re-installed Condor 2, downloaded all updates, deleted and reloaded the landscape from Condor updater three times.
Any thoughts or assistance will be most appreciated.
Thank you
Steve
This started suddenly as I had no previous issues and had changed nothing.
It appears to only occur when I am using the North Texas landscape. I had been using this landscape for a year with no problems.
I have deleted all condor documents, and files, have uninstalled and re-installed Condor 2, downloaded all updates, deleted and reloaded the landscape from Condor updater three times.
Any thoughts or assistance will be most appreciated.
Thank you
Steve