Winsock 2 fatal exception

[Guest]

Archived from groups: microsoft.public.win95.general.discussion (More info?)

Sometimes I get this error when Windows is starting and I have to reboot, then Windows
will start properly. At least so far it has started on the second try.

Does anyone else get this error? What is wrong and how can I fix it?

Thanks.

 

[Guest]

Archived from groups: microsoft.public.win95.general.discussion (More info?)

Winsock is a Windows component that supports connections to the
Internet.

The fact that the error is intermittent at startup suggests that it
may be caused by defective hardware.

The fact that restarting seems to eliminate the error suggests that
the error may be related to the temperature of the hardware
components: the errors happen when the hardware is cold but not when
it is warm. It is quite common for circuit boards to develop tiny
cracks that open up when the boards are cool and thus interfere with
the boards' operation. As the boards warm up, the cracks can close up
and allow the boards to function normally. Try leaving your computer
on all the time -- 24/7. If temperature is the cause of trouble,
keeping the computer warm should elimionate the trouble.
Bill Starbuck (MVP)

 

[Guest]

Archived from groups: microsoft.public.win95.general.discussion (More info?)

On Sun, 11 Sep 2005 05:31:40 -0700, Bill Starbuck <no_email@please.com> wrote:

>Winsock is a Windows component that supports connections to the
>Internet.
>
>The fact that the error is intermittent at startup suggests that it
>may be caused by defective hardware.
>
>The fact that restarting seems to eliminate the error suggests that
>the error may be related to the temperature of the hardware
>components: the errors happen when the hardware is cold but not when
>it is warm. It is quite common for circuit boards to develop tiny
>cracks that open up when the boards are cool and thus interfere with
>the boards' operation. As the boards warm up, the cracks can close up
>and allow the boards to function normally. Try leaving your computer
>on all the time -- 24/7. If temperature is the cause of trouble,
>keeping the computer warm should elimionate the trouble.
>Bill Starbuck (MVP)

Thanks Bill. The last time it happened, the computer had been on for hours.
I rebooted and when Windows was starting up, the error happened. The error
hadn't happened for several months before this. Also I only get this fatal
exception error when Windows is booting.

 

[Guest]

Archived from groups: microsoft.public.win95.general.discussion (More info?)

"The last time it happened, the computer had been on for hours."

There are two possibilities: (1) The computer had overheated. Open the
case an verify that the cooling fan is working. (2) You have a
marginal harddisk. Run ScanDisk several times in "thorough" mode.
Maybe the harddisk has a marginal sector in the area where Winsock is
stored.

"I rebooted and when Windows was starting up, the error happened."

Why did you reboot? What was wrong that induced you to restart the
computer? Maybe this stimulus was also the cause of the problem.

"The error hadn't happened for several months before this. Also I only
get this fatal exception error when Windows is booting."

Maybe the harddisk has a marginal sector in the area where Winsock is
stored. If ScanDisk does not find anything wrong, then you will
probably have to live with the problem until something more frequent
develops. A problem that occurs only once every several months seems
pretty easy to live with.

Bill Starbuck (MVP)

 

[Guest]

Archived from groups: microsoft.public.win95.general.discussion (More info?)

Help I am trying to post a new thread but nothing happens when i click on new
thread please help

"DaveJohnson12@nomail." wrote:

> Sometimes I get this error when Windows is starting and I have to reboot, then Windows
> will start properly. At least so far it has started on the second try.
>
> Does anyone else get this error? What is wrong and how can I fix it?
>
> Thanks.
>

 

[Guest]

Archived from groups: microsoft.public.win95.general.discussion (More info?)

You're using the Microsoft Support website to access these groups. Probably the
worst way there is, oddly enough. If you have Outlook Express, you can use it to
read these groups more efficiently. Just click on this link:
news://msnews.microsoft.com/microsoft.public.win98.gen_discussion

Or.if you prefer a web interface, try Google Groups.
http://groups.google.com/groups/dir?q=win98.gen_discussion&hl=en&sel=16823695%2C16823681

You'll have to sign up, etc., in order to post. Be sure to use a nonsense email
address so that yours doesn't end up on millions of mailing lists. Use one that
can't *possibly* be real, like notbody@nowhere.not

--
Gary S. Terhune
MS-MVP Shell/User


"debhep" <debhep@discussions.microsoft.com> wrote in message
news1567382-E43E-4F1F-8F2E-56BFF5998982@microsoft.com...
> Help I am trying to post a new thread but nothing happens when i click on new
> thread please help
>
> "DaveJohnson12@nomail." wrote:
>
>> Sometimes I get this error when Windows is starting and I have to reboot,
>> then Windows
>> will start properly. At least so far it has started on the second try.
>>
>> Does anyone else get this error? What is wrong and how can I fix it?
>>
>> Thanks.
>>

 

[Guest]

Archived from groups: microsoft.public.win95.general.discussion (More info?)

Sorry, I had you in the wrong group. The links you want are:

Outlook Express (or any other newsreader client):
news://msnews.microsoft.com/microsoft.public.win95.general.discussion

Google Groups:
http://groups.google.com/groups/dir?q=win95.general.discussion&hl=en&sel=16823695

--
Gary S. Terhune
MS-MVP Shell/User

"debhep" <debhep@discussions.microsoft.com> wrote in message
news1567382-E43E-4F1F-8F2E-56BFF5998982@microsoft.com...
> Help I am trying to post a new thread but nothing happens when i click on new
> thread please help
>
> "DaveJohnson12@nomail." wrote:
>
>> Sometimes I get this error when Windows is starting and I have to reboot,
>> then Windows
>> will start properly. At least so far it has started on the second try.
>>
>> Does anyone else get this error? What is wrong and how can I fix it?
>>
>> Thanks.
>>