Issues, Workarounds & Localization

Still waiting CCP. Game still ****** on some computers. Have you found the problem yet? Are you working on it?

Oh yeah,

confirming the Nvidia Beta Driver did the trick for me. Everything works smoothly now.

Random system freezes have been seriously bugging me now for weeks. Never had a problem with EVE before. I updated everything - but nothing seemed to work. I, like others in this thread, had a feeling it was somehow Flash related.

So rather than updating Flash at the first opportunity I uninstalled the latest version and rolled back to 11.2.202.235 plug-in (Firefox), the version released before my PC started locking up...

...and my system has been stable now for over a week - no crashes at all (fingers crossed), even when running two clients. Hope this 'fix' will work for you guys too

Direct download links for Flash Player 11.2.202.235 (Windows):

ActiveX installer for Internet Explorer on 64-bit systems

http://fpdownload.macromedia.com/pub/flashplayer/current/licensing/win /install_flash_player_11_active_x_64bit.exe

Plugin installer for other browsers on 64-bit systems

http://fpdownload.macromedia.com/pub/flashplayer/current/licensing/win /install_flash_player_11_plugin_64bit.exe

ActiveX installer for Internet Explorer on 32-bit systems

http://fpdownload.macromedia.com/pub/flashplayer/current/licensing/win /install_flash_player_11_active_x_32bit.exe

Plugin installer for other browsers on 32-bit systems

http://fpdownload.macromedia.com/pub/flashplayer/current/licensing/win /install_flash_player_11_plugin_32bit.exe

just wanted to chip in: same problems here, Win7/64, nVidia GTX 570, non-beta 301.42, 2 clients, 2 displays: intermittent freezes, sometimes windows is able to recover it, mostly not.

downgrading the graphics in eve doesn´t help, even in "low"-settings the machine freezes.

wait, see, hope...

Did not for me. My desktop is still fubarred for eve with that driver. Meawhile my laptop keeps motoring fine with 301.42. Sadly, the problem, whatever it is, is not as simple as a which driver version.

I'm experimenting with the flash player active x version suggestion itt above. Can't seem to get my desktop to load the old version for the active x. It loaded the plugin for that version fine though. ******* computers, can't live with them can't live without them. Well you can but it would mean no eve.

EDIT- And if anyone from CCP is still monitoring this subforum please post SOMETHING

Same issue running a GTX 670.

Screen goes black and looks like it's about to minimise and freezes for 4-5 seconds. Once I come back it's stuck at 30fps.

I find docking up and resetting the Interval setting between different options before going back to the top one (interval immediate i think it's called?) seem to fix the framerate issue. Happens once every 1-2 hours for me, only in Eve no other games / programs.

Well, flash switcheroo did not work either. Regardless, still can run only one very intermitent full-screen client on the desktop (whereas before I could run two clients windowed quite well). About the only thing the one very intermittent client is good for is in station activities or mining. And even then any mouse movement can set off a freeze. Oddly, if I don't move the mouse it doesn't seem to freeze. But then if you don't move the mouse you're not really doing much.

just a quick update (and to keep the thread on the first page *g*):


updated to beta 306.2 - yes, that was better /sarcasm: because the system froze completely. got back to 301.42 and got me a long indexfinger to reach the reset-button on my machine...

st.

The following any help? This only happens in EVE.

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: 867dd5c8, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 872a4148, Pointer to a DEFERRED_WATCHDOG object.
Arg3: f7b21cb4, Pointer to offending driver name.
Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

Debugging Details:

---

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT

CUSTOMER_CRASH_COUNT: 1

BUGCHECK_STR: 0xEA

LAST_CONTROL_TRANSFER: from a935bb50 to 804db856

STACK_TEXT:
a935bb0c a935bb50 867dd5c8 ffdff120 866fbc60 nt!RtlpBitsClearHigh+0xd6
WARNING: Frame IP not in any known module. Following frames may be wrong.
a935bb50 bf8653c7 00000000 00000000 00000000 0xa935bb50
a935bb6c bd0a0484 866fbc58 a935bb80 f7e1d030 win32k!fnHkINLPCBTCREATESTRUCT+0x5af
a935bb84 bd07b49f e2251808 a935bbd4 00000001 nv4_disp!CBaseTexture::UnlockUserForCPU+0x4
a935bc24 a935bc7c a935bc64 bf9648b3 a935bc01 nv4_disp!CNonLocalHeap::create+0x34f
a935bc28 a935bc64 bf9648b3 a935bc01 e1d25714 0xa935bc7c
a935bc7c e1b39730 00000000 00000000 00000000 0xa935bc64
a935bc80 00000000 00000000 00000000 00040000 0xe1b39730


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_disp!CBaseTexture::UnlockUserForCPU+4
bd0a0484 ?? ???

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nv4_disp!CBaseTexture::UnlockUserForCPU+4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4fb206eb

FAILURE_BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2012_05_15

BUCKET_ID: 0xEA_IMAGE_nv4_disp.dll_DATE_2012_05_15

Followup: MachineOwner
---------

OMG eve is beautiful again and not a giant frustration. Well, at long last I seem to have fixed my eve problem.

I think there is something with eve that wasn't getting along with the drivers and may have somehow corrupted them. But my laptop never encountered the problem, while my desktop did. I have no idea what it was that I did with eve on my desktop that I haven't done with my laptop (other than eve-voice, or ui scaling, or ts overlay). Whatever it was, though it fubared something with the driver. Even when I would download a new driver the problem would remain and even get worse.

Somehow in trying to update drivers since the problems started, I recently disabled my drivers.

So what I did with the latest driver update, 306.23, was I downloaded it to desktop. Then I shut down the computer and disconnected power cord.

Then I disconnected the power cable to the video card and unseated the card from the motherboard. Then reseated it and reconnected the power cable.

After bootup, I went to programs and features and uninstalled everything nvidea. One program would not unstall until after I restarted (again).

So then after restart, since I had already downloaded the new driver to desktop, I double clicked the nvidia driver version 306.23 to install it, and checked advanced option and then checked "do a clean install." It then installed the new drivers.

Whatever driver settings that may have been sitting in the system and had been fubarred by whatever eve settings or something I had done in or with eve must have either been cleaned out or overwritten with the reinstallation of the card and clean install of the driver. My desktop is happily running eve again as it used to.

I suggest folks that are not using nvidia try a similar method with their ATI drivers. Hopefully they have the ability to disable their drivers, unseat and reinstall their video card, do a clean install on their new driver.

I am quite reticent to mess with any display settings I currently have in eve and won't be using eve voice again or ts overlay or changing the ui scaling for fear that something with changing eve features or an addon voice display from ts can lead to some driver and card problem. If the freezing problem starts to occur again though I won't just ignore it at first if it is minor but take it as a warning that it could get worse and try to report what occurred just prior to the first event, in the hope that it helps CCP pinpoint what might be at the root of these freezing problems. Whether it be an issue with eve code, or video card manufacturer code, or some miscommunication between the two.

I hope this help others that have been having problems. o7

edit - all these steps might be necessary because previously i had tried a normal updat/install of the 306.23 driver and it had not fixed anything.