Ndis miniport driver crash on vista while work perfectly with XP

Tech-Archive recommends: Speed Up your PC by fixing your registry

My Ndis driver is based on the passthru sample (6001.18001).

The driver will route all TCP traffic to a local listener application on a
known port.
Then the application will send this packet to a dummy destination, this way
the driver will identify the outgoing packet.
This will allow the driver to resend the packet with the known dummy
destination to the original destination.
For example:
1. first packet from IP:x1 and PORT1 to IP:x2 and PORT:x2
2. The driver will change the destination IP to x1 (the local address) and
the PORT to the known port. The driver will indicate this packet UP.
3.The next packet sent by the listener application to a dummy known address
4.The driver will identify the dummy address and will replace the
destination to the original one IP = x1 and PORT = x2, The driver will use
ndissend() to forward this packet
5. For incoming traffic the driver will do the same, meaniing change the
address as needed so the application will act as a router

This works perfectly with windows XP when running the driver with Vista
Ultimate it will crash randomly.

Any help will be appreciated,

Thanks,
Bumper.
.

Relevant Pages

  • Re: Changes in the network interface queueing handoff model
    ... bouncing around for some time is a restructuring of the network interface packet transmission API to reduce the number of locking operations and allow network device drivers increased control of the queueing behavior. ... to "start" output by the driver. ... encapsulation and wrapping, and notifies the hardware. ... The ifnet layer send queue is becoming decreasingly useful over time. ...
    (freebsd-arch)
  • Re: Changes in the network interface queueing handoff model
    ... bouncing around for some time is a restructuring of the network interface packet transmission API to reduce the number of locking operations and allow network device drivers increased control of the queueing behavior. ... to "start" output by the driver. ... encapsulation and wrapping, and notifies the hardware. ... The ifnet layer send queue is becoming decreasingly useful over time. ...
    (freebsd-net)
  • PATCH: Remove file riowinif.h from rio driver (unused file)
    ... -/* The RUP (Remote Unit Port) structure relates to the Remote Terminal Adapters ... - CONFIG is sent from the driver to configure an already opened port. ... - Packet structure is same as OPEN. ... - of the specified port's RTA address space. ...
    (Linux-Kernel)
  • Re: Changes in the network interface queueing handoff model
    ... layer output routine via ifp->if_outputwith the ifnet pointer, packet, ... as ARP), and hands off to the ifnet driver via a call to IFQ_HANDOFF, ... encapsulation and wrapping, and notifies the hardware. ... The ifnet layer send queue is becoming decreasingly useful over time. ...
    (freebsd-arch)
  • Changes in the network interface queueing handoff model
    ... 5BOne of the ideas that I, Scott Long, and a few others have been bouncing around for some time is a restructuring of the network interface packet transmission API to reduce the number of locking operations and allow network device drivers increased control of the queueing behavior. ... to "start" output by the driver. ... encapsulation and wrapping, and notifies the hardware. ... The ifnet layer send queue is becoming decreasingly useful over time. ...
    (freebsd-net)