|
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. ![[image loading]](http://imgur.com/ftuwc.jpg) 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. ![[image loading]](http://imgur.com/ftuwc.jpg) 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)
|
|
|
|