windbg - Sometimes Windows Crash while LabView operator Advantech PCI-1716 card -

the system include 2 advantech pci-1716 card:http://www.advantech.com/products/pci-1716/mod_86ec4c4d-f497-45c5-81da-b8600c0eb36f.aspx

i write program ni labview 7.1. labview program can control 2 pci 1716 card. work good.

but year later, computer crashed , auto restart. nobody change software , hardware.

i used windbg analysis windows crash dump file , think find abnormal.

for windbg result, think maybe pci-1716 driver broken re-installed it. problem happen.

and re-installed windows xp. problem happen again.

i don't know how.

maybe pci 1716 hardware broken. how find one,there 2 pci 1716 card.

the windbg result is:

loading dump file [f:\windbg\mini012313-01.dmp] mini kernel dump file: registers , stack trace available  symbol search path is: srv*c:\documents , settings\cky\symbols*http://msdl.microsoft.com/download/symbols executable search path is:  windows xp kernel version 2600 (service pack 2) mp (2 procs) free x86 compatible product: winnt, suite: terminalserver singleuserts built by: 2600.xpsp_sp2_rtm.040803-2158 kernel base = 0x804d8000 psloadedmodulelist = 0x8055d700 debug session time: wed jan 23 23:09:23.250 2013 (gmt+8) system uptime: 0 days 23:47:48.802 loading kernel symbols ....................................................................................................... loading user symbols loading unloaded module list .... ******************************************************************************* *                                                                             * *                        bugcheck analysis                                    * *                                                                             * *******************************************************************************  use !analyze -v detailed debugging information.  bugcheck 1000000a, {ffdf, 2, 1, 806e5a8e}  unable load image ads1716s.sys, win32 error 0n2 *** warning: unable verify timestamp ads1716s.sys *** error: module load completed symbols not loaded ads1716s.sys caused : ads1716s.sys ( ads1716s+f08 )  followup: machineowner ---------  0: kd> !analyze -v ******************************************************************************* *                                                                             * *                        bugcheck analysis                                    * *                                                                             * *******************************************************************************  irql_not_less_or_equal (a) attempt made access pageable (or invalid) address @ interrupt request level (irql) high.  caused drivers using improper addresses. if kernel debugger available stack backtrace. arguments: arg1: 0000ffdf, memory referenced arg2: 00000002, irql arg3: 00000001, bitfield :     bit 0 : value 0 = read operation, 1 = write operation   bit 3 : value 0 = not execute operation, 1 = execute operation (only on chips support level of status) arg4: 806e5a8e, address referenced memory  debugging details: ------------------   write_address:  0000ffdf   current_irql:  2  faulting_ip:  hal!keacquirequeuedspinlock+42 806e5a8e 8902            mov     dword ptr [edx],eax  customer_crash_count:  1  default_bucket_id:  driver_fault  bugcheck_str:  0xa  process_name:  labview.exe  last_control_transfer:  804efbb0 806e5a8e  stack_text:   aa286c00 804efbb0 aa286c20 804f0de4 aa286c1c hal!keacquirequeuedspinlock+0x42 aa286c08 804f0de4 aa286c1c 8602dc38 806e53b8 nt!ioacquirecancelspinlock+0xe aa286c20 804f104a 8602dc38 00000001 aa286c58 nt!iopstartnextpacket+0x18 aa286c30 f788ef08 8602dc38 00000001 85eb0230 nt!iostartnextpacket+0x38 warning: stack unwind information not available. following frames may wrong. aa286c58 80575529 85eb0230 86090da0 85f32448 ads1716s+0xf08 aa286c80 805d1cb9 85f32448 85f32448 85f32690 nt!iocancelthreadio+0x33 aa286d08 805d209a 00000001 85f32448 00000000 nt!pspexitthread+0x403 aa286d28 805d2275 85f32448 00000001 aa286d64 nt!pspterminatethreadbypointer+0x52 aa286d54 8054160c 00000000 00000001 0012e810 nt!ntterminateprocess+0x105 aa286d54 7c92eb94 00000000 00000001 0012e810 nt!kifastcallentry+0xfc 0012e810 00000000 00000000 00000000 00000000 0x7c92eb94   stack_command:  kb  followup_ip:  ads1716s+f08 f788ef08 ??              ???  symbol_stack_index:  4  symbol_name:  ads1716s+f08  followup_name:  machineowner  module_name: ads1716s  image_name:  ads1716s.sys  debug_flr_image_timestamp:  45b96de9  failure_bucket_id:  0xa_w_ads1716s+f08  bucket_id:  0xa_w_ads1716s+f08  followup: machineowner ---------  0: kd> lmvm ads1716s start    end        module name f788e000 f7893ac0 ads1716s t (no symbols)                loaded symbol image file: ads1716s.sys     image path: ads1716s.sys     image name: ads1716s.sys     timestamp:        fri jan 26 10:56:41 2007 (45b96de9)     checksum:         00010c75     imagesize:        00005ac0     translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0 

i'd run memtest86+ see if have bad ram.

following maybe can pull 1 card out , write simple script i/o (similar you're doing maybe). if takes while put loop , run while , see if can force crash. repeat test on each card see if have issues 1 of cards.

does crash happen or rarely?