Crashing after 09/03/2009 update [Archive] - EQ2 Forum Archive @ EQ2Wire

View Full Version : Crashing after 09/03/2009 update

Decimiss

11-03-2009, 06:01 PM

I ran the patcher this afternoon and downloaded the very small update. Game runs fine until attempting to load the character select screen, and now suddenly crashes. This is the first this comp has crashed on everquest2. It's a custom built pc:ATI Radeon 3600 1gb video cardAMD Athlon x2 dual core 2.8 gb ProcesserKingston 2gb DDR2 1066 RAMWindows Xp64 (x86)When the game crashes it gives me an exception code: 0xc0000005It has run perfectly smooth until today.

BDoodle

11-04-2009, 05:43 AM

3 things to check, directly from the Microsoft support page:With reference to the 0xc0000005 condition,This issue may occur if all the following conditions are true:<ul><li>You are running Windows XP SP2 on an AMD Athlon 64-based computer. </li><li>You have the Data Execution Prevention (DEP) switch (/noexecute) enabled in the Boot.ini file. </li><li>You have Norton CleanSweep configured to automatically load and monitor installations when Windows starts.</li></ul>It may or may not help, but it's a place to start.

Kalria

11-04-2009, 09:43 PM

Same problem. However, I was able to log in last night without the crash. Now I cannot get it to load at all. I updated to the latest driver (10-5) and still same problem.One good news is, I don't seem to get memory errors since it crashes out before ever getting into game <img src="/smilies/8a80c6485cd926be453217d59a84a888.gif" border="0" alt="SMILEY" />

Zadig

11-05-2009, 11:10 AM

I'm having this problem too, but only in fullscreen. If I try to load the game in fullscreen it crashes right after I press the "Play Game" button on the launcher and EQ2 starts to load.if I load the game in window mode it loads up, but if i try to switch to fullscreen, it crashes as soon as I click the checkbox.

BDoodle

11-05-2009, 01:22 PM

When you crash, do you get an error message? If so, can you post it?

TSR-DanielH

11-05-2009, 05:09 PM

<cite>BDoodle wrote:</cite><blockquote>3 things to check, directly from the Microsoft support page:With reference to the 0xc0000005 condition,This issue may occur if all the following conditions are true:<ul><li>You are running Windows XP SP2 on an AMD Athlon 64-based computer. </li><li>You have the Data Execution Prevention (DEP) switch (/noexecute) enabled in the Boot.ini file. </li><li>You have Norton CleanSweep configured to automatically load and monitor installations when Windows starts.</li></ul>It may or may not help, but it's a place to start.</blockquote>That's interesting and I'm specifically concerned with the 3rd listing. For the people experiencing this issue, are you using Norton on that computer? If so, have you tried disabling it when running the game? Please let us know.

Isilsisial

11-05-2009, 07:24 PM

no norton... no messing with DEP settings... after the patch 2 days ago our playing in the evening has gone from difficult(crashing alot after patch 53) to impossible, my husband and I have both been getting booted to character select screen multiple times while trying to do shard runs, no error messages. And once after being booted to the character select screen we had to complete reset his computer, because he could not zone in,even after restarting game, it would just sit there on the loading screen. And the lag has been incredible with voice chat lagging, ping through the roof shows 2-8k plus while in game(4 billion ms on tracert), characters action lagging, and our actual fps has been pretty stable.if the unplayable lag starts up again, sprint said to call them and they'd look into it while it was happening, so we will start there... but I just wanted to know, if anyone else was having any kind of similar problems.At least we haven't had the out of memory this week...

TSR-DanielH

11-05-2009, 08:56 PM

<cite>Isilsisial wrote:</cite><blockquote>no norton... no messing with DEP settings... after the patch 2 days ago our playing in the evening has gone from difficult(crashing alot after patch 53) to impossible, my husband and I have both been getting booted to character select screen multiple times while trying to do shard runs, no error messages.</blockquote>Are you posting in the correct thread? I believe the issue being discussed here is a crash to desktop with a memory error. A crash to character select without an error message would be a different issue, probably.Are you using a router with your current system? If so, please try bypassing it to see if that resolves the problem. If it corrects the problem then we'll need to help you configure that router.Also, if this problem is inconsistent then try running the tracert/pathping tests in the connection test subforum when it is happening. That will give us a better idea about why this is occurring.

Isilsisial

11-08-2009, 01:02 PM

No, I'm sure this is likely to be the wrong place to post this. I should have started a new thread but I don't often post on any forum and couldn't see where to start a new one...My husband is having the same lagging issues I'm having and he is connected direct, I connect to the internet through his computer via a router. after this going on for several days we have noticed that we only seem to have the game breaking lag when we are in the same group in the same zone...?? how is that happening?Just crashed to character select and thought I would post the tracert...Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.C:Documents and SettingsAdministrator>tracert unrest.everquest2.comTracing route to sdkeq2-05-01.everquest2.com [199.108.12.161]over a maximum of 30 hops: 1 4294966844 ms 4294966844 ms 4294966844 ms 192.168.0.1 2 4294966989 ms 4294966954 ms 4294967034 ms 68.28.89.69 3 4294966968 ms 4294966960 ms 4294966944 ms 68.28.89.91 4 4294966954 ms 4294966960 ms 4294966943 ms 68.28.91.55 5 * * * Request timed out. 6 4294966973 ms 4294967009 ms 4294967034 ms 68.28.95.1 7 4294966960 ms 4294966947 ms 4294967030 ms 68.28.95.16 8 4294966965 ms 4294966922 ms 4294966940 ms 68.28.93.69 9 4294966938 ms 4294966949 ms 4294967033 ms sl-crs3-chi-0-1-5-0.sprintlink.net [144.223.61.129] 10 4294966941 ms 4294966943 ms 4294966941 ms sl-crs3-chi-0-1-1-0.sprintlink.net [144.232.3.139] 11 4294966971 ms 4294966948 ms 4294966983 ms sl-st20-chi-0-0-0.sprintlink.net [144.232.19.144] 12 4294967026 ms 4294966949 ms 4294966947 ms 144.232.19.174 13 509 ms 4294967104 ms 4294967000 ms ae-31-53.ebr1.Chicago1.Level3.net [4.68.101.94] 14 106 ms 4294967006 ms 4294966995 ms ae-6.ebr1.Chicago2.Level3.net [4.69.140.190] 15 4294967021 ms 4294967051 ms 4294967065 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61] 16 4294966993 ms 4294967043 ms 4294967045 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 17 4294967081 ms 4294966984 ms 4294966975 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106] 18 4294967051 ms 4294967137 ms 4294967031 ms ae-4-4.car2.SanDiego1.Level3.net [4.69.133.213] 19 165 ms 4294967011 ms 4294967014 ms ge-6-2.hsa1.SanDiego1.Level3.net [4.69.142.158] 20 4294967011 ms 4294967036 ms 4294967036 ms vl861.sdtermswitch-1.sonyonline.net [63.215.251.130] 21 4294967021 ms 196 ms 4294967009 ms vl831.sdkollsw-1.sonyonline.net [64.37.144.82] 22 4294966983 ms 4294967019 ms 4294967087 ms sdkeq2-05-01.everquest2.com [199.108.12.161]Trace completeThat is the worst I have ever seen it....I thought it would be important to note, that despite it saying so many jumps took over 4 billion ms, it took way less than 10 seconds to complete the trace.when I do the tracert on his machine there is usually only 1-3 jumps with the 4294966971 ms (most often its the sandiego links twice it has been one of the 68.28. xx.xx numbers)...Now, I have tried two different connection softwares and called sprint multiple times yesterday. They help me reset my connection on my end, then they reset the connection on their end. Did another firmware update... nothing they are doing is helping this lag and crashing. Is this more likely an isp problem, a game problem, or a router problem...?Also note that we were playing absolutely fine until game update 53, then it was tons of the memory crashes and lots of lag(not completely unplayable) where there had been none before. Now after this week's patch the crashing to character select starts and the lag goes through the freaking roof.

Isilsisial

11-08-2009, 01:08 PM

20 minutes later of just sitting at the character select screen, this is what it looks like... sigh.Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.C:Documents and SettingsAdministrator>tracert unrest.everquest2.comTracing route to sdkeq2-05-01.everquest2.com [199.108.12.161]over a maximum of 30 hops: 1 <1 ms 4294966841 ms <1 ms 192.168.0.1 2 76 ms 109 ms 233 ms 68.28.89.69 3 98 ms 99 ms 98 ms 68.28.89.91 4 175 ms 89 ms 114 ms 68.28.91.55 5 * * * Request timed out. 6 152 ms 142 ms 142 ms 68.28.95.1 7 144 ms 207 ms 93 ms 68.28.95.16 8 92 ms 117 ms 108 ms 68.28.93.69 9 181 ms 167 ms 179 ms sl-crs3-chi-0-1-5-0.sprintlink.net [144.223.61.129] 10 181 ms 188 ms 187 ms sl-crs3-chi-0-1-1-0.sprintlink.net [144.232.3.139] 11 213 ms 187 ms 116 ms sl-st20-chi-0-0-0.sprintlink.net [144.232.19.144] 12 5 ms 133 ms 110 ms 144.232.19.174 13 180 ms 629 ms 202 ms ae-31-53.ebr1.Chicago1.Level3.net [4.68.101.94] 14 198 ms 172 ms 604 ms ae-6.ebr1.Chicago2.Level3.net [4.69.140.190] 15 185 ms 133 ms 168 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61] 16 147 ms 167 ms 134 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 17 4294967032 ms 159 ms 146 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106] 18 4294967204 ms 187 ms 194 ms ae-4-4.car2.SanDiego1.Level3.net [4.69.133.213] 19 178 ms 166 ms 234 ms ge-6-2.hsa1.SanDiego1.Level3.net [4.69.142.158] 20 185 ms 4294967012 ms 223 ms vl861.sdtermswitch-1.sonyonline.net [63.215.251.130] 21 186 ms 180 ms 214 ms vl831.sdkollsw-1.sonyonline.net [64.37.144.82] 22 4294967002 ms 154 ms 158 ms sdkeq2-05-01.everquest2.com [199.108.12.161]Trace complete.C:Documents and SettingsAdministrator>And yes, we have tried the instructions on resetting routers/modems after a patch several times...

TSR-DanielH

11-10-2009, 04:21 PM

Greetings,Do you have these same issues if you are plugged directly into the modem, bypassing the router entirely? Also, what kind of internet connection do you have?