none
WLK1.6: CHAOS Concurrent Hardware And OS Test fail and BSOD RRS feed

  • Question

  • When I test WLK1.6: CHAOS Concurrent Hardware And OS Test ,   SUT restart will BSOD 0xD1.

    Does any one know how to fix this issue?

       // Handle status
        //

        if (Status == STATUS_PENDING) {

            //
            // IO is queued, if device is not busy start it
            //

            if (StartIo) {
                AcpiEcServiceDevice (EcData);
            }

        } else { .......................................................................error occur

            IoCompleteRequest(Irp, IO_NO_INCREMENT);
        }

     

    and another

          //
            // While service invocation pending, loop
            //

            while (EcData->InServiceLoop) {
                EcData->InServiceLoop = FALSE;

                //
                // Determine service action
                //

                KeReleaseSpinLock (&EcData->Lock, OldIrql);

                //
                // Dispatch service handler
                //

                AcpiEcServiceIoLoop (EcData);

                //
                // Loop and re-service
                //

                KeAcquireSpinLock (&EcData->Lock, &OldIrql);......................................error occur

            }

     

    Thanks.

    Saturday, May 7, 2011 8:16 AM

Answers

  • jarvis.chen wrote:
    >
    >How can I check that, because I had no experience during coding driver?
     
    If you are not a driver developer, then you are not likely to be very
    successful in debugging a driver crash.  Are you a QA team?
    --
    Tim Roberts, timr@probo.com
    Providenza & Boekelheide, Inc.
     

    Tim Roberts, DDK MVP Providenza & Boekelheide, Inc.
    Tuesday, May 10, 2011 5:28 AM

All replies

  • jarvis.chen wrote:
    >
    >When I test WLK1.6: CHAOS Concurrent Hardware And OS Test ,   SUT restart will BSOD 0xD1.
    >
    >Does any one know how to fix this issue?
     
    Well, by debugging, basically.  You haven't given us very many clues, like
    the !analyze -v output.
     
    >        while (EcData->InServiceLoop) {
    >            EcData->InServiceLoop = FALSE;
    >
    >            //
    >            // Determine service action
    >            //
    >
    >            KeReleaseSpinLock (&EcData->Lock, OldIrql);
    >
    >            //
    >            // Dispatch service handler
    >            //
    >
    >            AcpiEcServiceIoLoop (EcData);
    >
    >            //
    >            // Loop and re-service
    >            //
    >
    >            KeAcquireSpinLock (&EcData->Lock, &OldIrql);......................................error occur
    >        }
     
    Is it possible the EcData structure gets freed during the execution of
    AcpiEcServiceIoLoop?
    --
    Tim Roberts, timr@probo.com
    Providenza & Boekelheide, Inc.
     

    Tim Roberts, DDK MVP Providenza & Boekelheide, Inc.
    Saturday, May 7, 2011 10:03 PM
  • How can I check that, because I had no experience during coding driver?

     

     thanks.

    Monday, May 9, 2011 12:54 AM
  • Another information.

    That should be point to kernel mode address not user mode address.

    Please tell me how should I fix it, if you know?

     

    Monday, May 9, 2011 1:31 AM
  • jarvis.chen wrote:
    >
    >How can I check that, because I had no experience during coding driver?
     
    If you are not a driver developer, then you are not likely to be very
    successful in debugging a driver crash.  Are you a QA team?
    --
    Tim Roberts, timr@probo.com
    Providenza & Boekelheide, Inc.
     

    Tim Roberts, DDK MVP Providenza & Boekelheide, Inc.
    Tuesday, May 10, 2011 5:28 AM
  • Hi Tim Roberts,

    Yes, I'm not a driver developer, and I am QA.

    I was be supported to fix the driver WHQL issue, but I really did not have any sense.

    Could you share the information to fix the issue?

     

    Thank you very much.


    Tuesday, May 10, 2011 8:49 AM
  • Hi, I am new to driver development and debugging.

    I too has BSOD on this test , and also on device path exerciser.

    Please let me have a hint to debugging tools

    How did you get from BSOD the hint to code lines? 

    I am interested because I too must find it, 

    I tried with winddb but could not find any precise hint from call stack.

    Thanks


    Thursday, February 7, 2013 3:46 PM