iqdax BSOD

W1RE · May 2014

Flex 6700.

SSDT 1.2.1

Windows 8.1 x64

Please see below. Twice today I have had an iqdax BSOD. I have the memory.dmp (it's 2 GB!) if needed.

Loading Dump File [C:WindowsMEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available

************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred 1.SRV*C:Windowssymbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: 1.SRV*C:Windowssymbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 8 Kernel Version 9600 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
Machine Name:
Kernel base = 0xfffff800'5c074000 PsLoadedModuleList = 0xfffff800'5c33e2d0
Debug session time: Sun May 11 14:36:32.428 2014 (UTC - 4:00)
System Uptime: 0 days 0:41:06.193
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols

Loading unloaded module list
............

************* Symbol Loading Error Summary **************
Module name Error
ntkrnlmp The system cannot find the file specified

You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2, 2, 1, fffff8005c044450}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for hal.dll -
*** ERROR: Module load completed but symbols could not be loaded for iqdax.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information. Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information. Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information. Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information. Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information. Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information. Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information. Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information. Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information. Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information. Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information. Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that   ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information. Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   *

W1RE · May 2014

Apparently the community cuts off posts at a certain point. Here's the most important info for you: If you send me the symbols I can rerun the trace for you if you'd like.

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: iqdax

FAULTING_MODULE: fffff8005c074000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 52d59c2a

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
0000000000000002

CURRENT_IRQL: 0

FAULTING_IP:
hal!HalHandleNMI+85a0
fffff800'5c044450 1832 sbb byte ptr [rdx],dh

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff8005c1d3ae9 to fffff8005c1c7fa0

STACK_TEXT:
fffff800'5dd3d658 fffff800'5c1d3ae9 : 00000000'0000000a 00000000'00000002 00000000'00000002 00000000'00000001 : nt!KeBugCheckEx
fffff800'5dd3d660 fffff800'5c1d233a : 00000000'00000001 00000000'00000001 fffff800'5dd3d800 fffff800'5dd3d7a0 : nt!setjmpex+0x37e9
fffff800'5dd3d7a0 fffff800'5c044450 : fffff801'365f471a 00000000'000000ff 00000000'00000000 ffffe001'289f6010 : nt!setjmpex+0x203a
fffff800'5dd3d938 fffff801'365f471a : 00000000'000000ff 00000000'00000000 ffffe001'289f6010 ffffe001'289f6701 : hal!HalHandleNMI+0x85a0
fffff800'5dd3d940 fffff801'365f17a6 : ffffffff'fe5ce4d0 fffff800'5c0d1240 fffff800'5dd3db00 fffff800'5dd3db00 : iqdax+0x971a
fffff800'5dd3d970 fffff800'5c0cd810 : fffff800'5dd3db00 fffff800'5dd3dab0 ffffe001'289f6720 fffff800'5c35a180 : iqdax+0x67a6
fffff800'5dd3d9b0 fffff800'5c1cbaea : fffff800'5c35a180 fffff800'5c35a180 fffff800'5c3c1a00 ffffe001'24fd8880 : nt!KeRemoveQueueEx+0x3b80
fffff800'5dd3dc60 00000000'00000000 : fffff800'5dd3e000 fffff800'5dd38000 00000000'00000000 00000000'00000000 : nt!KeSynchronizeExecution+0x2efa

STACK_COMMAND: kb

FOLLOWUP_IP:
iqdax+971a
fffff801'365f471a 4883c428 add rsp,28h

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: iqdax+971a

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: iqdax.sys

BUCKET_ID: WRONG_SYMBOLS

FAILURE_BUCKET_ID: WRONG_SYMBOLS

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:wrong_symbols

FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}

Followup: MachineOwner
---------

0: kd> lmvm iqdax
start             end                 module name
fffff801'365eb000 fffff801'365f9a80   iqdax      (no symbols)
    Loaded symbol image file: iqdax.sys
    Image path: SystemRootsystem32DRIVERSiqdax.sys
    Image name: iqdax.sys
    Timestamp:        Tue Jan 14 15:20:58 2014 (52D59C2A)
    CheckSum:         00016858
    ImageSize:        0000EA80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Ed - W2RF · May 2014

I have never seen this. I have seen CWSkimmer cause a BSOD when I am using WDM audio output drivers to an M-Audio delta.

W1RE · May 2014

Thanks Ed. I believe your comment above may have helped me to understand why these crashes are occurring and (hopefully) avoid them going forward.

While playing with Bridge and Skimmer all weekend I was 'fiddling' with the skimmer audio settings. I changed them to experiment with skimmer's capabilities and changed one to use a 'sound card' attached to my monitor. I.e. my monitor has an integrated audio capability which is nice. The problem is all these crashes (and I had FOUR in a single day) occurred when I was powering off my monitor but leaving the system up and running. When I went back to check on things I notice the system had restarted.

I looked at all four crashes and they were all different and clearly not identical looking. That's strange because I hadn't had a single crash with this system before installing Bridge Skimmer, WriteLog and using SSDR IQDAX and yesterday I had four very bizzare crashes all quite different looking.

Your comment triggered my memory that I had made changes in the Audio setting of one of the skimmer panels so I went and put it back to the defaults. So far I have not had any new BSODs despite turning off my monitor and letting things run with it off.

Skimmer, being a user mode app, can't directly cause a BSOD in a protected mode OS like windows. It can however cause latent defects in the kernel or other device drivers to be exposed. I suspect that is the case here and that my skimmer configuration changes, combined with my turning off the monitor (which I suspect causes the integrated audio device to 'disappear' when powered down) caused the integrated Nvidia audio driver to corrupted memory/pool/TQEs in some way that cause iqdax.sys to trip over it and crash (iqdax is a victim no the real culprit). At least that is what I am hoping and I should be able to have better confidence that this is the case this in another day or two the longer I run w/o any new BSODs.

Thanks for the thoughts - I hope I am now on the path to stability.

- Bob

W1RE · May 2014

Tim,

I would like to withdraw this bug report. I had built a new system for SmartSDR and associated apps and found I had a HW issue that appears to be the root cause for this (and a few other) unexplained crashes. I have resolved the HW issues and SmartSDR is now running well with 8 pan adapters and 8 slice receivers, plus SDR Bridge and CW Skimmer without any crashes for several days. I also confirmed it is working on a totally separate system, so I have so I am confident this was a red herring.

Thanks,

- Bob

iqdax BSOD

Comments

Leave a Comment

Categories