|
PureBytes Links
Trading Reference Links
|
A page fault can be caused by a multitude of things, none of which may
actually be the program that gets reported as the culprit. There are a
couple of ways to find out if it is MSWin or not.
1) Use safe mode and see if the same error happens. If not, then there
is a driver out there that is causing the problem, most likely the video
driver. Safe mode uses the standard Win 95 VGA driver and does not load
other unnecessary( to itself) drivers. A very handy troubleshooting
method. To start in safe mode, press F-8 (function key 8) when
"Starting Windows" appears on the screen. You must be quick.
Let us know the outcome of the safe mode test.
Equis Support
> -----Original Message-----
> From: Teo Soon Bock [SMTP:teosb@xxxxxxxxxxxxxx]
> Sent: Monday, June 02, 1997 7:57 AM
> To: metastock-list@xxxxxxxxxxxxx
> Subject: mswin caused an invalid page fault in module mswin.exe
>
> I am stumped by the following problem encountered by my friend when he
> ran
> MS 6.0. I thought he had insufficient RAM in his PC, but he has 48 mb
> of
> RAM in his Pentium.
>
> Any help in identifying the problem and solving it would be
> appreciated.
>
> >while trying to open layout in the metastock6.0 which contains
> multiple
> >charts and securities; the following message persists and can not be
> >resolved by closing
> >and reopening.
> >
> >message:
> >this programme has performed an illegal operation and will be shut
> down. if
> >the problem persists...
> >
> >details:
> >mswin caused an invalid page fault in module mswin.exe at
> >014f:0043e3b7.registers
> >
> >eax=00000000 cs=014f ep=0043e3bf eflgs=001024
> >ebx=01681ca8 ss=0157 esp=009ff460 esp=00000000
> >ecx=00000000 ds=0157 es1=01681 ca8 fs=2f97
> >edx=00000005 es=0157 ed1=00000000 cs=0000
> >byte at cs:e1p:
> >86 00 ff 90 54 01 00 00 83 f8 03 08 85 03 01 00
> >stack dump:
> >00000000 00000000 01682824 01681ca8 00000000
> >01682824 004c3c51 01682824 009ff520 00000000
> >01682790 00638248 00000000 00000000 000000000
> >00000000
> >looking forwards to heard from your advice.
> >thanks.
> >
> >note:could this problem caused by improper shutting down of win95?
> >
|