What does this Windows crash dump mean?

0

Yesterday my system software got crashed on WINDOWS 2003 server. The Core shown below.

  kernel32.dll!_RaiseException@16()  + 0x3c bytes 

  rpcrt4.dll!_RpcpRaiseException@4()  + 0x21 bytes 

  rpcrt4.dll!_NdrGetBuffer@12()  - 0x1d3fe bytes 

  rpcrt4.dll!_NdrClientCall2()  + 0x132 bytes 

  hnetcfg.dll!_FwOpenDynamicFwPort@16()  + 0x1d bytes 

  hnetcfg.dll!_IcfOpenDynamicFwPort@12()  + 0x6a bytes 

  mswsock.dll!_WSPBind@16()  + 0xa55 bytes 

  ws2_32.dll!_bind@12()  + 0x4e bytes 

  sal.dll!s_SktBind(s_Socket * sp=0x05943800, SAL_AddrBuf_t 
* addrp=0x057cfe00,unsigned int addrsz=0x00000042)  Line 76 + 0x14 bytes C++

  sal.dll!SAL_SktBind(SAL_SktHandle_t * sh=0x05943800, SAL_AddrBuf_t 
*addrp=0x057cfe00, unsigned int addrsz=0x00000042)  Line 101 + 0xe bytes C++

Note: sal.dll is my software module. it is calling System Call bind() from our function SktBind()

Could you please tell, why it was crashed ? and how can I solve this problem.

If you have any comments or suggestion , please share with me.

crash
windows-server-2003
crash-dumps
asked on Stack Overflow Jan 10, 2010 by SIVA • edited Jan 10, 2010 by itowlson

4 Answers

1

The call to bind() from function s_SktBind() in sal.dll has caused the crash.

The first thing I would check is that you bind() is being called with proper arguments.

answered on Stack Overflow Jan 10, 2010 by R Samuel Klatchko
0

This doesn't look like kernel programming to me (re the tag).

Which process faulted? Looks like your program, since you have line number info.

What was the fault? AV? Or some other exception?

Paste the line and surrounding code that crashed. (Line 101 of the file that defines SAL_SktBind).

answered on Stack Overflow Jan 10, 2010 by Alex Budovski
0

hnetcfg.dll is a process associated with Home Networking Configuration Manager from Microsoft Corporation.

Search Microsoft support for relevant articles (e.g. maybe this one)

The code that is the origin of the problem seems to be dealing with networking. Is this correct?

answered on Stack Overflow Jan 10, 2010 by John K
0

I don't think you have posted the full call stack, but sal.dll is a dll that is provided by Novell and this is from where the error originates. So you might want to check if a newer version of this dll is available.

answered on Stack Overflow Jan 11, 2010 by steve

User contributions licensed under CC BY-SA 3.0