I saw this problem on my Windows XP with latest NVIDIA drivers during shutdown, while Salamander was running.
We are not loading nview.dll directly so it looks it's loaded by somehow (third-party shell extension?), later unloaded due to shutdown, while Salamander is still running.
The real problem is that this library probably register some hook that is not unregistered in library unload section. So our process is calling unloaded dll.
Any idea when and why is nview.dll loaded into process? We need to reproduce this problem to be able fill bug for NVIDIA: http://www.nvidia.com/object/driverqual ... rance.html
Code: Select all
Information About Exception:
Exception: access violation: read on 0x010C3B80
Exception origin: thread ID = 0xC84, execution address = 0x010C3B80 (nview.dll: 0x73B80)
Call Stacks:
Thread with Exception (ID: 0xC84)
WinMainBody(0x400000, , , 7)
WinMainBody::FindLatestConfiguration
WinMainBody::StartupDialog
WinMainBody::inicialization
WinMainBody::load_config
WinMainBody::message_loop
Modules:
Unloaded Modules:
(15656 ms) 0x01050000 (size: 0x173000) (ver: 6.14.10.11154): nview.dll (C:\WINNT\system32\nview.dll)
(OR) (xxxx ms) 0x10000000 (size: 0x195000) (ver: 6.14.10.12524): nview.dll (C:\Program Files\NVIDIA Corporation\nView\nview.dll)
(15656 ms) 0x10000000 (size: 0x15000) (ver: 6.14.11.7431): nvwddi.dll (C:\WINNT\system32\nvwddi.dll)
Stack Back Trace:
Thread ID: 0xC84 (Thread with Exception)
EIP = 0x010C3B80 (UNLOADED: nview.dll)
0x7E42B317 USER32.dll
0x7E4278D0 USER32.dll
0x7C90E473 ntdll.dll
0x004D537D salamand.exe
0x7E431923 USER32.dll
0x7E42B317 USER32.dll
0x7E4278D0 USER32.dll
0x7C90E473 ntdll.dll
0x004CDE2F salamand.exe
0x004CE942 salamand.exe
0x00526646 salamand.exe
0x7C817077 kernel32.dll
----