1. another page fault !
EXW caused an invalid page fault in
module EXW.EXE at 0137:0040a9d0.
Registers:
EAX=04ad00c0 CS=0137 EIP=0040a9d0 EFLGS=00010206
EBX=007f0030 SS=013f ESP=0056fc20 EBP=00683650
ECX=034800c4 DS=013f ESI=01e40030 FS=3707
EDX=bfffffff ES=013f EDI=03490030 GS=0000
Bytes at CS:EIP:
8b 1b 83 c0 04 8b 13 83 c3 04 89 50 fc 81 fa ff
Stack dump:
00683650 803c8006 0056fc46 803c8006 00000001 0064efa8 00413d7b
00580960 006a1000 0056fca8 00000013 005807f8 00423618 0056fc50
803c8006 00000000
2. Re: another page fault !
On Sat, 14 Apr 2001, Kat wrote:
> EXW caused an invalid page fault in
> module EXW.EXE at 0137:0040a9d0.
Kat:
That could be a symptom of memory going bad, but there are other
things to try first, for example, removing & re-installing the memory sticks.
How long has it been since you reloaded Windows?
I usually get errors like that (not just from Euphoria, but from
Delphi, and others) after a few weeks of heavy use. My solution,
probably not the best one, is to wipe the disk and re-install Windows
from the CD.
Regards,
Irv
3. Re: another page fault !
Kat,
If Eu has been humming along nicely and all of a sudden is causing GPFs or
Page Faults, etc., then the problem is most likely not with Eu. Send me
your program or post it on this list--if we don't get the same results,
then the problem is undoubtedly not with Eu.
I'd try this kind of stuff:
1) Remove Eu and reinstall it. Delete it with one of those programs that
really deletes program data, instead of justs setting the deleted flag.
Many are available on the web--I know www.cnet.com has quite a few.
2) Scan for viruses with a current (as in very very current) scanner.
3) Run Scandisk & perform a surface test, too.
(scandisk c: /autofix /nosave /surface)
4) Try your program on other machines.
--Ted
--On Saturday, April 14, 2001 02:22:33 PM -0500 Kat <gertie at PELL.NET> wrote:
>
>
> EXW caused an invalid page fault in
> module EXW.EXE at 0137:0040a9d0.
> Registers:
> EAX=04ad00c0 CS=0137 EIP=0040a9d0 EFLGS=00010206
> EBX=007f0030 SS=013f ESP=0056fc20 EBP=00683650
> ECX=034800c4 DS=013f ESI=01e40030 FS=3707
> EDX=bfffffff ES=013f EDI=03490030 GS=0000
> Bytes at CS:EIP:
> 8b 1b 83 c0 04 8b 13 83 c3 04 89 50 fc 81 fa ff
> Stack dump:
> 00683650 803c8006 0056fc46 803c8006 00000001 0064efa8 00413d7b
> 00580960 006a1000 0056fca8 00000013 005807f8 00423618 0056fc50
> 803c8006 00000000
>
>
>
>
4. Re: another page fault !
On Sat, 14 Apr 2001, Everett L.(Rett) Williams wrote:
> Irv,
>
> I don't know how much budget you have or whether your time is
> worth more than your money, but here is a solution that I have known
> and used for years. This is not an ad. Steve Gibson's Spinrite will
> keep your data fresh and fix most problems on a hard drive that are
> fixable. It has been around since MFM days, and I have been using
> it since before 1990. It isn't cheap($89), but it should keep you from ever
> having to wipe and re-install Windows. Further, wiping and re-installing
> does not necessarily resolve all the problems with a hard drive. If there
> is an area that tends to lose signal over time, Spinrite will detect it and
> either re-write it or mark it as unuseable.
>
Thanks, I've used Spinrite in the past, and liked it. However, there's no
physical problem with the disks. It's rogue Windows code randomly
writing stuff on top of otherwise useful data, I think.
A perfect example from one of my clients:
His A/R program ( a Medlin program ) crashed. A little browsing the data files
with Dave's EE showed a bunch of html mixed into the middle of the A/R data.
Browsing thru the HTML bits turned up a lot of links to erm... "adult" websites.
Now we know what the bookeeper was _really_ doing
while balancing the books. I chalk this up to IE playing fast and loose with
its cache. Maybe there's another explanation, but the same computer and
drive have worked flawlessly since the browsing stopped.
Regards,
Irv
5. Re: another page fault !
On 14 Apr 2001, at 15:42, Irv Mullins wrote:
>
> On Sat, 14 Apr 2001, Kat wrote:
>
> > EXW caused an invalid page fault in
> > module EXW.EXE at 0137:0040a9d0.
>
> Kat:
>
> That could be a symptom of memory going bad, but there are other
> things to try first, for example, removing & re-installing the memory sticks.
Ok, i replaced the two sticks i was using with one 128meg stick, and still,
this happened:
EXW caused an invalid page fault in
module EXW.EXE at 0137:004142ab.
Registers:
EAX=00000000 CS=0137 EIP=004142ab EFLGS=00010246
EBX=00808500 SS=013f ESP=0056fc3c EBP=0056fc46
ECX=0064ef7c DS=013f ESI=800d2b70 FS=2ff7
EDX=00698000 ES=013f EDI=00000000 GS=0000
Bytes at CS:EIP:
8a 02 89 03 8d 42 01 83 c3 04 89 45 2a eb e1 8b
Stack dump:
00580960 006a1000 0056fca8 00000013 005807f8 00423618 0056fc50
00000000 00000000 00000000 00580820 00000000 00000000 00698000
00000001 0058deef
> How long has it been since you reloaded Windows?
> I usually get errors like that (not just from Euphoria, but from
> Delphi, and others) after a few weeks of heavy use. My solution,
> probably not the best one, is to wipe the disk and re-install Windows
> from the CD.
I have been using the same install for a few years now.
Kat
