Help - repeated blue screen - CUSL2-C

[WhiteTornado]

I have an Asus CUSL2-C mobo with Windows 2000 I had several blue screens with XP, and I am trying to find what has been causing this, I was also getting "emptying of the physical memory" errors, I had 2 X 256 sdram, A Matrox Millenium G450 with a PIII Intel 1000, I had an Epson scanner 1660 plugged on it on a USB2 card. I reinstalled the OS a few times and still had constant recurring troubles. I installed Win 2000, I swapped the memory for a 512 stick, I replaced the Video for a 3DFX card and now I am testing it. I am getting this PCI device which I found out is the SMBUS CONTROLER, A 82801BA ICH2-M Intel for which I have NOT been able to find any drivers anywhere!!!

So, anyone can help me with this driver?

Any input on the above config and known issues which could give me some data as to why so much troubles with the config?

Cheers!

 

[bcastner]

You are probably fine with this specific chip. But what you do is to download and run the "Intel Chipset Software Installation Utility" which will automate the driver task for you:

http://downloadfinder.intel.com/scripts-df/Product_Filter.asp?ProductID=816

What is really needed from you is more specific details from your System logs. Start, run, eventvwr.msc
Post some details of why the machine is having issues.

 

[WhiteTornado]

Ok great, tks v much for the link. This is what was in the event viewer:
Error 20063, 20065 - RASMAN
Error 20071, 20151 - REMOTRE ACCESS MANAGER
Error 1003 - SYSTEM ERROR

 

[bcastner]

I perhaps was not clear enough earlier. When I asked you to post the errors, I expected something like this:

Event ID:20070
Source:RemoteAccess
Remote Access Connection Manager failed to start because the Point to Point Protocol failed to initialize. The specified module could not be found.

Event ID:20063
Source:Router
Remote Access Connection Manager failed to start because the Point to Point Protocol failed to initialize. The specified module could not be found.

Event ID:7001
Source:Service Control Manager
The Routing And Remote Access Service service depends on the Remote Access Connection Manager service which failed to start because of the following error:
The specified module could not be found.

Event ID:7023
Source:Service Control Manager
The Remote Access Connection Manager service terminated with the following error:
The specified module could not be found


These are Windows 2000 and not XP errors, so I suggest you post them in that Forum.

But the issue is explained here:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q823405

 

[WhiteTornado]

Ok, I see what you mean, only trouble is that I reinstalled the OS, I had taken notes earlier and these were the notes I had. These were on the XP system though... but, now I think of it, the XP was done as an update of Win 2000 which had the SP4 installed on it, this is probably why i got these Win2K errors despite running XP Pro.

Cheers!

 

[bcastner]

If you note the progrssion in the errors messages I posted above you will see that the core issue is that a dependent service has not started.

"Remote Access Connection Manager failed to start because the Point to Point Protocol failed to initialize. The specified module could not be found."

This can be an indication of a Winsock service stack problem. It can also be an issue of not having installed all the client services that XP expected to have available when other options where enabled.

I would:

. Be certain that the adapter I was enabling RAS services to had Client for Microsoft Networking bound;

. Run a utility to rebuild the Winsock service stacks in the registry:

http://members.shaw.ca/techcd/VB_Projects/WinsockFix.zip

. Re-apply any and all TCP/IP Properties customizations;

. Start, Help and Support, and query on "services" You will get a listing of the default status for all XP services as they should be. Then Start, Run, net start
to get a listing of the status of your services as they are now. You can use NET START to try and enable a service, or use the Start, Run, services.msc
snap-in to configure the services for Start, and to set the startup desposition of the Service as specified in the Help and Support listing from the earlier step.

I have had several people who have "tweaked" their service entries find the little registry restorer on the Black Viper site a godsend to restore the service entries to their native and default state:

http://www.blackviper.com/WinXP/servicecfg.htm

As a final note if you do a site Keyword Search you should easily find several technical notes I have left here about using the Recovery Console and the "enable" command to restart balky services, the notes refer to search for deal with the RPC service, but apply to any XP service.

Best wishes,
Bill Castner