none
System crush immediately occurs when SDR ethernet adapter is on.

    Question

  • Hello, again.

     

    I'm trying to communication between SORA client and commercial 802.11 device. But i keep encountering the same system crush.

    i've already done what you've said in this forum when system crush occurs. But these are not working.

    At this point where the SDR ethernet adapter, not HWTest adapter, is added, system crash always occurs. 

    I'll attach mini dump of this crush and my computer configuration.

     

    if there is any one who has the same experience with the above or knows the solution, please help me.

     

    -- MINI DUMP

     

     

    Loading Dump File [C:\WINDOWS\Minidump\Mini081110-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

     

    Symbol search path is: C:\WINDOWS\Symbols

    Executable search path is: 

    Unable to load image ntoskrnl.exe, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for ntoskrnl.exe

    Windows XP Kernel Version 2600 (Service Pack 3) MP (8 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Machine Name:

    Kernel base = 0x804d9000 PsLoadedModuleList = 0x8055f720

    Debug session time: Wed Aug 11 16:07:20.625 2010 (UTC + 9:00)

    System Uptime: 0 days 1:04:59.212

    Unable to load image ntoskrnl.exe, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for ntoskrnl.exe

    Loading Kernel Symbols

    ...............................................................

    .............................................................

    Loading User Symbols

    Loading unloaded module list

    ...................

    Unable to load image SDRMiniport.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for SDRMiniport.sys

    *** ERROR: Module load completed but symbols could not be loaded for SDRMiniport.sys

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    Use !analyze -v to get detailed debugging information.

     

    BugCheck 100000D1, {78, 1c, 0, ae5dd7b8}

     

    Probably caused by : SDRMiniport.sys ( SDRMiniport+27b8 )

     

    Followup: MachineOwner

    ---------

     

    2: kd> !analyze -v

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    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: 00000078, memory referenced

    Arg2: 0000001c, IRQL

    Arg3: 00000000, value 0 = read operation, 1 = write operation

    Arg4: ae5dd7b8, address which referenced memory

     

    Debugging Details:

    ------------------

     

     

    READ_ADDRESS:  00000078 

     

    CURRENT_IRQL:  1c

     

    FAULTING_IP: 

    SDRMiniport+27b8

    ae5dd7b8 8b82d8000000    mov     eax,dword ptr [edx+0D8h]

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  DRIVER_FAULT

     

    BUGCHECK_STR:  0xD1

     

    PROCESS_NAME:  System

     

    LAST_CONTROL_TRANSFER:  from ae5dd6aa to ae5dd7b8

     

    STACK_TEXT:  

    WARNING: Stack unwind information not available. Following frames may be wrong.

    afc7cd44 ae5dd6aa 00000004 a746d944 00000000 SDRMiniport+0x27b8

    afc7cd58 ae5dda09 00000004 00000000 875d207c SDRMiniport+0x26aa

    afc7cdac 805d1f64 875d2078 00000000 00000000 SDRMiniport+0x2a09

    afc7cddc 805480de ae5dd950 875d2078 00000000 nt!IopQueryReconfiguration+0x17

    afc7cdf8 00000000 00000000 00000000 00001f80 nt!ExpRemovePoolTracker+0x6b

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP: 

    SDRMiniport+27b8

    ae5dd7b8 8b82d8000000    mov     eax,dword ptr [edx+0D8h]

     

    SYMBOL_STACK_INDEX:  0

     

    SYMBOL_NAME:  SDRMiniport+27b8

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: SDRMiniport

     

    IMAGE_NAME:  SDRMiniport.sys

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4c624bc9

     

    FAILURE_BUCKET_ID:  0xD1_SDRMiniport+27b8

     

    BUCKET_ID:  0xD1_SDRMiniport+27b8

     

    Followup: MachineOwner

    ---------

     

    2: kd> lmvm SDRMiniport

    start    end        module name

    ae5db000 aea49100   SDRMiniport T (no symbols)           

        Loaded symbol image file: SDRMiniport.sys

        Image path: SDRMiniport.sys

        Image name: SDRMiniport.sys

        Timestamp:        Wed Aug 11 16:05:45 2010 (4C624BC9)

        CheckSum:         0047D7E2

        ImageSize:        0046E100

        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4





    -- PC Configuration

     

    CPU : Intel I7 Lynnfield  930

    MainBoard : ASUS P6X58D-E STCOM

    RAM : Samsung DDR3 2G PC3-10600

    OS : Window XP SP 3 32bit

     

     

    Friday, August 13, 2010 5:54 AM

Answers

All replies

  • Hi, your case is almost the same as Kim's.

    We're trying to figure out the exact cause now.

    Please stay tuned.

    I'll update you about the progress.

    Friday, August 13, 2010 11:43 AM
    Owner
  • Hi,

    I'm having the same issue. Just downloaded ans installed the v1.1 SDK, compiled the samples, etc. HWTest and PCIE drivers load successfully but when adding the Miniport driver, I get an instant BSOD. I'm using a C2D E6600 machine, WinXP Pro x86 SP3, 4GB RAM. Here is the minidump file: http://db.tt/1qTi2Bq

    Any ideas?

    Regards,

    Thursday, December 23, 2010 6:16 PM
  • abr28 , could you share the matched sdrminiport.pdb? thanks

    Sen

    Sunday, December 26, 2010 6:07 PM
    Moderator
  • From the minidump, crashed module belongs to windows kernel.

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    f792ad2c 805379ba 80564c50 80564c48 8053ff83 nt+0x603ee
    f792adac 805cff62 00000000 00000000 00000000 nt+0x609ba
    f792addc 8054611e 8053fef6 00000000 00000000 nt+0xf8f62
    00000000 00000000 00000000 00000000 00000000 nt+0x6f11e

    It seems a different issue.

    Sunday, December 26, 2010 6:36 PM
    Moderator
  • Well, the crash only happens when that driver is used, the system is fine otherwise and never BSODs. It can't be a different issue. The pdb is:

    chk: http://db.tt/HSi4Nqr
    fre: http://db.tt/cjRcKbx

    I will try the board in a Quad Core C2D (Q6600) and let you know. Is Sora supposed to work ok in Dual Core C2D systems (E6600)?

    Wednesday, January 05, 2011 4:51 PM
  • I tried with a Q6600 (quad core, core 2 duo) with a fresh win xp pro sp3 installation (+ all updates) and it crashes the moment i insert the miniport driver. Here are the crash dump and the pdb files: http://db.tt/kfw2Woo

    Is there a quick way to make sure that the board actually works (tx / rx)?

    Tuesday, January 11, 2011 3:27 PM
  • bump ... anyone?
    Monday, January 17, 2011 5:18 PM
  • could you try hwtest device?

    btw, is your xp of english version?

    Thursday, January 20, 2011 5:03 AM
    Moderator
  • Tuesday, February 15, 2011 4:18 AM
    Moderator
  • could you try hwtest device?

    btw, is your xp of english version?


    How to test the hwtest device? I haven't found any proper test method or documentation ... can you please give a step by step method of testing and making it work please? until now I've noticed only short answers that didn't get me anywhere.

    The solutions you were pointing to above do not work. Also, if you debug the minidump it says that the possible cause is the sdrminiport driver.

    My XP is english, yes.
    Tuesday, February 22, 2011 7:51 PM
  • abr28:

    I am a little confused due to the long thread. Could you send me email about your problem to senxiang AT microsoft dot com.

    Thanks for your feedback.

    sen


    Sen Xiang (项森)
    Wednesday, February 23, 2011 3:51 AM
    Moderator