PC restarting during CCE progress

[Kool3ds]

hey guys i m facing a lil problem here

whenever i try to run the CCE progress whenever it reaches around 30-50% my PC just restarts does anyone has any idea of wats going on?

[therat]

Is your computer overclocked at all? CCE is well known for totally stressing a computer so if any component is faulty or starting to fail then CCE will hasten it.
Try setting your computer to default speeds and if it still happens then I suggest you test the various components, especially RAM.

Try downloading memtest and running it to make sure you don't have bad RAM.

cheers

[Kool3ds]

Is your computer overclocked at all? CCE is well known for totally stressing a computer so if any component is faulty or starting to fail then CCE will hasten it.
Try setting your computer to default speeds and if it still happens then I suggest you test the various components, especially RAM.

Try downloading memtest and running it to make sure you don't have bad RAM.

cheers

no my PC is not overclocked.

while running the memtest i got this one error.

http://i13.tinypic.com/4mma1ih.jpg

got any idea how to fix this thing up?

[wmansir]

First , use memtest86 or memtest86+. They are bootable tests that remove a lot of other possible errors causes from the equation.

Assuming you are out of warranty, here's what I would do:

1. Swap your mem modules around in the MB's memory slots. mods and slots can be picky and this is a free and easy potential fix. Check your MB manual to see if you need to use certain slots.

While your in there check for heat issues. Dead fans, dust buildup on the modules or in fans/heatsinks , etc It's probably a good time to blow out that dust anyway.

2. Reduce your memory timings. This is entirely dependent on your MB and it's BIOS. Some will have advanced timing options, some will have none. At the very least you should be able to change it from "Turbo" or something to standard, etc.

Alternatively you can increase your memory voltage if that is an option. Although I would read up on overclocking before attempting this.

I would first drop the timings fairly low and then test for stability. From there treat it as if you are overclocking, there are lots of guides explaining how to do that. It's basic trial and error.

A relatively small error like this could be fixed with a small timing adjustment that doesn't hurt performance too much.

3. Buy new memory. Memory prices are pretty good right now and you can probably upgrade while you are at it. In a situation like this I like to buy local if possible because it may turn out not to be the memory at all and returns are easier if that's the case. Unless you hit a sale though most local retailers overcharge for memory.

If you have more than one module of memory than you can test them individually (by removing the others) with memtest86 to see which one is bad. Since it's bootable you don't have to worry about not having enough memory for Windows to run properly.



No matter how you do it, don't consider it fixed until memtest86 can run for several hours without a single error. The bare minimum is one full pass of all tests. As a final check I would let it run over night.

[Blue_MiSfit]

Good post. Memory quality has gone up a lot even in the value sector since the old days, but I still run into stuff like this on my customers' machines.

You definitely need to be able to run memtest86+ for several hours before you can have confidence in your RAM.

Good luck.

~MiSfit

[Kool3ds]

First , use memtest86 or memtest86+. They are bootable tests that remove a lot of other possible errors causes from the equation.

Assuming you are out of warranty, here's what I would do:

1. Swap your mem modules around in the MB's memory slots. mods and slots can be picky and this is a free and easy potential fix. Check your MB manual to see if you need to use certain slots.

While your in there check for heat issues. Dead fans, dust buildup on the modules or in fans/heatsinks , etc It's probably a good time to blow out that dust anyway.

2. Reduce your memory timings. This is entirely dependent on your MB and it's BIOS. Some will have advanced timing options, some will have none. At the very least you should be able to change it from "Turbo" or something to standard, etc.

Alternatively you can increase your memory voltage if that is an option. Although I would read up on overclocking before attempting this.

I would first drop the timings fairly low and then test for stability. From there treat it as if you are overclocking, there are lots of guides explaining how to do that. It's basic trial and error.

A relatively small error like this could be fixed with a small timing adjustment that doesn't hurt performance too much.

3. Buy new memory. Memory prices are pretty good right now and you can probably upgrade while you are at it. In a situation like this I like to buy local if possible because it may turn out not to be the memory at all and returns are easier if that's the case. Unless you hit a sale though most local retailers overcharge for memory.

If you have more than one module of memory than you can test them individually (by removing the others) with memtest86 to see which one is bad. Since it's bootable you don't have to worry about not having enough memory for Windows to run properly.



No matter how you do it, don't consider it fixed until memtest86 can run for several hours without a single error. The bare minimum is one full pass of all tests. As a final check I would let it run over night.

thx a lot bro. Switching the slot and running memtest86 fixed the problem. :thanks::thanks::thanks:

[foxyshadis]

If exchanging the chips "fixed" it, pull the first chip out and rerun memtest with only the second chip in its second slot. The chip might still be bad and just not getting tested as hard.

If you switched the second from a dual channel to a second single channel, though, it's probably fine and just not compatible enough timings for dual.