Page fault error in installation

I'm trying to upgrade my D2K software but when I run the setup process I get a page fault error in module KERNEL32.DLL at 0137:bff9a485 when it reaches OIIMPL32.DLL. This appens only with Win95 (users), I installed succesfully ver 6.0 on NT (my pc of course). Any comments???
Thanx in advance.

>>Posting Guide<<

Similar Messages

  • LabVIEW 4.0 Invalid Page Fault Errors

    I've got myself stumped on this problem - we had a LabVIEW based PC/DAQ system that started giving invalid page fault errors and crashing in Win95. This may have been concident with a revision to a vi file. To rectify the problem I've tried the following:
    1. Reinstall LabVIEW 4.0 with NI-DAQ 6.6
    2. Wipe HD, reinstall Win95, LV 40, NIDAQ 6.6
    3. Full HD scan and MEMTEST86 memory test
    4. Install on another PC
    The PCs are P5-60 Gateways with 128 MB of RAM. DAQ config is 1 AT-AO-10 and 1 AT-MIO-16DE-10
    Nothing seems to help. With a reinstall of LV40, I can get it to run, but once I copy the .vi files back into User.lib LV crashes.
    Does LV40 look in User.lib upon startup and crash if it finds something it doesn't like? A corrupted vi?
    Thanks!

    Blair Hogg wrote:
    ...guess the next step is to go in and load each .vi manually to see if there is one that is causing problems. Hopefully some of you out there are finding this somewhat interesting, and I'm not just cluttering up the forum...
    Hi Blair Hogg,
    I like your sence of humor ;-) Don't worry, even if nobody reads your
    thread (well... I just did) you need to write MUCH more for it to be
    considered clutter. Now, if you had created 25 duplicates of the same
    thread, then  we would be talking about cluttering...
    I'm curious about this issue even thought NI only supports LabVIEW two
    versions back - officially. My guess is that a VI is corrupted and
    kills LabVIEW when the VI loads. Therefore I do aggree that the
    procedure from now on is to load every single VI one by one and then
    notice what VI will make LabVIEW crash. I might be able to repair that
    VI if you submit it to the thread.
    Another thing to try is to mass compile the user.lib. The log after the
    mass compile will show if any VIs were bad or had problems getting
    compiled.
    Well, I hope you find the source for this issue - even if I'm the only one that cares ;-)
    Have Fun!
    - Philip Courtois, Thinkbot Solutions

  • Page fault error while calling reports from forms

    dear friends.
    when a report is called from forms, just before opening up of background engine the application gets hanged with page fault. One has to forcibly shut down the application before loggin again.
    The error mesage generated from log file is
    Fatal NI connect error 12203, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle80)(ARGV0=oracle80orcl)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=orcl)(CID=(PR OGRAM=C:\ORAWIN95\BIN\RWRBE60.EXE)(HOST=SOUMYADIP)(USER=Soumya))))
    VERSION INFORMATION:
    TNS for 32-bit Windows: Version 8.0.5.0.0 - Production
    Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.0.4.0.0 - Production
    Time: 06-MAY-00 14:03:32
    Tracing not turned on.
    Tns error struct:
    nr err code: 12203
    TNS-12203: TNS:unable to connect to destination
    ns main err code: 12560
    TNS-12560: TNS:protocol adapter error
    ns secondary err code: 0
    nt main err code: 102
    TNS-00102: Keyword-Value binding operation error
    nt secondary err code: 0
    nt OS err code: 0
    After closing if we run the report next time it runs, but after 3/4 attempts the above error again occurs.
    Please Help
    Prashant

    I'm getting this also. I thought it was
    due to my use of DATA PARAMETER. I've
    logged TARS on this and have yet to hear
    back from Oracle.
    Maybe if enough of us get the error Oracle
    will give some guidance on this one.

  • Wine page fault error on running Sims

    Hi All,
    I am suffering excruciating pressure from my teenage daughter who wants to run Sims on my Arch Laptop.
    It installs fine, but running it gives the following page fault:
    wine .wine/drive_c/Program\ Files/Maxis/The\ Sims/Sims.exe
    wine: Unhandled page fault on write access to 0x00000088 at address 0x409885 (thread 0009), starting debugger...
    Unhandled exception: page fault on write access to 0x00000088 in 32-bit code (0x00409885).
    Register dump:
    CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
    EIP:00409885 ESP:0033fd34 EBP:0033fe1c EFLAGS:00210216( R- -- I -A-P- )
    EAX:0033fd3c EBX:00000001 ECX:00000067 EDX:00400000
    ESI:7ee189c0 EDI:00400000
    Stack dump:
    0x0033fd34: 00000067 0040e5bd 00000000 00400000
    0x0033fd44: 00000067 00416840 00130d06 7ee4b7e8
    0x0033fd54: 0033fd74 7ef83a2f 0010f248 00419aa1
    0x0033fd64: 7ef94bdb 7efe4448 005605b0 00000094
    0x0033fd74: 00000005 00000001 00000a28 00000002
    0x0033fd84: 76726553 20656369 6b636150 00003320
    Backtrace:
    =>0 0x00409885 in sims (+0x9885) (0x0033fe1c)
    1 0x00416992 in sims (+0x16992) (0x0033fea8)
    2 0x7ee0f7c4 start_process+0x54() in kernel32 (0x0033fee8)
    3 0x7efbb254 call_thread_func+0xc() in ntdll (0x0033fef8)
    4 0x7efbb460 call_thread_entry_point+0x70() in ntdll (0x0033ffc8)
    5 0x7ef97d6a in ntdll (+0x37d6a) (0x0033ffe8)
    0x00409885: movl %esp,0x21(%ecx)
    Modules:
    Module Address Debug info Name (51 modules)
    PE 400000- 444000 Export sims
    PE 10000000-1000c000 Deferred drvmgt
    ELF 7bf00000-7bf03000 Deferred <wine-loader>
    ELF 7e508000-7e574000 Deferred rpcrt4<elf>
    \-PE 7e510000-7e574000 \ rpcrt4
    ELF 7e588000-7e591000 Deferred libxcursor.so.1
    ELF 7e591000-7e596000 Deferred libxfixes.so.3
    ELF 7e596000-7e599000 Deferred libxcomposite.so.1
    ELF 7e599000-7e5a0000 Deferred libxrandr.so.2
    ELF 7e5a0000-7e5a9000 Deferred libxrender.so.1
    ELF 7e5a9000-7e5ae000 Deferred libxxf86vm.so.1
    ELF 7e5ae000-7e5ce000 Deferred imm32<elf>
    \-PE 7e5b0000-7e5ce000 \ imm32
    ELF 7e5ce000-7e5e7000 Deferred libxcb.so.1
    ELF 7e5e7000-7e5fe000 Deferred libice.so.6
    ELF 7e5fe000-7e718000 Deferred libx11.so.6
    ELF 7e718000-7e720000 Deferred libsm.so.6
    ELF 7e743000-7e7de000 Deferred winex11<elf>
    \-PE 7e750000-7e7de000 \ winex11
    ELF 7e880000-7e8a6000 Deferred libexpat.so.1
    ELF 7e8a6000-7e8d1000 Deferred libfontconfig.so.1
    ELF 7e8d1000-7e8e5000 Deferred libz.so.1
    ELF 7e8e5000-7e969000 Deferred libfreetype.so.6
    ELF 7e969000-7e96e000 Deferred libxdmcp.so.6
    ELF 7e96e000-7e97c000 Deferred libxext.so.6
    ELF 7e98c000-7e99f000 Deferred system.drv16.so
    PE 7e990000-7e99f000 Deferred system.drv16
    ELF 7e99f000-7e9b2000 Deferred lz32<elf>
    \-PE 7e9a0000-7e9b2000 \ lz32
    ELF 7e9b2000-7ea08000 Deferred advapi32<elf>
    \-PE 7e9c0000-7ea08000 \ advapi32
    ELF 7ea08000-7eaa6000 Deferred gdi32<elf>
    \-PE 7ea20000-7eaa6000 \ gdi32
    ELF 7eaa6000-7ebeb000 Deferred user32<elf>
    \-PE 7eac0000-7ebeb000 \ user32
    ELF 7ed9c000-7ef08000 Export kernel32<elf>
    \-PE 7edb0000-7ef08000 \ kernel32
    ELF 7ef08000-7ef2e000 Deferred libm.so.6
    ELF 7ef2f000-7ef32000 Deferred libxinerama.so.1
    ELF 7ef32000-7ef35000 Deferred libxau.so.6
    ELF 7ef35000-7ef39000 Deferred libuuid.so.1
    ELF 7ef39000-7ef51000 Deferred version<elf>
    \-PE 7ef40000-7ef51000 \ version
    ELF 7ef51000-7f000000 Export ntdll<elf>
    \-PE 7ef60000-7f000000 \ ntdll
    ELF b74a8000-b74ac000 Deferred libdl.so.2
    ELF b74ac000-b75f2000 Deferred libc.so.6
    ELF b75f2000-b760b000 Deferred libpthread.so.0
    ELF b7622000-b762e000 Deferred libnss_files.so.2
    ELF b762e000-b7769000 Deferred libwine.so.1
    ELF b776a000-b7788000 Deferred ld-linux.so.2
    Threads:
    process tid prio (all id:s are in hex)
    00000008 (D) Z:\home\bmentink\.wine\drive_c\Program Files\Maxis\The Sims\Sims.exe
    00000009 0 <==
    0000000e
    0000001e 0
    0000001d 0
    00000015 0
    00000014 0
    00000010 0
    0000000f 0
    00000011
    00000016 0
    00000013 0
    00000012 0
    00000017
    00000018 0
    0000001a
    0000001f 0
    0000001c 0
    0000001b 0
    Backtrace:
    =>0 0x00409885 in sims (+0x9885) (0x0033fe1c)
    1 0x00416992 in sims (+0x16992) (0x0033fea8)
    2 0x7ee0f7c4 start_process+0x54() in kernel32 (0x0033fee8)
    3 0x7efbb254 call_thread_func+0xc() in ntdll (0x0033fef8)
    4 0x7efbb460 call_thread_entry_point+0x70() in ntdll (0x0033ffc8)
    5 0x7ef97d6a in ntdll (+0x37d6a) (0x0033ffe8)
    Anyone know how to progress this?
    Thanks,
    Bernie

    PirateJonno wrote:yup, see here: http://appdb.winehq.org/objectManager.p … n&iId=1015. It's a good idea to check there before trying to install something. I can personally confirm that the sims 3 works though.
    Thanks for that ... When you say Sims 3, is that the name, or does it have another title.
    Cheers,
    Bernie

  • Invalid page fault error in module kernel32.dll

    I'm a VB programmer attempting to learn java. I downloaded the j2se 1.40 sdk (At present I am running Windows 98) and installed it. The download and installation process was smooth. However when I attempt to launch the program, I get the illegal operation dialog with details as follows:
    SPLASH caused an invalid page fault in
    module KERNEL32.DLL at 0177:bff766bc.
    Registers:
    EAX=0055003c CS=0177 EIP=bff766bc EFLGS=00010202
    EBX=00000000 SS=017f ESP=00550000 EBP=00550010
    ECX=00000000 DS=017f ESI=00550108 FS=305f
    EDX=bff76855 ES=017f EDI=817b5b68 GS=0000
    Bytes at CS:EIP:
    e8 13 ad ff ff 8b 55 08 8f 82 b0 00 00 00 8b 4d
    Stack dump:
    002a0014 00000000 0055003c 0055003c 00550024 bff766fd 0055003c 005501b4 00000000 005501b4 bff883ed 0055003c bff79060 00000000 0064ffec ffffffff
    I suspect this has something to do with the OS. Can anyone shed some light on this for me.
    Thanks
    Nancy

    What command did you use to launch the program?
    The readme file explains how to set the path and classpath; if you've done that, try this command in a DOS window:
    java -version
    C:\>java -version
    java version "1.4.0"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
    Java HotSpot(TM) Client VM (build 1.4.0_01-b03, mixed mode)
    Good luck,
    Mike Rainville

  • Invalid Page Fault Error Messages - ICC Profiles and Fonts

    Possible causes of these error messages include bad ICC profiles and/or bad fonts. See below for corrective measures

    Q: Message reads:
    PHOTOSHP caused an invalid page fault in module
    KERNEL32.DLL at 017f:bff7b9f5. Registers:
    EAX=796692e0 CS=017f EIP=bff7b9f5 EFLGS=00210202 EBX=00d0fe28 SS=0187 ESP=00c10000...
    A: You have an incompatible or corrupt ICC profile in your
    Windows/System/Color folder (win 98/98SE/Me) or ./system32/spool/drivers/color (win2k).
    Make a temporary folder, ICMs, under and move all the
    ICM and ICC files to that folder.
    Start PS and make sure it restarts OK.
    Now move back JUST THE PROFILES YOU NEED to Windows\System\Color (win 98/98SE/Me) or ./system32/spool/drivers/color (win2k)
    Also see: http://www.adobe.com/support/techdocs/1c4f6.htm

  • Invalid Page Fault Error

    I an running PLUS80W on a P3 1GHz machine and
    when I start up the SQL Plus 8.0 application I get an invalid page fault in ORA805.dll
    If I use forms6i or reports 6i no problems.
    Is this a known problem and how do I solve it.
    Thanks
    null

    This sounds like a problem to work with Oracle Support on.
    - CJ

  • Every startup, I'm getting a full screen of AMD-Vi PAGE FAULT Errors

    Hello,
    I've been running arch for a while now, but ever since installation, every time I boot the computer I get a full page of AMD-Vi: Event Logged IO_PAGE_FAULT. It's the same message over and over again. I have an AMD FX 6300 Six-Core processor.
    Any help? Let me know if I can provide any more information

    Add "iommu=pt" to your kernel boot flags and make sure it's enabled in your BIOS/UEFI.
    Wiki guide on adding kernel parameters
    Last edited by elken (2014-11-07 18:10:25)

  • A page fault

    Hello..
    My program was working properly..But now i receive a page fault error like that..
    an invalid page fault in
    module visa32.DLL at 017f:63150934
    Registers:
    EAX=00120000 CS=0167 EIP=021b2fc4 EFLGS=00010246
    I can't see any reason..How can i choose this problem... (My OS is 98 and i use labview 7.0)
    thanks..

    Hi,
    Probable cause: Y2K bug in Oracle Installer.
    Set the clock back to 1999 or use a patch..
    See http://www.chow1.myweb.nl (33110C)
    HTH
    Martin

  • Page fault in nipalk.sys when writing large file , system crashes

    When reading from VXI 2211 and writing to a file the system crashes with a page fault error in nipalk.sys. I tried loading new drivers for VISA, VXI, even DAQ which I don't use. Where does nipalk.sys come from??

    jcnoble wrote:
    > When reading from VXI 2211 and writing to a file the system crashes
    > with a page fault error in nipalk.sys. I tried loading new drivers for
    > VISA, VXI, even DAQ which I don't use. Where does nipalk.sys come
    > from??
    This is the low level device driver used by all NI hardware device
    drivers. PAL stands most probably for Platform Abstraction Layer and
    what that means it is providing an uniform device driver API for
    managing memory, IO addresses, DMA channels and Interrupts. Most
    probably this NIPAL device driver API is almost the same on all
    platforms NI develops modern hardware drivers for. This allows easier
    porting of device drivers to new hardware as the big work for porting a
    hardware driver is about porting this NIPAL device driver.
    I
    would not think that disk writing is the real culprit here, but it may
    trigger a problem occuring earlier during VXI access.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Invalid page fault (only on one computer)

    I keep receving a whole set of invalid page fault errors when I try to open my VI.
    It is strange because the VI works perfectly on another, less powerful, computer running the same OS (Win98) and same version of LV (6.1)
    Does anyone have any advice?

    What all is in your code? Are you doing anything with ActiveX? Which module does the fault occuring in? This is possible a hardware issue at this point. It is possible that this could be cause by faulty memory. A page fault is generated when errors occur while moving pages in between your system memory and virtual memory. Is this a very large application? Try running other large programs (large Word or Powerpoint documents, etc.) to see if you can reproduce the page fault there. Are there any other VIs that will generate this same fault? What other software do you have on your system?
    Just a few guiding questions that might help determine were this page fault is generated.

  • System Level Page Fault Count

    Hi,
    Awesome work on this project.
    I am looking to get a count of the system wide page faults. I see that using new Sigar()).getSwap() there is some paging information, but it does not give me page faults.
    I can get page faults on a process level, and so a way to get total page faults is to add up all process page faults, but that is not performance friendly.
    Is there a way to get system level page faults with SIGAR?
    Thanks,
    SDY

    jcnoble wrote:
    > When reading from VXI 2211 and writing to a file the system crashes
    > with a page fault error in nipalk.sys. I tried loading new drivers for
    > VISA, VXI, even DAQ which I don't use. Where does nipalk.sys come
    > from??
    This is the low level device driver used by all NI hardware device
    drivers. PAL stands most probably for Platform Abstraction Layer and
    what that means it is providing an uniform device driver API for
    managing memory, IO addresses, DMA channels and Interrupts. Most
    probably this NIPAL device driver API is almost the same on all
    platforms NI develops modern hardware drivers for. This allows easier
    porting of device drivers to new hardware as the big work for porting a
    hardware driver is about porting this NIPAL device driver.
    I
    would not think that disk writing is the real culprit here, but it may
    trigger a problem occuring earlier during VXI access.
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Page fault handler will be paged out

    Hi All,
    I have a doubt. I know PageFault Handler handles the page fault error. Will PageFault thread be preempted?
    Also I wanted to know whether PageFault handler when it is Preempteed will be Paged out?

    page faults happen on the thread where the fault occurs. the IRQL will raise to dispatch to handle the exception, but the wait for the page will be synchronous. no, the handler will not page out
    d -- This posting is provided "AS IS" with no warranties, and confers no rights.

  • Page Fault Processor Exception (Error code 00000004) GWIA

    About every 24 - 36 hours GWIA aneds and unload GWIA from its address
    space
    Running 8.01 (with patches) on NW65 sp8 (with patches)
    Novell Open Enterprise Server, NetWare 6.5
    PVER: 6.50.08
    Address space GWIA removed Monday, April 12, 2010 11:53:27.355 am
    Abend 0 on P00: Server-5.70.08: Page Fault Processor Exception (Error
    code 00000004)
    Registers:
    CS = 001B DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0023
    EAX = 00000000 EBX = CA56C50C ECX = CA56C50C EDX = CA5CA998
    ESI = CA5CA998 EDI = CA56C1EC EBP = CA56C4C8 ESP = CA56BBF8
    EIP = F530E65E FLAGS = 00010246
    F530E65E 66AD LODSW
    EIP in LIBC.NLM at code start +0009465Eh
    Access Location: 0xCA5CA998
    The violation occurred while processing the following instruction:
    F530E65E 66AD LODSW
    F530E660 84C0 TEST AL, AL
    F530E662 7503 JNZ F530E667
    F530E664 AA STOSB
    F530E665 EB06 JMP F530E66D
    F530E667 66AB STOSW
    F530E669 84E4 TEST AH, AH
    F530E66B 75F1 JNZ F530E65E
    F530E66D 8B44240C MOV EAX, [ESP+0C]
    F530E671 5E POP ESI
    Running process: Server 00:35 Process
    Thread Owned by NLM: SERVER.NLM
    Stack pointer: CA56BBF8
    User Space Stack limit: 0
    Scheduling priority: 67371008
    Wait state: 50500F0 Waiting for work
    Stack: --CA2F5820 ?
    --C0E5BC80 ?
    F44B6290 (GWIA.NLM|ImapEngineCallback+9BC)
    --CA56C1EC ?
    --CA5CA998 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --CA5CA8B0 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --C8FE5EC0 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --CA56C50C ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --C1D45DC0 ?
    --C9BF50C0 ?
    --C9BF50C0 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    Additional Information:
    The CPU encountered a problem executing code in LIBC.NLM. The
    problem may be in that module or in data passed to that module by a
    process owned by SERVER.NLM.

    that's all that's in the ABEND log .... for each of the times that the
    GWIA unlaods
    The system doesn't actually abend - it just unloads the GWIA from the
    protected memeory space
    ataubman wrote:
    >
    > You haven't given us the modules list so we can't see what versions
    > you have. This problem should be fixed in GW 8 SP1 HP1.

  • Page Fault Processor Exception (Error code 00000002)

    We have begun to experieince the following abend on our Netware 6.5 server running GroupWise 8.
    Novell Open Enterprise Server, NetWare 6.5
    PVER: 6.50.08
    Server halted Wednesday, December 8, 2010 8:08:15.459 am
    Abend 1 on P02: Server-5.70.08: Page Fault Processor Exception (Error code 00000002)
    Registers:
    CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
    EAX = 78DBF1DC EBX = 6D86C060 ECX = 00446A97 EDX = FCAEF520
    ESI = 6FF57EE0 EDI = 7B4AB000 EBP = A067C9A0 ESP = A197F668
    EIP = 8038B5D8 FLAGS = 00010202
    8038B5D8 F2A5 **REPNE* MOVSD
    EIP in LIBC.NLM at code start +000945D8h
    Access Location: 0x7B4AB000
    The violation occurred while processing the following instruction:
    8038B5D8 F2A5 **REPNE* MOVSD
    8038B5DA 2403 AND AL, 03
    8038B5DC 8AC8 MOV CL, AL
    8038B5DE F2A4 **REPNE* MOVSB
    8038B5E0 8B44240C MOV EAX, [ESP+0C]
    8038B5E4 5E POP ESI
    8038B5E5 5F POP EDI
    8038B5E6 C3 RET
    LIBC.NLM|memcmp:
    8038B5E7 57 PUSH EDI
    8038B5E8 56 PUSH ESI
    Running process: GWIMAP-BCC_-Handler_2 Process
    Thread Owned by NLM: GWPOA.NLM
    Stack pointer: A197F418
    OS Stack limit: A19711C0
    Scheduling priority: 67371008
    Wait state: 3030070 Yielded CPU
    Stack: --038068DC ?
    --78DBF180 ?
    90246CD4 (THREADS.NLM|realloc+B8)
    --78DBF180 ?
    --6D86C060 ?
    --038068DC ?
    --03806900 ?
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --038068DC ?
    --A197F6A8 ?
    --00000100 (LOADER.NLM|KernelAddressSpace+100)
    --475BE354 ?
    A046BF23 (GWENN5.NLM|GWENN5@_WpmemRealloc+13)
    --6D86C060 ?
    --03806900 ?
    --475BE340 ?
    --A197F6C4 ?
    A045F6BA (GWENN5.NLM|GWENN5@?GetHandle%NgwBufIStream%%QAEKP APAX%Z+2BA)
    --03806900 ?
    --475BE354 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    -9AD5EF0C (GWENN5.NLM|GWENN5@??_7NgwBufIStream%%6B%+8)
    --4C60D600 ?
    --A197F6F4 ?
    9FC3E61B ?
    --4E457B00 ?
    --00001FFC (LOADER.NLM|KernelAddressSpace+1FFC)
    --A197F6DC ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00001FFC (LOADER.NLM|KernelAddressSpace+1FFC)
    9FBBAD00 ?
    --44DC2080 ?
    --4C60D600 ?
    --44DC2080 ?
    --A197F980 ?
    --A197F704 ?
    9FC3E425 ?
    --475BE340 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --A197F71C ?
    9FC2EBAD ?
    --475BE340 ?
    -9F31FACD ?
    -9F31F957 ?
    --A197F980 ?
    --A197F73C ?
    9FBBA181 ?
    --44DC2500 ?
    --00000002 (LOADER.NLM|KernelAddressSpace+2)
    --0006F734 ?
    --44DC2500 ?
    -9F31F957 ?
    --A197F980 ?
    --A197F750 ?
    9FBBB830 ?
    --44DC2500 ?
    --A197F980 ?
    -9F31F957 ?
    --A197F764 ?
    9FBBA640 ?
    --44DC2500 ?
    -9F31F957 ?
    --A197F980 ?
    --A197F78C ?
    9FBBA5B5 ?
    --44DC2500 ?
    --A197F78C ?
    --B18F2280 ?
    --B18F2320 ?
    --439CE400 ?
    -9F31FAF9 ?
    -9F31F957 ?
    --A197F980 ?
    --A197F7AC ?
    9FBBA143 ?
    --44DC2400 ?
    --A197F980 ?
    --0008EBC0 ?
    --44DC2840 ?
    -9F31F957 ?
    --A197F980 ?
    --A197F7C4 ?
    9FBBA6EE ?
    --475BEBC0 ?
    --4B23E4C0 ?
    --A197F980 ?
    -9F31F957 ?
    --A197F7D8 ?
    9FBBA024 ?
    --475BEBC0 ?
    -9F31F957 ?
    --4B8595AE ?
    --A197F9DC ?
    9FB85D78 ?
    --44DC2300 ?
    --00000067 (LOADER.NLM|KernelAddressSpace+67)
    --B18F2F60 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --4B859F60 ?
    Additional Information:
    The CPU encountered a problem executing code in LIBC.NLM. The problem may be in that module or in data passed to that module by a process owned by GWPOA.NLM.
    Emulated 5000 and found no RET instruction
    Function may never return.
    We are running GW 8 SP 1 on a Netware 6.5 SP 8 OS. I truncated due to character limit.
    Any help would be greatly appreciated.

    Originally Posted by utman
    My guess is that it is a problem in the GWIN code. Is SP 1 the latest? Usually when the code dies in libc it isn't really libc but the function that called libc.
    We just downloaded SP 2 (fairly new support pack) and some subsequent Hotfixes for SP 2. We will be loading those tonight.
    Thanks for your response.

Maybe you are looking for