|
Let me preface this by saying that I tried the official SC2 tech support forum first. Their policy seems to be to ignore any thread entirely if they don't know how to fix the issue, so no Blizzard person ever responded.
Computer specs:
955 BE (no overclocking whatsoever)
GTX460 768mb
4gb (2x2gb) Mushkin DDR3 RAM
500gb 7200 RPM HDD
500W OCZ PSU
Windows 7 64 bit
I'm having a serious issue with SC2. Occasionally, without warning, the game will crash and bring up the following error:
ACCESS_VIOLATION (0xC0000005)
occurred at 0023:00CB7039. The memory at '0x00000000' could not be read.
Before I go into my own troubleshooting, I should point out that my computer is less than 3 months old and this problem has been happening from the beginning. My old computer, which was much less powerful, never had any crashing issues.
I naturally suspected that there was something wrong with my RAM, since defective RAM sticks aren't uncommon. Memtest86+ ran for 14 hours and found 0 errors. Some people claim that HCI Memtest is better at finding things, so I downloaded it, closed every program, and ran it. After 12 hours, it didn't find anything. I highly doubt the RAM sticks are defective if over 24 combined hours of testing can't find one fault. I took the RAM out and reseated both sticks, but the crashing continued.
After verifying that my RAM is probably good, I thought it might be an issue with the SC2 installation. Using the repair tool did not help, so I uninstalled and reinstalled, but to no avail. The issue isn't heat-related, as I always run CPUID HWMonitor, and the CPU cores and GPU max out at 52C and 45C respectively in SC2. I have the exe set to run as administrator. The Nvidia drivers are up to date, and I have tried reinstalling them. The RAM voltage is at 1.5V.
I really don't know what else to do here. The problem has forced me into an SC2 hiatus, as it ruins my ability to ladder. I tried to ladder last night and crashed in my third game (~20 min after starting the program). I've also had the error pop up in the lobby, with the game minimized, so it's not dependent on actually being in a match. The error usually says that the memory could not be "read" but I've also seen "written" and "executed."
I can provide any further info upon request. Thanks in advance for any assistance with this frustrating matter.
|
Do you have any other video cards lieing around?
Maybe its the VRAM on your GTX 460 (explaining the cannot read write, ex)
At this point anything seems like it is worth a shot. It s worth trying to narrow down if it is a hardware issue.
last thing id say is reformat =/
Im sorry to hear this, it must be very frustrating for you.
|
Unfortunately I don't have any other video cards. This is my first desktop since the early 2000s.
|
Well-written, detailed opening post.
I don't agree that it's GPU related, especially since it crashes at idle and temperatures are not a problem. Even then, i think the nVidia driver would have logged something That said, have you gone through your event viewer logs? See if there are any other error messages near or at the same time as your system crashes.
Is CnQ enabled btw?
|
CnQ is set to auto in the BIOS.
As for the event viewer, those are uncharted waters for me, but I'll have a look anyway. Note that it's not actually a system crash. SC2 crashes and I just end up on my desktop with the SC2 error log.
|
Does this happen with any other game or program? Or is it only with SC2?
|
SC2 is the only PC game I play (I bought the comp to handle D3 in the future, so it's a little overkill for SC2). Firefox's plugin-container.exe crashes sometimes, but I don't really use any other memory-intensive programs.
|
|
|
Dominican Republic913 Posts
why dont u try the repair.exe that is located in your SC2 folder
|
As much as I appreciate the reply, the guy in the bnet forum thread is talking nonsense. A huge amount of people play SC2 with a multicore processor and 64 bit windows without any issue.
On January 11 2011 04:16 2GRe-Play- wrote:
why dont u try the repair.exe that is located in your SC2 folder
I already wrote in the OP that I tried repairing AND reinstalling, but the crashing didn't go away.
|
On January 11 2011 04:20 city42 wrote:As much as I appreciate the reply, the guy in the bnet forum thread is talking nonsense. A huge amount of people play SC2 with a multicore processor and 64 bit windows without any issue. Show nested quote +On January 11 2011 04:16 2GRe-Play- wrote:
why dont u try the repair.exe that is located in your SC2 folder I already wrote in the OP that I tried repairing AND reinstalling, but the crashing didn't go away.
How about you try it without getting angry?
|
Who's angry? I think I was pretty nice, considering the guy didn't read the OP.
|
Given what you have done already:
-Make sure you have the latest chipset & video drivers (yes I read the op), use driver cleaning software if you need to install different ones.
-Run windows update.
-Try disabling your anti-virus and see if it still happens.
-Flash your BIOS with the latest version.
-Try a different video card? This is a stretch, but who knows.
If that doesn't do it I would just re-format & use windows backup & recovery to transfer all of your libraries back onto the new installation via removable drive.
I think this has something to do with windows data execution prevention (DEP). It's basically the OS telling SC2 that it isn't supposed to be using that memory.
|
On January 11 2011 04:20 city42 wrote:As much as I appreciate the reply, the guy in the bnet forum thread is talking nonsense. A huge amount of people play SC2 with a multicore processor and 64 bit windows without any issue. Show nested quote +On January 11 2011 04:16 2GRe-Play- wrote:
why dont u try the repair.exe that is located in your SC2 folder I already wrote in the OP that I tried repairing AND reinstalling, but the crashing didn't go away.
http://www.updatexp.com/0xC0000005.html
|
run some 3dmark benchmarks/other games/Prime95, if it crash again try downclockin the processor then try down clockin the video card. Good start will be to reset bios to default and look for new bios for ur mobo. Something is faulty, and i doubt it's Starcraft
|
On January 11 2011 04:32 city42 wrote:
Who's angry? I think I was pretty nice, considering the guy didn't read the OP.
Who said he didnt?
the tone of your post made you come off as dont even want to try to fix the problem.
He showed you that thread because it has the same error.
Did you read what he linked too?
Sounds like you havnt tried that yet. SO TRY IT, OR DONT EVEN BOTHER FIXING THE PROBLEM.
|
Lol the two posters clearly didn't bother to read city's first post. If they did, they would have realized that city42 has already exhausted the official BNet resources and has already tried repairing/reinstalling.
City42 has every right to be angry - they're wasting his time talking about things he has already tried. The one link just involves changing affinity settings. That is clearly not a solution.
|
On January 11 2011 04:49 mav451 wrote:
Lol the two posters clearly didn't bother to read city's first post. If they did, they would have realized that city42 has already exhausted the official BNet resources and has already tried repairing/reinstalling.
City42 has every right to be angry - they're wasting his time talking about things he has already tried. The one link just involves changing affinity settings. That is clearly not a solution.
Umm... well he never stated that "i have tried this specific fix"
Its possible he ONLY read the official troubleshooting thread. He also said he posted a thread, but nothing about anything hes tried from the site.
Anyways, gl.
|
I like how you find it appropriate to argue about arguing. Stay classy, Marcus.
When attempting to reinstall, you might try deleting your temp files. Something in there might be fucking up with your error, which, I think, is normally caused by corrupted files. Could be wrong.
edit: actually apparently i have no idea what i'm talking about. herp derp nevermind
|
Russian Federation410 Posts
Here's what you do. (...And no, you don't need to update bios, it's not your video card, it's not the anti-virus, it has nothing to do with temporary files)
1. Install latest video drivers, or, better yet, first remove older ones and then install the latest version
2. Remove one of the RAM sticks, run SC2 with one, see if it crashes, if it does/doesn't, use another one.
If #1-#2 prove ineffective, go into Control Panel - Administrative - Event viewer, (System and Software sections), copy the ones that are registered to the time of BSOD (kernel error) and the ones just prior to that.
You can also try running "BIOS Safe Mode" (do not confuse with Windows Safe Mode).
|
|
|
|
|
|
EPT
