768k Skylake Problem/Bug

[pegnose]

Originally Posted by LaurV

Why the bigger time commitment? Add another SSD with the same size, configure it as RAID1, run for a while or use sync software provided by the bios or by the os, take the old one out.

Nice! :)

[s1riker]

Originally Posted by LaurV

Why the bigger time commitment? Add another SSD with the same size, configure it as RAID1, run for a while or use sync software provided by the bios or by the os, take the old one out.

Sure, if money were no issue :) .. between buying another Samsung 850 Pro 512GB and another Z170 motherboard to try out, and the tanking CAD dollar, this build is going to end up costing me well over $2.5k

[pegnose]

Looks like I am through with upping voltages. Now I am at disabling onboard devices. HD Audio, USB 3.1, Thunderbold, ASMedia Sata are all off. We'll see.

My final shot before RMAing major components would be a fresh OS on a drive I haven't used in that system, yet.

In any way, it might be that my previous RAM issues had nothing todo with my system being unstable on load. I don't even know whether they manifested in the OS at all. I am beginning to believe that I have (had) two issues, one of which is not RAM and is responsible for the hard locks. Because my machine finally survived whole days of memtesting, but the issues in Win10 are as present as ever.

[s1riker]

Originally Posted by pegnose

Looks like I am through with upping voltages. Now I am at disabling onboard devices. HD Audio, USB 3.1, Thunderbold, ASMedia Sata are all off. We'll see.

My final shot before RMAing major components would be a fresh OS on a drive I haven't used in that system, yet.

In any way, it might be that my previous RAM issues had nothing todo with my system being unstable on load. I don't even know whether they manifested in the OS at all. I am beginning to believe that I have (had) two issues, one of which is not RAM and is responsible for the hard locks. Because my machine finally survived whole days of memtesting, but the issues in Win10 are as present as ever.

Yeah I'm done with touching voltages as well, it doesn't make sense to touch them anyway, because they are all handled, or should be handled dynamically.

Before I go ahead and try a different drive, I've disabled Intel LPM in the Rapid Storage Management console. Since that affects idle operation, it's worth a shot. I assume you've already tried that?

The other thing I've done is setup HWInfo to log everything it can every second, and write it to a file, in the hopes that I can take a look at the log info the next time it happens and see if anything looks weird, ie. sudden drop of voltage, jump in temp, etc.

[chalsall]

Originally Posted by pegnose

... but the issues in Win10 are as present as ever.

Have you considered that the OS might be the issue? It's not like Micro$oft has never had bugs....

[s1riker]

Originally Posted by chalsall

Have you considered that the OS might be the issue? It's not like Micro$oft has never had bugs....

People are saying the same thing happens in Windows 7 and linux, but who knows if it's the exact same problem pegnose and I are having. A lot of people in the Tom's forum think they have the same problem, but in many cases it's your standard run of the mill BSOD, crash under load or something entirely different. But you're right, it's definitely something to consider.

[pegnose]

Originally Posted by s1riker

People are saying the same thing happens in Windows 7 and linux, but who knows if it's the exact same problem pegnose and I are having. A lot of people in the Tom's forum think they have the same problem, but in many cases it's your standard run of the mill BSOD, crash under load or something entirely different. But you're right, it's definitely something to consider.

Well, I had this before upgrading from Win7 to Win10. But as I said: "My final shot before RMAing major components would be a fresh OS on a drive I haven't used in that system, yet."

[pegnose]

Originally Posted by s1riker

Yeah I'm done with touching voltages as well, it doesn't make sense to touch them anyway, because they are all handled, or should be handled dynamically.

Before I go ahead and try a different drive, I've disabled Intel LPM in the Rapid Storage Management console. Since that affects idle operation, it's worth a shot. I assume you've already tried that?

I didn't have it installed until very recently. And LPM is still disabled, I think. Plus it is not enabled in the bios (although that options says "Aggressive Link Power Management").

Originally Posted by s1riker

The other thing I've done is setup HWInfo to log everything it can every second, and write it to a file, in the hopes that I can take a look at the log info the next time it happens and see if anything looks weird, ie. sudden drop of voltage, jump in temp, etc.

Yeah, I am doing that too. But I have never seen anything interesting in that. Tell us if you do.

[pegnose]

I will go play some Fallout 4 now. See you after the next crash. ;)

[chalsall]

Originally Posted by pegnose

Well, I had this before upgrading from Win7 to Win10. But as I said: "My final shot before RMAing major components would be a fresh OS on a drive I haven't used in that system, yet."

If I may give some advise, based on decades of experience (I'm an old guy)...

The issue /may/ be in the current Windows codebase, but it /might/ also be the drivers supplied for and by third party hardware suppliers (even if "Certified" by M$), including the drivers for the MB.

One suggestion would be, if you're going to try a "Fresh OS", to try to install as little additional hardware (and thus, drivers) as possible, and see how that goes.

Another suggestion would be to fall back to an OS before Win7 (if that is even possible), and see how things go. This last suggestion is a shot in the dark; I haven't used any Micro$oft software for more than twenty years, but it might be worth trying if possible.

[pegnose]

Originally Posted by chalsall

If I may give some advise, based on decades of experience (I'm an old guy)...

The issue /may/ be in the current Windows codebase, but it /might/ also be the drivers supplied for and by third party hardware suppliers (even if "Certified" by M$), including the drivers for the MB.

One suggestion would be, if you're going to try a "Fresh OS", to try to install as little additional hardware (and thus, drivers) as possible, and see how that goes.

That is definitely a very good advice!

Originally Posted by chalsall

Another suggestion would be to fall back to an OS before Win7 (if that is even possible), and see how things go. This last suggestion is a shot in the dark; I haven't used any Micro$oft software for more than twenty years, but it might be worth trying if possible.

I doubt that Skylake would run very well under XP.