Firefox 4 crashing display driver

I am using acer aspire4741G with an NVIDIA GEFORCE GT330M' driver version 8.16.11.8886'(ForceWare 188.86). when i browse using firefox the display driver crash and show me one message like (the display driver has stopped working and recover successfully). Firefox is the best browser with the perfect extensions but this problem make me sad

Hi every buddy its me again.I just successfully solve my previous problem. How? its so easy' just update your firefox browser. I think this problem happen only in the firefox 4 beta 7 and 8. The new version of the firefox 4 beta 9 to12 and 4RC is much batter than before. Thanks everyone and run the fox as you wish....

Similar Messages

  • MSI 660 TI PE Display Driver crashes

    First, here is my system.
    i5-2500k Processor (http://www.newegg.com/Product/Product.aspx?Item=N82E16819115072) (Processor is overclocked to 4.3ghz, temp on it never goes over 45-50°C though)
    MSI Geforce GTX 660TI PE Video card (http://www.newegg.com/Product/Product.aspx?Item=N82E16814127696)
    Asus P8Z68-V Pro\Gen 3 Motherboard (http://www.newegg.com/Product/Product.aspx?Item=N82E16813131790)
    Corsair HX series HX650 Power Supply (http://www.newegg.com/Product/Product.aspx?Item=N82E16817139012)
    4x4GB of G.Skill Ram (http://www.newegg.com/Product/Product.aspx?Item=N82E16820231314)
    When my old MSI P67A-GD55 Motherboard bricked a month ago, instead of waiting on RMA I went ahead and got the Asus board, at the same time I went ahead and upgraded my old Asus GTX 560TI card to the MSI GTX 660TI card. Since the upgrade, I am constantly getting display driver crashes "Display driver nvlddmkm stopped responding and has successfully recovered." when playing games. Guild Wars 2 and Starcraft 2 are the only ones I've had time to try, but both consistently give driver crashes after awhile (sometimes as soon as 15-20 mins, sometimes takes several hours of gameplay).
    Here is the list of things I've already tried:
    -First, I tried the most recent Nvidia drivers. Still crashes.
    -Second, I tried running driver sweeper, removing all old drivers and reinstalling. Still crashes.
    -Third, I tried disabling TDR in the Win7 registry. Still crashes.
    -Fourth, I really ramped up the auto fan speeds. So far it hasn't crashed while doing this, but I can't do it for too long because the fans get so loud that it annoys me greatly.
    -Fifth, I thought it might be an old Motherboard driver conflict of some sort, so I completely formated my OS hard drive and reinstalled Windows 7. Still getting crashes.
    -Sixth, I used driver sweeper again and rolled back to the last official MSI drivers (the ones from October). Still getting crashes.
    I really don't think the card is overheating. The most recent crash happened tonight after playing Starcraft 2 for about 20 minutes, and the temperature of the card never got over 60°C. That's why even with the extremely ramped up fan speeds I tried, I think if I used them long enough, the driver would still crash.
    The power supply is the same as what I used with the 560TI and it didn't have these issues. And from my understanding, the 560TI consumed more power than the 660TI.
    At this point, I'm at my wits end. The only thing else I know to try is swapping out the old 560TI in with the new motherboard or waiting for my old motherboard to come back from RMA and trying the 660TI in it. Though that means rebuilding the case, uninstalling the new mobo drivers and installing the old mobo drivers and authenticating Windows. Doing all of that is going to kill most of a day and I really only want to do that if I absolutely have to.
    I've had such limited time for troubleshooting the card, that I'm regrettably past the 30day limit on RMA replacements to Newegg. So unfortunately that means I'm looking at an RMA directly to MSI and that takes about a month. Before I do that, does anyone have any advice on something to try that might be the cuplrit or can help determine the culprit? I can't find any details in the Event Viewer as to what caused the driver crash. Just that it has stopped responding and has recovered. I wish it could tell me if there was a loss of power, or anything. Power Management Mode is set to prefer maximum performance btw.
    Btw, as a brief description of what happens. The screen goes black, and then comes back and the game is running very slowly. There will also usually be a popup above the taskbar saying that the driver had crashed. I keep the MSI Afterburner info window open in my second monitor and Power usage never goes over 80%, GPU Usage is usually around 95-99%. Core Clock and Memory clock drop to about 324mhz (which is what it idles at) temporarily during the crash. GPU Usage of course dips to very low levels while the driver is crashing, as well.
    Oh and in an added twist, I've run Kombuster several times. Burn-in test DirectX 11 1920x1600 8xMSAA as long as five hours, and the display driver has never crashed. I'll probably turn it on, and disable the computer's sleep and display off tonight and let it run for about 8-9 hours and see what happens. That's one thing that throws me off, if it's a hardware defect, wouldn't Kombuster cause it to crash?
    edit-Here is a screenshot of the Afterburner monitor during a crash while playing Starcraft 2. The huge dip in the bars that I have the cursor over is when the crash occured.

    Well with the Power% limited to 75%, I just had another crash in Starcraft 2. Temp was only at 56°C just before the crash.
    Here is a shot of the Afterburner Hardware Monitor when it crashed:
    Unfortunately I do not have another PC to test the card in. And I don't know anyone around here with a system that the card could work in.
    If I swapped out the 660TI with my old 560TI and I do not get any crashes, wouldn't that indicate it's the 660TI's fault and I'd need to RMA since the 560TI is a more power hungry card?

  • Far Cry 4 - Display driver stopped responding and has recovered

    After several hours of play without driver crash i get today first driver crash in Far Cry 4.. Application stopped. Then i saw on events: Nvlddmkm Display driver stopped responding and has recovered. Its very random , sometimes i can play even 24 hours without driver crash and sometimes like today its crashed driver after 5 minutes of started game.
    Its problem with driver or my its just my card? ( i am using stock Gtx 980 ). I am using the newest drivers. All other games runs without even single crash. I tested Unigine Heaven for 10 hours, without crash. I tested Metro Last Light for few hours without crash too.
    Only Far Cry 4 sometimes crash after 5 minutes,but mostly often i can play 24 hours without driver crash.
    Using 347.88 WHQL.
    All my pc is stock, cpu is 4790k stock. GPU is on stock too.
    From what i know,crashing display driver Nvlddmkm its always graphic card ( hardware ) failure? Rma graphic card?
    TDR's are always happening because of "bad/broken" hardware?Or it can be software too?

    Well add proper specs: >>Posting Guide<<

  • When I have firefox open, it crashes at the same time as my display driver crashes (Crash signature: kernelbase.dll@0xb9bc)

    The screen turns black (audio remains normal if I'm playing music) and then flickers back on. I get a message that says "Nvidia display driver stopped responding and has recovered successfully." This happened before and Firefox wouldn't always crash, but the last few days it happens several times a day and Firefox always crashes at the same time as the display driver.

    No, they aren't working on the same files. All 3 employees are working on different files.
    They are all on Dell Optiplex GX745 with 4 Gb of RAM.
    The crashes are at different times, not all 3 crashing at the same time. Therefore, I don't believe network is the cause of the issues. Also, it didn't crash on CS5, but now it does on CS6.
    What I'm looking for are possible settings within Illustrator CS6 that I can tweak to make it a more stable program.
    Thanks

  • Firefox can't recover after my display driver crashes

    My display driver is garbage, it crashes multiple times a day. It always has (I got this laptop second-hand).
    I'm used to it. I've tried reinstalling drivers, editing the registry, reinstalling windows, switching browsers, etc etc etc
    It's fine, I guess I can live with it crashing throughout the day, it flicks back on in a second or two.
    HOWEVER, I can not live with it shutting down my browser EVERY TIME. Chrome and IE can recover from this, but apparently Firefox can't. Firefox just goes blank and won't respond- I lose all my pages. Chrome and IE will bounce back with the pages and tabs that were open when the display crapped out on me.
    I guess my question is, how do I prevent this from happening?
    Or can you fix firefox so that it can recover from this? I really hate using chrome. Help me out, firefox

    Did you already disable hardware acceleration in Firefox?
    *https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration
    *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
    Make sure that you do not run Firefox in permanent Private Browsing mode (Never remember history).
    *https://support.mozilla.org/kb/Private+Browsing
    *Tools > Options > Privacy > Firefox will: "Use custom settings for history"
    *Deselect: [ ] "Always use Private Browsing mode"

  • With hardware acceleration enabled, and with plenty of tabs open, using the Windows 7 taskbar preview option will almost always crashed the nVidia display driver.

    Latest Firefox 4 beta 6.
    nVidia GT240 1GB DDR3 with driver version 258.96.
    Windows 7 Ultimate.
    If I have plenty of tabs opened, in Firefox 4 beta 6 with hardware acceleration enabled, using the Windows 7 Taskbar preview feature (that will show all the tabs Firefox has loaded) will cause the Nvidia display driver to crash. When this happen, the GUI part of Firefox will be unusable and has to be killed via Task Manager.
    This doesn't happen if hardware acceleration is disabled.

    It is beta software and the older 4.0 b6 version may not work with all display drivers.
    You can trey the test extension: http://jagriffin.wordpress.com/2010/08/30/introducting-grafx-bot/

  • Intel display driver crashes on S1 Yoga running 64-bit Windows 8.1

    Whenever my machine comes out of suspend mode, the display driver crashes.  It goes to a black screen for about 8 seconds then I get the error "display driver intel hd graphics drivers for windows 8 (r) stopped responding and has successfully recovered".   The black screen is consistent but the error is occasional.  I also got the error when performing a right click on the desktop to enter the display properties. I am running the most current driver for my graphics card and the most current BIOS version.  After researching this problem online it appears that it is a known issue but the fixes I saw posted all included using an older driver from another manufacturer.  Is there a better fix from Lenovo out there?

    Hi @curtisa, @guigs2 and @rmcguigan,
    Thanks for your responses.
    I managed to get eWallet working correctly for 24 hours approx. by uninstalling Firefox, running CCleaner, deleting all Mozilla references on my system drive, scanned for virus using Win Defender, SuperAntiSpyware, and SpyHunter, (nothing reported) then again downloading and installing the current version of FF to "Program Files (x86)".
    However next morning, it had failed again.
    I checked the Windows event log and it shows an error with a Source of .NET Runtime. The application is eWallet.exe, Framework Version V4.0.30319, Exception Info SystemAccessViolationException.
    I'm not sure what that all means, and would welcome any further suggestions.
    Cheers
    Steve

  • Google+ Stories crashes NVIDIA display driver until computer gets a BSOD. Help?

    Google+ Stories, the automatic scrapbook, is the one responsible for giving my computer a BSOD.
    Whenever I go to my photos in Google+ and into a Google+ Story, my screen just turns black for about 3-5 seconds and back with a message "NVIDIA Driver Driver stopped responding and has successfully recovered.". After 1-5 seconds, my screen would turn black again and eventually displays a Blue Screen of Death 0x00000116.
    This only happens when I'm using Firefox while in Google+ Stories.

    This seems more fitting to go onto a Microsoft forum rather than here.
    Try this:
    Step 1- Open Windows in Safe Mode
    Restart your computer. When the computer is restarting, hold the F8 key for the Advanced Boot Options. From there, select the Safe Mode option and press the enter key.
    Step 2 -- Open Computer Properties
    After the Windows boots up in safe mode, open the Start menu and right click on Computer. From the drop down menu, select the Properties option.
    Step 3 -- Open Device Manager
    Once the System Properties window opens, click on the Device Manager.
    Step 4 -- Uninstall display adapter
    As a result, the Device Manger window will open up. Over there, we will expand the Display adapters and you will notice that a display driver is installed. We will right click on it and select the Uninstall option.
    Step 5 -- Agree to uninstall
    With that done, a confirmation pop window will open; click on the Ok button to remove this device.
    Step 6 -- Restart your computer
    Now close all the open windows and restart your computer in normal mode.
    When the Desktop appears, go to the notification area and you will notice that the callout will appear. Click on it in order to view the status.
    Step 7 -- Restart after Driver Software Installation
    As a result, the Driver Software Installation window will open and it will start installing the Video Driver which is compatible with your windows.
    Once the installation completes, it will ask you to restart the windows in order to apply the changes. Click on the Restart Now button.
    To see if Firefox is contributing to this BSOD, can you see if Firefox has any crash reports submitted?
    #Enter ''about:crashes'' in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
    #Copy the '''5''' most recent Report IDs that start with '''bp-''' and paste them into your response here.

  • Beta repeatedly crashing Nvidia display driver; no other app does. What's up?

    Toshiba Qosmio with lots of memory.
    Beta crashes the display driver, which self reboots, principally when I try to use the Back button.
    The computer is rock solid in other apps.

    The latest drivers do not fix this very common problem that people are widely posting about on the web. In fact the problem is the latest, and not so latest drivers. The current bypass for this long standing bug in nVidia`s software, quality control, training and HR practices is to install the old 275.33 drivers.
    If you can 100% fix the problem with a software change it is a software problem not a hardware problem, and that is the case with the Firefox crashes.
    If you have other problems, not just Firefox, then you have some other problem -- so start your own topic.
    nVidia GTX460, never over-clocked, and it crashes Firefox with any version of the nVidia WHQL drivers later than version 275.33.
    Anyone wanting proof that this problem is caused by nVidia is invited to install the 275.33 drivers and see that this particular problem goes away.
    I'm shocked. I pointedly advise everyone to stay away from nVidia because nVidia has been so incredibly intransigent in its refusal to admit the problem is its drivers.
    I've done clean installs, even installs with DriverSweeper, all the WHQL versions since 275.33, as clean as is possible without re-formatting and re-installing Windows, and it just does not help.
    But you know, if a clean install did fix it, it would still be a bug in nVidia's code because requirements for clean installs are due to bugs in install scripts.
    Anyway, clean installs don't fix it. You can only fix it by going back to an earlier nVidia driver, (one that doesn't have the optimization for SkyRim, the game I'm waiting to play).
    nVidia's corporate attitude on this is a disgrace. The immediate solution they should provide are fixed drivers and install scripts, but this problem has gone on for so long now that a software fix is just a bypass. The real bug is poor management attitude.

  • Photoshop CC 2014 having a problem with display driver then crashes computer

    Since the Photoshop update in October most of the time when I open Photoshop CC 2014, either my computer crashes with the driver state power failure or the program is able to boot and provide an error message involving a problem with the display driver and then my computer crashes with the driver state power failure. I did not have this problem until the update in October. Any help would be greatly appreciated.
    I am using Windows 8.1 64-bit
    Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz processor
    12.0 GB of RAM
    NVIDIA GeForce GTX 860m
    Intel HD Graphics 4600
    All drivers and programs are up to date.

    VHail wrote:
    …All drivers and programs are up to date.
    You need to update your video driver from the website of the manufacturer of your video card.  You cannot rely on Windows Update or Microsoft, which typically have outdated drivers.

  • R400/T400/T500/W500: display driver "amdkmdap" crashes

    Executive summary: All current Lenovo ThinkPads with switchable graphics (R400, T400, T500, and W500) have usability issues in connection with Vista and the use of external monitors. For more than half a year, users were plagued by frequent Windows crashes. During that time frame, Lenovo did not comment on the various available reports and complaints. By the end of April 2009, Lenovo resolved many issues by releasing a new official driver. Though several problems, including severe ones, remain as of today. Lenovo has said to be actively working on the remaining issues (without outcomes so far).
    Important information for affected users: If you're having one of the issues reported here, then Lenovo advises you to call your local Lenovo Support. Demand that a case is submitted to hardware engineering. In particular, you should ask for "a CMVC case to be created and escalated". Using these "code words" ensures that your case is properly addressed.
    Old problem description
    On Vista 32 and Vista 64, the ATI display driver "amdkmdap" crashes when an external monitor was active before OR an application (game) using DirectX technology is used. The user typically receives a couple of so-called "Timeout Detection and Recovery" (TDR) messages from Vista:
    (Click here for an explanation of the message from Microsoft)
    Sometimes, amdkmdap crashes several times in a row. Then Windows crashes with a so-called "BSOD", likely resulting in data loss. Typically, Windows detects "atikmpag.sys" as the crashing driver. Sometimes, also an instantaneous reboot happens independent of prior TDR crashes. In such a case, no BSOD is displayed.
    The following movie illustrates the phenomenon: http://www.youtube.com/watch?v=LBX9QsCmrpY
    This behavior above has been confirmed for the following ThinkPad models: R400, T400, T500, and W500 (see below). Problem reports indicate that the symptoms are often related to playing games and/or the notebook being docked and the external monitor being connected via DVI.
    Though, the presence of these two conditions is not necessary to trigger the driver crash:
    There are reports where no dock was involved and the external monitor was connected directly to the notebook's VGA port.
    Furthermore, there are reports where the notebook was docked and an external monitor was connected to the DVI port.
    So far, there has been no report relating to a monitor being connected to the Display Port which is available on some models. (Possibly because this port is not used.)
    There are a few reports where neither a dock nor an external monitor was involved.
    Playing certain games reliably triggers the crash.
    Steps to reproduce
    While intially (around September 2008 - October 2008) the crash could be triggered easily, the situation is now (December 2008) more complex. The crashes do still occur, though there is no clear pattern anymore. According to various reports, the display driver crash can be triggered as follows:
    Resuming from standby
    Watching a DVD.
    Playing one of these games: Fallout 3, Bioshock, Team Fortress 2, Knights of the Old Republic.
    Arbitrarily during normal work. On a normal working day, the problem occurs at least once.
    Further issues
    Here are more issues which seem to be related. More information can be found in other posts of this thread:
    The notebook display and/or the external monitor runs at a low resolution after resuming from standby.
    After the login both monitors flicker while adjusting the resolution of the monitor.
    The external monitors cannot be activated using Presentation Director.
    The external monitor is blank after docking or undocking.
    There are some reports about display driver crashes on machines running Windows XP.
    The switchable graphics drivers limit the useable RAM under Vista 32 to 2.5GB (i.e. 500MB-1GB less than usual).
    Workarounds
    Lenovo has released a new "tip" document which provides a link to a new driver. Get it here but be sure to read the instructions!
    (Old tips follow below the line. Consider them as obsolete.)
    Here are some tips which might make the problem occur less often. I have not tried all of them. Though, A. and B. have improved the situation for me; your mileage may vary.
    A. If you do not have to use an external monitor, then switch to Intel graphics for time being.
    Otherwise:
    B. Make some changes to your system:
    Disable Aero.
    Create a new profile in the power manager with the following setting: When running on AC, turn off the monitor after 40 minutes. (Thereby, the notebook goes less often to standby.)
    Install the newest graphics drivers.
    Install the newest BIOS.
    Install the newest Hotkey utility.
    Install the newest drivers.
    C. Disable the switchable graphics in the BIOS setup and install modded drivers from ATI (see zilla's post in this thread for instructions).
    The last workaround (C.) has been confirmed to work reliably by several users. Though, thereby you use drivers which have not been tested by Lenovo. It's possible (but not very likely) that damage results by doing so. Also, it might be difficult to install a future Lenovo driver which resolves the issues reported here. Finally, you cannot use the power-saving Intel graphics. Thus, you should only use this workaround if you know what you are doing.
    The programs can be downloaded from the following locations. Notice that System Update does not always offer you immediately the lastest versions.
    R400 and T400 users: Go here.
    T500 and W500 users: Go here.
     User opinions
    "Is there any chance this will be fixed, or should I just get used to my "workstation-class" machine crashing regularly?"
    "I [am] thinking about to sell my w500 if this problems won't be fixed in the next weeks."
    "I've got a T400 w/ Vista 64 and I'll say the Switchable drivers on it S[**]K bad."
    "Unfortunately for Lenovo, our IT Manager is at the point of a awarding a new and rather substantial Enterprise Agreement for our whole organization's PC's, which included a rollout of many new PC's for 2009. The contract was going to go to Lenovo. He mumbled something about HP when I asked him about the state of affairs with my PC... [O]ur firm's IT Manager decided to return all the faulty Lenovo's for a refund and would replace them with HP's."  
    "Is someone from Lenovo paying attention[?]"
    "i'm getting angry with ati and lenovo."
    "there are no new drivers and no ETA for a fix."
    "ThinkPads are supposed to be good, so you'd think there wouldn't be a problem like this."
    "honestly it is completely unacceptable for lenovo to have done nothing this long. I paid extra to get the ATI card, and now I can't hook up my laptop to an external monitor without it crashing. I will probably end up selling the laptop soon since using an external monitor is extremely important to me and lenovo doesn't seem to care about fixing the situation."
    Update:
    - Lenovo support has informed me today (2008-10-24) that they are working on the problem.- changed subject (was: Major troubles with DVI-port and a T400) to reflect new information.- changed message body to reflect new information
    - See MIGR-70490 (dated 2008-09-21) for an official statement from Lenovo.
    - 2008-11-15: The problems are still present and there is still no ETA for a fix.
    - As expected, also R400 models are affected. See below for reports.
    - 2008-11-26: Still no word from Lenovo when the problem will be fixed. Added information on (partial) workarounds.
    - 2008-12-03: Lenovo updated MIGR-70490. Though, problems persist.
    - 2008-12-13: Updated problem description on the basis of new reports.
    - 2008-12-16: Updated problem description on the basis of new reports.
    - 2009-01-07: Updated problem description on the basis of new reports. Still no word from Lenovo. I called Lenovo's customer service in the Netherlands and was promised to receive a callback. Though, so far they didn't (want to) get back to me.
    - 2009-01-08: Updated workaround description on the basis of new reports.
    - 2009-01-10: Updated executive summary on the basis of new reports.
    - 2009-01-14: Updated problem description on the basis of new reports (movie).
    - 2009-01-19: Updated workaround section.
    - 2009-01-21: Happy birthday MIGR-70490! It's now 4 months. Updated workaround section. I called Lenovo's customer service in the Netherlands again.
    - 2009-01-22: Added section "User opinions"
    - 2009-01-23: Updated problem description on the basis of new reports.
    - 2009-01-24: Small updates.
    - 2009-02-02: Small updates.
    - 2009-02-03: Changes to section "Executive summary". Added section "Important information for affected users".
    - 2009-02-04: Update to section "Credits".
    - 2009-02-19: Update to section "Credits".
    - 2009-02-27: Quick update to "Executive summary" and "Workarounds".
    - 2009-03-10: Quick updates to section "Executive summary" and "Important information for affected users".
    - 2009-03-21: Quick update to "Executive summary"
    Credits
    Workaround "Aero off": Bubbi, TonyK
    Workaround "Modded ATI drivers": jtull89,  zilla
    Thanks to Mark_Lenovo and Confederate for their work behind the scenes 
    Thanks to feedback from: ajgiordano, Andy_7575, ben2e, brettgri, bri0831, Brimstar, Bubbi, CodeNameSly, cpueschner, dandill, diablo2man, ewilansky, gaccounts, gan, gandalf7, golffreaksi, Homer, hubertlam, Jiraiya, johnsonjf, jordan_moss, jmark, jtull89, kbarina, lenardg, lukest, misitmichaelf, mlb, MMetts, ojisan, pendaluent, Qot, rmccallen, sarnil, shaofengsd, Snakecharmed, StephanK, tarzan23, Texas1040, TheNewNumber2, TonyK, trickyDick, vedman, Vitalus, Waschbecken, xpnet, xrafx, zilla, ZPrime
     (Please don't expect that this list is complete. I am not paid to keep it accurate and complete and, actually, I have a life besides writing about Lenovo's problems. )
    Original post
    Hi there!
    I have major troubles using a Dell 2709W monitor with my T400. 
    The notebook is attached to a Advanced Mini Dock to which the monitor is connected via DVI.
     The problems are as follows.
    A. Activating the external monitor often fails
    Steps to reproduce:
    1. Attach a Dell 2709W via DVI to an Advanced Mini Dock which is connected to a T40
    2. Start Windows and make sure that the T400 is running on the ATI card.
    => Dell monitor enters power saving mode because no signal is coming.
    3. In Windows use either the Presentation Director, Windows, or the ATI tools to activate the Dell monitor.
    Expected result: The Dell monitor is activated and the Windows desktop is shown on it.
    Actual result: It takes 1-3 seconds for the Dell monitor to display something. The monitor shows the Windows desktop for a short period. Then it's black again and the monitor returns to the power saving mode .
    Analysis: It seems that the Presentation Director, Windows, or the ATI tools (or more aptly, I guess, the ATI driver) expect a quick response from the DVI-port that a monitor is present. If they do not receive the response, the DVI-port is deactivated again. Since the monitor is too slow to respond and enters the power saving mode too quickly, the monitor can hardly ever be activated.
    Suggested change: Change these tools (or the ATI driver) so that they wait longer for a response on the DVI-port.
    B. Resuming from monitor sleep causes Windows to fall back to a low resolution if the Dell monitor was activated before
    Steps to reproduce:
    1. Attach a Dell 2709W via DVI to an Advanced Mini Dock which is connected to a T400
    2. Start Windows and make sure that the T400 is running on the ATI card.
    3. Select the Energy Star profile
    4. Activate the Dell monitor
    5. Don't use Windows until the notebook display and the Dell monitor are set to sleep by Windows.
    6. Wake up the displays (e.g. by pressing some keys)
    Expected result: Both displays are run in the display mode as before.
    Actual result: The Dell monitor still sleeps. The notebook displays is run at a lower resolution (I guess 800x600). The Windows login prompt is not visible and it has to be guessed that it is shown. Though the typical Windows login background is visible. If the password is entered, then Windows can be used again. Though, the resolution is still low and the Dell monitor still sleeps.
    Analysis: It seems that by sending the Dell monitor to sleep, the monitor deactivates the DVI-interface or enters a low-power interface mode. This seems to disturb some component in Windows (the Presentation Director, Windows, the ATI tools, the ATI driver) in a way that Windows only activates the notebook display when it resumes from "monitor sleep".
    Suggested change: Change these tools (or the ATI driver) so that they can cope with the situation that the DVI-interface is deactivated and wait longer for the interface to be in a useable state. Reactivate an external monitor even if it "sleeps very deeply".
    Relevant system information
    - T400 2767-CTO (T9400, 2x2GB RAM, ATI, WXGA+ LED)
    - Advanced Mini Dock
    - Vista 32 Business (German) - fully updated
    - All Lenovo updates via System Update are installed- Dell 2709W
    - The system runs the ATI graphic card in the described scenarios
    Message Edited by Izmi on 05-21-2009 10:34 AM
    Message Edited by Izmi on 06-29-2009 03:13 PM
    Solved!
    Go to Solution.

    Lenovo support made me reinstall presentation director to rule out this component as a factor. After the reinstallation, the amdkmdap-problem is still present. Letting Windows go to standby and waking the system up afterwards, is a reliable method in my case to reproduce the problem on condition that an external monitor was active. The problem does not occur if no external monitor is present.
    A web search for "amdkmdap", "atikmpag","BSOD" with one of the ThinkPad-series names (like "T400") shows that other persons also have this problem with R400s, T400s, T500s, and W500s:
    - t400: Display driver crashes
    - W500 Display Driver
    - My W500
    - T400 Display driver stopped working...
    - T500 Video/Video Driver Issues (2056-4SU)
    - NUS T400 issues
    - T400 Display Driver Issue
    - Vista64 + 4GB RAM + External Display = BSOD
    - R400 problem report (in Chinese)
    - T500 problem report (in Chinese)
    - Bioshock keeps crashing (seems related)
    -  Vista x64, ATI graphics, dock + external LCD = bluescreens? (a report by a W500 user)
    - many problems with lenovo w500
    - another R400 problem report (in Chinese)
    -  Vista BSOD on Lenovo T500 with new Switchable Graphics
    - switchable graphics and external monitor through port replic
    - Problem with Lenovo T500 notebook & external LCD
    - Lenovo ThinkPad T400 - some impressions.
    - T400 freezes with graphics Intense programes
    - Standard Laptop mit ein paar Macken (in German)
    Some possibly related Non-Lenovo cases: 
    - Why Vista crashes so often when dual display is enabled?
    - Vista and 7.3 Display driver atikmdag stopped responding error
    - 4870 vista x64 multi-mon = atikdmag BOOM
    In the cases in which people observe the "amdkmdap"-problem and describe the circumstances, the use of an external monitor is always a factor. These other reports also indicate that it is likely not an issue with the hardware of my notebook (or then a general problem for many batches of these machine types). For it happens a) on many systems and b) on different kinds of systems.
    If others want to contribute to the problem solution, then we should provide Lenovo and ATI a good problem description. So, please add your description.
    Message Edited by Izmi on 02-03-2009 11:53 AM

  • Photoshop CS5.1 Crashes Upon Opening: "Photoshop has encountered a problem with the display driver-"

    Every time I try to open photoshop I get a window that pops up and says:
    "Photoshop has encountered a problem with the display driver, and has temporarily disabled GPU enhancements.  Check the video card manufacturer's website for the latest software.
    GPU enhancements can be enable in the Performance panel of Preferences."
    Then windows shuts the program down.  The details of the problem are:
    "Files that help describe the problem:
      C:\Users\Owner\AppData\Local\Temp\WER70AD.tmp.WERInternalMetadata.xml
      C:\Users\Owner\AppData\Local\Temp\WER9389.tmp.appcompat.txt
      C:\Users\Owner\AppData\Local\Temp\WER9407.tmp.hdmp"
    I'm on a custom Asus
    I'm using Win7 Home Premium 64-bit
    16GB RAM
    Nvidia Geforce GTX 560 2GB video card
    Intel i7 core 2.2 GHz
    12 GB of memory
    The error happens so quickly that I don't have time to do anything.  Please help.  >.<  I've been on hold for *checks phone* 2 hours exactly.  Wow.  It is a legit copy and was working last month with no trouble.  I've updated the drivers and tried a few solutions that have worked for other people that I found on Google (such as disabling CUDA and setting my "power management mode" to "prefer maximum performance" on my video card) but so far nothing has worked.
    Thanks in advance!

    It has stopped crashing because somehow it turned off "Enable GL Drawing" on its own because I could never even get a menu open.  Not sure how it did that but I am grateful.  I still get the error when I open Photoshop up but at least it hasn't crashed yet.  At the time when it was crashing I never would have been able to get you the system info due to the speed that it was crashing upon just opening the program.  In case you still need it:
    Adobe Photoshop Version: 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch]) x64
    Operating System: Windows 7 64-bit
    Version: 6.1 Service Pack 1
    System architecture: Intel CPU Family:6, Model:10, Stepping:7 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
    Physical processor count: 8
    Processor speed: 2394 MHz
    Built-in memory: 16361 MB
    Free memory: 13322 MB
    Memory available to Photoshop: 14694 MB
    Memory used by Photoshop: 60 %
    Image tile size: 128K
    Image cache levels: 4
    OpenGL Drawing: Disabled.
    OpenGL Drawing Mode: Basic
    OpenGL Allow Normal Mode: True.
    OpenGL Allow Advanced Mode: False.
    OpenGL Crash File: Detected.
    OpenGL Allow Old GPUs: Not Detected.
    Video Card Vendor: NVIDIA Corporation
    Video Card Renderer: GeForce GTX 560M/PCIe/SSE2
    Display: 1
    Display Bounds:=  top: 0, left: 0, bottom: 1080, right: 1920
    Video Card Number: 1
    Video Card: NVIDIA GeForce GTX 560M
    Driver Version: 9.18.13.697
    Driver Date: 20121002000000.000000-000
    Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Video Mode: 1920 x 1080 x 4294967296 colors
    Video Card Caption: NVIDIA GeForce GTX 560M
    Video Card Memory: -2047 MB
    Serial number: 92628077745082451425
    Application folder: C:\Program Files\Adobe\Adobe Photoshop CS5.1 (64 Bit)\
    Temporary file path: C:\Users\Owner\AppData\Local\Temp\
    Photoshop scratch has async I/O enabled
    Scratch volume(s):
      C:\, 931.4G, 511.4G free
    Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS5.1 (64 Bit)\Plug-ins\
    Additional Plug-ins folder: not set
    Installed components:
       A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112  
       ACE.dll   ACE 2010/12/13-23:37:10   64.449933   64.449933
       adbeape.dll   Adobe APE 2011/01/17-12:03:36   64.452786   64.452786
       AdobeLinguistic.dll   Adobe Linguisitc Library   5.0.0  
       AdobeOwl.dll   Adobe Owl 2010/06/03-13:43:23   3.0.93   61.433187
       AdobeOwlCanvas.dll   Adobe Owl Canvas   3.0.68   61.2954
       AdobePDFL.dll   PDFL 2010/12/13-23:37:10   64.341419   64.341419
       AdobePIP.dll   Adobe Product Improvement Program   5.5.0.1265  
       AdobeXMP.dll   Adobe XMP Core   5.0   64.140949
       AdobeXMPFiles.dll   Adobe XMP Files   5.0   64.140949
       AdobeXMPScript.dll   Adobe XMP Script   5.0   64.140949
       adobe_caps.dll   Adobe CAPS   4,0,42,0  
       adobe_OOBE_Launcher.dll   Adobe OOBE Launcher   2.0.0.36 (BuildVersion: 2.0; BuildDate: Mon Jan 24 2011 21:49:00)   1.000000
       AFlame.dll   AFlame 2011/01/10-23:33:35   64.444140   64.444140
       AFlamingo.dll   AFlamingo 2011/01/10-23:33:35   64.436825   64.436825
       AGM.dll   AGM 2010/12/13-23:37:10   64.449933   64.449933
       ahclient.dll    AdobeHelp Dynamic Link Library   1,6,0,20  
       aif_core.dll   AIF   2.0   53.422628
       aif_ogl.dll   AIF   2.0   53.422628
       amtlib.dll   AMTLib (64 Bit)   4.0.0.21 (BuildVersion: 4.0; BuildDate: Mon Jan 24 2011 21:49:00)   1.000000
       amtservices.dll   AMTServices (64 Bit)   4.0.0.21 (BuildVersion: 4.0; BuildDate: Mon Jan 24 2011 21:49:00)   1.000000
       ARE.dll   ARE 2010/12/13-23:37:10   64.449933   64.449933
       asneu.dll    AsnEndUser Dynamic Link Library   1, 7, 0, 1  
       AXE8SharedExpat.dll   AXE8SharedExpat 2011/01/10-23:33:35   64.436825   64.436825
       AXEDOMCore.dll   AXEDOMCore 2011/01/10-23:33:35   64.436825   64.436825
       Bib.dll   BIB 2010/12/13-23:37:10   64.449933   64.449933
       BIBUtils.dll   BIBUtils 2010/12/13-23:37:10   64.449933   64.449933
       boost_threads.dll   DVA Product   5.0.0  
       cg.dll   NVIDIA Cg Runtime   2.0.0015  
       cgGL.dll   NVIDIA Cg Runtime   2.0.0015  
       CoolType.dll   CoolType 2010/12/13-23:37:10   64.449933   64.449933
       data_flow.dll   AIF   2.0   53.422628
       dvaadameve.dll   DVA Product   5.0.0  
       dvacore.dll   DVA Product   5.0.0  
       dvaui.dll   DVA Product   5.0.0  
       ExtendScript.dll   ExtendScript 2011/01/17-17:14:10   61.452840   61.452840
       FileInfo.dll   Adobe XMP FileInfo   5.0   64.140949
       icucnv36.dll   International Components for Unicode 2009/06/17-13:21:03    Build gtlib_main.9896  
       icudt36.dll   International Components for Unicode 2009/06/17-13:21:03    Build gtlib_main.9896  
       image_flow.dll   AIF   2.0   53.422628
       image_runtime.dll   AIF   2.0   53.422628
       JP2KLib.dll   JP2KLib 2010/12/13-23:37:10   64.181312   64.181312
       libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)  
       libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0  
       LogSession.dll   LogSession   2.1.2.1263  
       MPS.dll   MPS 2010/12/13-23:37:10   64.450375   64.450375
       msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.4940  
       msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.4940  
       msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195  
       msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.4940  
       pdfsettings.dll   Adobe PDFSettings   1.04  
       Photoshop.dll   Adobe Photoshop CS5.1   CS5.1  
       Plugin.dll   Adobe Photoshop CS5   CS5  
       PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   2.5.0.232  
       PSArt.dll   Adobe Photoshop CS5.1   CS5.1  
       PSViews.dll   Adobe Photoshop CS5.1   CS5.1  
       SCCore.dll   ScCore 2011/01/17-17:14:10   61.452840   61.452840
       tbb.dll   Threading Building Blocks   2, 1, 2009, 0201  
       TfFontMgr.dll   FontMgr   9.3.0.113  
       TfKernel.dll   Kernel   9.3.0.113  
       TFKGEOM.dll   Kernel Geom   9.3.0.113  
       TFUGEOM.dll   Adobe, UGeom©   9.3.0.113  
       updaternotifications.dll   Adobe Updater Notifications Library   2.0.0.15 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   2.0.0.15
       WRServices.dll   WRServices Thursday January 21 2010 12:13:3   Build 0.11423   0.11423
       wu3d.dll   U3D Writer   9.3.0.113  
    Installed plug-ins:
       3D Studio 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Accented Edges 12.0
       ADM 3.11x01
       Angled Strokes 12.0
       Average 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Bas Relief 12.0
       BMP 12.0.2
       Camera Raw 6.7
       Chalk & Charcoal 12.0
       Charcoal 12.0
       Chrome 12.0
       Cineon 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Clouds 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Collada 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Color Halftone 12.0.2
       Colored Pencil 12.0
       CompuServe GIF 12.0.2
       Conté Crayon 12.0
       Craquelure 12.0
       Crop and Straighten Photos 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Crop and Straighten Photos Filter 12.0.2
       Crosshatch 12.0
       Crystallize 12.0.2
       Cutout 12.0
       Dark Strokes 12.0
       De-Interlace 12.0.2
       Dicom 12.0
       Difference Clouds 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Diffuse Glow 12.0
       Displace 12.0.2
       Dry Brush 12.0
       Eazel Acquire 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Embed Watermark 4.0
       Entropy 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Extrude 12.0.2
       FastCore Routines 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Fibers 12.0.2
       Film Grain 12.0
       Filter Gallery 12.0
       Fresco 12.0
       Glass 12.0
       Glowing Edges 12.0
       Google Earth 4 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Grain 12.0
       Graphic Pen 12.0
       Halftone Pattern 12.0
       HDRMergeUI 12.0
       IFF Format 12.0.2
       Ink Outlines 12.0
       JPEG 2000 2.0
       Kurtosis 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Lens Blur 12.0
       Lens Correction 12.0.2
       Lens Flare 12.0.2
       Lighting Effects 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Liquify 12.0.1
       Matlab Operation 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Maximum 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Mean 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Measurement Core 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Median 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Mezzotint 12.0.2
       Minimum 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       MMXCore Routines 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Mosaic Tiles 12.0
       Multiprocessor Support 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Neon Glow 12.0
       Note Paper 12.0
       NTSC Colors 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Ocean Ripple 12.0
       OpenEXR 12.0.2
       Paint Daubs 12.0
       Palette Knife 12.0
       Patchwork 12.0
       Paths to Illustrator 12.0.2
       PCX 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Photocopy 12.0
       Photoshop 3D Engine 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Picture Package Filter 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Pinch 12.0.2
       Pixar 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Plaster 12.0
       Plastic Wrap 12.0
       PNG 12.0.2
       Pointillize 12.0.2
       Polar Coordinates 12.0.2
       Portable Bit Map 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Poster Edges 12.0
       Radial Blur 12.0.2
       Radiance 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Range 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Read Watermark 4.0
       Reticulation 12.0
       Ripple 12.0.2
       Rough Pastels 12.0
       Save for Web & Devices 12.0
       ScriptingSupport 12.1
       Shear 12.0.2
       Skewness 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Smart Blur 12.0.2
       Smudge Stick 12.0
       Solarize 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Spatter 12.0
       Spherize 12.0.2
       Sponge 12.0
       Sprayed Strokes 12.0
       Stained Glass 12.0
       Stamp 12.0
       Standard Deviation 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Sumi-e 12.0
       Summation 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Targa 12.0.2
       Texturizer 12.0
       Tiles 12.0.2
       Torn Edges 12.0
       Twirl 12.0.2
       U3D 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Underpainting 12.0
       Vanishing Point 12.0
       Variance 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Variations 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Water Paper 12.0
       Watercolor 12.0
       Wave 12.0.2
       Wavefront|OBJ 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       WIA Support 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       Wind 12.0.2
       Wireless Bitmap 12.1 (12.1x20110328 [20110328.r.145 2011/03/28:10:30:00 cutoff; r branch])
       ZigZag 12.0.2
    Plug-ins that failed to load: NONE
    Flash:
       Mini Bridge
       Kuler
       Access CS Live
       CS Review
    Installed TWAIN devices: NONE

  • "Your system display driver has caused Photoshop to Crash" MacBookPro June 2012 MacOS 10.7.4 Photosh

    I am getting this error message when I launch Photoshop -- I just started getting it yesterday, August 28, 2012, when I tried to open a .tif image. Photoshop crashed.  What has changed?  I don't remember doing any updates to OS or to Photoshop.  I am using Photoshop 12.0.4 x64   I've had the new MacBookPro June 2012 laptop for about a month, and Photoshop CS5 has been working fine.  Now I'm getting this error message.
    What can I do?
    thank you!

    It's entirely possible for the display driver file to get corrupted, though it's not common.
    If you have Applejack, run it now.  If you don't know what that is, skip this suggestion for now.
    If you have Disk Warrior, or Cocktail or Onyx, run them now.
    You might try booting off the install DVD and running Repair Disk with Apple's Disk Utility from there.
    If it is indeed a corrupted kext file (the driver), then you can try running the 10.7.4 Combo Update over your existing OS install of that same version.  That gives you fresh files as needed.
    If none of that works, then you are looking at having to do an Archive and Install of the OS from the DVD, which will put you at 10.7.0, so you'd have to run the 10.7.4 Combo Update again to get you to where you are now (OS version wise).

  • Firefox crashes when opening a local file (a .jpg photo) click drive, click directory and it crashes.

    Firefox crashes when clicking FILE / OPEN FILE / Drive (G:)/and when double clicking the directory containing the file. It happens every time I'm trying to open a local file. Must close, go to Internet Explorer, Opera or Chrome which have no problems doing this.

    You are running out of memory. In the stack notice this line:
    Caused by: java.lang.OutOfMemoryError: Java heap space
    Edit the sqldeveloper.conf file and add this
    AddVMOption -Xmx1024M
    That will bump it up some.
    -kris

  • Editing software crashing-do I need Display driver update for Satelite C660

    Hi folks,
    recently I have installed trial versions of Adobe Premier cs5, then avid media composer and neither of them are loading, (not responding) and Adobe crashes on importerquicktime.prm.
    Everywhere I look it seems to be telling me I need to update my drivers, but I have the latest driver available for this model,
    Is it a QuickTime issue?
    Or a driver issue?
    Can anyone help me or even let me know what my options are?
    Thanks
    Conor

    Hi
    In internet I could find this interesting info:
    +I am having issues with the ImporterQuicktime.prm with the new update 5,03.+
    +Ive been editing on a project for months, and exported a QT with Avid DNxHD codec,+
    +I started another project with this QT DNxHD file (to make sample clips), and then I updated to 5.03, and now PPro CS5 runs very slow, and then locks up. I did read the forums to find a solution.+
    +I noticed when re launching PPro CS5, it would hang on the Exporter, and Importer Quicktime .prm, so I tested removing the plugin from the PPro>plugin>common folder. PPro CS5 launches very quickly and runs smooth- although the QT files are off line+
    It looks like its not display driver issue If the info above would not help you, you should get in contact with Adobe support

Maybe you are looking for

  • Why does my iPad suddenly say no sim?

    iPad suddenly says no sim. Why does thi s happen?

  • Apple iTunes U Contact for Business Development

    Hello,  I would like to talk with an Apple iTunes U Product Manager or Business Development Manager.  Does anyone have a contact they can provide?  Thank you.

  • NetConnection.Call.BadVersion - Channel disconnected

    I am facing NetConnection.Call.BadVersion error when I run flex based application with BlazeDS on S64 with Weblogic application server. At application start up, it makes 4 calls to server and get appropriate data. However once the application is up a

  • How to  set the classpath for servlet and jsp???

    i add C:\tomcat-5.0\common\lib\servlet-api+jsp-api to the class path from DOS prompt, as show below: set CLASSPATH=%classpath%;C:\tomcat-5.0\common\lib\servlet-api.jar;C:\tomcat-5.0\common\lib\jsp-api.jar then, i compile the servlet: javac FirstServl

  • IPod Touch 2.0.2 wifi problems?

    My iPod Touch worked perfectly fine with my wifi network until I updated to 2.0.2. If you have the same problem, or a similar problem, please reply.