BSOD soon after login, error 0x00000050, Page_fault_in_non_paged_area

Hello Wiyld, I'll see if I can help. You have had a whole bunch of BSODs today but none before today
All of the 7 or 8 that I checked were 1 of 2 kinds. either

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
REGISTRY_ERROR (51)
Something has gone badly wrong with the registry.  If a kernel debugger
is available, get a stack trace. It can also indicate that the registry got
an I/O error while trying to read one of its files, so it can be caused by
hardware problems or filesystem corruption.
It may occur due to a failure in a refresh operation, which is used only
in by the security system, and then only when resource limits are encountered.

OR

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8a003469000, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003112bdf, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000000, (reserved)

I would suggest to try a System Restore to a point before the BSODs started System Restore

If that does not work try Driver verifier, but first create a restore point, System Restore Point - Create

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and therefore it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How we know that DV is enabled:
It will make the system bit slow and sluggish.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no Restore points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

I would also make sure there are no firmware updates for your SSD, and if you have a toolbox installed, ckeck the health.

Let us know the results, with the subsequent crash dumps, if any.

Ok. Sometimes it works that way. Just my opinion, but I think sometimes it says it didn't work, meaning everything wasn't restored. But, some things were restored. That is just my opinion. You may need to save your firefox settings and bookmarks, and uninstall it and reinstall it. Apparently some of the registry changes Firefox did not agree with. That happens with registry changes sometimes with several programs.