Windows error 0x000000E1, 225

Detailed Error Information

VIRUS_INFECTED[1]

MessageOperation did not complete successfully because the file contains a virus or potentially unwanted software.
Declared inwinerror.h

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

WORKER_THREAD_RETURNED_AT_BAD_IRQL[2]

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

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 Code225 (0x00e1)

Questions

0votes
2answers

How to access the full stack trace of mallocs in an MFC 8.0 application?

I'm trying to find a memory leak in a windows MFC 8.0 application (Release build). After failing to show the full stack trace of allocations using WinDbg (or umdh) due to VC8 CRT's malloc problem with FPO, I've tried to apply the solution proposed here (i.e. using LeakDiag with DbgHlp [...] read more
windows
debugging
visual-c++
memory-leaks
leakdiag

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