*** Official Clevo P870DM2/P870DM3 (Sager NP9873/NP9872) Owner's Lounge! - The Phoenix 2 is here! **

don't have a USB keyboard and never will use one

if it was just me, we could say it's my system but I've seen more than 6 people so far with this issue including Tbonesan

 

I have no doubt it is real... Totally believe it is. Just curious if it happens on USB as well. Maybe @TBoneSan can check and let us know.

I thought initially it might be a bug with CCC, but I installed the newest CCC beta and still do not have the issue.

 

if it happens on a USB keyboard, then it is a Windows 10 issue in the latest build 14393

 

That is exactly what I am wondering. I am dual booting W7 and W10 Enterprise 2016 LTSB. Maybe that is why I do not have the issue. As you already know, I seldom install Windows Updates.

 

also, you are running with CSM enabled if I am not mistaken

 

Yeah, absolutely. I have to use Legacy video for Windows 7, plus I like Legacy better anyway.

 

I'm using dual Windows 10 Pro installations (stock BIOS 'til Thursday) through UEFI.... One for work/gaming, one for benching. I don't have the issue

 

This kind of thing could be a lot of trouble to diagnose. It could be a totally unrelated driver (of a version with a glitch that perhaps only some people are using) that is taking too long to load and interfering with the keyboard driver loading. Or, it could be a buggy Windows Update... lots of things could cause it, which might be an explanation why not everyone encounters the issue.

 

I do sometimes get my keyboard not responding for a bit early on. Bash a few keys and it starts responding. It's something in the Prema EC'/Bios as it does not happen at stock.

It only does it once and not for very long though.

 

EC2 controls keyboard strokes, which is plain stock also on the Mod.
EC1 only controls backlight as far as the keyboard is concerned.

 

Do you know if the U/J ghosting issue is a wiring problem or an EC problem?

 

Speculation, To me it feels like W10 is attempting to inject a keylogger or Telemetry and gives the instruction 150% system priority since they're filthy gold diggers.
This wasn't always a problem. Is it folks just using W10 having this problem?
I'll try my USB keyboard as soon as I get the chance.

 

It was a bug in the first EC2 MP version and was fixed in the first update.

 

My OS knowledge is a bit rusty but I'm pretty sure your OS handles the keyboard interrupts. It doesn't need to inject anything because it already has access.

 

Hm, I haven't tested the issue since the PM flash. Does the process also flash EC2?

 

It flashes everything to the latest and greatest that is there to flash (well almost everything), so you will no longer see the problem that you described.

 

@Mr. Fox - Is the display upgrade process on the DM3 pretty much the same as the DM or has it been streamlined at all? Is it still necessary to remove heatsink, GPUs, etc? I don't mind doing it and repasting, but would like to skip it if not required.

Thanks

Edit: think i see what i need to do here.

Sent from my Nexus 6P using Tapatalk

 

For what its worth, i may as well inform that i dont feel any delay or lag in using keyboard after booting up.

 

Ok. I got out the external USB keyboard and detection worked as normal. I also removed the USB keyboard, did a full shutdown, started up and then the internal keyboard worked as it should...

I don't know what to say at this point. I've since done multiple restarts and full shut down / restarts. I'd be stoked if it was fixed. I'll just have to wait and see if I encounter this phenomenon again.

 

I get the keyboard lag as well. I usually just hit the windows key once and the keyboard works fine from then on. Even through reboots and crashes. It's when it's been off for a while that i get the delay.

 

That´s no speculation.
Some over 3000 server addresses are contacted.
Keyboard inputs are monitored.
For this, the license terms are signed.

If you want to know who is contacted - you should set up a free host server where the connections are logged.

And if you want to switch off the telemetry data - there are tools for it.
ShutUp is one tool. Every Update from Windows 10 overwrite the settings of the tools.
Or you open the one DLL with a hex editor and delete the server addresses.

 

I am using OOSU10 first on every fresh installation...

 

I have a FedEx tracking number for the 780W AC adapter and a Tornado F5 Extreme Edition (7700K and 1080 and 64GB DDR4-3200). Delivery is set for Monday.

 

The best way to do it is edit the ISO and delete all of the cancer cells from the WIM files before installing Windows, then there is nothing available to metastasize later. No telemetry functions, no Cortana the digital slut, no Windows Store, no UWA crapps or XBOX filth, no biometrics, no keyloggers, no Skype or OneDrive garbage, etc. Just Windows 10 barebones, the way it should have been done in the first place.

 

once youre done reviewing that little ÜBER-beast, youre very welcome to send it my way

 

That´s OOUSU =
O&O ShutUp10

 

Cool idea.
Only you have enormous work with it.
Or do you do this with a tool?
The various commands dism are very error-prone.
You can do almost anything with NLite.
And then close the image again.
I will try.
After all, I have already provided WIM with drivers.
Is almost the same.

 

Mr. Fox,

When you remove everything from telemetry from the WIM and you get Windows updates - new regkeys are written in the 7 database files of the registry.
Have you ever looked at yourself or tried over a host server if not some telemetry data are sent?
Or is your system still clean?

That would be interesting.

For all who are interested.
It is not enough to fill the host file in the system with the servers that are not allowed to access, because this one dll file will still drive the entire server list even though the host should actually exclude these addresses.
This is why you have to edit this dll with a hex editor.
And here all addresses must be set to NULL - except the update servers. Of course you could also take the update servers out and get only WSUS updates.

Where you can still defend yourself is in the file of me to see.
Researchers from Michigan are developing hardware-based tools to interrogate data = telemetry.
It is in German Language.
Maybe you can find it in the USA?
I do not want to know, if not already such hardware tools exist.

 

Yes, I use a tool, but not NLite.

You provided a WIM with drivers? I must have missed that post.

I have W10 Enterprise 2016 LTSB.

I generally do not allow Windows Updates to infect my systems. Once in a while I will selectively apply something using a third party tool that allows me to pick and choose, but for the most part I have no use for the updates. Hosts file is also modded to block communication with Micro$haft.

 

New version of AIDA64 for @Prema BIOS + 7700K

https://www.aida64.com/downloads/latesta64xebeta

 

@Meaker@Sager

What drivers did you update with the 7700K. Just want to get prepared before I update my bios once it is emailed to me. Right now I am running all the drivers on Sager's site listed as August 29th.

 

If they add the Motherboard name going by HWID and not BIOS info strings, then they will have the same mobo showing as different mobo models depending on CPU/GPU that is currently used.
Clevo changed their BIOS code over that last year and board IDs are no longer consistent but flexible. So the above approach will no longer work...pull the 7700K out and the 6700K in and you will see. Also there is no P870DM3, mobo is called P870DM2.

 

They should already have the old HWID for the 6700K in their database. After switching to 7700K it showed as unknown motherboard until they added the new hardware ID. I will ask Tamas to change it to P870DMx(-G) if that's OK.

 

I'm intrigued with the P870DM2/P870DM3. How's the cooling on this beast on the 7700k and 1080GTX or SLI?

 

They should read the BIOS board info (as defined by standards and done by CPU-Z etc) for motherboard, not adding names to HWIDs.
P870DM3 can alter it's own board ID depending on CPU and GPU model and the newer P870DM3 would end up being detected as old P870DM or P870DM-G model same for P870KM and all P7xxDM models. Going by ID simply no longer works to detect the actual board as it did a couple years ago.

 

Well, it's better than "unknown motherboard" like it used to be. In CPU-Z mine says the manufacturer is Alienkiller and the model is II powered by PremaMod. Maybe an email from you to Tamas to explain how Clevo is doing things would work best. If you need his email address let me know. Every time something new comes out and shows as "unknown motherboard" at least one person with the new configuration has to send a report to them to tell them what it is. Maybe if you explain what AIDA64 should read from to identify it that would eliminate the need in the future.

 

That's only your system brother.
Every other model will show actual data. That same data they have to use.

Spoiler

 

So, I should ask them to make AIDA64 read what shows in the BIOS on all Clevo systems, if they can do that? I'm only assuming, but if AIDA64 was made to function that way rather than using HWID it would not have said "unknown motherboard" to begin with so they may have to make some changes to how AIDA64 identifies motherboards before that will work.

 

I'd say cooling can be pretty decent with the right tweaks and work done. Thermal pad replacement, delidding CPUs and using Liquid Metal thermal paste, overclock fan profile, raising back of machine, etc.

@Donald@HIDevolution @Ted@HIDevolution @Zoltan@HIDevolution and Vivian (whose @ I don't know) are doing fantastic work by only offering delidded CPUs and auto-overclocking them for people pretty much free of charge, and @John@OBSIDIAN-PC is also going the extra mile, even changing out thermal pads for great contact for all their systems.

Fantastic work and definitely places to buy from to get the best system out the gate. Plus, the delid warranty and Prema bios support (though obsidian cannot sell with them) also push things to the tops.

 

Don't expect cool temperatures with 7700K. Especially, with something with a cooling system inferior to the P870DM3, which has an excellent cooling system. I'd expect insane temperatures on a system with a unified heat sink design... probably unmanageable temperatures with a substantial overclock. 6700K is a much cooler-running CPU.

 

But he was asking about the P870DMx?

Though yes, I agree about the unified design. However john from Obsidian said he managed to get was it an OC'd CPU with a 1080 in the P775DM3 down to 75c on GPU and 82c max on CPU running AIDA64 full system stress with just overclock fan profile and nothing else? Imagine what he'd do on a P870DM3 =O

 

I did that with a 6700K, testing a 7700K in the next couple of days.

My system is stable with stock bios at 4.58Ghz (4 cores), plus OCed GTX 1080, Overclock fan profile, little undervolt, ZERO CRASH! Kick ass temperatures
Stock clocks with overclock fan and you don´t need undervolt for ZERO throttle unit pulling 100% usage from 6700K + GTX 1080

No P870KM in atm, will test it soon, i´m getting both dual card units and single 1080 units

 

Yes, that is correct. The last part that begins with "I'd expect" was not related to his question. I should have hit my enter key and made it a separate paragraph.

 

What is the difference between p870dm2/3 (vapor chamber) cooling and p870km1 (vapor chamber)?

 

Nothing. Also, P870DM3 is defined by the vapor chamber. DM2 is non-vapor chamber. The difference is basically only the heatsinks.

 

But then what does Mr. Fox mean by the bold part?

 

He's talking about the machines like the P775DMx or P750DM2

 

Vapor chamber is for the GPU. That is unrelated to my comments about the 7700K CPU running extremely hot and needing an excellent cooling system like the one offered in the P870DM3. 7700K runs super hot so you need a better than average cooling system for that CPU, and even then it might not be as cool as you'd like it to be.

Exactly. I cannot imagine being able to cool a 7700K effectively in those machines, and especially not if the CPU is overclocked.

 

Just had to re-install the video drivers due to the changing of the system ID and the need to do the unsigned driver work around.

 

Ok thank you. Hopefully Nvdia will update soon.