kernel32.dll

  • Thread starter Thread starter Goose
  • Start date Start date
G

Goose

After reading the answers and suggestions I tried to evoke
the KERNEL32.DLL error message and hoped that it was
accompagnied by a request to send an error report to
Microsoft.

I managed to get this done by opening several IE windows
and closing them by pressing the X-box.

The first lines of the report sent to MS read (I could not
copy it, so there may be a zero too many or too less):

AppName: iexplore.exe
AppVer: 6.0.2800.1106
ModName: unknown
ModVer: 0.0.0.0 Offset: 11c067a0

Exception Information
Code: 0xc0000005
Flags: 0x00000000
Record: 0x00000000000000000
Address: 0x0000000011c067a0

Does this help to identify the source of the error?
By the way, this time I could get rid of the error message
by clicking the X. It did NOT reappear this time.

Regards, Goose.
 
Select Module Unknown on this error page.
http://www.generation.net/~hleboeuf/erriexpl.htm

Easy to find out if the cause is some parasite.

Try this: Tools > Internet Options > Advanced > Browsing
Uncheck the Enable 3rd party browser extensions

If this clears your problem then find out who the culprit(s) is/are with
these tools.

Let AD-Aware Scan your system for advertising Spyware
http://www.lavasoftusa.com

or:

SpyBot-S&D
http://security.kolla.de/

p.s Reset the 3rd party browser setting.
 
ModName: unknown
ModVer: 0.0.0.0 Offset: 11c067a0
Click to expand...

Goose,

That could help is you knew that there is a module which
normally loads in that area. (E.g. this would then be a symptom
of a caller making an otherwise valid call either before the module
was loaded or (more likely) after it was unloaded.)
However, usually it is just an attempt to take a wild branch using
a corrupt pointer.

Is this on NTx? You might be able to get some clues from
its drwtsn32.log. There won't be any instructions to interpret
so you might not find a FAULT -> line (or your language's
equivalent) but you could probably find EIP=11c067a0
or EIP=0000000011c067a0 in a register dump
which would identify the crashing task. From there you would
page ahead to its Stack Back Trace (or your language's equivalent)
and perhaps be able to see what module might have caused this error
or at least get some more ideas about what was happening leading up
to the crash.


Good luck

Robert Aldwinckle
 
Back
Top