EPTACCESS_VIOLATION (0xC0000005)
occurred at 0023:009C2AB0. The memory at '0x00000024' could not be read.
Access Violation: Memory could not be read
| Forum Index > Tech Support |
|
dcberkeley
Canada844 Posts
ACCESS_VIOLATION (0xC0000005) occurred at 0023:009C2AB0. The memory at '0x00000024' could not be read. | ||
|
Adila
United States874 Posts
| ||
|
KOFgokuon
United States14894 Posts
| ||
|
Myrmidon
United States9452 Posts
| ||
|
Doko
Argentina1737 Posts
| ||
|
Asianic
Singapore99 Posts
check with memtest86 check voltage test with another set of RAM sticks | ||
|
Spythe
United States24 Posts
| ||
|
KOFgokuon
United States14894 Posts
| ||
|
R1CH
Netherlands10340 Posts
| ||
|
dcberkeley
Canada844 Posts
On October 04 2010 08:14 Spythe wrote: I just did a memory check and no errors at all so I do not think its RAM issue, their are a few people complaining about the same problem. Hopefully bliz comes with a fix soon Whoa another person with the same problem! It's possible it's not the ram? I tried doing a memtest but I failed to get it to boot to cd so I just took it to the local store for them to check it out. They did it and apparently didn't find any problems with it. I left it there for about a few hours so I think they did a few cycles with it. As for if there's an error with anything else, I have BSOD'd once or twice I think but I always did SC2 stuff right before. I haven't played most any other games. BTW, where are these people with the problem? Can you direct me to a link? I don't think I've seen anything like this on the blizz forums. | ||
|
Spythe
United States24 Posts
@R1CH its just SCII and it just started recently, I've played most of beta and since release never crashed in an actually game. Then I updated windows and got the latest patch and I almost crash constantly. @DcBerkeley, I highly doubt its a our PC problem here is one thread I posted it http://us.battle.net/sc2/en/forum/topic/628240449?page=1#10 And here is another one with a few replies http://us.battle.net/sc2/en/forum/topic/791239965 Here is some guy claiming fix it yourself, I did a few thing he suggested but haven't tried it yet http://us.battle.net/sc2/en/forum/topic/801780737 | ||
|
dcberkeley
Canada844 Posts
| ||
|
R1CH
Netherlands10340 Posts
| ||
|
Spythe
United States24 Posts
Fault bucket , type 0 Event Name: PCA2 Response: Not available Cab Id: 0 Problem signature: P1: StarCraft II.exe P2: 2.1.2.1890 P3: Blizzard Launcher P4: Blizzard Launcher P5: Blizzard Entertainment P6: 200 P7: -1 P8: P9: P10: Attached files: C:\Users\Spythe\AppData\Local\Temp\{babcfede-2d76-40eb-8f0d-4de6f4b7a67a}\appcompat.txt C:\Users\Spythe\AppData\Local\Temp\Tab38FA.tmp These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: 4f8d1c20-ce69-11df-8aab-001e8ca4212b Report Status: 0* | ||
|
Dinosaur
Denmark112 Posts
| ||
|
lahtel
United States11 Posts
| ||
|
nalF
United Kingdom1 Post
Also tried changing shader settings. Game runs fine apart from these crashes Updated all drivers, at a loss really. Here's what it says on my last crash ACCESS_VIOLATION (0xC0000005) occurred at 0023:6CCCB6B2. The memory at '0x692047A8' could not be read. sent dxdiag/msinfo and crash txt to blizzard tech, no response yet Cant find any error reports in windows event logs | ||
|
krew406
United States115 Posts
| ||
|
kflynn
69 Posts
that being said, if you are always getting the exact same error (complaining about the exact same memory location) then most likely you have a driver problem. experiment with different vid driver versions, see if there are updated firmware for either your mobo or vid card. fiddle the with SC2 graphics settings, such as toggling vsync and disabling physics. | ||
|
PrincessLeila
France170 Posts
might be a software bug, dereferecing a null struct pointer member mov whatever, [eax+24] with eax = 0 | ||
| ||
