#201
|
|||
|
| ||
#202
|
|||
|
This is happening to me almost constantly when zoning into Butcherblock since the patch. I zone crashed before the patch, but it is way worse with that zone now.
| ||
#203
|
|||
|
Crashing when zoning
Windows 7 home premium 64bit
AMD Phenom II x4 3.4Ghz 1 x ASUS M4A87TD EVO AM3 AMD 870 SATA 6Gb/s USB 3.0 ATX AMD Motherboard On board Sound Card 1 x ASUS M4A87TD EVO AM3 AMD 870 SATA 6Gb/s USB 3.0 ATX AMD Motherboard On Board Network Adapter Time Warner Cable (fastest internet package) N 300 NetGear WNR 2000 No Anti Virus - No Firewall 2014-03-23 17:00:21 Item done, MSG_WEATHER_EVENT received. 2014-03-23 17:00:21 2014-03-23 17:00:24 Item done, MSG_WEATHER_EVENT received. 2014-03-23 17:00:24 2014-03-23 17:08:15 Item done, MSG_WEATHER_EVENT received. 2014-03-23 17:08:15 2014-03-23 17:10:31 D3DXCreateTextureFromFileEx() failed to create texture spelja.png for particle system. 2014-03-23 17:10:31 D3DXCreateTextureFromFileEx() failed to create texture spelja.png for particle system. 2014-03-23 17:10:34 D3DXCreateTextureFromFileEx() failed to create texture spelja.png for particle system. 2014-03-23 17:17:55 Networking: Connection Closed [0] with 0 pending bytes. 2014-03-23 17:17:55 Stopping world display. 2014-03-23 17:17:55 Attempt to send message 30546 on a void connection. 2014-03-23 17:17:55 Beginning EnterZone block. 2014-03-23 17:17:55 2014-03-23 17:17:55 Calling WorldAuthenticate. Countdown is 4 2014-03-23 17:17:55 2014-03-23 17:17:55 Networking: using port [57977]. 2014-03-23 17:17:55 Networking: Connection Established [1] 2014-03-23 17:17:55 WorldAuthenticate: Initiating Login. 2014-03-23 17:17:56 WorldAuthenticate. I got a message of type 0xfa6 (4006). 2014-03-23 17:17:56 WorldRPServer message: server name project1999 2014-03-23 17:17:56 2014-03-23 17:17:56 WorldAuthenticate. I got a message of type 0x3c25 (15397). 2014-03-23 17:17:56 WorldAuthenticate. I got a message of type 0x7cba (31930). 2014-03-23 17:17:56 WorldAuthenticate. I got a message of type 0x52a4 (21156). 2014-03-23 17:17:56 WorldAuthenticate. Access granted. 2014-03-23 17:17:56 2014-03-23 17:17:56 Check 1sa. 0xa3b46c81 2014-03-23 17:17:56 2014-03-23 17:17:56 Check 1x. 0x9e15bc94 2014-03-23 17:17:56 2014-03-23 17:17:56 Waiting to connect to zone... Character Khavok 2014-03-23 17:17:56 | ||
#204
|
|||
|
hey rogean, it has done it since i started playing about 2-3 months ago or so. not sure what is causing the issue it seems totally random, some days i will be on for 4 + hrs and not a single crash then other times its like almost every time i zone, doesn't seem to matter if there are 300 people or 1300 on the server. i will try to mess around with the program mentioned and let you know what happens.
| ||
#205
|
|||
|
After the last patch, I crash about 50% of the time upon zoning. Was closer to 10% before last patch.
| ||
#206
|
|||
|
After the patch that introduced sit aggro (two patches ago as of this moment, I believe) I crash a lot more often. I didn't change any settings, install new programs, or anything like that. All I did was update p99 patch files as I normally would.
The really weird thing for me is that its a bit less common (considering it rarely ever happened at all before, its still a notiiceable difference since downloading that patch) for me to crash while zoning, but I crash about 90% of the time I use the /camp command. If I do, about 9/10 attempts will result in a client crash. I can't even use /q either, it just causes a client crash message to pop up and I have to open everquest again. As of right now, and for the last month or two, the only way I can exit game without a client crash followed by a 1018 is to first /camp as usual and wait for my character to camp then alt-F4 to close EQ before the client crash message shows up. Ill post that log file immediately after I experience this again, as I'm stuck at work right.now.
__________________
-Aftermath-
Tasslehof - 60 Druid Barlow - 60 monk Blueberrii - 60 Mage Gigglepurr - 60 Shaman Kids - 60 Rogue Fornfamnad - 60 Cleric | ||
#207
|
|||
|
I regularly get zoning crashes. The most reliable way for me to reproduce them is:
- Run under WinEQ2 - Begin zoning process - Click outside the EQ window (I have 3 tiled screens as my desktop, regular multi-monitor not a 3x spanned one using Eyefinity or the like) - Click back into the EQ window before zoning has completed, EQ crashes - If I wait until zoning has completed everything is OK This is not a "windows thinks EQ has crashed because it doesn't respond as it is busy loading stuff" kind of thing, but rather the process immediately terminating. This is running on Win 7 Ultimate SP1, 64x on Intel i5 2500K @ 3.60 GHz, 32GB ram, GeForce GTX 780. Choice of storage for EQ-P1999 doesn't seem to affect it (tried both SSD and classic disks). Connection-wise I get about 45ms with no packet loss on Teksavvy cable (ON) on Rogers cable infrastructure.
__________________
Blue Server || My WTS/WTT/WTB list
| ||
#208
|
||||
|
Quote:
This happens with no router or firewall active at all. But I do have a very poor connection, with a typical 800 ping (one of the reasons I play EQ in the first place, its very forgiving to this). So add that little data point to the others who say connection quality is a part of this crash bug. | |||
#209
|
|||
|
Crashing while zoning happens about 20% of the time, no pattern to it except some zones are worse than others. Zoning into Felwithe from G'fay I crash more often than not.
__________________
^*^ Aveenia ^*^ - Druid TEAL
^*^ Aveenia Inverse ^*^ - Druid 38 BLUE (RIP) | ||
#210
|
|||
|
I was having an issue on my laptop (running windows 8), I had slow zone times and would crash during some of them. This was not happening on my desktop computer that was running windows vista 64 bit so I figured it had something to do with windows 8. Also anytime I would camp on one toon to switch to another I would crash. This is what fixed the problem for me and hopefully fix it for anyone else experiencing this problem.
1st be using latest version of wineq 2nd make the wineq default eq1 shortcut and have the icon on your desktop 3rd right click on that icon then click "troubleshoot" 4th accept the option they provide of running it in windows xp service pack 3 mode. This corrected all the issues I was having and I haven't crashed once since I did this 3 days ago. Also, my zone times are much faster. | ||
|
|