Windows error 0x00000074, 116

Detailed Error Information

BAD_SYSTEM_CONFIG_INFO[1]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x74: BAD_SYSTEM_CONFIG_INFO.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][3]
DescriptionThe default facility code.[2][3]
Error Code116 (0x0074)

Possible solutions

3

Delphi: TList Creation, memory error

delphi
tlist

The code in the question is fine. The code that is wrong is that which calls the constructor. I am prepared to bet that it reads:

var
  Data: IpNameData;
....
Data.Create;

where it should read:

Data := IpNameData.Create;
answered on Stack Overflow Apr 27, 2015 by David Heffernan
2

How to convert ascii to char in NDK?

android
c
android-ndk
jni

You need to provide NewStringUTF() a c-string (i.e. an array of char with an ending null):

value = "116";
char word[2];
word[0] = atoi(value);  // first char converted as you want
word[1] = 0;            // null termination (aka '\0')              
return (*env)->NewStringUTF(env, word);
answered on Stack Overflow Mar 28, 2015 by Christophe • edited Mar 28, 2015 by Christophe
2

How do I diagnose this crash?

visual-c++
postmortem-debugging

Forget MAP files, better use PDB files. For this enable linker option /DEBUG - yes, even for Release builds. /DEBUG is linker option, _DEBUG is compiler option. Only _DEBUG controls the code, and any conditional compilation that source/headers have put against this.

Debug builds have optimizations disabled, _DEBUG macro enabled. Release builds have optimizations enabled, _DEBUG macro disabled. /DEBUG would just put debugging-information into the EXE/DLL, and wont affect anything else.

Coming back to problem, when crash occurs. Do NOT close the application when WER (Windows Error Reporting) says it crashed. Instead keep it there, goto Task Manager, goto Process tab, select that crashed/crashing process, and hit "Create Dump File". Dump file (full-dump) will be created in some local folder (the path will be shown by task-manager). You can now close the crashing application (the WER window).

Now copy this .DMP file into some safe location, preferably the folder having your original Release folder. Open it in Visual Studio or WinDbg. On VS, just hit F11/F10, and you will be shown call stack. If multiple threads are running (in your crashed application), launch "Threads" view, and see the only suspended thread, double click it and you'll find the crash location.

You must have correct PDBs along with all binaries, and absolutely same code to see Code, otherwise call stack wont be good.

To get more information about PDB and stuff, you can read this article.

answered on Stack Overflow Feb 15, 2012 by Ajay
2

What is stuff beyond .data section in Assembly?

assembly

When the system loads your file into memory, it does not stop reading at the end of the data section because there is no reason to, and it is more efficient not to. Since the executable says nothing is there, the code should not access it, so putting something there does not matter. It is more efficient because the system can use pages from the file system cache instead of copying the data, which saves physical memory and avoids a copy.

That being said, that is the content of the executable file after the data section on disk. If you look at the beginning of that extra data as strings, you will see that it is the names of sections in the file (the first two are ".symtab" and ".strtab"). After that comes other information from the file. This is data used by the linker or loader to parse the file, which just happens to have been placed in memory.

answered on Stack Overflow Sep 27, 2013 by ughoavgfhw
2

Connect Thread and access public variables

multithreading
qt

You create a Thread on the stack in PPI's constructor. This means it will be destroyed the second you function returns. I think you want something like this:

PPI::PPI(QWidget *parent, Qt::WFlags flags)
: QMainWindow(parent, flags)
{
    ui.setupUi(this);

    ppiScene = new PPIScene(this);
    ppiScene->setSceneRect(0,0,SCENEWIDTH,SCENEHEIGHT);
    ui.gVPPI->setScene(ppiScene);

    videoImage = new QImage();
    videoPixmap = ppiScene->addPixmap(QPixmap::fromImage(*videoImage));


    VideoUDPSocketThread * videoUDPSocketThread = new VideoUDPSocketThread();

    // connect BEFORE starting to ensure thread safety (this is very important)
    // connect the finished signal to the deleteLater slot to make sure your memory doesn't leak
    // also use the new connection syntax, compiler warnings are nice
    connect( &videoUDPSocketThread->videoSocket, &VideoUDPSocket::videoRead, this, &PPI::onVideoRead );
    connect( videeoUDPSocketThread, &QThread::finished, videeoUDPSocketThread, &QObject::deleteLater ); 

    // now you can start the tread
    videeoUDPSocketThread->start();
}

I hope this helps

answered on Stack Overflow Oct 5, 2015 by Teimpz
1

SKMaps OpenSourceDemo crashing

android
openstreetmap
skmaps

What worked for me was deleting the app and reinstalling it, so assets where copied again, and then it suddenly worked :X

answered on Stack Overflow Jun 12, 2014 by Niels
1

Customizing Fantacy Remote .INI file

remote-desktop
remote-access

In my opinion you should change this:

On server side, set iAcceptInput in [SERVER] section to 0. This might disable mouse and keyboard input.

On client side, in section [MENU] you have to try different values for the key iWindowMode. Try 1, 2 or 3.

answered on Super User May 27, 2010 by user4085
0

SFML - RenderWindow Runtime Errors with EVERYTHING

c++
visual-studio
visual-studio-2012
sfml

I agree with RetiredNinja's comment above: If it happens as soon as you create the render window, it's most likely some STL version difference (from the passed string; since sf::String is part of sfml-system), which is typically the case when you mix up versions (Visual Studio releases or Release/Debug builds).

Are you sure you've picked the correct download from SFML's download page? As an alternative, you could try downloading and compiling SFML from the official repository.

answered on Stack Overflow Dec 31, 2016 by Mario
0

Delphi: TList Creation, memory error

delphi
tlist

As per David's reply + comments, you should replace

procedure TForm1.FormCreate(Sender: TObject);
begin
   ServerData.DataModule2.Data.Create;
end;

with

procedure TForm1.FormCreate(Sender: TObject);
begin
   ServerData.DataModule2.Data:=IpNameData.Create;
end;

and update

IpNameData = class
  private
    ips : TList<String>;
    ports : TList<integer>;
    names : TList<String>;

to

IpNameData = class
  private
    ips : TList<String>;
    ports : TList<integer>;
    names : TList<String>;
    destructor Destroy; override;

and add

destructor IpNameData.Destroy;
begin
  ips.Free;
  ports.Free;
  Name.Free;
  inherited Destroy;
end;

and change

constructor IpNameData.Create;
begin
  ips := TList<String>.Create();
  ports := TList<integer>.Create();
  names := TList<String>.Create();
end;

to

constructor IpNameData.Create;
begin
  inherited Create;
  ips := TList<String>.Create();
  ports := TList<integer>.Create();
  names := TList<String>.Create();
end;

Feel free to give David the "Checkmark" for reply - I have merely specified his reply in detail.

answered on Stack Overflow Apr 27, 2015 by HeartWare
0

Loading symbol file while linking

c
linker
arm
static-linking
symbol

If you're using the GNU linker, just create a file that looks something like this and include it on the linker command line:

__intstk_top__ = __syspage_base__ + 0x2000;
__abortstk_top__ = __syspage_base__ + 0x3000;
__undefinedstk_top__ = __syspage_base__ + 0x4000;
__svcstk_top__ = __syspage_base__ + 0x6000;
__sysstk_top__ = __syspage_base__ + 0x8000;
__boot_pgd__ = __syspage_base__ + 0x8000;
__boot_pgd_physical__ = __syspage_physical_base__ + 0x8000;
__boot_pte0__ = __syspage_base__ + 0xC000;
__boot_pte0_physical__ = __syspage_physical_base__ + 0xC000;
__boot_pte1__ = __syspage_base__ + 0xD000;
__boot_pte1_physical__ = __syspage_physical_base__ + 0xD000;
__syspage_physical_base__ = 0x48000000;
__syspage_base__ = 0x80000000;
__syspage_size__ = 0xE000;
__device_base__ = 0xC0000000;
__user_limit__ = 0x7FFFFFFF;
__virtual_offset__ = 0x80000000 - __syspage_physical_base__;
__dev_offset__ = 0xC0000000;
__mmu_enabled__ = 1;
__kernel_base__ = __syspage_base__;

As you can see, the symbols can be defined as constants or with simple expressions that can be resolved at link time.

answered on Stack Overflow Mar 4, 2015 by Richard Pennington
0

DWARF - How to find the prologue end/epilogue start addresses of functions in a given binary?

c
assembly
objdump
dwarf
readelf

Try

readelf -wi

And look for DW_AT_low_pc and DW_AT_high_pc for the subroutine you are looking at.

The DWARF spec says:

A subroutine entry may have either a DW_AT_low_pc and DW_AT_high_pc pair of attributes or a DW_AT_ranges attribute whose values encode the contiguous or non-contiguous address ranges, respectively, of the machine instructions generated for the subroutine (see Section 2.17).

If I remember correctly, the DW_AT_low_pc is the address immediately after the prologue and DW_AT_high_pc is the last address before the epilogue.

Don't worry about the opcodes being 'special' that just means that they don't take arguments to save space in the encoded line number program.

answered on Stack Overflow Sep 28, 2014 by Torleif
-2

Windows 7 Setup BSOD BAD_SYSTEM_CONFIG_INFO

windows-7
windows-xp
drivers
bsod

You can start to research the problem via this URL:

http://msdn.microsoft.com/en-gb/library/windows/hardware/ff559188%28v=vs.85%29.aspx

Good starting point

answered on Super User Sep 27, 2014 by Ben Lavender

Comments

Leave a comment

(plain text only)

Sources

  1. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx
  3. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0