From: "Jeroen Besse" Received: from mxout4.mailhop.org ([63.208.196.168] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 290336 for os2-wireless_users@2rosenthals.com; Tue, 15 Aug 2006 02:14:15 -0400 Received: from mxin1.mailhop.org ([63.208.196.175]) by mxout4.mailhop.org with esmtp (Exim 4.51) id 1GCsBp-000JQe-0s for os2-wireless_users@2rosenthals.com; Tue, 15 Aug 2006 02:14:14 -0400 Received: from nf-out-0910.google.com ([64.233.182.189]) by mxin1.mailhop.org with esmtp (Exim 4.51) id 1GCsBo-000LXm-GA for os2-wireless_users@2rosenthals.com; Tue, 15 Aug 2006 02:14:12 -0400 Received: by nf-out-0910.google.com with SMTP id p46so226102nfa for ; Mon, 14 Aug 2006 23:14:10 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jYvGbuGLvIXmLfK1VcmwU7O+AmeMqUu2Kal1ZEPEa10tyu6n+GnZDPu3n7e1NG+MPyUsqxMnQDas23fgejfblSEun50ASwnCDpIO8xAdYYyqTzjREeuVQqUtifcBt89fr2kXEnZdsZjvPHE9Ez7ffcE9KDnvbHiZdIXXE8+UeZk= Received: by 10.49.10.3 with SMTP id n3mr869525nfi; Mon, 14 Aug 2006 23:14:10 -0700 (PDT) Received: by 10.78.139.6 with HTTP; Mon, 14 Aug 2006 23:14:10 -0700 (PDT) Message-ID: <7234a03c0608142314w1e4a8bd6r3e1546252bfffcf9@mail.gmail.com> Date: Tue, 15 Aug 2006 08:14:10 +0200 To: "OS/2 Wireless Users Mailing List" Subject: Re: [OS2Wireless]SOCKET.SYS crash - Dump Screen (was: I give up) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.3 (--) On 8/15/06, Rick R. wrote: > Hi Folks ! > > OK, here is the contents of that dreaded dump screen: > > SOCKETS > TRAP 000e > ERR CD 0000 > EAX 0026001C > EBX 0026001 > ECX 000017C7 > EDX 00008000 > > Can anyone tell me how to fix this? My 1st guess would be to check the MPTS level: [C:\] syslevel c:\mptn which should give a current CSD level 8708 for the TCP/IP stack. But probably you're already there. You also mentioned a trap E in an other driver before... which gives me the feeling it might be hardware related... I had some trap E problems on my computer a few years ago. Windows did not have problems, strangely enough. These traps occurred more often over time. Finally, after reinstalling everything (which didn't fix anything), I lowered the processor speed, which did fix things for a short time. Then, I replaced my mainboard, processor and memory, and all was well again. So, if you didn't have this problem before, but are experiencing it more often in time, you might be experiencing a hardware problem here. Best regards, Jeroen Besse