"Activate Windows" does not stick

@Superfly

I did nothing (through Nov 17th afternoon to late night, as per your advice. The "Activate Windows" message was there, taunting for an action, but I could resist... Until I got a Blue Screen of Death at 22h40 (see below for details if you are interested).

At reboot time (or this morning?), there was no"Activate Windows" msg, the Settings->Activation windows showed that everything was almost OK- I am writing "almost" as there was a suggestion to Troubleshoot activation, which I did. [I know I should have recorded the time...].

Since then (6 or 14 hours elapsed) no issue.

Gilbert

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000e6 (0x0000000000000026, 0xffffd489b15cc570, 0x00000000000000a1, 0x0000000000000005). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c009b8f5-c807-404f-85de-f219c2d9e330.

In fact, the dump did not save (5' into it, still 0%). The detail is:

- System

- Provider

[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck

- EventID 1001

[ Qualifiers] 16384

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2019-11-17T21:40:30.088978000Z

EventRecordID 5784

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer Noname

Security


- EventData

param1 0x000000e6 (0x0000000000000026, 0xffffd489b15cc570, 0x00000000000000a1, 0x0000000000000005)
param2 C:\WINDOWS\MEMORY.DMP
param3 c009b8f5-c807-404f-85de-f219c2d9e330

@Superfly: Thanks a lot for your interest and many advises. WRT Macrium and clean install... Wait and see!

Gilbert

Not sure I want to do a clean install, as I do not understand what other issues it would create (including a lot of program re-install & tuning, etc).

I

I re-opened the thread, even though I do not need anyone to take action. This mail is for the record (so that, just in case, there is a trace elsewhere than in my memory).

Yesterday (2019-11-21) at 23h12: crash+reboot (no memory.dmp). Event logs include:

System: besides the ones below, no error was showing:

23:14:28 Dump file creation failed due to error during dump creation. [I wrote a similar useless error msg when I was coding 30 years ago]
23:14:46 The previous system shutdown at 11:12:22 PM on ‎11/‎21/‎2019 was unexpected.

The crash is seemingly related to around 150+ Bonjour Service (now disabled) error events of two types:

Task Scheduling Error: m->NextScheduledEvent 5406
Task Scheduling Error: Continuously busy for more than a second

Today at 9-ish, LicensingDiags gives the correct key and says (among other things)

LicensingStatus: SL_LICENSING_STATUS_LICENSED
LicensingStatusReason: 0x4004F401
LocalGenuineState: SL_GEN_STATE_INVALID_LICENSE

I decided to wait for the automatically try to activate the license - nothing after 7 hours ; I went to the activate screen and clicked on the "Troubleshoot" button, which did the job.

Gilbert

A reset or restore did the job, no need to reactivate since 2 days now.

I was still expecting someone at Microsoft would look at the detail... A few calls were needed (7). The first 3 resulted into the same scenario of checking my id, verifying the W10 Pro key, and do a "phone activation" - spelling 9 groups of 6 digits out and in). During the 3rd call, the support person did (remotely) type in three slmgr (/upk, /ipk <key> and /ato). The next 3 calls were less glorious (two were just "wait and hang", the 3rd one was about "let me check your key and do a phone activation and it will work" ).

Finally, the last call resulted into a L2 escalation. They explained that the only solution is to restore W10.

As mentioned, resolved, but not solved.

Superfly said:

Thanx for the report back... has the diag report changed in anyway?

Here is the result after the "fix"., as an attachment.

G.