Kernel Errors

[Chaz]

Hello,

I have Visio2000 standard edition. I also have a non MS
programm called Racktools that runs in Visio as a series
of templates. If I open a Racktools template from Visio or
start Visio by opening Racktools I get the following
windows pop-up error message:

Visio32

This program has preformed an illegal operation
and will be shut down.

If I click the details button the window expands and
reads:


VISIO32 caused an invalid page fault in
module KERNEL32.DLL at 0167:bff8585c.
Registers:
EAX=00000020 CS=0167 EIP=bff8585c EFLGS=00010216
EBX=43918000 SS=016f ESP=0063d6fc EBP=0063d724
ECX=43918000 DS=016f ESI=00000001 FS=112f
EDX=00003000 ES=016f EDI=8176e8b0 GS=0000
Bytes at CS:EIP:
83 3b 00 0f 85 e6 fe ff ff b8 01 00 00 00 5f 5e
Stack dump:
8176e8b0 8176ea70 00005fff 43913000 00000020
00000020 8176eb2c 8176e9a8 8176eb34 00000002
0063d758
bff85a99 817400f5 817400f5 00002d8f 000003c7

Any ideas on this????

Many thanks,
Chaz Christianson
The Sound Center
9278 Civic Center Drive.
Beverly Hills CA 90210
310-274-6951

 

[Jorjejones]

Sounds like the racktools program is wrtten with bad code.
Has it ever worked for you yet?
What Windows version are you using?

Here is some more info on this error:

Q: At least once or twice a day during a save or exit routine in Visio
5.0, I receive the following message: "VISIO32 caused an invalid page
fault in module KERNEL32.DLL at 0137: bff9a5d0." In spite of the error
message, I am not aware of any harm or difference in the Visio drawing
files. It would be nice if someone could summarize or otherwise explain
the DLLs within Visio. A good start would be an explanation and purpose
of KERNEL32.DLL.
- Dean Wilson
A: Sorry, I cannot help you because DLL errors are due to a fundamental
flaw in Windows. DLLs (dynamic Link libraries) were meant to make the
life of programmers easier, by allowing the use of shared code. For
example, one DLL determines the elements of the user interface. Change
the DLL, and the user interface for all Windows programs changes.
While this is convenient for programmers, it is inconvenient for
the user. The fundamental drawback to DLLs is 'version control.' Here
is an example: Microsoft writes a DLL, which inevitably contains bugs;
application programmers figure out workarounds. Microsoft issues a new
version of the DLL, which fixes the bugs (but usually introduces new
bugs). The programmers' workarounds clash with the new DLL -- and crash
the software or sometimes the computer.
It has been said that the #1 reason for Window crashing is due to
the clash of DLL versions. The problem has become so bad that even
components of Microsoft Office (Word, PowerPoint, etc) use different
versions of the same DLLs!