Official GIGABYTE Forum

Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Peter_K on September 15, 2011, 04:48:38 pm

Title: p55-ud4 + kingstone hyperX 1600 = crash in stress (why?)
Post by: Peter_K on September 15, 2011, 04:48:38 pm

As in topic:

I have this MoBo and just yesterday i bought 16 gb of ram from kingstone (4x 4gb KHX1600C9D3X2K2/8GX).

On auto settings in bios ram is set to 1333 (standard spd from kingstone) and it works fine, but when i change it to xmp profile1 ( and change ram to 1600 mode) and put my rig in some stress work (like video render) after 1-3 min there is crash.

And by crash i dont mean BSOD but pc jsut turn off itself (like in overheating?).

At first i thought maybe it's ram fault so i run some memtest+ 4.20 and as for now there are 0 errors.

Any more suggestions?

BTW im using newest bios (f9)

Title: Re: p55-ud4 + kingstone hyperX 1600 = crash in stress (why?)
Post by: Dark Mantis on September 15, 2011, 07:38:05 pm

Hi

There are a couple of possible reasons why this could happen. You say you ran Memtest86+  but did you do it thoroughly. One module at a time and for ten full cycles/loops each ?

The other thing is that it is possible that there might be some bent pins on the CPU socket. I would do the full Memtest first though as it is easier than pulling the CPU to check.

Title: Re: p55-ud4 + kingstone hyperX 1600 = crash in stress (why?)
Post by: Peter_K on September 15, 2011, 08:58:08 pm

Well so...

I managed to solve the problem but i dunno how...

I changed the CPU cooling to Scythe Katana3 (i bought it with ram 'cause my old box cooling was laud and not doing well), and doing so i also rearranged the some of the ram on the MoBo again... so one of those 2 things and now everything is working ok... weird but well...

Title: Re: p55-ud4 + kingstone hyperX 1600 = crash in stress (why?)
Post by: Dark Mantis on September 16, 2011, 02:19:05 pm

As long as everything is working alright now then I guess it doesn't matter but if or when it happens again just post back here and we can try and sort it out.