beaglefish 0 Posted June 21, 2004 Share Posted June 21, 2004 I fixed one series of problems on my dedicated server by upgrading it from Windows 98SE to Windows XP. BTW, didn't know you could install the same copy of XP to more than one computer... Now I have a different problem. Occasionally the Dedicated Server crashes to desktop. Here are the specs: Pentium III 800 MHz NVidia Riva TNT2 Model 64 (don't think it should matter for DServer) 384MB RAM Netgear RP614v2 router Netgear cable modem I've gotten this sort of problem a few times--read or write access violations. Any ideas on how to fix? Thanks. Here's IkeCrash: GhostRecon caused an Access Violation in module GhostRecon.exe at 001b:00549120. Exception handler called in Main Thread. Error occurred at 6/20/2004 21:03:26. C:\Program Files\Red Storm Entertainment\Ghost Recon\GhostRecon.exe, run by David. 1 processor(s), type 586. 384 MBytes physical memory. Read from location 00000068 caused an access violation. Registers: EAX=09882400 CS=001b EIP=00549120 EFLGS=00010206 EBX=00000000 SS=0023 ESP=0012fac4 EBP=09882400 ECX=00000000 DS=0023 ESI=00000000 FS=003b EDX=0012faec ES=0023 EDI=098b07c0 GS=0000 Bytes at CS:EIP: 8b 41 68 8b 50 50 42 89 50 50 8b c2 8a 91 10 01 Stack trace: 00549120: GhostRecon.exe! <no symbol>, <no file>, <no line> 0085B3CC: GhostRecon.exe! <no symbol>, <no file>, <no line> 0040BE10: GhostRecon.exe! <no symbol>, <no file>, <no line> Module list: names, addresses, sizes, time stamps and file times: C:\WINDOWS\System32\d3d8thk.dll, loaded at 0x00320000 - 8192 bytes - 3df82460 - file date is 12/12/2002 00:14:32 C:\Program Files\Red Storm Entertainment\Ghost Recon\GhostRecon.exe, loaded at 0x00400000 - 6402084 bytes - 3da72199 - file date is 10/11/2002 15:08:34 C:\WINDOWS\System32\d3d8.dll, loaded at 0x00960000 - 1156608 bytes - 3dedc941 - file date is 12/12/2002 00:14:32 C:\PROGRA~1\mcafee.com\vso\McVSSkt.dll, loaded at 0x01bc0000 - 106496 bytes - 408fefc3 - file date is 4/28/2004 10:54:12 C:\WINDOWS\System32\rsaenh.dll, loaded at 0x0ffd0000 - 133632 bytes - 3ccdcab0 - file date is 3/31/2003 06:00:00 C:\DOCUME~1\David\LOCALS~1\Temp\~ef6034\~df394b.tmp, loaded at 0x10000000 - 822824 bytes - 3c76503b - file date is 6/20/2004 20:51:58 C:\WINDOWS\System32\DSOUND.dll, loaded at 0x51080000 - 336384 bytes - 3dedc968 - file date is 12/12/2002 00:14:32 C:\WINDOWS\System32\uxtheme.dll, loaded at 0x5ad70000 - 203264 bytes - 3d6df9da - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\KsUser.dll, loaded at 0x5ef80000 - 4096 bytes - 3dedcbf6 - file date is 12/12/2002 00:14:32 C:\WINDOWS\system32\wininet.dll, loaded at 0x63000000 - 588288 bytes - 402447cf - file date is 2/6/2004 18:05:06 C:\WINDOWS\System32\HID.DLL, loaded at 0x688f0000 - 22528 bytes - 3b7dfe68 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\DINPUT8.dll, loaded at 0x6ce10000 - 168960 bytes - 3d6dfa10 - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\SHLWAPI.dll, loaded at 0x70a70000 - 395264 bytes - 400f08cd - file date is 1/21/2004 15:18:42 C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.1331_x-ww_7abf6d02\comctl32.dll, loaded at 0x71950000 - 921600 bytes - 4036cb88 - file date is 2/20/2004 21:07:54 C:\WINDOWS\System32\mswsock.dll, loaded at 0x71a50000 - 228352 bytes - 3b7dfe31 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\wshtcpip.dll, loaded at 0x71a90000 - 17408 bytes - 3b7dfe33 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\WS2HELP.dll, loaded at 0x71aa0000 - 18944 bytes - 3b7dfe32 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\WS2_32.dll, loaded at 0x71ab0000 - 70656 bytes - 3f0dbc2c - file date is 7/10/2003 12:19:10 C:\WINDOWS\System32\WSOCK32.dll, loaded at 0x71ad0000 - 21504 bytes - 3b7dfe31 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\netapi32.dll, loaded at 0x71c20000 - 306176 bytes - 4068d1f4 - file date is 3/29/2004 19:48:36 C:\Program Files\Red Storm Entertainment\Ghost Recon\DBGHELP.dll, loaded at 0x72a00000 - 163088 bytes - 3af32067 - file date is 8/10/2001 09:27:10 C:\WINDOWS\System32\msacm32.drv, loaded at 0x72d10000 - 20480 bytes - 3b7dfe2a - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\wdmaud.drv, loaded at 0x72d20000 - 22016 bytes - 3b7dfe2a - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\cryptnet.dll, loaded at 0x73d50000 - 53248 bytes - 3b7dfe24 - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\userenv.dll, loaded at 0x75a70000 - 667136 bytes - 3d6dfa1a - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\Apphelp.dll, loaded at 0x75f40000 - 115712 bytes - 3d6dfa1b - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\MSASN1.dll, loaded at 0x762a0000 - 51712 bytes - 4068d1f4 - file date is 3/29/2004 19:48:36 C:\WINDOWS\system32\CRYPT32.dll, loaded at 0x762c0000 - 544256 bytes - 3d8f9151 - file date is 9/23/2002 16:10:26 C:\WINDOWS\System32\SETUPAPI.DLL, loaded at 0x76670000 - 932864 bytes - 3d6dfa1e - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\WINMM.dll, loaded at 0x76b40000 - 171520 bytes - 3d6dfa20 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\rtutils.dll, loaded at 0x76e80000 - 39936 bytes - 3b7dfe11 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\rasman.dll, loaded at 0x76e90000 - 55808 bytes - 3d6dfa22 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\TAPI32.dll, loaded at 0x76eb0000 - 165376 bytes - 3d6dfa22 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\Rasapi32.dll, loaded at 0x76ee0000 - 217088 bytes - 3d6dfa22 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\DNSAPI.dll, loaded at 0x76f20000 - 139264 bytes - 3d6dfa22 - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\WLDAP32.dll, loaded at 0x76f60000 - 168448 bytes - 3d6dfa22 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\secur32.dll, loaded at 0x76f90000 - 52224 bytes - 3d6dfa22 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\winrnr.dll, loaded at 0x76fb0000 - 14848 bytes - 3b7dfe11 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\rasadhlp.dll, loaded at 0x76fc0000 - 6144 bytes - 3b7dfe11 - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\OLEAUT32.dll, loaded at 0x77120000 - 569344 bytes - 3d6dfa22 - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\ole32.dll, loaded at 0x771b0000 - 1183744 bytes - 4049346b - file date is 3/5/2004 20:16:12 C:\WINDOWS\system32\comctl32.dll, loaded at 0x77340000 - 557056 bytes - 3d6dfa2a - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\shell32.dll, loaded at 0x773d0000 - 8348160 bytes - 4036cb88 - file date is 2/20/2004 21:07:54 C:\WINDOWS\System32\midimap.dll, loaded at 0x77bd0000 - 17920 bytes - 3b7dfe0f - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\MSACM32.dll, loaded at 0x77be0000 - 67072 bytes - 3b7dfe0f - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\VERSION.dll, loaded at 0x77c00000 - 16384 bytes - 3b7dfe0f - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\MSVCRT.dll, loaded at 0x77c10000 - 323072 bytes - 3d6dfa27 - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\USER32.dll, loaded at 0x77d40000 - 560128 bytes - 3f731c7d - file date is 9/25/2003 10:49:02 C:\WINDOWS\system32\ADVAPI32.dll, loaded at 0x77dd0000 - 558080 bytes - 3d6dfa28 - file date is 3/31/2003 06:00:00 C:\WINDOWS\system32\kernel32.dll, loaded at 0x77e60000 - 930304 bytes - 3d6dfa28 - file date is 3/31/2003 06:00:00 C:\WINDOWS\System32\ntdll.dll, loaded at 0x77f50000 - 654336 bytes - 3eb1b41a - file date is 5/1/2003 17:56:12 C:\WINDOWS\system32\RPCRT4.dll, loaded at 0x78000000 - 535552 bytes - 4049346b - file date is 3/5/2004 20:16:12 C:\WINDOWS\system32\GDI32.dll, loaded at 0x7e090000 - 257536 bytes - 4068d1f4 - file date is 3/29/2004 19:48:36 Quote Link to post Share on other sites
ROCO*AFZ* 0 Posted June 21, 2004 Share Posted June 21, 2004 the ike crash doesn't tell us much but if you can grab the ike log imeditaly after the crash (before it comes back up if on auto start on gr crash) we should be able to help you out Quote Link to post Share on other sites
countrytom 0 Posted December 19, 2004 Share Posted December 19, 2004 I am having the exact same problem occasionally. Read from location 00000068 caused an access violation appears everytime. I think that log IS from immediately after the crash. Mine looks the same. Any help would be greatly appreciated. Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.