When I have run msconfig.exe, the PC hangs with a "kernel32" error message when I close msconfig, even when no changes have been made. Silly, isn't it ...? What on earth might this be?
It's not necessarily bad ram especially if they have no other problems. Kernel32 errors can be caused by all kinds of things including spyware, viruses and low resources to name a few.
A comment from Ron Martell MS MVP quoted from elsewhere:
[[Kernel32.dll is the 32 bit kernel or "heart and soul" of Windows. As such it is involved in virtually every task or function that is run on the computer. Therefore whenever some application program or device driver misbehaves or malfunctions it is quite likely that kernel32.dll will be
affected in some way.
The detailed error message for these instances can be summarized as follows:
<culprit> caused a <type of error> in module <victim> (at <address>).
In at least 99 and 44/100% of the known instances involving kernel32.dll it is the victim and not the culprit. And in resolving these problems it is generally productive to pay at least as much attention to the culprit as you do to the victim.
Because of the prevalence of errors involving kernel32.dll there are a number of web sites that specialize in assisting with solving of these problems. A very good starting point is MVP Jim Eshelman's Kernel32 errors page at
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.