Windows = Borked

Everything was reset in bios, the only mod was to disable Intel gfx.

Left it running the full test while I went out. It's succeeded on 3 passes so far. Seems to only be when I tell it to run test 11 alone that it fails.

Pretty confusing. I'll open a ticket with corsair and see what they have to say
 
Test 11 [Random number sequence, 64-bit]

This test is the same as Test 8, but native 64-bit instructions are used.

So only 1 stick errors or both?
Stock cooler?
 
It's a bit fade test. W/e that means. Both sticks, every slot, paired or solo.

I've fired a question off to Corsair Support. Such odd results I think it's memtest. There was precendence for this with v4.x but they apparently fixed it in the next release.
 
I got new sticks from Corsair, with interesting results.

Firstly they defaulted to 2400MHz in the BIOS, without XMP enabled. Previously they defaulted to 1333MHz.

Unfortunately that's where the good news ends. Memtest still fails at 37% on test 11 with both sticks. I didn't bother testing all slots.

Gonna look for an RMA on the mobo now, although it could be the processor?

Considering I bought the mobo in Oct last year, what are the chances the retailer will handle it? I've had a ticket open with gigabyte for over almost 2 weeks now without any response beyond "we are looking into it".
I don't really fancy paying for all my shipping costs anyway.
 
I went ahead and bought an asus mobo while I wait for the RMA.

This is even worse. With stock BIOS, a run in OCCT just hard reset the system after 10mins.

This is eithr CPU or PSU now. Could this actually be PSU?
If it's the CPU I'm screwed - the original retailer redirects me to Intel, and Intel aren't interested in the slightest.
 
Sorry to hear you are still having trouble with this :(

OCCT shuts down the pc at stock settings? or when chasing 4.6GHz?

Intel / Retailer probably wont be interested in having the CPU back if it works fine @ stock, as that's all you are guaranteed...

You sure you didn't just loose the silicon lottery hard?
 
At stock i.e. 4 with 4.4 turbo.

I think it was a bios setting with regards to voltage protection. Something the giga didn't have a switch for which explains all the hard resets. Since turning it off I've only blue screened.

But yep I've lost the lottery hard. I'm messing with bclk now. Ftt test in prime has been running for 3 hours so far at 4.625 with 125 base. Not happy with temps and volts - 80 max but hovering close. However, it's the most stable I've had this and I'm feeling slightly less irritated!

As for the thread title - this wasn't a Windows issue after all!
 
You shouldn't accept it not doing what it should do at stock... it should work fine with everything on auto.

I know I've gone on about it lots, and I'm probably annoying you, but your defiantly not testing it on OCCT with the RAM running at 2400MHz? Because that will give you a high chance of an unstable system with everything on auto... The CPU cant run ram that fast without bumping some other voltages most of the time...
 
Unfortunately I've already told intel that i was trying to overclock and wasn't getting anywhere. I assume they will take no interest now if I show them it failing at stock.

I was testing with 2400 for a while, dialled that back to 1333 and still failed. It's currently on 1750.

Any chance you could me a favour and run test 11 on memtest? It still fails with new ram and mobo so it's either the cpu or memtest itself.
 
Tried it on my work machine and I get the same memtest errors. I think that points to the software...
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom