STOP 0xD1

Archived from groups: microsoft.public.windowsxp.device_driver.dev,microsoft.public.windowsxp.general,microsoft.public.windowsxp.help_and_support (More info?)

I am developing a application that does simple management of interfaces,
send udp packets among other things
When I shutdown the application, I call exit(0).
Occasionally I get one of the following Stop errors

STOP: 0x000000D1 (0xE1229000, 0x00000002, 0x00000001, 0xBF873C74)
win32k.sys - Address BF873C74 base at BF800000, DateStamp 3f73195d

STOP: 0x000000D1 (0x7E62D09, 0x00000000, 0x00000001, 0X77E62D09)
(in this case there is no driver file indication)

This occurs immediately after the call to exit(0). What is the exact
processing in exit() so that I can trace back my code to see if I am doing
some thing wrong. Or what is the likely cause for this situation?
thanks
ravi
2 answers Last reply
More about stop 0xd1
  1. Archived from groups: microsoft.public.windowsxp.device_driver.dev,microsoft.public.windowsxp.general,microsoft.public.windowsxp.help_and_support (More info?)

    See:
    http://aumha.org/win5/kbestop.php#0xd1
    --
    Cari
    MS-MVP Windows Technologies - Printing/Imaging/Hardware
    www.coribright.com
    "Ravi" <arensun@yahoo.com> wrote in message
    news:%23Y9icyuMEHA.3668@TK2MSFTNGP11.phx.gbl...
    >I am developing a application that does simple management of interfaces,
    > send udp packets among other things
    > When I shutdown the application, I call exit(0).
    > Occasionally I get one of the following Stop errors
    >
    > STOP: 0x000000D1 (0xE1229000, 0x00000002, 0x00000001, 0xBF873C74)
    > win32k.sys - Address BF873C74 base at BF800000, DateStamp 3f73195d
    >
    > STOP: 0x000000D1 (0x7E62D09, 0x00000000, 0x00000001, 0X77E62D09)
    > (in this case there is no driver file indication)
    >
    > This occurs immediately after the call to exit(0). What is the exact
    > processing in exit() so that I can trace back my code to see if I am doing
    > some thing wrong. Or what is the likely cause for this situation?
    > thanks
    > ravi
    >
    >
    >
    >
  2. Archived from groups: microsoft.public.windowsxp.device_driver.dev,microsoft.public.windowsxp.general,microsoft.public.windowsxp.help_and_support (More info?)

    Thanks Cari for the link. I have read the same, and doesn't seem to be the
    same as the one that I have.
    I did some additional debugging of the stack trace and all seem to point the
    function call ExitProcess(). Following is the stack trace obtained from the
    memory.dmp

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at
    an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 77f9c266, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000000, value 0 = read operation, 1 = write operation
    Arg4: 77f9c266, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: 77f9c266

    CURRENT_IRQL: 2

    FAULTING_IP:
    ntdll!RtlDetectHeapLeaks+0
    77f9c266 ?? ???

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    TRAP_FRAME: eff27d64 -- (.trap ffffffffeff27d64)
    ErrCode = 00000004
    eax=00000000 ebx=00000000 ecx=0012ec58 edx=7ffe0304 esi=77f5c448
    edi=00000001
    eip=77f9c266 esp=0012ebec ebp=0012ec60 iopl=0 nv up ei pl zr na po
    nc
    cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000
    efl=00010246
    ntdll!RtlDetectHeapLeaks:
    001b:77f9c266 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 77f62744 to 77f9c266

    STACK_TEXT:
    0012ebe8 77f62744 00000001 77f5c448 00000000 ntdll!RtlDetectHeapLeaks
    0012ec60 77e798cc 0012f1cc 00000001 00000000 ntdll!LdrShutdownProcess+0x29
    0012ed50 77e7990f 00000001 77e8f3b0 ffffffff kernel32!_ExitProcess+0x37
    0012ed64 77c379c8 00000001 77c37ad9 00000001 kernel32!TerminateProcess
    0012ed6c 77c37ad9 00000001 00528bff 77c37aea msvcrt!__crtExitProcess+0x2f
    0012ed78 77c37aea 00000001 00000000 00000000 msvcrt!_cinit+0xe4
    0012ed88 0041a58e 00000001 007b70c0 00000001 msvcrt!exit+0xe
    WARNING: Stack unwind information not available. Following frames may be
    wrong.
    0012eda0 00414b56 007be860 00220037 00000001 client+0x1a58e
    0012edc0 005b4e5f 007be860 00220037 00000001 client+0x14b56
    0012edd8 005b4a5d 007b70c0 00220020 007b60b2 foxdll+0x94e5f
    0012edf8 00524b22 007b70c0 00220020 007b60b2 foxdll+0x94a5d
    0012ee24 0052459a 007b70c0 00010000 007b60b2 foxdll+0x4b22
    0012ee44 00619e55 007b70c0 00010000 007b60b2 foxdll+0x459a
    0012ee6c 00618b6a 007b6028 00010000 007b60b2 foxdll+0xf9e55
    0012ee8c 0053f0a3 007b6028 00010000 007b60b2 foxdll+0xf8b6a
    0012eeac 005d89e3 007b6028 00010000 007b60b2 foxdll+0x1f0a3
    0012eecc 0060b05c 007b6028 00010000 007b60b2 foxdll+0xb89e3
    0012eeec 005a5ed6 007b6028 00010000 007b60b2 foxdll+0xeb05c
    0012ef0c 00414b70 007b6028 00010000 007b60b2 foxdll+0x85ed6
    0012ef2c 005291f0 007b6028 00010000 007b60b2 client+0x14b70
    0012f020 00414920 000f00ec 00000100 00000051 foxdll+0x91f0
    0012f140 00528c23 000f00ec 00000100 00000051 client+0x14920
    0012f158 77d43a50 000f00ec 00000100 00000051 foxdll+0x8c23
    0012f184 77d43b1f 00528bff 000f00ec 00000100 USER32!InternalCallWinProc+0x1b
    0012f1ec 77d43d79 00000000 00528bff 000f00ec
    USER32!UserCallWinProcCheckWow+0x150
    0012f24c 77d44374 0012f278 00000001 0052796d
    USER32!DispatchMessageWorker+0x306
    0012f258 0052796d 0012f278 007b6028 0012f294 USER32!DispatchMessageA+0xb
    0012f268 00527bb2 0012f278 007b6028 000f00ec foxdll+0x796d
    0012f294 00527a46 007b6028 00000002 007b6096 foxdll+0x7bb2
    0012f2c8 0041bfac 70a9f1ab 80000002 7ffdf000 foxdll+0x7a46
    0012ff4c 00470ba5 00000001 007b4850 007b2968 client+0x1bfac
    0012ffc0 77e814c7 70a9f1ab 80000002 7ffdf000 client+0x70ba5
    0012fff0 00000000 00470ac2 00000000 78746341 kernel32!BaseProcessStart+0x23


    FAILED_INSTRUCTION_ADDRESS:
    ntdll!RtlDetectHeapLeaks+0
    77f9c266 ?? ???

    FOLLOWUP_IP:
    ntdll!RtlDetectHeapLeaks+0
    77f9c266 ?? ???

    FOLLOWUP_NAME: MachineOwner

    SYMBOL_NAME: ntdll!RtlDetectHeapLeaks+0

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .trap ffffffffeff27d64 ; kb

    BUCKET_ID: INVALID_KERNEL_CONTEXT

    MODULE_NAME: Unknown_Module

    Followup: MachineOwner

    "Cari (MS-MVP)" <Newsgroups1@coribright.com> wrote in message
    news:etfvWP6MEHA.2628@TK2MSFTNGP12.phx.gbl...
    > See:
    > http://aumha.org/win5/kbestop.php#0xd1
    > --
    > Cari
    > MS-MVP Windows Technologies - Printing/Imaging/Hardware
    > www.coribright.com
    > "Ravi" <arensun@yahoo.com> wrote in message
    > news:%23Y9icyuMEHA.3668@TK2MSFTNGP11.phx.gbl...
    > >I am developing a application that does simple management of interfaces,
    > > send udp packets among other things
    > > When I shutdown the application, I call exit(0).
    > > Occasionally I get one of the following Stop errors
    > >
    > > STOP: 0x000000D1 (0xE1229000, 0x00000002, 0x00000001, 0xBF873C74)
    > > win32k.sys - Address BF873C74 base at BF800000, DateStamp 3f73195d
    > >
    > > STOP: 0x000000D1 (0x7E62D09, 0x00000000, 0x00000001, 0X77E62D09)
    > > (in this case there is no driver file indication)
    > >
    > > This occurs immediately after the call to exit(0). What is the exact
    > > processing in exit() so that I can trace back my code to see if I am
    doing
    > > some thing wrong. Or what is the likely cause for this situation?
    > > thanks
    > > ravi
    > >
    > >
    > >
    > >
    >
    >
Ask a new question

Read More

Drivers Microsoft Device Driver Windows XP