|
error images and txts
![[image loading]](http://imgur.com/ypgBT.jpg)
![[image loading]](http://imgur.com/Gn0hP.png)
ACCESS_VIOLATION (0xC0000005)
occurred at 0023:37F49B88. The memory at '0x37F49B88' could not be executed.
--------------------------------------------------------------------------------
----------------------------------------
Manual Stack Trace (ID:4068 Stack:0x05A40000 + 8,388,608 "Main Thread")
----------------------------------------
DBG-ADDR<37F49B88>("")
DBG-ADDR<00C6ECCD>("SC2.exe")
DBG-ADDR<00D03A38>("SC2.exe")
DBG-ADDR<01282F04>("SC2.exe")
DBG-ADDR<00C648C5>("SC2.exe")
DBG-ADDR<00C66C3A>("SC2.exe")
DBG-ADDR<00C66E6C>("SC2.exe")
DBG-ADDR<00C66FCC>("SC2.exe")
DBG-ADDR<00C67935>("SC2.exe")
(my computer)
CPU Intel Sandybridge 2600K
Mainboard MSI P67-GD65
RAM G.SKILL DDR3 1333 8G (2x4GB)
VGA NVIDIA GeForce GTX 570
HDD WDC WD20EARS 2TB 64MB SATA 3.0Gb/s
ODD LITE-ON DVD
Power Antec HCG-750 750W
Case Antec Lanboy Air Yellow
Cooler ZALMAN CNPS9900ALED 120mm 2 Ball Low-noise Blue LED CPU
Monitor iiyama LCD 22 Inch
Sound/SP Creative X-Fi Titanium Fantal1ty Professional series
KB/Mouse Razer Blackwidow Ultimate / MS intelliexplore 3.0
Router/ISP D-Link DIR-655 / LAN Card - BIGFOOT Killer 2100
OS Microsoft WIndows 7 Home-edition
Ive been getting sc2 crash so many times even on the tournament games.
Let me explain my situation first
I newly bought my computer its been 1 and half month
First month i had no crash at all but recently.
Since the error is about memory I thought my RAM is broken or burnt
So i tried to use only 1 ram (im using 2 of 4GB) but still crashed
so i used another one but still crashed.
I figured its not ram problem.
Then what?
So I thought it can be my graphic card.
So i took my geforce 570 out and put my old graphic card geforce 9800 GTX
the result? still got sc2 crash.
I figured its not VGA problem..
I put my geforce 570 back and figured it can be sound card (Motherboard soundcard)
So i took out my bigfoot network card and put creative X-FI titanium soundcard (because I was using Intel mini atax mainboard at that time. There was only 1 Pci slot left since my graphic card took over the space)
??.... still crashed so its not soundcard.
However I bought new mainboard (MSI P67-GD65) since i wanted to use both network card and sound card
It came yesterday and i built it.
and i was hoping for it to be fixed.
Today i was playing fxopen tournament it crashed me out of game again.
SO..... WHAT NOW?
CPU? POWER ? HDD ?
I don't understand
how can CPU only crash sc2?
How can POWER crash 1 software?
how can HDD crash only sc2??? ( i reinstalled window 7 and sc2 several times)
or can it be both of ram are broken??
Help me please T_T... I dont have time to deal with this stupid thing T_T
I have to practise......
|
2629 Posts
I hope you get it fixed soon T_T
edit: sorry for useless help
Have you tried memtest-ing ?
|
It's not your hardware. A lot of us have been crashing since patch 1.3 came out. Just gotta wait for blizz to fix this.
|
Haven't tried memtest
I have tried Prime95 tho
ok im going to try memtest right now
It is definitely my hardware because i never get crash with my old desktop and laptop thats how i continued playing on the tournament.
|
|
|
Im running memtest no error so far its been 2.5 hours
|
Interesting...I have pretty much the same PC, and also crash when playing SC2. I hope you are luckiers than me, because nothing I did helped solve the problem. >_>
Maybe it's the MB - at least the SATA-Ports are known to be defect in some, and who knows what Intel has botched in other parts...
|
It's probably ram anyway, but not the sticks themselves and instead clock settings or faulty mb.
I also could run memtest forever and in 3 cases of 4 it still was the memoryu's fault. This other time it was the power 'unit' or whatever you call it, that had broken. RAM is almost always the cause and especially at those times you think it's not.
|
The stop 0x50 message indicates that requested data was not found in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.
Run memtest 5-8 passes on each stick of memory individually. From the specs of your computer I would guess you built it yourself. It might behoove you to initiate RMA request now.
|
I've been experimenting with overclocking ram recently trying to ascertain exactly what is going on with so many people having these crashes. It seems the latest patch may be (for whatever reason) exposing systems with flaky memory/memory running out of spec.
Do not use memtest solely as your memory tester.
Run blend tests on prime95 also, I had had memory last 12 hours in memtest only to fail in minutes running blend tests on prime.
Also what speed, timings and voltage is your ram running at?
|
I should think that it's the power.
COD6 also crashed on me, I had GTX460 and i5 on 600Watt.
I'd suggest getting more power or changing it, maybe it's not working well.
But I might be wrong, I just talk from my experience!
|
Every time you crash, are these numbers the same?
occurred at 0023:37F49B88. The memory at '0x37F49B88' could not be executed
If they are different every time, it's most likely a hardware issue. If not, software.
|
On March 27 2011 21:51 Flammable wrote:
I should think that it's the power.
COD6 also crashed on me, I had GTX460 and i5 on 600Watt.
I'd suggest getting more power or changing it, maybe it's not working well.
But I might be wrong, I just talk from my experience!
I believe his processor has a TDP of 95W (I realize this isn't power draw but a reasonable estimate to go by) and that GPU pulls like 350W MAX (from memory) when extremely heavily overclocked. If his system pulls more power than his 750W PSU can provide I'll eat my hat.
|
On March 27 2011 22:43 Speight wrote:Show nested quote +On March 27 2011 21:51 Flammable wrote:
I should think that it's the power.
COD6 also crashed on me, I had GTX460 and i5 on 600Watt.
I'd suggest getting more power or changing it, maybe it's not working well.
But I might be wrong, I just talk from my experience! I believe his processor has a TDP of 95W (I realize this isn't power draw but a reasonable estimate to go by) and that GPU pulls like 350W MAX (from memory) when extremely heavily overclocked. If his system pulls more power than his 750W PSU can provide I'll eat my hat.
There's no way, I'm running i7 930, SLI460, Hyper 212+, and multiple drives off a 650W.
I'd be triple checking chipset drivers and graphics drivers, personally.
|
my starcraft 2 has been crashing since the last patch, maybe it was the patch that messed things up T_T
|
Personally I'd try using the repair tool, or reinstalling sc2 since it seems unlikely to be a hardware fault.
|
|
|
Ugh already two posts wasted on PSU. It's not the PSU - he draws maybe 370W, TOTAL, at load (~240 for the GTX 570 and ~130 for the i7). Please put it to rest guys, if you don't know what you are talking about, don't waste his time.
My hunch is that using the 4GB DIMMs (vs. 2GB DIMMs) may be stressing the IMC, or that the sticks were over-rated slightly. Just to rule out some things, check that it is running at 2T (command rate), as 1T may be overaggressive. Also check that all the timings are being set correctly, as Auto can be hit/miss when pulling for SPD.
And the other thing may just be bumping the DRAM voltage, to say 1.55v.
|
Since it's just SC2, could be corrupted files or a bad HDD sector as well.
Edit: In the other thread on SC2 crashing since the patch, some people reported running SC2 as admin fixed the problem.
|
Hmm speaking of HD, I didn't realize Select was running off a WD Green :|
I'd check the SMART info with CrystalDiskInfo just to rule things out, but I don't think it'll find much. If he had HD health problems, it would have been manifesting even outside of SC2.
|
On March 28 2011 01:28 mav451 wrote:
Hmm speaking of HD, I didn't realize Select was running off a WD Green :|
I'd check the SMART info with CrystalDiskInfo just to rule things out, but I don't think it'll find much. If he had HD health problems, it would have been manifesting even outside of SC2.
Well, it's new so it probably isn't heavily fragged, and if SC2 is the only thing on the (currently theoretical) one bad sector, it could just cause hassle there. I also saw some stuff on google about some sata controllers hating that particular drive, but on this new of a build, I doubt that's the problem.
|
to answer some questions and clarify a few points:
His files are not corrupt. He has reformatted his HDD multiple times and is still experiencing crashes.
His motherboard is brand new. It has the B3 revision chipset (That's the SATA port fix, fyi). Both new and old boards are causing crashes.
His power supply is plenty good for his configuration. Check http://support.asus.com/PowerSupplyCalculator/PSCalculator.aspx?SLanguage=en-us to verify. He really only needs about 300W of power total.
It's also not because of patch 1.3. He says he's been crashing since before it came out.
Anyone else experiencing similar errors please post your system configuration too.
|
I'll repost this since it seems to have been ignored:
I've been experimenting with overclocking ram recently trying to ascertain exactly what is going on with so many people having these crashes. It seems the latest patch may be (for whatever reason) exposing systems with flaky memory/memory running out of spec.
Do not use memtest solely as your memory tester.
Run blend tests on prime95 also, I had had memory last 12 hours in memtest only to fail in minutes running blend tests on prime.
Also what speed, timings and voltage is your ram running at?
|
Sounds pretty rough, my guess would be power supply, i had some trouble with mine recently and the same thing happened.
how i knew it was my power supply was i decided to look through my BIOS settings and in there one of the power supply numbers was red, as in my computer wasnt getting enough power.
|
On March 27 2011 22:10 R1CH wrote:Every time you crash, are these numbers the same? If they are different every time, it's most likely a hardware issue. If not, software.
their numbers are always different.. so should i get new hard disk? can hard disk make sc2 crash?
|
On March 27 2011 23:20 KOVU wrote:
Personally I'd try using the repair tool, or reinstalling sc2 since it seems unlikely to be a hardware fault.
Of course I have tried reinstalling window 7 , sc2 , repairing tool several time as i mentioned above 
|
On March 28 2011 05:51 Speight wrote:
I'll repost this since it seems to have been ignored:
I've been experimenting with overclocking ram recently trying to ascertain exactly what is going on with so many people having these crashes. It seems the latest patch may be (for whatever reason) exposing systems with flaky memory/memory running out of spec.
Do not use memtest solely as your memory tester.
Run blend tests on prime95 also, I had had memory last 12 hours in memtest only to fail in minutes running blend tests on prime.
Also what speed, timings and voltage is your ram running at?
Ive ran prime95 for a day i didn't get any error after overcloacking my cpu 3.4 -- > 4.2
also yesterday ive ran memtest for 12 hours and i didn't get any error
|
btw my ram timing is 6-6-6-20 (original setting) I haven't touched anything about ram yet
voltage is 1.488
|
Oh wow didn't realize you were overclocked. I'd set it back to stock to remove all variables here.
Can you post a link to your specific set of G.Skill RAM?
What concerns me is that most DDR3 kits are usually cas 7 and above, I don't think I've seen a cas 6 set before. And I would highly suggest putting in the timings manually, as my previous posts have touched on, make sure that command rate is set at 2T, not 1T.
|
unclock your cpu or make sure turbo mode is switched off, switching it off after i over clocked stoped all system instability for me. if i remember right turbo mode sends more power to one of the cores if it detects it needs it so mabye thats the power issue ur having because ur over clocked
also alot of people are ahving trouble with the MSI P67-GD65. so try unclocking everything and see if it still happens then what i would do is trial and error swapping 1 part at a time until it stops if it doesent stop prob your motherboard
|
try new ram even if ram test says its good
|
On March 28 2011 07:26 mav451 wrote:
Oh wow didn't realize you were overclocked. I'd set it back to stock to remove all variables here.
Can you post a link to your specific set of G.Skill RAM?
What concerns me is that most DDR3 kits are usually cas 7 and above, I don't think I've seen a cas 6 set before. And I would highly suggest putting in the timings manually, as my previous posts have touched on, make sure that command rate is set at 2T, not 1T.
I overcloaked recently after I built with New motherboard because when i was using my old motherboard (intel atax miniboard) I was still crashing and this board is locked on overcloacking. It is not about overcloack.
![[image loading]](http://imgur.com/ftuwc.jpg)
because it is 1333 i think.. :O?
what ram timing would u recommand me?
|
On March 28 2011 07:30 CKone wrote:
unclock your cpu or make sure turbo mode is switched off, switching it off after i over clocked stoped all system instability for me. if i remember right turbo mode sends more power to one of the cores if it detects it needs it so mabye thats the power issue ur having because ur over clocked
also alot of people are ahving trouble with the MSI P67-GD65. so try unclocking everything and see if it still happens then what i would do is trial and error swapping 1 part at a time until it stops if it doesent stop prob your motherboard
 like i said with my old mainboard (which doesn't provide overclocking) Intel atax miniboard I still had a crash
I guess u didn't read my main post 
|
Your timings and speed appear to be reasonable. I highly doubt it is your cpu overclcok since it seems fairly mild, but let's not rule that out yet.
Try increasing your rams voltage a little. I recommend 1.575V, this is still within Intel's spec for sandy bridge. Let me know if that makes any difference.
|
665.2 Mhz is running at 1333, so don't worry about that. Its just how cpu-z reports ddr ram, you always have to double the amount displayed.
|
On March 28 2011 08:00 SeleCT wrote:Show nested quote +On March 28 2011 07:26 mav451 wrote:
Oh wow didn't realize you were overclocked. I'd set it back to stock to remove all variables here.
Can you post a link to your specific set of G.Skill RAM?
What concerns me is that most DDR3 kits are usually cas 7 and above, I don't think I've seen a cas 6 set before. And I would highly suggest putting in the timings manually, as my previous posts have touched on, make sure that command rate is set at 2T, not 1T. I overcloaked recently after I built with New motherboard because when i was using my old motherboard (intel atax miniboard) I was still crashing and this board is locked on overcloacking. It is not about overcloack. because it is 1333 i think.. :O? what ram timing would u recommand me?
Check your SPD tab in CPU-Z. I mean, the most common kits I've seen run at 7-7-7-21 for the cas7 kits, and usually it's 1.50v (maybe 1.525 if your board overvolts). I don't think 1.575 is necessary though, as that is hitting at the white paper limits for SB. I thinking loosening the timings to 7-7-7-21 will do the trick though.
Alot of 1.65v kits (Lynnfield era) run easily at 1.6 or even 1.55v, so I don't think it'll be a problem for your sticks to run +/- what is spec-ed in the SPD.
|
On March 28 2011 08:06 Speight wrote:
Your timings and speed appear to be reasonable. I highly doubt it is your cpu overclcok since it seems fairly mild, but let's not rule that out yet.
Try increasing your rams voltage a little. I recommend 1.575V, this is still within Intel's spec for sandy bridge. Let me know if that makes any difference.
Seems like a lot of jump at once. I would never suggest spiking a voltage that much in one go.
|
People have been running 1.65v ram at 1.65v through sandy bridge and asus have even stated that they have seen no issues with it. I considered this when I made my recommendation to him and as such I think 1.575v is a reasonable recommendation to make. He may be safe to run the ram at cas 6 since it is only clocking at 1333Mhz. If he was clocking it at 1600+MHz it would be a different story. I won't rule out the possibility that the cas 6 timing may be too aggressive but I'd like to see if his system becomes stable with the voltage increase.
|
occurred at 0023:5EE840C0. The memory at '0x5EE840C0' could not be executed.
god... just crashed again it was my first game today versus "favored" player there goes my -24 points
-_-
|
On March 28 2011 08:12 mav451 wrote:Show nested quote +On March 28 2011 08:00 SeleCT wrote:On March 28 2011 07:26 mav451 wrote:
Oh wow didn't realize you were overclocked. I'd set it back to stock to remove all variables here.
Can you post a link to your specific set of G.Skill RAM?
What concerns me is that most DDR3 kits are usually cas 7 and above, I don't think I've seen a cas 6 set before. And I would highly suggest putting in the timings manually, as my previous posts have touched on, make sure that command rate is set at 2T, not 1T. I overcloaked recently after I built with New motherboard because when i was using my old motherboard (intel atax miniboard) I was still crashing and this board is locked on overcloacking. It is not about overcloack. because it is 1333 i think.. :O? what ram timing would u recommand me? Check your SPD tab in CPU-Z. I mean, the most common kits I've seen run at 7-7-7-21 for the cas7 kits, and usually it's 1.50v (maybe 1.525 if your board overvolts). I don't think 1.575 is necessary though, as that is hitting at the white paper limits for SB. I thinking loosening the timings to 7-7-7-21 will do the trick though. Alot of 1.65v kits (Lynnfield era) run easily at 1.6 or even 1.55v, so I don't think it'll be a problem for your sticks to run +/- what is spec-ed in the SPD.
oh.. u are right
here is new post
![[image loading]](http://imgur.com/qtSQD.jpg)
![[image loading]](http://imgur.com/805On.jpg)
|
Ok loosen up the timings, let's be super conservative and set 9-9-9-24.
|
Also, play against the AI! You won't tank points if it crashes! Your mobo may have auto-clocked your ram too aggressively by default. That's why I thought it may not have been the timings straight away (you said it was default).
|
Yes.. it is default I haven't touched anything (since i never changed ram timing in my life )
I didn't even know where do i set my ram timing until by now
im going to try 9-9-9-24 now
BIOS right?
|
On March 28 2011 08:31 SeleCT wrote:oh.. u are right here is new post
Alrite, now that we know it's only rated for 9-9-9-24, go ahead and change that in your BIOS. I'd still manually set your Command Rate as well. Manually set your voltages as well.
|
Yep in the bios. I'm not familiar with your particular motherboard since I have been using asus boards for sandy bridge. But if you have a bit of a search in there it should be fairly obvious.
|
ok im on my laptop im gonna write what im seeing on my bios
command rate2 2 [auto]
tCL2 9 [auto]
tRCD 9 [auto]
tRP2 9 [auto]
tRAS2 25 [auto]
tRFC2 107 [auto]
tWR2 10 [auto]
tWTR2 6 [auto]
tRRD2 5 [auto]
tRTP2 6 [auto]
tFAW2 21 [auto]
tWCL2 7 [auto]
tCKE2 4 [auto]
tRTL2 36 [auto]
like i said i have no idea about it
could u help me what to change?
|
On March 28 2011 08:46 SeleCT wrote:ok im on my laptop im gonna write what im seeing on my bios command rate2 2 [auto]
tCL2 9 [auto]
tRCD 9 [auto]
tRP2 9 [auto]
tRAS2 24 [auto]tRFC2 107 [auto] tWR2 10 [auto] tWTR2 6 [auto] tRRD2 5 [auto] tRTP2 6 [auto] tFAW2 21 [auto] tWCL2 7 [auto] tCKE2 4 [auto] tRTL2 36 [auto] like i said i have no idea about it could u help me what to change?
Change what I've bolded, so that it's no longer on auto.
Yes make sure it's on Command Rate 2.
|
Nevermind i got it but what should i set my command rate to? its on 2 as auto
|
Ok manually set the following:
tCL: 9
tRCD: 9
tRP: 9
tRAS: 25
That is setting the ram to 9-9-9-25.
Once you have done that save the setting and reboot. Open cpu-z to verify the change has taken place. If it has, test in sc2.
|
I ran my CPU-Z and compared to before screenshot
and it hasn't changed anything lol the numbers are all same
|
Sorry my posts are a little slow. I'm doing this on my phone from work.
|
Are you comparing it to SPD info tab or memory info tab?
|
both of SPD and memory info tab haven't changed its same
I think my ram timing was 9-9-9-25 as auto before and now i manually set it to 9-9-9-24
I double checked my bios its on 9-9-9-24 manually
new screenshot
![[image loading]](http://imgur.com/npKgz.jpg)
old ones
|
The memory tab represents the "live" settings. The SPD is just the recommended settings from the manufacturer.
|
Hm if cpu-z is still reporting the same timing even though you have some different manually set something is overriding you for some reason. You don't have xms enabled or some sort of auto bios overclocking thing (sorry, not familiar with your mobo. I know asus calls it tpu) enabled do you?
|
the memory tab shows me 6-6-6-20 still........... what the
|
Check the memory tab and post that. SPD just reads manufacturer settings.
|
On March 28 2011 09:07 Speight wrote:
Hm if cpu-z is still reporting the same timing even though you have some different manually set something is overriding you for some reason. You don't have xms enabled or some sort of auto bios overclocking thing (sorry, not familiar with your mobo. I know asus calls it tpu) enabled do you?
no i don't see anything about that ...
|
|
|
there we go
my rams were on slot 3 , 4
i replaced them on slot 1 , 2
and now it shows 9-9-9-24 on memory tab now im going to try if i get crash
![[image loading]](http://imgur.com/uDA0g.jpg)
|
mine is 1333
do u think i should overcloack to 1600mhz?
btw whats the difference between 6-6-6-20 and 9-9-9-24 ?
|
generally to get the memory running in duak channel mode you need to put them in slots 2 and 4 (sometimes 1 and 3 or 1 and 2). Again I'm not totally familiar with your mobo, but the manual will detail it to you.
|
Don't try and O.C your ram any more until we are sure your current settings run sc2 stable. At best, overclocking your ram will give u 3 fps more. If you're just gonna be gaming stability is the key here. Let's aim for that first.
|
Indeed
so i replaced it to 1, 3 slot (blue colors) thank you for the helps
im going to try few games and see still crashing
|
its how long the ram takes to get ready to use by the mem controler and cpu, if its to fast ur cpu might not be ready for the info. start at a high timing 9-9-9-24 and then try 8-8-8-24 until ur system crash's then go back to the last setting, is waht i do anyway
|
No problem man, glad to be of assistance. Be sure to post once you've tried it out a bit! Then we can try to o.c. your ram the right way if you really want to.
|
oh... so 6-6-6-20 was highest setting? l o l i have no idea why auto setting forced it to 6-6-6-20
|
yea lower is faster, can you help me oc mine the right way?
|
On March 28 2011 09:20 SeleCT wrote:there we go my rams were on slot 3 , 4 i replaced them on slot 1 , 2 and now it shows 9-9-9-24 on memory tab now im going to try if i get crash
Excellent, looks like our work is done here.
As for OCing your RAM to 1600 speeds, I wouldn't really bother. RAM OCing on its own doesn't really provide tangible benefits. If you want tangible benefits, I'd go back to OCing your CPU, assuming the RAM troubles are over with :p
On March 28 2011 09:34 SeleCT wrote:
oh... so 6-6-6-20 was highest setting? l o l i have no idea why auto setting forced it to 6-6-6-20
With RAM, the lower the number, the tighter the timing (and hence more aggressive). These are latencies after all - higher number means it's slower, lower number means it's faster.
|
For ram timings, the lower the number the 'faster' it is. What is going on is when you set a lower timing is the ram is waiting less clocks to execute an instruction than it would otherwise do at a higher timing.
Is sc2 not crashing now?
|
I'd be glad to assist anyone o.c.ing although I'm no 1-stop-shop I can certainly try. Just shoot me a pm.
Also, to clarify what I meant by 'the right way' was to do it manually and methodically. Not letting something auto do it to the point of instability.
|
oh can i send you my cpu-z text file an you tell me if theres anything there i sohuldent of done? or if there are any serious bottle necks, i think i've done it right but am no expert
|
Sure man no problem.
Select: running ok?
|
woo.. i guess im sOOOOO unlucky
never have succeed overcloaking my sandy 2600k can't even run for 4.2 G
i like how it passed 20 hours of prime tho.. -_- and failed running sc2 for 1.5 hour
|
|
|
Are you still running the RAM voltage at 1.5? If so, try turning it up to about 1.6V. A lot of RAM (particularly if it's good quality dual-channel) is much more stable at a slightly higher voltage.
For the timings you're probably best off looking up the recommended defaults for your RAM and using them. While you're doing that, see whether you can find the recommended voltage for your RAM as well. Some manufacturers will suggest a higher voltage than the default provided by your MB.
|
no crash so far looking good
|
3 suggestions come to mind based on those I have helped with similar issues (including the 0xc..5).
First: Windows Updates, including custom.
Many times microsoft will surprise us and fix problems they have previously stated as being not their responsibility to fix. This leads to developers to hotfix the issue which can then have adverse effects when on the whim of Bill they decide to instead fix said issue. It is an obnoxious dance you may be stuck in the middle of. After this I would still make sure nothing funky is going on with windows. I instinctually blame windows, so I would also check sfc (system file checker) if you think there is any chance there could be something funky from windows.
Second: Hard Drive, current state.
Start by checking the SMART, (for those unfamiliar http://en.wikipedia.org/wiki/Comparison_of_S.M.A.R.T._tools ) your model of HDD seems to have a higher than normal return rate. If that is looking solid, I would run chkdsk.
Third: Computer Management (Manage from right click my computer)
Watch event viewer listing and performance when things are going amiss. These can give you clues as to related issues.
|
Yeah seems really odd that it would pass memtest and prime but fail at starcraft, I may be wrong but I think the latest patch has something to do with it. Seems a lot of people with flaky memory/settings are having problems.
Good to hear it's gone without a crash so far. Keep updating!
Edit: How often do you guys get threads where people are trying to give advice after the problem is already (potentially) solved?
|
select fighting
|
ok just crashed guess it wasn't about ram timing -_-
im mad now
|
Well it went longer without a crash this time than last, which, given the error, still leads me to believe its the ram. Still running at 1.575V? Have you got any other ddr3 ram around you could try out?
|
i told ya TT
I have 2 of 4GB
I tried using only 1 and crashed
tried the other one and crashed
so do u think two of them are broken? no i don't have any other ram to try
It was running as 1.488V when i checked on BIOS
which is 1.5 i think
|
On March 28 2011 11:49 tzagear wrote:3 suggestions come to mind based on those I have helped with similar issues (including the 0xc..5). First: Windows Updates, including custom. Many times microsoft will surprise us and fix problems they have previously stated as being not their responsibility to fix. This leads to developers to hotfix the issue which can then have adverse effects when on the whim of Bill they decide to instead fix said issue. It is an obnoxious dance you may be stuck in the middle of. After this I would still make sure nothing funky is going on with windows. I instinctually blame windows, so I would also check sfc (system file checker) if you think there is any chance there could be something funky from windows. Second: Hard Drive, current state. Start by checking the SMART, (for those unfamiliar http://en.wikipedia.org/wiki/Comparison_of_S.M.A.R.T._tools ) your model of HDD seems to have a higher than normal return rate. If that is looking solid, I would run chkdsk. Third: Computer Management (Manage from right click my computer) Watch event viewer listing and performance when things are going amiss. These can give you clues as to related issues.
I don't understand at all what u r saying
Im not too good with computer just only basics
after i saw the link i was so confused
|
Regarding SMART data, run CrystalDiskInfo. I mentioned this in my earlier posts - this is just to rule out the hard drive.
http://crystalmark.info/software/CrystalDiskInfo/index-e.html
See if you have anything under the Raw Values column for
05 - Reallocated Sectors
07 - Seek Error Rate
and C4 through C8.
I'm pretty sure you won't find anything, but this is just to rule it out.
On March 28 2011 13:20 SeleCT wrote:
i told ya TT
I have 2 of 4GB
I tried using only 1 and crashed
tried the other one and crashed
so do u think two of them are broken? no i don't have any other ram to try
It was running as 1.488V when i checked on BIOS
which is 1.5 i think
Thought I'd reword this. Considering you've been crashing with both sticks in, and each stick individually, I am hesistant to still point to the RAM. Normally this would have me thinking you need to bump vNB or VTT (called system agent voltage on MSI boards), but I dunno how important that is on the p67. The other thing is we have already considerably relaxed the timings from cas 6 to cas 9. I suppose we could still try 1.55vDIMM, but it seems somewhat moot considering the relaxed timings.
Are you still overclocking your CPU currently?
|
On March 28 2011 13:20 SeleCT wrote:
i told ya TT
I have 2 of 4GB
I tried using only 1 and crashed
tried the other one and crashed
so do u think two of them are broken? no i don't have any other ram to try
It was running as 1.488V when i checked on BIOS
which is 1.5 i think
As mentioned, you should go into the BIOS and try turning the RAM voltage up a bit.
|
On March 28 2011 13:29 mav451 wrote:Regarding SMART data, run CrystalDiskInfo. I mentioned this in my earlier posts - this is just to rule out the hard drive. http://crystalmark.info/software/CrystalDiskInfo/index-e.htmlSee if you have anything under the Raw Values column for 05 - Reallocated Sectors 07 - Seek Error Rate and C4 through C8. I'm pretty sure you won't find anything, but this is just to rule it out. Show nested quote +On March 28 2011 13:20 SeleCT wrote:
i told ya TT
I have 2 of 4GB
I tried using only 1 and crashed
tried the other one and crashed
so do u think two of them are broken? no i don't have any other ram to try
It was running as 1.488V when i checked on BIOS
which is 1.5 i think Thought I'd reword this. Considering you've been crashing with both sticks in, and each stick individually, I am hesistant to still point to the RAM. Normally this would have me thinking you need to bump vNB or VTT (called system agent voltage on MSI boards), but I dunno how important that is on the p67. The other thing is we have already considerably relaxed the timings from cas 6 to cas 9. I suppose we could still try 1.55vDIMM, but it seems somewhat moot considering the relaxed timings. Are you still overclocking your CPU currently?
I don't think its board problem either u know i had a crash with my old board too (intel atax miniboard)
|
ok i just increased voltage to 1.550 lets see what happen..
|
i've been getting the exact same problem.
if i play 5 games one of them would be like a fatal error .
im pretty sure this is something with the patch =/
i've tried just about everything to make sure nothing is wrong on my end (hardware wise)
edit :
it's just extremely weird that this is only happening to some people and some are not having any problems;
i don't mean to sound so negative but judging by the fact that other people are also having this same problem, i don't think doing anything on your end will change anything.
|
ok.. I thought my laptop is fine but i just got crashed playing on my laptop ( first time)
holy shit....
EDIT : and crashed again right after the first crash. now im crashing everygame with laptop too
How do i practise for mlg.. rofl
|
Hey select, it might be your recently installed program or windows update.
Try to system restore it to like 2 months back or as far back as it will let you. Don't install any windows update or any programs after restoring the system - just starcraft 2. Then play like you normally do. If everything works, its probably a program that's causing the problem.
To system restore on windows 7: Right click on My Computer->Properties->System Protection->System Restore
Hope this helps.
Edit: I also just build my sandy ridge 2500k with Asus p67 board though. No starcraft 2 crash for me. I haven't updated my service park though. Or rather, it won't let me update it, lol.
Edit2: Make sure to backup your files!
|
come to think of it ive had some problems on my pc since windows 7 service pack 1, mostly with firefox not sc2 but as this was pretty recent mabye that is what is causing problems on some peoples systems. just a thought
|
Control Panel\All Control Panel Items\Windows Update\View update history go here and see if an update occured roughly when it started crashing. if so click "installed updates" and uninstall that update
|
If this works for you, I want 90% of your prize money for major tournaments for a year.
|
i don't think it is related to windows update ... or maybe
|
Just system restore. It should work. it will return your computer to when it was working.
It's unlikely that it will kill your hard drive, but in case just save some really really really extremely important thing on a flash drive or email to yourself. then do it.
|
there was no time it was working all i did was format reinstall window 7 and install sc2 and play
the bad thing about window 7 is that I set it to "never update windows"
i turn off my computer and it was updating automatically when i click "shut down" button.
I really don't like window 7
|
From the other reports I'm hearing described it could just be a problem with the latest patch on sc2. Increase the ram voltage slightly to ensure a little more stability (ram wise) but I do not recommend going over 1.575v (as does Intel) however there have been reports from a large number of people running a higher voltage and not having a problem.
Other than that I don't think the problem is on your end and you may have to wait for Blizzard or Microsoft to make a fix.
|
Select, I have the same problems. I have posted about it numerous times on SC2 Tech Support forums and they have been of no help so far. Will post back here if I find a solution.
I highly doubt that thousands of people's hardware is the problem all of a sudden after this patch, I believe Blizzard have broken something and this is all a fault on their end they must fix.
|
yea if its happening on your laptop and desktop then has to be software really, and if its only sc2 thats doin it prob sc2 thats the problem
|
If its like windows xp killing the automatic updates service should do the trick.
Before you can do anything else worthwhile you need to make sure is not ram so either take it to a friend's house and try them on his pc or buy a new pair of sticks and return them
Even after trying the sticks individually there's nothing else pointing to any other kind of problem in your system. The last pair of Gskill sticks that I bought one was busted. Changed them and the new ones also had one busted so getting a double is not that strange. Ended up putting the one that was working and a single Kingston and now its working fine.
Once you are 100% that the ram is working fine you can pretty much assume that either your RAM doesn't like your motherboard (not that rare either) or that your motherboard is the problem.
|
I've been hearing some word on people having crashes. I hope this can be fixed so you can practice.
Select fighting!
|
On March 28 2011 16:59 weaknurse wrote:
Select, I have the same problems. I have posted about it numerous times on SC2 Tech Support forums and they have been of no help so far. Will post back here if I find a solution.
I highly doubt that thousands of people's hardware is the problem all of a sudden after this patch, I believe Blizzard have broken something and this is all a fault on their end they must fix.
I know.. but i have had the crash even before the patch ^^ but not this much
|
On March 28 2011 17:34 SeleCT wrote:Show nested quote +On March 28 2011 16:59 weaknurse wrote:
Select, I have the same problems. I have posted about it numerous times on SC2 Tech Support forums and they have been of no help so far. Will post back here if I find a solution.
I highly doubt that thousands of people's hardware is the problem all of a sudden after this patch, I believe Blizzard have broken something and this is all a fault on their end they must fix. I know.. but i have had the crash even before the patch ^^ but not this much
Hmm ok, interesting. I also had this crash, but only once in about (200 games worth of playing) prior to the patch. Hope Blizzard can find a solution.
|
contact blizzard: 1-800-592-5499
Tell them your problem. Then add, I'm Select - MLG coming up yo.
Or better yet, don't you have David Kim's email?
|
Sell ur current setup and buy a new pc ... good luck tho.
|
Are there any other games or other programs which put a similar load on your computer that also cause it to crash? Was there anything at all which changed when the laptop started crashing? How recently before that had you played successfully on it? And has there been any improvement in your desktop with the changes you've tried?
|
just stop overclocking and put it back on normal settings, remove every unneeded peripherals, use high timing on ram (start with 1 stick) and reinstall windows with this configuration
test just using SC
if it works, try to put things one by one continuing testing
|
I think us fixing your memory timings have solved the problems you were having post-patch.
Given that the new patch has added instability and after the testing we have done today and the problems others have been having, I'd say the problem is now on Blizzard's end.
|
On March 28 2011 17:37 Neosta2 wrote:
contact blizzard: 1-800-592-5499
Tell them your problem. Then add, I'm Select - MLG coming up yo.
Or better yet, don't you have David Kim's email?
he is on balance team not technical problem..
|
On March 28 2011 17:41 water-hand wrote:
just stop overclocking and put it back on normal settings, remove every unneeded peripherals, use high timing on ram (start with 1 stick) and reinstall windows with this configuration
test just using SC
if it works, try to put things one by one continuing testing
already tried everything u mentioned if u see my original post
|
On March 28 2011 18:03 Speight wrote:
I think us fixing your memory timings have solved the problems you were having post-patch.
Given that the new patch has added instability and after the testing we have done today and the problems others have been having, I'd say the problem is now on Blizzard's end.
I think so too
I wonder when they are going to fix this sigh..
|
On March 28 2011 18:27 SeleCT wrote:
[cut]
already tried everything u mentioned if u see my original post
even the OC settings? u don't talk at all about it, and that's what probably affect you
without thinking about giving overvoltage may broke the hardware, that's could be the answer of "no crash" at beginning
|
On March 28 2011 19:07 water-hand wrote:Show nested quote +On March 28 2011 18:27 SeleCT wrote:
[cut]
already tried everything u mentioned if u see my original post even the OC settings? u don't talk at all about it, and that's what probably affect you without thinking about giving overvoltage may broke the hardware, that's could be the answer of "no crash" at beginning
its happening on his laptop and desktop only on sc2 and other people are saying its happening to them so must be software not hardware
|
On March 28 2011 19:16 CKone wrote:Show nested quote +On March 28 2011 19:07 water-hand wrote:On March 28 2011 18:27 SeleCT wrote:
[cut]
already tried everything u mentioned if u see my original post even the OC settings? u don't talk at all about it, and that's what probably affect you without thinking about giving overvoltage may broke the hardware, that's could be the answer of "no crash" at beginning its happening on his laptop and desktop only on sc2 and other people are saying its happening to them so must be software not hardware
Yep, as annoying as it is all we can really do is wait until Blizzard get the problem sorted.
|
On March 28 2011 19:07 water-hand wrote:Show nested quote +On March 28 2011 18:27 SeleCT wrote:
[cut]
already tried everything u mentioned if u see my original post even the OC settings? u don't talk at all about it, and that's what probably affect you without thinking about giving overvoltage may broke the hardware, that's could be the answer of "no crash" at beginning
"I overcloaked recently after I built with New motherboard because when i was using my old motherboard (intel atax miniboard) It was still crashing and this board is locked on overcloacking. It is not about overcloack."
|
|
|
I have the same problem with the crashing. It is Blizzards job to fix it.
|
well i already tried those basic things such as installing driver reinstalling win7 formating repair too etc.
|
also getting this problem.
I've used memtest as well and also tried isolating my RAM but no luck..
memtest showed up with no problems so i'm pretty sure this is something on Blizzard's end.
It's so frustrating how they seem to just ignore this problem..
|
I posted this on another thread about these crashes but I thought I'd post it here to just spread the word
"people have theories on the BNET forums
theyre saying it only happens to Terran and it has to do with how your units make the unit sounds every single time u switch control groups now. So spamming your control groups as Terran seems to be the cause :O! Makes a lot of sense to me now. really hope Blizzard fixes this soon."
|
As far as I can tell its definitely a problem with SC2 since 1.3
If you play Terran and have high APM, the game tends to crash.
So keeping you APM down... or your Terran^^ helps
|
funny MVP just got sc2 crash on GSL match versus dimaga
|
On March 29 2011 19:05 seAman wrote:
I posted this on another thread about these crashes but I thought I'd post it here to just spread the word
"people have theories on the BNET forums
theyre saying it only happens to Terran and it has to do with how your units make the unit sounds every single time u switch control groups now. So spamming your control groups as Terran seems to be the cause :O! Makes a lot of sense to me now. really hope Blizzard fixes this soon."
not sure about this because i have tried to play with no sound (turned off all sound on option) but still crashed.
|
I don't know why they change unnecessary thing when they patch.
1.28 -- > 1.29 terran building complete sound has disappeared ( they haven't fixed)
1.29 -- > 1.30 u know... the spamming sounds -.-... lol
|
On March 29 2011 21:40 SeleCT wrote:
I don't know why they change unnecessary thing when they patch.
1.28 -- > 1.29 terran building complete sound has disappeared ( they haven't fixed)
1.29 -- > 1.30 u know... the spamming sounds -.-... lol
The spamming sounds are so infuriating. Holy Shit did I rage it.
|
|
|
finally got a blue post on my thread.
source : http://us.battle.net/sc2/en/forum/topic/2301721994?page=3#50
This is an issue we've been tracking, and we've isolated it to changes in the portraits during selection sound changes. It seems to be isolated to portraits with lip sync, so primarily Terrans.
This issue occurs for players using 3D portraits. The temporary workaround if you are experiencing this issue is to turn off 3D portraits and to use 2D portraits for the time being.
________________________________________________
lol . i guess try this out and see.
still kind of skeptical because obviously not everyone that plays terran with 3d portrait is getting this error to my knowledge.
|
gj namkung and your revolutionary thread <3
btw this is Jay's friend LOL
|
I think the terran-theory is off, today alone my PC has crashed 5 times during games, and I'm a protoss :p
|
I would do a memtest and a FurMark test for the memory and the graphics card stability. Run the memtest for 8 rounds and FurMark for 6-8 hours.
Edit: this does not apply.
|
I hope you're gonna be okay for MLG SeleCT! Wasn't there anybody you could go and practice with before the weekend?
|
I had it again today.... yesterday everything worked and today.... crash..
|
+ Show Spoiler +On March 30 2011 08:31 Namkung wrote:finally got a blue post on my thread. source : http://us.battle.net/sc2/en/forum/topic/2301721994?page=3#50This is an issue we've been tracking, and we've isolated it to changes in the portraits during selection sound changes. It seems to be isolated to portraits with lip sync, so primarily Terrans. This issue occurs for players using 3D portraits. The temporary workaround if you are experiencing this issue is to turn off 3D portraits and to use 2D portraits for the time being. ________________________________________________ lol . i guess try this out and see. still kind of skeptical because obviously not everyone that plays terran with 3d portrait is getting this error to my knowledge.
Seems accurate. I found this on the Battle.net forums:
http://us.battle.net/sc2/en/forum/topic/2325032618
|
On March 30 2011 08:31 Namkung wrote:finally got a blue post on my thread. source : http://us.battle.net/sc2/en/forum/topic/2301721994?page=3#50This is an issue we've been tracking, and we've isolated it to changes in the portraits during selection sound changes. It seems to be isolated to portraits with lip sync, so primarily Terrans. This issue occurs for players using 3D portraits. The temporary workaround if you are experiencing this issue is to turn off 3D portraits and to use 2D portraits for the time being. ________________________________________________ lol . i guess try this out and see. still kind of skeptical because obviously not everyone that plays terran with 3d portrait is getting this error to my knowledge.
Wow this is one situation where my low APM helped me out, thanks crappy mechanics!
Hopefully this fixes the issue for Select.
|
It's not your computer. I am having the exact same issue that Select is. There are a lot of other people that are having the exact same problem.
Up from beta to 1.2-1.3 I don't think I had a single crash. Then these patches hit and the game stability goes from flawless to complete garbage.
My computer is completely stable and its temps are low and no crashes at all in everything else I do. This includes Prime 95, Crysis, Dead Space 2, Fallout 3, Civilization 5, Mass Effect. This pretty much proves the problem is isolated to Starcraft 2.
I wish Blizzard would acknowledge they have a problem with stability right now. Because Blizzard has the tendency to just blame all the crashes on the user when really right now they have a serious software problem. They have already acknowledged that 3d portraits particularly with terran causes crashes with high apm, so at least they are trying to figure this out. Unfortunately I feel they have just barely scratched the surface of this issue as I have disabled 3d portraits and am still crashing.
|
|
|
|
|
|
EPT
