X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: lry Newsgroups: comp.os.msdos.djgpp Subject: SWSVPKT and NMI Date: Wed, 16 Jan 2008 16:05:40 -0800 (PST) Organization: http://groups.google.com Lines: 10 Message-ID: NNTP-Posting-Host: 72.64.14.104 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: posting.google.com 1200528340 12911 127.0.0.1 (17 Jan 2008 00:05:40 GMT) X-Complaints-To: groups-abuse AT google DOT com NNTP-Posting-Date: Thu, 17 Jan 2008 00:05:40 +0000 (UTC) Complaints-To: groups-abuse AT google DOT com Injection-Info: s12g2000prg.googlegroups.com; posting-host=72.64.14.104; posting-account=n4_UaQkAAAD8duFWZvVLT1Ge8bpBqjgJ User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com I installed swsvpkt1005 as the only protocol for my NIC under Windows XP SP2. My DJGPP app ran successfully - thank you, Software Systems! However, a little later my year-old Dell laptop crashed with a blue screen "NMI Parity Check", which Dell said could be either hardware or software. After a normal restart and another hour of operation, the crash occurred again. A Microsoft RAM test utility reported no RAM defects. I removed the swsvpkt protocol and replaced it with the usual Windows TCP/IP, etc, and the system has now been running normally for several hours. Is there any possible link between "NMI Parity Check" and swsvpkt, or is this just a scary coincidence?