Discussion in 'Windows Vista Drivers' started by Peter, Apr 2, 2006.

  1. Peter

    Peter Guest

    I met following error. It occurres only sometimes in calling
    DeviceIoControl() to my IM ndis driver with different control codes, not
    How can I to solve this problem ?

    This is a kernel internal error which can occur only on a checked build.
    The most common reason to see such a bugcheck would occur when a
    filesystem had a mismatched number of KeEnterCriticalRegion calls compared
    to KeLeaveCriticalRegion calls. This check is made on exit from a system
    Arg1: 812f984a, address of system function (system call)
    Arg2: 00000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
    Arg3: 0000ffff, Thread->KernelApcDicable
    Arg4: 00000000, Previous KernelApcDisable
    Peter, Apr 2, 2006
    1. Advertisements

  2. You have to debug to find out information about the thread and owning
    process and see if that's yours. Then you have to narrow it down to a
    specific request. Somebody disabled KernelApc and forgot to reenable. Turn
    on driver verifier on NDIS and your driver.
    Eliyas Yakub [MSFT], Apr 3, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.