Windows error 0x00000053, 83

Detailed Error Information

FAIL_I24[1]

MessageFail on INT 24.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x80070053.

NO_BOOT_DEVICE[2]

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

HRESULT analysis[3]

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[3][1]
DescriptionThe default facility code.[3][1]
Error Code83 (0x0053)

Possible solutions

6

Analyzing a CLR .dmp file in WinDbg

c#
debugging
windbg

Managed code needs a matching platform of sos.dll for proper analysis. Use the 'x86' debugger.

You would have to use the x86 debugger/WinDbg to debug an x86 memory dump. Use .loadby sos mscorwks to load the appropriate sos. You could also verify if the extension is loaded properly by using the .chain command.

Tess has some good debugging tutorials.

answered on Stack Overflow Feb 27, 2011 by Naveen • edited May 7, 2017 by Peter Mortensen
4

Microsoft Advertising error

c#
xaml
uwp
advertising

yes other developers are seeing this issue, too.

Please upvote the problem here.

answered on Stack Overflow Dec 15, 2015 by Andreas Thenn • edited Dec 15, 2015 by elnigno
3

Analyzing a CLR .dmp file in WinDbg

c#
debugging
windbg

This tutorial is a good start to see some of the WinDbg commands. I think the following commands should show you the current stack trace:

.sympath SRV*d:\localsymbols*http://msdl.microsoft.com/download/symbols
!reload
.loadby sos mscorwks
K
answered on Stack Overflow Feb 26, 2011 by BrandonAGr • edited May 7, 2017 by Peter Mortensen
2

IMUL OllyDbg multiplication

assembly

The result of this multiplication does not fit into a 32-bit value, as a result the value you see in EAX is only the lower 4 bytes of the result.

Since this multiplication results in: 0x31367AA048, the lower 4 bytes:0x367AA048 are put into EAX, as you are seeing.

answered on Stack Overflow Jun 24, 2013 by Iridium
1

Analyzing a CLR .dmp file in WinDbg

c#
debugging
windbg

Debugging managed crash dumps in WinDbg requires additional modules (primarily SOS.dll) and commands.

Some good starting links are here.

answered on Stack Overflow Feb 25, 2011 by John Arlen
1

Missing source line information when analyzing minidump in WinDbg

c#
.net

The following worked:

Prerequisites: Debugging Tools for Windows installed

Managed interface C++/CLI

DbgHelpNet.h:

    // DbgHelpNet.h
#pragma once

#include <dbghelp.h>

using namespace System;
using namespace System;
using namespace System::IO;
using namespace System::Diagnostics;
using namespace System::Runtime::InteropServices;
using namespace System::Configuration;

namespace DbgHelpNet {

 /// <summary>Defines the information density of the mini dump (see MINIDUMP_TYPE on MSDN)</summary>
 public enum class MiniDumpTypeEnumeration
 {
  MiniDumpNormal                         = 0x00000000,
  MiniDumpWithDataSegs                   = 0x00000001,
  MiniDumpWithFullMemory                 = 0x00000002,
  MiniDumpWithHandleData                 = 0x00000004,
  MiniDumpFilterMemory                   = 0x00000008,
  MiniDumpScanMemory                     = 0x00000010,
  MiniDumpWithUnloadedModules            = 0x00000020,
  MiniDumpWithIndirectlyReferencedMemory = 0x00000040,
  MiniDumpFilterModulePaths              = 0x00000080,
  MiniDumpWithProcessThreadData          = 0x00000100,
  MiniDumpWithPrivateReadWriteMemory     = 0x00000200,
  MiniDumpWithoutOptionalData            = 0x00000400,
  MiniDumpWithFullMemoryInfo             = 0x00000800,
  MiniDumpWithThreadInfo                 = 0x00001000,
  MiniDumpWithCodeSegs                   = 0x00002000,
  MiniDumpWithoutAuxiliaryState          = 0x00004000,
  MiniDumpWithFullAuxiliaryState         = 0x00008000,    
  MiniDumpWithPrivateWriteCopyMemory     = 0x00010000,
  MiniDumpIgnoreInaccessibleMemory       = 0x00020000,
  MiniDumpValidTypeFlags                 = 0x0000ffff,
 };

 public ref class MiniDumpWriteDump
 {
 public:
  static void MiniDumpWriteDump::WriteDump(String^ path);
  static void MiniDumpWriteDump::WriteDump(String^ path, IntPtr exceptionPointers, MiniDumpTypeEnumeration MiniDumpType);
 };
}

DbgHelpNet.cpp:

    // This is the main DLL file.

#include "stdafx.h"

#include "DbgHelpNet.h"
#include <dbghelp.h>
#pragma comment( lib, "dbghelp")

namespace DbgHelpNet
{
 void MiniDumpWriteDump::WriteDump(String^ path)
 {
  IntPtr pep = System::Runtime::InteropServices::Marshal::GetExceptionPointers();
  WriteDump(path, IntPtr(pep), MiniDumpTypeEnumeration::MiniDumpWithFullMemory);
 }

 void MiniDumpWriteDump::WriteDump(String^ path, IntPtr exceptionPointers, MiniDumpTypeEnumeration MiniDumpType)
 {

  PEXCEPTION_POINTERS pep = reinterpret_cast<PEXCEPTION_POINTERS>(exceptionPointers.ToPointer());
  MINIDUMP_EXCEPTION_INFORMATION mdei = {GetCurrentThreadId(),pep,FALSE}; 
  MINIDUMP_TYPE miniDumpType = static_cast<MINIDUMP_TYPE>(MiniDumpType);

  System::IO::FileStream^ fileStream = File::Create( path );

  BOOL blnMiniDumpWriteDumpRetVal = ::MiniDumpWriteDump(
   GetCurrentProcess(),
   GetCurrentProcessId(), 
   fileStream->Handle.ToPointer(),
   miniDumpType,
   (pep != NULL) ? &mdei : NULL,
   NULL,
   NULL);

  fileStream->Close();

  if(blnMiniDumpWriteDumpRetVal)
  {
   Trace::WriteLine("Successfully created minidump.");
  }
  else
  {
   Trace::TraceError( String::Format("Failed to create minidump! Last Error: {0}",GetLastError() )); 
  }
 }
}

Test Code:

using System;
using System.Collections.Generic;
using System.Text;
using System.Runtime.InteropServices;
using System.IO;
using System.Diagnostics;

namespace MiniDumpTest
{
class Program {

    static void Main(string[] args) {
      AppDomain.CurrentDomain.UnhandledException += new UnhandledExceptionEventHandler(CurrentDomain_UnhandledException);        

      Console.WriteLine("started");

      try {
        Console.WriteLine(MyFunc());
      } finally {
        Console.WriteLine("finished");
        Console.ReadLine();
      }
    }

    static void CurrentDomain_UnhandledException(object sender, UnhandledExceptionEventArgs e) {
        Console.WriteLine("CurrentDomain_UnhandledException");

        DbgHelpNet.MiniDumpWriteDump.WriteDump(@"c:\temp\MyDump.dmp");

        Console.WriteLine("MiniDump written");
    }

    static int MyFunc() {
      int i = 0;
      ++i;
      if (i == 1) {
        throw new ApplicationException("bla");
      }

      return i;
    }
  }
}

Windbg (6.7.5.0): 0:000> k 100 ChildEBP RetAddr
0012f30c 79eda99c kernel32!RaiseException+0x53 0012f36c 79fb48f8 mscorwks!RaiseTheExceptionInternalOnly+0x2a8 0012f430 00d08408 mscorwks!JIT_Throw+0xfc 0012f448 00d000dc MiniDumpTest!MiniDumpTest.Program.MyFunc()+0x70 [c:\temp\MiniDumpTest\MiniDumpTest\Program.cs @ 40] 0012f480 79e71b4c MiniDumpTest!MiniDumpTest.Program.Main(System.String[])+0x6c [c:\temp\MiniDumpTest\MiniDumpTest\Program.cs @ 18] 0012f490 79e821f9 mscorwks!CallDescrWorker+0x33 0012f510 79e96571 mscorwks!CallDescrWorkerWithHandler+0xa3 0012f648 79e965a4 mscorwks!MethodDesc::CallDescr+0x19c 0012f664 79e965c2 mscorwks!MethodDesc::CallTargetWorker+0x1f 0012f67c 79eefac5 mscorwks!MethodDescCallSite::CallWithValueTypes+0x1a 0012f7e0 79eef9e5 mscorwks!ClassLoader::RunMain+0x223 0012fa48 79eeff35 mscorwks!Assembly::ExecuteMainMethod+0xa6 0012ff18 79ef011f mscorwks!SystemDomain::ExecuteMainMethod+0x456 0012ff68 79ef004f mscorwks!ExecuteEXE+0x59 0012ffb0 79007c24 mscorwks!_CorExeMain+0x15c 0012ffc0 7c817077 mscoree!_CorExeMain+0x2c 0012fff0 00000000 kernel32!BaseProcessStart+0x23

answered on Stack Overflow Oct 9, 2009 by Volker von Einem
0

Microsoft Advertising error

c#
xaml
uwp
advertising

I found this fix from the MS forums.. crazy as it seems it fixed my issue with AdMediator.

Install the below test app from the store. It will copy the correct files you need onto your PC. You can run it on your phone also.

After you install it, build and deploy your app to ensure it works now.

You can uninstall the app after if you like, its not required to keep.

https://www.microsoft.com/store/apps/9nblggh63jtn

Link to MS Forum article:

https://social.msdn.microsoft.com/Forums/en-US/28207687-df4e-4918-8aff-6cb2b71ac13a/ad-mediator-crashes-app-on-startup?forum=aiasdk&prof=required

answered on Stack Overflow Dec 25, 2015 by Yosem
0

how to find the caller function in shared library libev when the application crashes

gdb
shared-libraries

try to use bt - to check more frames

like bt -100 will give you 100 frames or you can use up 100

answered on Stack Overflow Apr 18, 2011 by Vijay

Comments

Leave a comment

(plain text only)

Sources

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

User contributions licensed under CC BY-SA 3.0