Constant BSODs on freshly installed system

tomdsr said:

Upload a new v2 log collector file. Fair warning, it's easily seen if you did a new install or not. Changing the key is not enough.

Can you tell me why changing key is not enough? I told you the proccess of activation was after the problems started to occur. The process it self was legitimate (no changing of files). And you even said I dont need a fresh installation. I am confused, you just want to punish me, that I did not have legitimate copy? The process of installation would be the same, i would not enter the key on installation, i would do that later after installation.

rugharcz said:

Can you tell me why changing key is not enough? I told you the proccess of activation was after the problems started to occur. The process it self was legitimate (no changing of files). And you even said I dont need a fresh installation. I am confused, you just want to punish me, that I did not have legitimate copy? The process of installation would be the same, i would not enter the key on installation, i would do that later after installation.

1. answered why changing the key isnt enough.
2. irrelevant since you bypassed.
3. i said you dont have to, BUT what does my post above say if you dont?

Theres nothing to be confused about. Arguing it is just a waste of time

axe0 said:

Hi,

Illegally activating Windows through a KMS activation key is often done through software downloaded from untrusted sources. We don't know whether this was all that came along though, we can't be sure that no additional malware came with it that is waiting to be activated.
@tomdsr, as far as I know KMS activation doesn't replace files but mimics enterprise KMS activation.

never dug in to see if anything gets changed, but as you said, never know what else came with it.