Bsod 0xD1

Please run in an admin command prompt following command

Code:

slmgr /dlv

a pop-up will show within a few moments, please make a screenshot of it and post it.

Please don't forget to run below commands in an admin command prompt, simply copy/paste it

Code:

systeminfo > "%USERPROFILE%\Desktop\systeminfo.tmp"
findstr /v "Owner." "%USERPROFILE%\Desktop\systeminfo.tmp" > "%USERPROFILE%\Desktop\systeminfo.txt"
del "%USERPROFILE%\Desktop\systeminfo.tmp"

Upload the text file that it outputs.

I've asked an activation expert on this matter for a second thought about it and we both agree that the activation is counterfeit.

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

Forum rules

4) No piracy or discussion of piracy allowed at all. Such as software, music, videos and other intellectual property violations (e.g. downloading youtube videos locally etc).

axe0 said:

I've asked an activation expert on this matter for a second thought about it and we both agree that the activation is counterfeit.

Troubleshooting a counterfeit installation is useless as it is not known what has been modified to your system.
A counterfeit installation contains heavily modified code which causes the system to behave in unexpected ways.
For this reason, analyzing counterfeit systems is unreliable and most analysts won't try it.
I recommend to install a genuine copy of Windows.
If, after you have installed a genuine copy of Windows, you still get BSOD's we'll be happy to assist you.

Forum rules

Absolutely correct - but just to elaborate a bit more regarding the connection between netio.sys (which I assume is a network driver) and the counterfeit app in use - the latter uses a loopback IP to emulate a KMS server response on the local machine - so it's almost certainly the cause for the driver failing.

NETIO.sys = Network Input/Output System driver of Windows, Windows drivers are never the root cause but this specific driver does give some indications of where the root cause might be.
However no guidance as for instructions for finding the root cause can be given until the illegal activation is cleared up.

axe0 said:

NETIO.sys = Network Input/Output System driver of Windows, Windows drivers are never the root cause but this specific driver does give some indications of where the root cause might be.
However no guidance as for instructions for finding the root cause can be given until the illegal activation is cleared up.

Good to know... agreed.