Switch Hardware and Software

cancel
Showing results for 
Search instead for 
Did you mean: 

LV 8.2 niswdk.dll crash

Sorry about the delay in re-posting the crash data. I will get it up there this weekend (from my house). Our proxy servers horribly mangle long FTP sessions.

I figured as much with the MXI connection being severed. I have done hot-swapping in PCI systems before using older, DOS-based OSes (like Win9x). I'm guessing that the newer NT/2000/XP kernels get a bit cheekey when this happens, though.
--

Brian Rose
0 Kudos
Message 11 of 16
(5,787 Views)
The crashdump is now posted. I tested it by downloading it and I can open the ZIP file.

Enjoy!
--

Brian Rose
0 Kudos
Message 12 of 16
(5,774 Views)

Hi Brian,

I finally got around to testing the crash in my free time.  Was RelayOperate.vi the only VI in the .zip file?  It was the only one I found.  Earlier in your posts, you described a procedure consisting of the following:

a) Start machine
b) Turn off PXI chassis
c) wait 30 sec
d) Turn on PXI chassis
e) wait 30 sec
f) run application (no problem)
g) wait 30 sec
h) begin UUT test (crash!)

I was hoping to reproduce the issue.  I'm assuming the UUT test is performed by running RelayOperate.vi.  Is this a correct assumption?  In any case, I followed this procedure:

a) Start machine
b) Turn off PXI chassis
c) wait 30 sec
d) Turn on PXI chassis
e) wait 30 sec
f) run RelayOperate.vi (Error -200221 Max time exceeded)

Because the PXI chassis no longer communicates with the host computer, I expect this error.  Is there anything else I should've done in order to get the blue screen?

Please let me know.  Thanks!

Chad Erickson
Switch Product Support Engineer
NI - USA

0 Kudos
Message 13 of 16
(5,736 Views)

That should have triggered it. Perhaps the problem is elsewhere. I can send you other VIs, but they all use RelayOperate. The only other function in the PXI chassis is RS-232, but I would expect the problem in the NI-Serial module, not the NI-Switch module.

Also, in my "run application" step the software resets the switch cards. Perhaps that is needed as a precursor to the crash?

I can't attach the full application (too big). Does the crashdump give you a stack trace that tells you what VIs are involved?
--

Brian Rose
0 Kudos
Message 14 of 16
(5,726 Views)
I'm having the same problem.  I've had multiple blue screens with the "niswdk.dll" error.  My problem was intermittent on one computer.  I have had two other supposedly identical computers (same model #, same windows load) running the same hardware/software combo and had no issues.  A third computer with a new PXI chassis is giving me repeated unavoidable blue screens.
 
I sent this email to my NI field sales engineer asking for help:
 

Actually, my computer blue screens every time I send a command to the RF switch. I just started testing this system using my desktop computer with an ExpressCard adapter that we received with the previous order and a third party pcie to expresscard card. We have had an inordinately difficult time getting these PXI chassis's to work reliably and really wish they could have had boring old GPIB communication.

Our steps so far, in chronological order:

1.) Test 1033 chassis 1 & 2 in my desktop computer using expresscard adapter and a third party pcie to expresscard card. They both worked fine over the short duration of this test.

2.) Test 1033 chassis 1 & 2 in lab computer #1 using expresscard adapter and a third party pcie to expresscard card. They both worked fine over the short duration of this test.

3.) Test 1033 chassis 3 in my desktop using expresscard adapter and a third party pcie to expresscard card. It worked fine over the short duration of this test.

4.) Test 1033 chassis 3 in lab computer #2 using NI pcie card. It worked fine over the short duration of this test.

5.) Had problems with PCIe communication related to duplicate aliases between DAQmx devices and PXI System under measurement and automation explorer which you helped resolve.

6a.) Failed attempt at long term testing using 1033 chassis 1 & 2 in lab computer #1 using expresscard adapter and a third party pcie to expresscard card. Computer would blue screen periodically in unpredictable timing. Sometimes it would be after running for 1 hr, other times after a couple days.

7a.) Failed attempt at long term testing using 1033 chassis 1 & 2 in lab computer #1 using NI pcie card. Computer would blue screen periodically in unpredictable timing. Sometimes it would be after running for 1 hr, other times after a couple days.

6b,7b.) While lab computer #1 was failing to run its test, lab computer #2 with 1033 chassis 3 was running fine for ~ 2 weeks continuously with no blue screens. When we changed lab computer #1's PCIe adapter from the expresscard to the NI PCIe card, we swapped lab computer #2's from the NI PCIe card to the expresscard PCIe adapter.

8.) We swapped lab computer #1 with a new computer, lab computer #3. Please note that all three lab computers were identical Dell desktops with identical windows profiles loaded. We then let 1033 chassis 3 in lab computer #2 using expresscard adapter and a third party pcie to expresscard card and 1033 chassis 1 & 2 in lab computer #3 using NI pcie card run and both computers have now worked fine for ~ 1 week continuously. They are currently still running.

9.) Test 1045 RF switch chassis in my desktop using expresscard adapter and a third party pcie to expresscard card. My computer has blue screened each time I've tried to communicate with the chassis. Each switch successfully passed their self tests. The last time it blue screened it came up with an error which mentioned "niswdk.dll Address A67A07FA base at F6788000". After I rebooted and windows came back up I got the attached windows errors.

Please also note that the software running the two 1033 chassis's on the lab computers was the identical labview routine. The 1045 failures occur both using measurement and automation explorer to activate the switch as well as using the switch executive vi drivers.

I do not have a solution to the issue in item #9 and am highly reluctant to stop and/or modify the tests running well in item #8. My only ideas for fixing #9 are:

a.) test the new chassis using a new computer (which we'd need to purchase & load) this would be a major headache.

b.) purchase a new NI PCIe card to replace the expresscard adapter and third party pcie to expresscard card. This seems unlikely to produce a positive result given the testing performed above.

#9 just appeared this morning, and we had managed to get by before without calling you. Any help you could provide to address these issues would be greatly appreciated.

Dave

drines@luxtera.com

0 Kudos
Message 15 of 16
(4,861 Views)

Hi Dave,

I spoke with one of my coworkers, Neal, and he said you guys resolved the problem on the phone. It looks like the blue screens were caused by turning on the PXI chassis after the computer. The PXI chassis should always be powered on before powering on the computer. If this problem comes back up please let us know. Have a great weekend and take care.

Thanks,

Nathan
NI Chief Hardware Engineer
0 Kudos
Message 16 of 16
(4,847 Views)