Sari Issi
2005-01-04 12:45:01 UTC
XP Pro kone kaatuu melko usein ja sinisessä 'kuolemanruudussa' lukee
Havaittiin virhe, ja Windows sammutettiin tietokoneelle aiheutuvien
vahinkojen välttämiseksi.
DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x000000D1 (0x0000001E, 0x00000002, 0x00000000, 0xB82377F8)
*** NTSTAP1.SYS - Adress B82377F8 base at B8235000, DateStamp 3c86713c
Löysin seuraavan linkin, mutta huonolla englanninkielen taidollani en
oikein ymmärrä mitä pitäisi tehdä.
Minulla on kuitenkin P.P.P.o.E:llä toteutetussa yhteydessä
yhteysohjelmana alla mainittu Efficient Networks Enternet 300
yhteysohjelma. Mitä siis pitäisi tehdä jotta tuo ongelma poistuisi
Windows XP Professionalissa?
http://as.efficient.com/support/ntstap.html
NTSTAP Driver Issue
Error: EnterNet or Tango Access crashes occasionally in the ntstap1.sys
driver
A: This problem has been found to occur on some systems running older
versions of EnterNet and Tango Access products, on Windows XP, NT, and
2000/2003 systems. If you experience these crashes, either as a blue
screen or as an OnLine Crash Analysis report, which is detected and sent
by XP, a simple configuration change should resolve these crashes easily.
The best way to solve this problem is to reconfigure to use the Protocol
Driver instead of the default Filter Driver. You can do this easily
using the EnterNet application following these instructions. If using
Tango Access, follow these instructions.
Note: after changing this value, you will be prompted to reboot your
system in order for it to take effect.
If you still prefer to use the Filter driver (almost all users are
better off using the Protocol driver), you can download this unsupported
http://kb.efficient.com/article.asp?article=46048&p=351
This patch is provided as is, with no direct support to users. It will
not resolve all crashes, because the Filter driver was not designed to
handle the multi-processor features that have been added to higher speed
systems, like the Intel P4. The patch will have no effect on Windows 95,
98 or Me systems.
After executing the file by double-clicking after the download, it will
verify if the ntstap file has already been updated. If not, it will
update the ntstap files and save the old files for recovery in a folder
called "obsolete". You will be prompted to reboot when the patch is
finished.
Note: For ISP users who wish to change the Protocol driver setting
programmatically, this can be done with a simple ini change. Edit the
Efficient.ini file (usually stored in the \Program Files\Efficient
Networks\Tango Manager\Efficient directory) and make the following
Hain sivulta http://kb.efficient.com/article.asp?article=46048&p=351Havaittiin virhe, ja Windows sammutettiin tietokoneelle aiheutuvien
vahinkojen välttämiseksi.
DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x000000D1 (0x0000001E, 0x00000002, 0x00000000, 0xB82377F8)
*** NTSTAP1.SYS - Adress B82377F8 base at B8235000, DateStamp 3c86713c
Löysin seuraavan linkin, mutta huonolla englanninkielen taidollani en
oikein ymmärrä mitä pitäisi tehdä.
Minulla on kuitenkin P.P.P.o.E:llä toteutetussa yhteydessä
yhteysohjelmana alla mainittu Efficient Networks Enternet 300
yhteysohjelma. Mitä siis pitäisi tehdä jotta tuo ongelma poistuisi
Windows XP Professionalissa?
http://as.efficient.com/support/ntstap.html
NTSTAP Driver Issue
Error: EnterNet or Tango Access crashes occasionally in the ntstap1.sys
driver
A: This problem has been found to occur on some systems running older
versions of EnterNet and Tango Access products, on Windows XP, NT, and
2000/2003 systems. If you experience these crashes, either as a blue
screen or as an OnLine Crash Analysis report, which is detected and sent
by XP, a simple configuration change should resolve these crashes easily.
The best way to solve this problem is to reconfigure to use the Protocol
Driver instead of the default Filter Driver. You can do this easily
using the EnterNet application following these instructions. If using
Tango Access, follow these instructions.
Note: after changing this value, you will be prompted to reboot your
system in order for it to take effect.
If you still prefer to use the Filter driver (almost all users are
better off using the Protocol driver), you can download this unsupported
http://kb.efficient.com/article.asp?article=46048&p=351
This patch is provided as is, with no direct support to users. It will
not resolve all crashes, because the Filter driver was not designed to
handle the multi-processor features that have been added to higher speed
systems, like the Intel P4. The patch will have no effect on Windows 95,
98 or Me systems.
After executing the file by double-clicking after the download, it will
verify if the ntstap file has already been updated. If not, it will
update the ntstap files and save the old files for recovery in a folder
called "obsolete". You will be prompted to reboot when the patch is
finished.
Note: For ISP users who wish to change the Protocol driver setting
programmatically, this can be done with a simple ini change. Edit the
Efficient.ini file (usually stored in the \Program Files\Efficient
Networks\Tango Manager\Efficient directory) and make the following
tuon korjaustiedoston, ja asensin sen.
Nyt Sygate Personal Firewall Pron palomuurin Running Applications
kohtaan tulee uusi sovellus:
NTS TAP Lite Kernel Driver for NT version 4.15.0.0 C:\Program
Files\Efficient Networks\EnterNet 300\app\ntstpl1.sys
Tälle on annettava lupa "Allow" verkkoyhteyteen, jotta nettiyhteys
yleensä pelaa.
Application Details kohdasta näkee että "Incoming Allowed" ja "Outgoing
Allowed" liikennettä sovelluksen kautta kulkee enemmän kuin vaikkapa
esimerkiksi selaimen kautta, eli todella paljon.
Connection Details-kohdassa ntstpl1.sys:iä ei kuitenkaan näy ollenkaan,
eikä Traffic-lokissa näy yhteydenottoa kuin yhteyttä avattaessa.
Osaako joku sanoa, miksi NTS TAP Lite Kernel Driver for NT (ntstpl1.sys)
on päästettävä liikennöimään vapaasti, ja voiko tästä olla jotain
tietoturvaan liittyvää haittaa?