Windows xp ticket cache read causes crash

UPDATE Old title: Error calling function Protocol status: 1312 FormatMessage failed with 1815<br>
<br>
I have written an application that authenticates to kerberos using the KerberosLoginModule. It used to work fine on all OS�s. (Windows 98, 2k, xp and Linux tested.)<br>
Now I have upgraded my application to java 1.5 code. And it still works fine on all tested OS�s, except Windows xp. Wich in first case does not even throw�s a error. It just exits in javaws. If I run it manually with java -jar I get the following output:<br>
<br>
Error calling function Protocol status: 1312<br>
FormatMessage failed with 1815<br>
<br>
UPDATE:<br>
After some more messing around I found out it craches because it want to read the ticket cache.<br>
Now I can understand there are some differences in ticket cache versions, but then java could choose not to read the ticket, like under linux. But why does it crash under Windows XP if it only try's to read a ticket? <br>
Now I can only choose between no ticket cache at all on all os's, or to build in a Windows XP filter for the ticket cache option. <br>
Both not very good solutions. Why is this and how can it be solved?<br>
<br>
Message was edited by: <br>
[email protected]

The meeting was quite successful as I can obtain a a ticket from the Win2k KDC now by Acquire TGT using AS Exchange (I have to enter my logon username/password because we have a Novell Logon and not WinLogon...) which results in Commit Succeeded.
But the ticket is not stored in the Windows XP credential/ticket cache, klist tgt says "Error calling function LsaCallAuthenticationPackage: 0
Format message failed with 1815", klist tickets says "Cached tickets: (0)" and kerbtray is empty!
And I stll receive the same error messages as mentioned earlier: "Error calling function Protocol status: 1312
Eine angegebene Anmeldesitzung ist nicht vorhanden. Sie wurde gegebenenfalls bereits beendet."
Do you have any suggestions/ideas what could be wrong with my system/configuration?
Message was edited by:
Santacruzshores
Message was edited by:
Santacruzshores

Similar Messages

  • Windows xp, minidump, applemtm.sys caused crash

    hi, my mbp just crashed in windows xp.
    remained minidump said, applemtm.sys caused crash...
    ^^ i know this info is too little figure out the problem...
    but, is there anyone faced like this one?
    -------- minidump -----
    ATTEMPTEDSWITCH_FROMDPC (b8)
    A wait operation, attach process, or yield was attempted from a DPC routine.
    This is an illegal operation and the stack track will lead to the offending
    code and original DPC routine.
    Arguments:
    Arg1: 00000000, Original thread which is the cause of the failure
    Arg2: 00000000, New thread
    Arg3: 00000000, Stack address of the original thread
    Arg4: 00000000
    Debugging Details:
    *** Kernel symbols are WRONG. Please fix symbols to do analysis.
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Your debugger is not using the correct symbols *
    * In order for this command to work properly, your symbol path *
    * must point to .pdb files that have full type information. *
    * Certain .pdb files (such as the public OS symbols) do not *
    * contain the required information. Contact the group that *
    * provided you with these symbols if you need this command to *
    * work. *
    * Type referenced: nt!_KPRCB *
    * Symbols can not be loaded because symbol path is not initialized. *
    * The Symbol Path can be set by: *
    * using the NT_SYMBOLPATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    * Symbols can not be loaded because symbol path is not initialized. *
    * The Symbol Path can be set by: *
    * using the NT_SYMBOLPATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    FAULTING_MODULE: 804d9000 nt
    DEBUGFLR_IMAGETIMESTAMP: 47685ec5
    CUSTOMERCRASHCOUNT: 1
    DEFAULTBUCKETID: WRONG_SYMBOLS
    BUGCHECK_STR: 0xB8
    LASTCONTROLTRANSFER: from 80547c4b to 804fbf0e
    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bacd3c8c 80547c4b 000000b8 ffffffff 00000202 nt+0x22f0e
    bacd3ce4 b7e06569 00000000 00000000 00000000 nt+0x6ec4b
    bacd3d10 b7e4be4a 8a1711d8 00000000 8a451e08 Wdf01000+0x15569
    bacd3d2c b7fcb53b 8a171290 75dc0430 8a23fbc8 Wdf01000+0x5ae4a
    bacd3d4c b7fcb651 75bae3b8 8a00de70 bacd3da8 applemtm+0x53b
    bacd3d5c b7e261b2 760ef150 75dfc680 bacd3d80 applemtm+0x651
    bacd3da8 b7e26253 b7e57a08 8a203978 89f10ea8 Wdf01000+0x351b2
    bacd3dc0 b7dfd5d3 8a00df97 8a203978 00000000 Wdf01000+0x35253
    bacd3ddc b7dfd68d 01f10ea8 8962e450 bacd3e08 Wdf01000+0xc5d3
    bacd3dec 804f280d 8a46c5a8 8a00de70 89f10ea8 Wdf01000+0xc68d
    bacd3e08 804f36b0 8a46c5a8 8a00de70 8962e450 nt+0x1980d
    bacd3e38 b99210d5 8a00de70 88da4980 8a2d3028 nt+0x1a6b0
    bacd3ea0 b9921d47 895bd170 00000000 8a2d37d8 USBPORT+0xa0d5
    bacd3ed0 b9922944 026e6f44 8a2d30e0 8a2d30e0 USBPORT+0xad47
    bacd3f08 b992413a 8a2d3028 80548abc 8a2d3230 USBPORT+0xb944
    bacd3f34 b993224b 8a2d3028 80548abc 8a2d3028 USBPORT+0xd13a
    bacd3f70 b99323c2 8a2d3028 00000001 8a34a834 USBPORT+0x1b24b
    bacd3f8c ba6b8d54 8a2d364c 6b755044 00000000 USBPORT+0x1b3c2
    bacd3fbc 8a34adb2 8a34a310 b993225c bacd3fd0 sptd+0x11d54
    bacd3fc0 8a34a310 b993225c bacd3fd0 80547e6f 0x8a34adb2
    bacd3fc4 b993225c bacd3fd0 80547e6f 8a2d364c 0x8a34a310
    bacd3fc8 bacd3fd0 80547e6f 8a2d364c 8a2d3028 USBPORT+0x1b25c
    bacd3fcc 80547e6f 8a2d364c 8a2d3028 00000000 0xbacd3fd0
    bacd3fd0 8a2d364c 8a2d3028 00000000 00000000 nt+0x6ee6f
    bacd3fd4 8a2d3028 00000000 00000000 b401ff4a 0x8a2d364c
    bacd3fd8 00000000 00000000 b401ff4a 6803fe95 0x8a2d3028
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    applemtm+53b
    b7fcb53b ?? ???
    SYMBOLSTACKINDEX: 4
    SYMBOL_NAME: applemtm+53b
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: applemtm
    IMAGE_NAME: applemtm.sys
    BUCKET_ID: WRONG_SYMBOLS
    Followup: MachineOwner
    ---------

    My MBP crashed with exactly the same dump. The crashes occurred during a StandBy operation (My MBP crashed regularly but not reproducably while trying to stand by/sleep).
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Documents and Settings\vas\Desktop\Mini070508-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: srvc:symbolshttp://msdl.microsoft.com/download/symbols
    Executable search path is: c:\windows\i386
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpspsp2rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Sat Jul 5 22:53:49.999 2008 (GMT-7)
    System Uptime: 0 days 22:33:47.814
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    * Bugcheck Analysis *
    Use !analyze -v to get detailed debugging information.
    BugCheck B8, {0, 0, 0, 0}
    * WARNING: Unable to verify timestamp for applemtm.sys
    * ERROR: Module load completed but symbols could not be loaded for applemtm.sys
    Probably caused by : applemtm.sys ( applemtm+53b )
    Followup: MachineOwner
    1: kd> !analyze -v
    * Bugcheck Analysis *
    ATTEMPTEDSWITCH_FROMDPC (b8)
    A wait operation, attach process, or yield was attempted from a DPC routine.
    This is an illegal operation and the stack track will lead to the offending
    code and original DPC routine.
    Arguments:
    Arg1: 00000000, Original thread which is the cause of the failure
    Arg2: 00000000, New thread
    Arg3: 00000000, Stack address of the original thread
    Arg4: 00000000
    Debugging Details:
    CUSTOMERCRASHCOUNT: 1
    DEFAULTBUCKETID: DRIVER_FAULT
    BUGCHECK_STR: 0xB8
    PROCESS_NAME: System
    LASTCONTROLTRANSFER: from 80544c3b to 804f9c12
    STACK_TEXT:
    bace7ccc 80544c3b 000000b8 ffffffff 00000202 nt!KeBugCheck+0x14
    bace7cdc 8054498b bace7d24 88d3b418 bab40120 nt!ScPatchFxe+0x46
    bace7cf0 80502b17 88d3b488 88d3b418 804fad6c nt!KiSwapContext+0x2f
    bace7cfc 804fad6c 00000000 00000000 8a19a4b0 nt!KiSwapThread+0x6b
    bace7d24 b7022569 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x1c2
    bace7d50 b7067e4a 8a0c2a30 00000000 8a37efb0 Wdf01000!FxWaitLockInternal::AcquireLock+0x3a
    bace7d6c b939853b 8a0c2ae8 75e65b78 8a19a480 Wdf01000!imp_WdfWaitLockAcquire+0xc9
    WARNING: Stack unwind information not available. Following frames may be wrong.
    bace7d8c b9398651 75c81210 89eee008 bace7de8 applemtm+0x53b
    bace7d9c b70421b2 764c7c80 7652beb8 bace7dc0 applemtm+0x651
    bace7de8 b7042253 b7073a08 89ad4140 89b38378 Wdf01000!FxRequestBase::CompleteSubmittedNoContext+0x63
    bace7e00 b70195d3 89eee12f 89ad4140 00000000 Wdf01000!FxRequestBase::CompleteSubmitted+0x97
    bace7e1c b701968d 01b38378 88a9ed80 bace7e48 Wdf01000!FxIoTarget::RequestCompletionRoutine+0x195
    bace7e2c 804f053f 8a053350 89eee008 89b38378 Wdf01000!FxIoTarget::_RequestCompletionRoutine+0x35
    bace7e48 804f13e2 8a053350 89eee008 88a9ed80 nt!IopUnloadSafeCompletion+0x1d
    bace7e78 b9843ee5 89eee008 892f5ee0 8a25c028 nt!IopfCompleteRequest+0xa2
    bace7ee0 b9844b57 89bdc4a8 00000000 8a25c7d8 USBPORT!USBPORT_CompleteTransfer+0x373
    bace7f10 b9845754 026e6f44 8a25c0e0 8a25c0e0 USBPORT!USBPORT_DoneTransfer+0x137
    bace7f48 b9846f6a 8a25c028 80545aac 8a25c230 USBPORT!USBPORT_FlushDoneTransferList+0x16c
    bace7f74 b9854fb0 8a25c028 80545aac 8a25c028 USBPORT!USBPORT_DpcWorker+0x224
    bace7fb0 b9855128 8a25c028 00000001 89edc578 USBPORT!USBPORT_IsrDpcWorker+0x37e
    bace7fcc 80544e5f 8a25c64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
    bace7ff4 805449cb b3f6362c 00000000 00000000 nt!KiRetireDpcList+0x61
    bace7ff8 b3f6362c 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b
    805449cb 00000000 00000009 0081850f bb830000 0xb3f6362c
    STACK_COMMAND: kb
    FOLLOWUP_IP:
    applemtm+53b
    b939853b ?? ???
    SYMBOLSTACKINDEX: 7
    SYMBOL_NAME: applemtm+53b
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: applemtm
    IMAGE_NAME: applemtm.sys
    DEBUGFLR_IMAGETIMESTAMP: 47685ec5
    FAILUREBUCKETID: 0xB8_applemtm+53b
    BUCKET_ID: 0xB8_applemtm+53b
    Followup: MachineOwner
    Message was edited by: tourist604

  • Files for Adobe Reader Cause Crash

    Every time I try to open a file for adobe reader, whether I get it embedded in my browser or download it from the internet either Safari crashes or Adobe Reader application crashes no matter what it is. I switched to firefox because Safari kept unexpectedly quitting constantly and it was becoming so frequent that I couldn't even do anything. Any advice on how to get the adobe reader plugin for safari to work(which i did install)? Or how to get any files to work? My friend has this same problem on her iBook, too.

    Hello David:
    First, I would trash the Safari preference file (com.apple.safari.plist) and restart. Then I would uninstall the current Adobe reader you have installed (get all of it) and then download the latest version from the Adobe web site. FWIW, I have no trouble at all with either safari or reading PDF files.
    Barry

  • CC 2014 (18.1.0) | Text Field editing causing crashes (Windows)

    Greetings;
    I've noticed lately that when saving files from CC 2014 to a CS6 format - and having those files edited on Mac, in either CS6 or CC - when re-opening those files text fields have been causing crashes on the Windows client. When that same file is opened and text fields are edited on the Mac client, a prompt will just appear stating "Cannot Edit text" - yet it still allows it.
    This has caused multiple issues for our teams as it has created files we're starting to refer to as "mine fields" - as working with the .ai file is like playing Russian roulette with text fields, you never know which one is going to crash the file.
    I would love to work with a team member from Adobe to help find a resolution to the problem, and I'm willing to provide any additional details that might aid in that process.
    Thanks!

    Hello Pureweb,
    Please upload the crashdumps on some file sharing website say Dropbox and share the link with us by sending a mail to "[email protected]". We will analyze the dump and will suggest you the workaround appropriately.
    In parallel, please check that you do not have any 3rd Party plugins installed in it. Please try to remove them one-by-one and see which one causes the crashes or do reverse i.e. remove all the 3rd party plugins. Or Uninstall Ai and check at following location:
    C:\Program Files\Adobe\Adobe Illustrator CC 2014
    Please verify that nothing is left at above location on uninstalling Ai. Then try a fresh install and see if Ai works.
    Also, verify that you have the updated Wacom drivers on your system. This might be an issue with the 3rd party program as well. One of the user who was having a similar issue reported on the Ai forum that one of the 3rd party Stahl's ImageWorx DTG RIP - a program for printing to a Direct To Garment printer was causing the issue. So, you may check if the similar thing is not happening in your case.
    Regards,
    Dhirendra

  • AutoVue viewer caused crash while viewing .XSLX documents.

    We use AutoVue Desktop Deployment Viewer incorporated in our application (using JNI). When viewing XLSX (Microsoft Excel) documents on Windows 8.1 x64 system it caused crash of application. It's reproducible only on Windows 8 (8.1 or Server2012) systems. If we set compatibility mode (Windows 7) then problem isn't reproducible.

    I would recommend you log a ticket with customer support

  • Photoshop CC Content - Aware Move Tool causes crash

    Does anyone have any ideas why this is happening? Content Aware Move tool causes crash every time so far with tiff and jpegs and its getting frustrating!
    I have Windows 8.1 Pro with 8GB RAM
    NVIDIA GeForce GT 650M Graphics
    Photoshop CC 64 bit

    Thanks for the reply JJMack - I have to be honest, i'm not exactly sure what i'm looking for here!
    Source
    Adobe Photoshop CC 2014
    Summary
    Stopped working
    Date
    06/04/2015 09:45
    Status
    Report sent
    Description
    Faulting Application Path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
    Problem signature
    Problem Event Name: APPCRASH
    Application Name: Photoshop.exe
    Application Version: 15.2.2.310
    Application Timestamp: 5480338c
    Fault Module Name: FaceDetection.dll
    Fault Module Version: 2.2.6.32411
    Fault Module Timestamp: 52e12400
    Exception Code: c0000005
    Exception Offset: 000000000001704d
    OS Version: 6.3.9600.2.0.0.256.48
    Locale ID: 2057
    Additional Information 1: e87c
    Additional Information 2: e87c816cbb2acbf5e54624fc2b1f98cc
    Additional Information 3: 1879
    Additional Information 4: 1879b998534215d47b0a850e45784427
    Extra information about the problem
    Bucket ID: 2dac81db98a57fddf5997edfd40ba6eb (85993531415)

  • ILife Site Causes Crashes

    While at work on a PC, I've tried to browse the iLife site and had several different browsers crash due to a QuickTime "malfunction." I'm using QT 7.0.3 for Windows, and the following browsers IE 6, Firefox 1.5 and Opera 8 all crashed. The crashes occur at any given moment--sometimes immediately when the intro QT movie plays, sometimes when I go to each individual iApp page. I've been able to view some of the items under each iApp, but sooner or later--CRASH! Any advice would be much appreciated...otherwise, I guess I have to wait to view on my Mac at home.
    iMac G4 1GHz 17" widescreen flat-panel   Mac OS X (10.4.3)   512 MB RAM

    It seems they must have received enough response from others as they have changed the layout somewhat. And Quicktime 7.0.4 was released for Windows users...

  • Photoshop CS4 and graphic cards. Can cause crashing?

    Since upgrading to CS4 I seem to have increased crashing.
    Here are my system specs.
    Mac 2 x 2.66 GHz Dual-Core Intel Xeon
    9 GB of Ram
    250 GB internal dedicated scratch disc
    NVDIA GeForce 7300 GT with 256 VRAM
    After having endless techs look at my machine and upgrading everything. I am beginning to suspect the graphics card.
    With OpenGL can a underperforming video card cause crashing in photoshop especially with massive file sizes ( multilayered CMYK poster sized files the can exceed 7 GB)?

    Did you install the 11.0.1 update?
    Is your OS up to date with patches?
    Have you tried disabling OpenGL in preferences to avoid using the GPU/Graphics card?

  • Adobe Reader X Crashes after filling a specific form field

    I've recently upgraded to Adobe Reader X on some of our systems.  Now I have a user unable to fill out a form without reader crashing.  I've duplicated the issue on my PC, and confirmed that the form is functional with Reader 9.4.1 running on another system.
    The pdf we're having issues with is here:
    http://www.ime.state.ia.us/docs/CrossOverProfessional.pdf
    Usersa re able to fill out everything up to the field #21, titled "Billed Amount".  When a dollar amount is entered in this field, adobe reader crashes.  If I skip this field, reader also crashes when a dollar amount is entered in field #22, Allowed amount.  All other fields on the page can be filled out without issue.
    This document does seem to do some data verification as you leave a field, checking to confirm the data entered is the right number of digits, alpha or numeric, dates in the correct format, etc.  I suspect whatever type of checks it's trying to do on these two dollar amount fields must be causing the error. 
    Is this a bug in how Reader X handles forms created in previous versions of acrobat?  Short of asking for the form to be updated, is there anything I can do to make this work with Reader X, or do I need to roll back to version 9 for now?
    Thanks!

    Thanks.  I've posted there as well.  Anyone know if there's a workaround to keep reader from crashing with this form, or is my only option to roll back the servers until the creator of the form updates it?
    (I have notified their webmaster of the issue, but who knows how long it will take the state to update the form.)

  • Acrobat Reader 9 Crashes PC When Opening 2 Documents Simultaneously (2D Graphics Acceleration Relate

    Hey all,
    Weird issue. I noticed my Adobe Acrobat Reader 9 crashes when opening two PDF's simultaneously. The first one opens just fine. The second one, a new window opens, but there's only black inside the 2nd Reader window. It finally (after way too long) begins to show the document, and then I get a blue screen of death with a fault in nvlddmkm.sys, the nVidia display driver for my video card. It says it was unable to reset the display drivers, dumps the memory, and reboots. One interesting note is that if I close the "black" window before it blue screens, I can continue using the computer with no crash. It's only if I give it time to try to display.
    I already found the temporary fix for this, which is disabling 2D Graphics Acceleration in the Acrobat Reader (Edit -> Preferences -> Page Setup). Fortunately I'm on a fast computer, so this doesn't affect performance much, but it still obviously isn't ideal, and I'd like to see the problem resolved.
    I don't experience this problem with any other programs at the moment, so I'm thinking it's an issue with Adobe's product or possibly the nVidia drivers, but thought I should mention it and see if anyone has any other possible fixes where 2D Graphics Acceleration can remain enabled.
    Thanks all!

    I am having the exact same issue... it's so frustrating! Does anyone have a solution to this?
    Running CS4 on a Core i7 workstation w/ Win 7 64-bit, latest BIOS and video card drivers (ATI Radeon 4890). Acrobat is version 9.3 with all updates. It freezes for 30 seconds just as described, every single time you launch it.

  • Show hidden characters shortcut causes crash

    I'm running CS4 on Mac OS 10.5.8 (Indesign 6.0.4 which I believe is the latest).
    Lately, InDesign has started crashing when I use command+opt+I (the shortcut for show hidden characters), which I do A LOT for text design purposes. It doesn't crash every single time I use the key combo, but it's gotten to about 50% of the time, so that I'm afraid to use it. I'm very shortcut oriented rather than menu oriented, so please don't suggest I just stop using the shortcut (that's what my IT guy would suggest). It took me forever to even remember what the command was called that I was doing -- I ended up finding it by accident.
    Has anyone else run into this? Does anyone have any advice/suggestions?
    Thanks!

    I would start by Quitting Indesing, removing (putting on Desktop in case you have custom settings saved there) the Indesign Prefs;
    /Users/YOUR HOME FOLDER/Library/Preferences (Indesign Folder & .plist) and also removing the Indesign Cache folder;
    /Users/YOUR HOME FOLDER/Library/Caches.

  • Adobe Reader X Crashes after Java Update to Version 7 Update 51

    I just installed the new Java update Version 7 Update 51 and now Adobe Reader X crashes in Windows 8.1 within 3 seconds, any advise would be helpful.
    Bankruptcy Attorney

    Thanks.  I've posted there as well.  Anyone know if there's a workaround to keep reader from crashing with this form, or is my only option to roll back the servers until the creator of the form updates it?
    (I have notified their webmaster of the issue, but who knows how long it will take the state to update the form.)

  • How do I stop Adobe Reader from crashing on my unprivileged user?

    I am running Windows 7 and I needed to create an unprivileged user on my computer. When I open a PDF file, it almost instantly crashes (I can view the document for about three seconds). If I simply open Adobe Reader without a PDF and click Edit -> Preferences, it crashes. If I open a PDF in any browser, it crashes.
    From what I have been able to surmise, it seems that Adobe Reader is trying to read the registry of my privileged user. I have tried uninstalling Adobe Reader, temporarily giving privileges to my unprivileged user, installing Adobe Reader on that user, and then remove the permissions, but the crash still occurs. The only way to stop Adobe Reader from crashing is to start the program as an administrator or change the account type to administrator. How do I stop Adobe Reader from crashing on my unprivileged user?

    It said "Adobe Reader has stopped working" soon after I opened it, but I was still able to scroll down the document. It was only once I pressed Close Program that it stopped working.
    Upon trying it a second time, it immediately stopped letting me scroll down when the program crashed. Here is the error log, I receive the exact same exception code every time:
    Application Error
    Faulting application name: AcroRd32.exe, version: 11.0.1.36, time stamp: 0x50d0b932
    Faulting module name: AcroRd32.exe, version: 11.0.1.36, time stamp: 0x50d0b932
    Exception code: 0x40000015
    Fault offset: 0x000b7e40
    Faulting process id: 0x104c
    Faulting application start time: 0x01ce02e04f2d96cc
    Faulting application path: C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe
    Faulting module path: C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe
    Report Id: 961d161d-6ed3-11e2-9fb2-001fbc09988e

  • Satellite C660-23M - driver causing crash when program starts

    I have loaded a CAD program on my new 64bit laptop, the program will start then stops and windows closes it. In the crash reports the modules ntddll.dll and aticfx.dll both seem involved. Could there be some conflict, can I update a driver somehow?
    I have seen a report on a gaming website that the aticfx.dll isa the problen on the c660 range.
    Please help or the machine goes back to the shop.
    PS I have tried running in compatibility mode and disabling antivirus but the problem is unchanged
    Regards Ian

    Hi
    I think the CAD application is not fully compatible with the preinstalled graphic card driver.
    The ntddll.dll files is part of the windows system and aticfx.dll file seems to be a part of the graphic card driver and therefore I think that you would need to use another graphic card driver.
    The notebook seems to support an Intel HM55 HD graphic card. Try to update the driver using the newest version from the Intel page.

  • Barn doors transition causes crash

    Dear Community,
    Applied barn doors transition to a project in CS4. Stored that project in 2010.
    Opened the project in CS6 CC - and barn doors caused crashes - so I cleaned off the old and applied replacement barn door transitions in CS6 CC.
    Once the wipe is applied - its fairly stable - sometime crashes sometimes doesn't.
    If I apply a broder colour to the wipe - all ok.
    If I then apply a border thickness - crash every time.
    System;
    Premiere Pro CS6 - 6.0.3 (001 (MC: 264587)) through cloud membership
    Updated and current
    Win 7 Pro - SP1 - 64 Bit
    Source footage SONY EX3 - .mp4 and still image .png's
    No error messages - just crash and need to restart PP CS6
    Try to apply colour and border to a barn door transition causes the error
    This worked before on the smae project when created in CS4
    Not running other software at the time
    NewBlueFX modules installed but not applied to this area of sequence
    i7 - 3.20GHz, 16GB RAM, SSD OS drive, 4 x drive RAID on LSI RAID card, - No I/O hardware
    I am using Are you using Mercury Playback Engine Acceleration and CUDA
    Problem occurs during normal edit - as soon as I start to adjust the barn doors wipe - I don't get to compression
    Thanks
    Dave

    Doies it help anyone that I just received this from the email address; [email protected];
    Hello,
    You have received this email because the content you posted below has been rejected by our moderators.
    Re: Barn doors transition causes crash
    posted Jun 5, 2013 5:15 PM  
    Since the original report earlier today - I now just have to put the timeline scrubber over the barn doors transition and PP CS6 closes without an error message and without saving. The unfortunate part here is there doesn't seem to be any record or log of the crashes to be able to disseminate whats going wrong.
      Barn doors worked in CS4 - and the only change in this project is the re-opening in CS6 CC."
    Question; Did I put something in there that was defammatory, rude, obnoxious, incorrect or un-helpful?
    If anyone here believes I did, I sincerely apologise for the need of moderators to have intervened... and for causing any offence.

Maybe you are looking for