Illeagal Operations during boot-up

[cornerforce]

My colleagues PC has developed several illeagal operation calls during boot-up. These have remained after an overlay of Win98SE, and after a reformatting and re-installing.
They are Regsvr32, Rundll32, both files are causing illeagal operation calls to Winsock32.dll. Any advise would be welcome.

[Rog]

If you hadn't said these errors were occuring after a format, I would be replying that they are symptomatic of a viral infection. So if that is a possibility, you need to have him install a good scanner. The Hybris worm in particular is known to cause wsock32.dll errors.

If he reformats again, he should get a new boot disk, such as from www.bootdisk.com and write protect it before using.

If these problems occurred immediately after a format and before any additional software was installed, they are likely to be caused by either bad hardware (such as faulty ram) or a virus introduced from an infected boot disk.

You can troubleshoot the ram with a software tester:
http://www.simmtester.com/PAGE/products/doc/docinfo.asp


If any non-windows programs have been added, use of msconfig to troubleshoot by disabling them would be a good approach.
http://support.microsoft.com/support.../q188/8/67.asp

He should also test to see whether the errors occur in safe mode.
------------------
What the Dormouse said

[This message has been edited by Rog (edited 07-07-2001).]

[Kleinkramer]

I've never heard of Regsvr32 and Rundll32 page faults in module Wsock32.dll, although all three files might well be involved.
Why not try and get the exact text of each error message for us?
You could start off by having the system scanned at Trend Micro HouseCall free on-line virus scan: http://housecall.antivirus.com/

[This message has been edited by Kleinkramer (edited 07-07-2001).]

[cornerforce]

Thanx for your reply. The problem has now been rectifyed by looking through the bios settings. Unknown to me the PC was severly overclocked, and with the default bios settings, windows has installed perfectly. This has appeared to solve the problems, and is stable when the CPU speed is turned back up. The information was most useful anyway.

------------------
CorneRForce