Error code: -1073741819

[alderman2]

I did a lot of programming 3-4 years ago. I had no problems at all.
Now when I'm going to resume programming again I get in all my previous programs and the new one I'm trying to compile Error code: -1073741819
What is wrong?

EDIT1:
Could the error be due to the fact that I programmed in 32 bit in version 8 and a while ago updated to v11?

EDIT2:
I last used v10 and it worked fine. Why am I getting error code -1073741819 now?

[Vortex]

Hi alderman2,

The latest releaase of Pelles C is v12 :

https://forum.pellesc.de/index.php?topic=11416.0

Could you be more specific? Why type of project in the Pelles IDE is reporting that error message?

[alderman2]

Hi alderman2,

The latest releaase of Pelles C is v12 :

https://forum.pellesc.de/index.php?topic=11416.0

Could you be more specific? Why type of project in the Pelles IDE is reporting that error message?

A few months ago I programmed in 32bit without problems in v10.
Have installed v11 since then.
Now when I would continue to program it fails to compile, I get the error message -1073741819

[John Z]

Hi Alderman2,

I appreciate your frustration but repeating the error code without more information is not going to
help us, help you.  Many of us transitioned from earlier versions as well as V10 to V11 to V12 without issue.

So to help we need to know a bit more detail.  It would really help if you could post the project that
is giving you difficulty.. Pelles C under the 'Project' menu item has a method to zip the necessary files.

If you can't do that then some more information would still be helpful for example are any obj files created at all?

Have you tried doing a complete new install?  Remove the old version completely and reinstall version 12.

Have you tried installing Version 10 again and does it then all still work as it did years ago?

Be sure every C source file ends in an extra line feed at the end of the file....

Try deleting the 'project'.tag file - It will be recreated automatically.

Can you post just the ppj file ? We might see an error in it.

Help us help you,

Regards,
John Z

[Vortex]

Hi alderman2,

You can try to recreate the project in the IDE while preserving the source files. Copy your files to a safe location before removing the project folder.

[TimoVJL]

If someone pack Pelles C forder to zip package, it can be used later with -xml option too.
It is possible to use it with -x -xml options same time with others.

-1073741819 = FFFFFFFFC0000005
C0000005  is memory Access Violation

[alderman2]

I have tested all my previous projects and get the same error message without changing anything at all.
I'm going to reinstall v10 (which I tried before) and see if it works then.


ppj:
#
# PROJEKTFIL genererad av "Pelles C for Windows, version 10.00".
# VARNING! REDIGERA INTE DENNA FIL.
#

POC_PROJECT_VERSION = 9.00#
POC_PROJECT_TYPE = 0#
POC_PROJECT_MODE = Release#
POC_PROJECT_RESULTDIR = .#
POC_PROJECT_OUTPUTDIR = output#
!if "$(POC_PROJECT_MODE)" == "Release"
POC_PROJECT_ARGUMENTS = #
POC_PROJECT_WORKPATH = .#
POC_PROJECT_EXECUTOR = #
POC_PROJECT_ZIPEXTRA = #
CC = pocc.exe#
AS = poasm.exe#
RC = porc.exe#
LINK = polink.exe#
SIGN = posign.exe#
CCFLAGS = -std:C11 -Tx86-coff -Ot -Ob1 -fp:precise -W0 -Gz -Ze -Zx -openmp -Go -Gn -DWIN32_DEFAULT_LIBS#
ASFLAGS = -AIA32 -Gz#
RCFLAGS = #
LINKFLAGS = -subsystem:windows -machine:x86 kernel32.lib user32.lib gdi32.lib comctl32.lib comdlg32.lib advapi32.lib delayimp.lib#
SIGNFLAGS = -timeurl:http://timestamp.verisign.com/scripts/timstamp.dll -location:CU -store:MY -errkill#
INCLUDE = $(PellesCDir)\Include\Win;$(PellesCDir)\Include#
LIB = $(PellesCDir)\Lib\Win;$(PellesCDir)\Lib#
!elseif "$(POC_PROJECT_MODE)" == "Debug"
POC_PROJECT_ARGUMENTS = #
POC_PROJECT_WORKPATH = .#
POC_PROJECT_EXECUTOR = #
POC_PROJECT_ZIPEXTRA = #
CC = pocc.exe#
AS = poasm.exe#
RC = porc.exe#
LINK = polink.exe#
SIGN = posign.exe#
CCFLAGS = -std:C11 -Tx86-coff -Ot -Ob1 -fp:precise -W0 -Gz -Ze -Zx -openmp -Go -Gn -DWIN32_DEFAULT_LIBS -Zi#
ASFLAGS = -AIA32 -Gz -Zi#
RCFLAGS = #
LINKFLAGS = -subsystem:windows -machine:x86 kernel32.lib user32.lib gdi32.lib comctl32.lib comdlg32.lib advapi32.lib delayimp.lib -debug -debugtype:po#
SIGNFLAGS = -timeurl:http://timestamp.verisign.com/scripts/timstamp.dll -location:CU -store:MY -errkill#
INCLUDE = $(PellesCDir)\Include\Win;$(PellesCDir)\Include#
LIB = $(PellesCDir)\Lib\Win;$(PellesCDir)\Lib#
!else
!error "Unknown mode."
!endif

#
# Bygg Printback.exe.
#
Printback.exe: \
   output\Printback.obj \
   output\Printback.res
   $(LINK) $(LINKFLAGS) -out:"$@" $**

#
# Bygg Printback.obj.
#
output\Printback.obj: \
   Printback.c \
   ..\_ASSETC_\_ac_define.h \
   ..\_ASSETC_\ac_ButtonSimpleCreate_1.h \
   ..\_ASSETC_\ac_ButtonSimpleGrayed_1.h \
   ..\_ASSETC_\ac_ButtonSimpleUnGrayed_1.h \
   ..\_ASSETC_\ac_CheckBoxCreate_1.h \
   ..\_ASSETC_\ac_CheckBoxGetState_1.h \
   ..\_ASSETC_\ac_ClockGetLocalTime_1.h \
   ..\_ASSETC_\ac_DialogBoxDialog_1.h \
   ..\_ASSETC_\ac_DialogBoxMono_1.h \
   ..\_ASSETC_\ac_EditBoxCreate_1.h \
   ..\_ASSETC_\ac_EditBoxCreateFont_1.h \
   ..\_ASSETC_\ac_EditBoxGetText_1.h \
   ..\_ASSETC_\ac_EditBoxGrayed_1.h \
   ..\_ASSETC_\ac_EditBoxOpenText_1.h \
   ..\_ASSETC_\ac_EditBoxSaveText_1.h \
   ..\_ASSETC_\ac_EditBoxSetFont_1.h \
   ..\_ASSETC_\ac_EditBoxSetText_1.h \
   ..\_ASSETC_\ac_EditBoxUnGrayed_1.h \
   ..\_ASSETC_\ac_FileErase_1.h \
   ..\_ASSETC_\ac_FileFolderCreate_1.h \
   ..\_ASSETC_\ac_FileGetByteSize_1.h \
   ..\_ASSETC_\ac_FileGetCharSize_1.h \
   ..\_ASSETC_\ac_FileGetStorage_1.h \
   ..\_ASSETC_\ac_FileSetStorage_1.h \
   ..\_ASSETC_\ac_FileSetStorageAppend_1.h \
   ..\_ASSETC_\ac_FlowSetOnOff_1.h \
   ..\_ASSETC_\ac_GraphicCreateTextFont_1.h \
   ..\_ASSETC_\ac_GraphicMemoryCreate_1.h \
   ..\_ASSETC_\ac_GraphicMemoryPaste_1.h \
   ..\_ASSETC_\ac_GraphicMemorySelect_1.h \
   ..\_ASSETC_\ac_GraphicSetDC_1.h \
   ..\_ASSETC_\ac_GraphicSetLine_1.h \
   ..\_ASSETC_\ac_GraphicSetTextOut_1.h \
   ..\_ASSETC_\ac_GraphicSetTextOutNummerical_1.h \
   ..\_ASSETC_\ac_InternetDownloadFile_1.h \
   ..\_ASSETC_\ac_ProgramExecute_1.h \
   ..\_ASSETC_\ac_RandomNumber_1.h \
   ..\_ASSETC_\ac_StringAppend_1.h \
   ..\_ASSETC_\ac_StringCompare_1.h \
   ..\_ASSETC_\ac_StringCopy_1.h \
   ..\_ASSETC_\ac_StringGetByteSize_1.h \
   ..\_ASSETC_\ac_StringGetCharSize_1.h \
   ..\_ASSETC_\ac_StringnumDoubleToString_1.h \
   ..\_ASSETC_\ac_StringnumIntToString_1.h \
   ..\_ASSETC_\ac_StringnumStringToInt_1.h \
   ..\_ASSETC_\ac_WindowCreate_1.h \
   ..\_ASSETC_\ac_WindowGetActive_1.h \
   ..\_ASSETC_\ac_WindowMain_1.h \
   ..\_ASSETC_\ac_WindowMainGetArgument_1.h \
   ..\_ASSETC_\ac_WindowSetBackGroundColor_1.h \
   ..\_ASSETC_\ac_WindowSetBackGroundColorFade_1.h \
   ..\_ASSETC_\ac_WindowSetCenterPos_1.h \
   ..\_ASSETC_\ac_WindowSetResIcon_1.h
   $(CC) $(CCFLAGS) "$!" -Fo"$@"

#
# Bygg Printback.res.
#
output\Printback.res: \
   Printback.rc \
   ..\_ASSETC_\_ac_Resurce_1.h \
   PRINTBACK.ICO
   $(RC) $(RCFLAGS) "$!" -Fo"$@"

.OTHERFILES: \
   Y_projekt.txt

.SILENT:

.EXCLUDEDFILES:

[alderman2]

Strange!
When I first compile I get the error -1073741819. Then I do it one more time and then it works. So I get an exe file that starts as usual:

1- Changes in the code

2- Compiling:
Result=
Project build started
Project build ended in complete failure
Project=
Building template.obj.
*** Error code: -1073741819 ***
Clear.

2- Drive (Or 'start', not sure what it's called in English, has Swedish translation)
Project build started
Project build ended successfully

The exe file starts with the changes I made

EDIT:
Slightly OT, how do I get an email when someone has replied in the thread

[TimoVJL]

You can try to disable Add-Ins to eliminate them.

From profile -> Notifications are options for emails.

[John Z]

In addition to TimoVJL suggestion to disable Add-ins -

Also turn on the verbose setting under Project Options - each section
General
Resource Compiler
Linker

Set Compiler to Level 2

Set under Code Generation Optimizations NONE

restart everything to the point that it is the first compile then compile it, look in the verbose log for issues

John Z

[alderman2]

Thanks, I'll try this (also about emails when someone has replied)!
Will report back on how it went!

[HellOfMice]

In hexadecimal the code is FFFFFFFFC0000005
Have you tried to search in this way?
https://answers.microsoft.com/en-us/windows/forum/all/recurring-blue-screen-bugcheck-1000007e/e8f03131-18cf-4528-a3e2-acae1ddbb06f
or
https://forum.pellesc.de/index.php?topic=7115.0


HellOfMice

[alderman2]

Did as you wrote, no difference.
Works after twice "runs" (thus clicking twice on the button with the triangular arrow).
However, I received some warnings about errors in the code that I did not receive before on the first "Run".

[alderman2]

In hexadecimal the code is FFFFFFFFC0000005
Have you tried to search in this way?
https://answers.microsoft.com/en-us/windows/forum/all/recurring-blue-screen-bugcheck-1000007e/e8f03131-18cf-4528-a3e2-acae1ddbb06f
or
https://forum.pellesc.de/index.php?topic=7115.0


HellOfMice

Must do this!

[alderman2]

The first link doesn't seem to apply to me. It's about blue screen, I don't get that. The information about FFFFFFFFC0000005 was not handled in the test that person did (as I understand it).

TimoVJL answers under the link https://forum.pellesc.de/index.php?topic=7115.0:
"I use 32-bit poide.exe to debug 32-bit programs."

My programs are kompile in 32bit (use my own library with more than 800 functions and can't bear to convert them to 64bit right now).
I am currently using v11 but previously when it worked v10.
I read that v8 is the last version with support for 32bit. But I have compiled in v10 with 32bit and it worked. Now I have v11, it also works but I have to either "compile + run" or "run" twice. The first time I get warnings and Error code: -1073741819, the second time the program starts without problems.
I can work like this, it works, but I'm just wondering why this error suddenly appeared without changing anything except installing v11.
- Could it be due to a difference between v10 and v11?
- Could it be something to do with me compiling 32bit but v11 has problems with it
- Could it be related to v11 using 64bit to debug 32bit?

From v9 it says a little cryptically:
"For 64-bit Windows 7/8/10 host, targeting 32-bit or 64-bit Windows Vista/7/8/10."
Does that mean they can compile 31bit and 64bit?

I have also seen that v8 is the last version for 32bit.
How should it actually be? I'm wondering because the error I'm getting might be due to 32bit compilation in v11.