11 replies
by jdfcomputer
by dirtycar74
by pschuvie
I also have seen the problem somewhat frequently but usually a bit of investigation points out that something else or some other program is really the contributing factor to "caused an error in kernel32".
While it might be necessary to actually use the SFC extract I tend to find that getting a good scandisk and defrag from a SAFE mode having the strongest curative power. Also, of course checking to see what the system resources are like is also very good.
The scenario often goes I was doing this and this kernel error came up what do I do, and you check CAD and there are about 20 things running, system resources running around 50% and I don't know how or it never finishes is the defrag answer. Ok do we see stress here for the Memory manager, lol. Oh yeah I added xyz programs but deleted them. So what's up.
I don't think that the automatic extraction of kernel32 is the first step solution but then if the user is "reluctant" you can always suggest it, just make sure younote the ticket so you have knowledge that they should have already done that. Sometimes they want something interesting to do and it can get them to actually turn off the computer and let it set for 5 minutes and get a fresh boot.
Just some thoughts.
by dirtycar74
by jdfcomputer
No extracting the file will not fix the problem.
The only fix is to rebuild the swap file.
by dirtycar74
by bloodbath
As long as you are running an os with dos installed you can boot into dos and type:
del win386.swp
What this will do is delete the swap file and when you reboot the os will create a new swap file. After I do this I don't see another kernel error fof a long time. This how ever will not work in ME as Microsoft for some reason removed dos from the os (windows will not let you delete the swap file so it must be done in dos). As far as extracting it i'm not sure.
by dirtycar74
by bloodbath
As long as you are running an os with dos installed you can boot into dos and type:
del win386.swp
What this will do is delete the swap file and when you reboot the os will create a new swap file. After I do this I don't see another kernel error fof a long time. This how ever will not work in ME as Microsoft for some reason removed dos from the os (windows will not let you delete the swap file so it must be done in dos). As far as extracting it i'm not sure.
by dirtycar74
NO one was able to give me a valid answer. Yes you can extract Kernel32, and YES it does work, but it is not something you should do as a mainstay fix. There are other problems creating kernel32 errors which you should find and solve. Most ofthe time it has to do with memory and memory usage, so 'zingfu' is the closest answer. But still not exactly what I was looking for. This question has been closed.
SPAZ
by dirtycar74
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending