🚀 go-pugleaf

 Sun, 12 Sep 1999 05:32:32 GMT, Mark Bennett
<wicked@NOSPAMmalleenet.net.au> wrote:

>Hi all,
>It all started when i deleted my c:\ drive and reinstalled a fresh copy
>of Win98.  Since then i keep having the problem described below when
>installing a program i had running previously.  I have updated all my
>software drivers ie. cd/network/video etc etc. and still have the same
>problem. Can someone please help!
>
>Regards
>
>Mark Bennett
>-- the error --
>_INS0432 caused an invalid page fault in
>module KERNEL32.DLL at 0177:bff711be.
>Registers:
>EAX=81640000 CS=0177 EIP=bff711be EFLGS=00010246
>EBX=00000000 SS=017f ESP=006df4e4 EBP=006df4f0
>ECX=ffffffff DS=017f ESI=00000000 FS=351f
>EDX=816472bc ES=017f EDI=56000ce0 GS=0000
>Bytes at CS:EIP:
>f2 ae f7 d1 8b 75 0c 8b 7d 08 8b c7 fc 51 c1 e9
>Stack dump:
>816459d4 00000000 006df614 006df724 bff7e6ef 006df614 56000ce0 816459d4
>816459e8 00000000 bff7e840 81644b8c 81649382 8163f9ec 00000000 00000000
>-------------------------
>** remove NOSPAM to reply **

EXPLORER.EXE has caused an invalid page fault in module KERNEL32.DLL
at 015f:04500018

Don't worry if you don't understand anything of this purely technical
information, but there is one important bit here that can give you an
indication of what is going wrong: the 'address' of the crash. The
address is the location in your computer memory where the crash
occurred, in this example 015f:04500018. If this address keeps
returning, there may well be something wrong with the RAM. (In that
case, invalid page faults would also be caused in modules other than
kernel32.dll.) To test the memory, you could insert a command line in
your Config.sys file, located on your primary drive (usually C:\).
Simply open this file in Notepad and insert: 

device=C:\WINDOWS\HIMEM.SYS /TESTMEM:ON

The next time you boot, you could get a message that HIMEM has
detected unreliable memory at a certain address, and this address
could be the same as the one in your error messages. Maybe this
detection will not happen immediately, it could take a few days, or it
may never happen, in spite of an actual memory fault.

For what it's worth, we can tell you the following about the rest of
the 'details': 
- Registers: values of the register of the processor at the moment of
the crash. 
- Bytes in CS:EIP: value of the current instruction (in this case c9
74). 
- Stack dump: the route that caused the program to crash. 

Technical support services will be interested in this data, so write
them down if you get repeated error messages that look more or less
identical.

REMEMBER:
Most kernel32.dll errors are NOT caused by a corruption of the
kernel32.dll module.  If it's always the same program or application
that causes the invalid page fault, you should do something about that
program or application (e.g. uninstall and reinstall) and not concern
yourself with kernel32.dll.
Thank you and Regards,
Bud Allen
smeebud@worldnet.att.net

"As far as possible without surrender, be on good terms with all persons."
"Freedom exists in the unencumbered mind."

http://www.geocities.com/~budallen/
http://members.xoom.com/bud_allen_ts
Bud's Win95 Win98 Tips and Troubleshooter