NDXMERLIN: computer crash in nport driver

[FreddieAkeroyd]

The NDXMERLIN computer crashed this morning due to a bugcheck in the moxa npdrv.sys Analysis of minidump gave

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [\\isis\shares\ISIS_Experimental_Controls\MERLIN dumps\Minidump\071219-15718-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'x:\'
Symbol search path is: SRV*c:\web_symbols*\\isis\inst$\Kits$\CompGroup\ICP\EPICS\Symbols*http://msdl.microsoft.com/download/symbols;x:\
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.24308.amd64fre.win7sp1_ldr.181111-0600
Machine Name:
Kernel base = 0xfffff800`02c5f000 PsLoadedModuleList = 0xfffff800`02e98c90
Debug session time: Fri Jul 12 09:56:49.767 2019 (UTC + 1:00)
System Uptime: 20 days 4:25:07.538
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa80adb6f628, 2, 1, fffff88002c60a2b}

Unable to load image npdrv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for npdrv.sys
*** ERROR: Module load completed but symbols could not be loaded for npdrv.sys
Probably caused by : npdrv.sys ( npdrv+9a2b )

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

0: 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: fffffa80adb6f628, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88002c60a2b, address which referenced memory

Debugging Details:
------------------

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efc100
 fffffa80adb6f628 

CURRENT_IRQL:  2

FAULTING_IP: 
npdrv+9a2b
fffff880`02c60a2b 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  TPG300-IOC-01.

TRAP_FRAME:  fffff8800c67e700 -- (.trap 0xfffff8800c67e700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80adb6f628 rbx=0000000000000000 rcx=fffffa800e7a7730
rdx=fffffa8018321630 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002c60a2b rsp=fffff8800c67e890 rbp=fffff8800c67eb60
 r8=fffffa801168c470  r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
npdrv+0x9a2b:
fffff880`02c60a2b 488908          mov     qword ptr [rax],rcx ds:fffffa80`adb6f628=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d00d69 to fffff80002cf29a0

STACK_TEXT:  
fffff880`0c67e5b8 fffff800`02d00d69 : 00000000`0000000a fffffa80`adb6f628 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0c67e5c0 fffff800`02cfeb88 : 00000000`00000001 fffffa80`adb6f628 00000000`00000000 fffffa80`18321630 : nt!KiBugCheckDispatch+0x69
fffff880`0c67e700 fffff880`02c60a2b : 00000000`00000103 fffffa80`18321630 fffffa80`0cb891c0 00000000`00000000 : nt!KiPageFault+0x448
fffff880`0c67e890 00000000`00000103 : fffffa80`18321630 fffffa80`0cb891c0 00000000`00000000 fffffa80`18321630 : npdrv+0x9a2b
fffff880`0c67e898 fffffa80`18321630 : fffffa80`0cb891c0 00000000`00000000 fffffa80`18321630 fffff800`02ccff50 : 0x103
fffff880`0c67e8a0 fffffa80`0cb891c0 : 00000000`00000000 fffffa80`18321630 fffff800`02ccff50 fffffa80`00000000 : 0xfffffa80`18321630
fffff880`0c67e8a8 00000000`00000000 : fffffa80`18321630 fffff800`02ccff50 fffffa80`00000000 fffffa80`18321630 : 0xfffffa80`0cb891c0

STACK_COMMAND:  kb

FOLLOWUP_IP: 
npdrv+9a2b
fffff880`02c60a2b 488908          mov     qword ptr [rax],rcx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  npdrv+9a2b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: npdrv

IMAGE_NAME:  npdrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5136ed0a

FAILURE_BUCKET_ID:  X64_0xD1_npdrv+9a2b

BUCKET_ID:  X64_0xD1_npdrv+9a2b

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

[Tom-Willemsen]

This is in progress but no-one is assigned. Is any one looking at this?

[FreddieAkeroyd]

I think it is one to discuss with @ChrisM-S so will put into impeded for now

[ChrisM-S]

We committed to install the newest MOXA driver on MERLIN because although it is probably not the cause of the crash, the driver in the newer version (tested during the previous cycle on MUSR) may well be more robust and have a means of handling whatever exception occurred.

the kit is in the installs area

...\Applications\LabVIEW\Other bits\LabVIEW related\MOXA\MOXA NPort

and

drvmgr_setup_Ver3.0_Build_18081311_whql.exe

is the newest tested version and the one to install.

1) It will need checking out/exercising with IBEX after installation. 2) It would be worth checking the current version installed first, just in case it is necessary to regress. 3) Note that the package name has changed from "Admin Suite" to "Driver Manager". Seems to be the same software though.

[John-Holt-Tessella]

Instrument scientists contacted.

[John-Holt-Tessella]

Previous version: NPort Administration Suite Ver1.19.7 Current version 3.0

Documentation: https://github.com/ISISComputingGroup/ibex_developers_manual/wiki/NPort-install Instrument scientists informed.