Click to See Complete Forum and Search --> : error in kernel32.DLL


msacaa
June 10th, 2001, 07:12 PM
I have a emachine 733i celeron system with windows ME. After bringing the computer home I hooked it up to the net and went to microsoft's web site and down loaded all the critical updates. Well I have been consistently getting an error that says WCS 2000 error in kernel 32.DLL. Once I had to shut the computer off because it would not go away. What can I do to corret this? I did a search on this site and saw similar problems with windows me. I posted a new message because I was not sure if my problem was the same as the others since they were different systems and possibly different versions of win me. So what should I do, the microsoft site was not help at all.

Thanks,

msacaa

JungleMan1
June 11th, 2001, 05:48 PM
Tell you the truth that is just Windows ME..it causes a lot of problems with the Kernel (kernel32.dll)...

But if it happens CONSTANTLY then it may be a problem with the file or some program that is running on start up. Try going into msconfig or something (go to Start > Run and type msconfig), and going to the Startup tab and unchecking ALL items (Except something that relates to your printer...because i know Lexmark printers require a background program running)

If that doesn't work, go to start> run and type sfc, and restore the file from the Windows ME folder.

Sowulo
June 11th, 2001, 06:35 PM
A quick web search seems to point at Compuserve. Are you using Compuserve for that new internet connection? If so, check and see if there is a newer version of their software or update patches of any kind.

TYpY
June 18th, 2001, 06:27 PM
I'm having some problems with Kernell32.dll! When i connect to the internet (i have a 56k modem) when the connection is login into the server, hapears a windon saying that RNAAPP.exe has made and fatal error in a unknow program and then that kernel32.dll has made an fatal error in an unknow problem... I don't know why does this happens, because sometimes i can connect and others time i can't

Votan
June 18th, 2001, 09:35 PM
Originally posted by JMM:
<STRONG>Tell you the truth that is just Windows ME..it causes a lot of problems with the Kernel (kernel32.dll)...
</STRONG>

Sorry, but I did not have any problem with ME. Most of the errors attributed to ME are not really ME problem.

Chances are some bad files covered by Sowulo reply.

ThunderVamp9
June 19th, 2001, 11:34 AM
I agree, I'm dual-booting 2K and ME, and have never once experienced trouble with ME. Seems to run very stable for me. So far, I guess I'm one fo the few who likes it. *hides in fear*

paulsands
June 20th, 2001, 01:20 PM
if you are using cable internet's software (blueyonder it is know to cause problems by constantly displaying errors while on the net. since their software is not compatible with winme

i would suggest if this is the problem not to use their software and use standard windows me dial-up connection window

pcejim@dol.net
June 20th, 2001, 03:47 PM
I also ran ME fine for quite a while. Still have it on a couple of systems. My kids like 98, and I have an XP Beta2 on my machine. No real ME problems though. I also seem to be one of the few. But since the Hard Drive Cache Utility came out, we haven't had any problems at work either.
Jim

[NeoZeeD]
June 24th, 2001, 12:14 PM
i have windows ME and it pretty much SUCKS for me. i keep getting explorer error or netscape errors, or errors for my dsl modem. and stupid kernel errors, i think i might just go back to 98

Votan
June 24th, 2001, 06:56 PM
Originally posted by AbSoLuTeZeR0:
<STRONG>i have windows ME and it pretty much SUCKS for me. i keep getting explorer error or netscape errors, or errors for my dsl modem. and stupid kernel errors, i think i might just go back to 98</STRONG>

How ME got into your computer? Have you clean installed it?
- if not, then this the way to go,
- if yes, then have you verified your drivers up to date and compatible with ME? If not then you got the direction where to go. You will have a smooth friendly ME like I do.

Most errors from ME originates from either bugs in applications, or incompatible drivers.