that's logs not longs, lol.
Edited by Shinikaru, 09 March 2013 - 08:40 AM.
1
Is There A Place To Upload Error Longs For Devs?
Started by Shinikaru, Mar 09 2013 08:40 AM
2 replies to this topic
#1
-
-
- FP Veteran - Beta 1
- 131 posts
Member
Posted 09 March 2013 - 08:40 AM
since last patch every few games either starting or ending i get the dreaded failed to read memory at xxxxxxxxx error. is there a place here on the forums that the devs are accepting and looking at the generated error log in windows/temp?
that's logs not longs, lol.
that's logs not longs, lol.
#2
-
-
- Stone Cold
- 11,975 posts
Welcoming Committee
- LocationNewfoundland
Posted 09 March 2013 - 09:02 AM
Send an email to support@mwomercs.com
#3
-
-
- Bad Company
- 1,001 posts
Member
Posted 09 March 2013 - 02:14 PM
About the only way to avoid that error is to
1. Migrate to Win 7 x64
2. Slot on more Ram. I run 12 atm and have not had the mem error since closed beta.
3. It is possible that your install is corrupt. Personally I keep a complete backup of the game (my bandwidth sucks) to save up on MB if I have to reinstall..
4. If 1 and 2 fail you Try to do a vanilla install. You should be alright with going to x64. Note however that for some unlucky few using x64 does not work. YMMV
When contacting support:
Include a DXDiag log
The Omicron log of the crash.
That is standard.
1. Migrate to Win 7 x64
2. Slot on more Ram. I run 12 atm and have not had the mem error since closed beta.
3. It is possible that your install is corrupt. Personally I keep a complete backup of the game (my bandwidth sucks) to save up on MB if I have to reinstall..
4. If 1 and 2 fail you Try to do a vanilla install. You should be alright with going to x64. Note however that for some unlucky few using x64 does not work. YMMV
When contacting support:
Include a DXDiag log
The Omicron log of the crash.
That is standard.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
