Solved BSOD running Plex Media Server, now NIC not working and locking up

[NoelDP]

Interesting.
Where did you acquire your Windows License from?
The License type is OEM_SLP - which is only valid on machines preinstalled by larger manufacturers, but you appear to have a retail motherboard.

 

[doveman007]

I'm in the EU, where it's been ruled unlawful for Microsoft to tie software licences to hardware, which explains why Microsoft were happy to activate my licence.

I've still been having a problem with HwInfo64 making the screen go blank when launched, requiring a hard reset to recover. The author looked at the debug log for me and said it was locking up when scanning the Nebula PCI TV card, so I've removed that now (although sometimes HwInfo64 worked OK with it installed, so it's hard to know for sure if that's definitely the problem). Perhaps that was connected to some of the other problems as well, so I'll have to see if I have any more problems now it's removed.

I've attached the debug logs from HwInfo64, one working with the Nebula removed and one where it locked up with the Nebula installed.

 

[NoelDP]

That ruling applies ONLY in Germany - none of the other member states of the EU.

 

[bobafetthotmail]

Which also explains why I never heard of this while I'm in EU too.

 

[NoelDP]

See this article....
No, OEM Microsoft Windows licenses cannot be transferred to another PC - Microsoft Sales Excellence Manager - Eric Ligman - Site Home - MSDN Blogs

 

[doveman007]

That ruling applies ONLY in Germany - none of the other member states of the EU.

Well that's where I bought it. Clearly Microsoft consider that I have a valid licence or they wouldn't have activated it and confirmed it as genuine.

If the EU has ruled something trade-related unlawful, I'm pretty sure it would apply to the whole EU, regardless of which country bought the case to the court, as trade within the EU countries is the one area which all the countries agree the EU has jurisdiction over but I haven't read the whole judgement.

Unfortunately, I've had two BSOD since removing the Nebula card, so I don't seem to be making much progress here.

 

[bobafetthotmail]

post 41 is still true though. OEM_SLP activation like yours is only done by OEMs. And pirates using loaders.

 

[doveman007]

post 41 is still true though. OEM_SLP activation like yours is only done by OEMs. And pirates using loaders.

Well I'm certainly not a pirate using a loader and as I say, if Microsoft are happy to activate my licence as genuine (I had to phone them to do so, which doesn't seem like something they'd require OEMs to do for each licence/machine) then surely that should satisfy you that it's valid?

 

[NoelDP]

The only legal way to acquire OEM_COA_SLP Keys or OEM_SLP Keys in the UK is to purchase them preinstalled on machines from large manufacturers.


Computers that come pre-installed with Windows from large manufacturers usually come with two Product Keys.

OEM SLP: This is the key that came in Windows (from the factory). It works by connecting to a BIOS flag (the SLIC table) found only on computers from that Manufacturer. It also checks for the existence of proper matching licenses in the OS itself. Once it sees both, it self-activates every time the machine is rebooted.

COA SLP: This is the key seen on the sticker located on the side, bottom or in the battery compartment of your machine. This key is for use if the OEM SLP self-activation stops working for whatever reason.


It is not legal to sell COA_SLP Keys except in this way - and only the larger manufacturers have such keys in the first place.
If you purchased this license then it's a counterfeit, and may be blocked at any time.

 

[doveman007]

The only legal way to acquire OEM_COA_SLP Keys or OEM_SLP Keys in the UK is to purchase them preinstalled on machines from large manufacturers.


Computers that come pre-installed with Windows from large manufacturers usually come with two Product Keys.

OEM SLP: This is the key that came in Windows (from the factory). It works by connecting to a BIOS flag (the SLIC table) found only on computers from that Manufacturer. It also checks for the existence of proper matching licenses in the OS itself. Once it sees both, it self-activates every time the machine is rebooted.

COA SLP: This is the key seen on the sticker located on the side, bottom or in the battery compartment of your machine. This key is for use if the OEM SLP self-activation stops working for whatever reason.


It is not legal to sell COA_SLP Keys except in this way - and only the larger manufacturers have such keys in the first place.
If you purchased this license then it's a counterfeit, and may be blocked at any time.

As I said, I didn't acquire it in the UK though. As MGADIAG shows, it's a COA SLP key, not an OEM SLP as you said before, which might explain bobafetthotmail's comment.

I'm sure Microsoft were perfectly able to see that my machine doesn't have a SLIC table when activating and the fact that they activated it as genuine despite that shows they don't consider it counterfeit. I can't imagine they're likely to suddenly decide that a licence they activated as genuine suddenly isn't, despite nothing changing, as that would seem to be rather bad PR, and I think they'd find it very hard to legally justify suddenly changing their mind and deactivating my licence.

I can only guess that the reason I had to phone to activate is to confirm that I'm in the EU, where different rules apply.

 

[NoelDP]

COA SLP Keys are aa form of OEM_SLP Key.
There are three types of OEM Keys.

OEM_SLP and COA_SLP (more correctly called OEM_COA_SLP) - these are discussed above.
COA_NSLP Keys - which are the conventional System Builder keys, used by smaller manufacturers and hobbyists

Outside Germany it is not legal for anyone to sell OEM_COA_SLP/COA_SLP/OEM_SLP licenses and Keys except as part of a preinstalled system.

 

[doveman007]

Now that I've explained that my Windows is Genuine and properly activated, I'd be grateful if someone could take a look at the dumps I posted.

I seem to be able to trigger it by opening Explorer and searching C: for something. I don't have Indexer/Windows Search service running. The error refers to w32k.sys, Stop 050 and "PAGE_FAULT_IN_NONPAGED_AREA".

I googled that error and found this page, which is about firefox but I tried going to Windows\fonts and it BSOD, so it seems I may have the problem mentioned there. https://support.mozilla.org/en-US/questions/674779

Going to Control Panel - Fonts caused a BSOD as well, so I had to use \\PCNAME\C$\Windows\Fonts, which worked and then I selected all (446) fonts and clicked Install to reinstall them. After rebooting, I can now go to Windows\Fonts or open Control Panel - Fonts and it's not BSOD anymore

I wonder how it got messed up so that it was causing BSOD though?

 

[doveman007]

Seems my .NET Framework got messed up as well, as I was getting these errors when trying to start MCE Buddy:

Application: MCEBuddy.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEECD9D08D (000007FEECD90000) with exit code 80131506.

Faulting application name: MCEBuddy.Service.exe, version: 2.3.12.1, time stamp: 0x51620371
Faulting module name: clr.dll, version: 4.0.30319.1008, time stamp: 0x517a18ff
Exception code: 0xc0000005
Fault offset: 0x000000000000d08d
Faulting process id: 0x1210
Faulting application start time: 0x01ce8e21a5aae212
Faulting application path: C:\Program Files\MCEBuddy2x\MCEBuddy.Service.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: e4c6a25b-fa14-11e2-91ce-bc5ff40da1b3

Hopefully doing a repair install of .NET Framework will sort it out. I'd already done a sfc /scannow and chkdsk C: /F /R which didn't show any problems. If there's no way to check if system files are corrupt other than to wait until some program tries to use them, it makes it rather hard to test for problems.

If anyone still needs further clarification of the legal position in the EU, this is the 2012 judgement from the European Court of Justice (Grand Chamber), which makes it clear that in the EU the rightsholder's (i.e. Microsoft) right of distribution is exhausted at the first sale and that the purchaser has the right to subsequently sell the software and the right to use it
CURIA - Documents

Microsoft obviously knows about this judgement and that they would be behaving unlawfully if it did anything to prevent legal owners of software from using it, which is probably why they were happy to activate my licence as genuine.

 

[doveman007]

Hmm, I ran this installer and did a repair and rebooted but I'm still getting the same errors
Download Microsoft .NET Framework 4 (Web Installer) from Official Microsoft Download Center

My clr.dll is already dated July 2013, so I don't think this hotfix is applicable FIX: "Faulting module name: clr.dll" error message when you run a Microsoft .NET Framework 4-based application

EDIT: Sorted it by uninstalling .NET Framework both Client and Extended, then reinstalling the Client Profile, checked MCE Buddy launched OK, then applied the 13 Windows Updates that were now available and checked MCE Buddy again.