I tried contacting Trendnet's tech support, but the person there simply
wouldn't understand that it's impossible for an application to crash a
driver. He thought the problem was with the application.

The application in this case is mldonkey, a p2p client.

So, I'm posting my problem here for the unlikely event a developer of
the driver reads it (it uses a SIS chip, and they made the driver).

Here's a crash analysis dump:

---------------------
Microsoft (R) Windows Debugger  Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINNT\Minidump\Mini080705-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\winnt\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: symbols timestamp is wrong 0x3ee6c002 0x384d9b17 for
ntoskrnl.exe
Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86
compatible
Kernel base = 0x80400000 PsLoadedModuleList = 0x8046e1b8
Debug session time: Sun Aug  7 17:39:25.807 2005 (GMT-3)
System Uptime: not available
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: symbols timestamp is wrong 0x3ee6c002 0x384d9b17 for
ntoskrnl.exe
Loading Kernel Symbols
...............................................................................................................
Loading unloaded module list
...............
Loading User Symbols
*******************************************************************************
*
      *
*                        Bugcheck Analysis
      *
*
      *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {c0000005, be996d35, 1, 10}

Unable to load image sis163u.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for sis163u.sys
*** ERROR: Module load completed but symbols could not be loaded for
sis163u.sys
Probably caused by : sis163u.sys ( sis163u+3d35 )

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

kd> !analyze -v
*******************************************************************************
*
      *
*                        Bugcheck Analysis
      *
*
      *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address
pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this
address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: be996d35, The address that the exception occurred at
Arg3: 00000001, Parameter 0 of the exception
Arg4: 00000010, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
sis163u+3d35
be996d35 ??               ???

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  00000010

WRITE_ADDRESS: unable to read from 8047edb4
unable to read from 8047e864
unable to read from 8047e738
unable to read from 8046a85c
unable to read from 8047e750
unable to read from 8047e860
unable to read from 80471038
unable to read from 8047e8dc
unable to read from 8047ed80
00000010

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x1E

LAST_CONTROL_TRANSFER:  from 00000000 to 804559bc

STACK_TEXT:
eb8d36e0 00000000 c0000005 be996d35 00000001
nt!RtlpNewSecurityObject+0x2b8


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP:
sis163u+3d35
be996d35 ??               ???

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  sis163u+3d35

MODULE_NAME:  sis163u

IMAGE_NAME:  sis163u.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  41ab05b9

FAILURE_BUCKET_ID:  0x1E_W_sis163u+3d35

BUCKET_ID:  0x1E_W_sis163u+3d35

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

i had very similar problems, same Trendent adaptor, different inasmuch as
different P2P etc. It didn't crash it just stopped and then I would get a
blue death screen with a pointer to sis163u.sys. Also, I didn't do all the
diagnostics when I saw you had done them better than I could anyway. i
replaced my trendnet drivers with driver and a Wireless Configuration
Utility from SIS themselves and it all appears to be working fine now, after
a few hours of running it.

I am posting this in case it helps you but also because I was so astonished
to find I had a bad 163u.sys from Trendnet when there was a good one sitting
on http://www.opendrivers.
com/freedownload/232662/sis-sis163-wireless-lan-driver-v1.
05-windows-98-me-2000-xp-download.html

for reference:
The blue screen of death sis163u.sys is 167,424

Scheduler not working properly, having to reset password in job
Can't download Security Updates
windows 2000 professional Roll back
Net Add LocalGroup - question
Going to a specific web page
the following error occurred attempting to rename the computer ".."
Server Busy
IE Security - Trusted Sites Zone
Need some advice on some Required Whiteboard Software.
Explorer Question