BSOD - Bad Pool Header caused by NTOSKRNL

Hello, I've been having an issue this past week whenever my computer restarts (seems to be from Windows Updates) I come back to a Bad Pool Header BSOD. I was able to get it stopped by uninstalling Avast and doing a Clean Boot. After about 2 hours of restarting and just adding one new item to start up, everything seemed ok. Then this morning it started again, so I'm not sure at all what to do or whats causing it now. Any help would be really really appreciated.

Hello, just a quick check, have you activated windows yet?

Yes, as far as I know I have activated Windows 10. I've been using it for quite awhile now and did the free upgrade like a month after it was available.

I'm at work at the moment so will have to check that when I get home. Would that be caused by me being in Safe Mode? The only way I can get into the computer right now is booting it in safe mode. Otherwise I get the Bad Pool Header BSOD as soon as the login screen comes up after Windows boots up.

It says Windows is activated with a digital license linked to my Microsoft Account.

Please open a Command Prompt (via right click on Start button) and type the following: slmgr -dli

Please post the result that shows up in the dialog box.