Windows 10: Suddenly crash into blue screen registry error

it is the first time my computer crash into blue screen, just a few days after win10 update


bellowing is the dmp file content


runned a diagnostic with Dell F12, it seems no problem with the hardware.

hoping you guys can help me find out way!

Thanks a lot .

------------------------------------------------------------------------
Microsoft R Windows Debugger Version 6.10.0003.233 X86
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Raozeyuan\Desktop\042020-10156-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 18362 MP 8 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff806`0bc00000 PsLoadedModuleList = 0xfffff806`0c048150
Debug session time: Mon Apr 20 20:58:26.889 2020 GMT+8
System Uptime: 0 days 12:18:16.958
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
...........
ERROR: FindPlugIns 8007007b
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 51, {11, ffffa1876c594d50, 1, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files such as the public OS symbols do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files such as the public OS symbols do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files such as the public OS symbols do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files such as the public OS symbols do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files such as the public OS symbols do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files such as the public OS symbols do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files such as the public OS symbols do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files such as the public OS symbols do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware_ram PAGE_NOT_ZERO_VISTA

Followup: MachineOwner
---------

*** Memory manager detected 143337 instances of page corruption, target is likely to have memory corruption.

:)

 

Error. Blue Screen

Hi,

In addition to the above mentioned solutions by Community members, I would like to add the following:

Before we proceed I would like you to answer the following question:

• 
  What is the make and model of your computer?
  
• 
  Did you make any changes prior to the issue?
  

The issue might occur due to Viruses, or something changing/deleting in Registry Files, a failure during Bootup, or a corrupt file which could be due to age of a computer or viruses or somebody tampering with files.

I suggest you to follow the step below:

Step

I suggest you to refer the article below and check if it helps:

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Please get back to us with updated status, we will be happy to assist you.

 

Blue screen crashes

Hi Howard,

We would like to know if you're still experiencing blue screen errors. If yes, the error WHEA_UNCORRECTABLE_ERROR message you received may possibly occur due to a hardware error.
To efficiently assist you, kindly answer the following questions:

• Have you made any recent changes prior to this issue?
• What troubleshooting steps have you done so far?

Meanwhile, I suggest that you follow the steps in this article on how to troubleshoot WHEA_UNCORRECTABLE_ERROR.

If the issue still persists, I recommend that you follow the steps in this
article on how to troubleshoot blue screen errors. You can choose when did you get the error and perform
the instructions.

Let us know if you need further assistance.

 

Crash/blue screen

First, if this is in wrong place, I apologize, but this is first time to site and a couple times browsing could not find similiar discussion. I have had 2-3 blue screens, and a couple of blank screens in last 3-4-5 days, with internet explorer 2 sessions, one while windows update, and one just sitting quiet. MY operating system is; Vista Home Primium,Gateway manufactor,model LX6810-01, x64-based PC, processor intel Quad Q8200 @2.33 Ghz,2336mghz, 8 GB RAM.

Here is some errors and listings on "event view log". 1). gupdate(either component that gives rise to event is not on computer or installation is corrupt.) 2).Loadperf???
3). WMI(Error) (Event can not be delivered thru this filter until the problem is corrected.).
4). 4 Sidebyside errors 5). LicCtrlService error. There was also an application error from yesterday. From yesterday and other days a Warning(Windows has detected your registry file is in use by other application or service. There was another warning about restart for Steam application.

Now finially, a lot of the numbered listings, I listed, are repeated repeatedly over the last month or so(when I scrolled thru event log). So in closing can you all point in a direction to look into, I am a complete noobie about fixing problem. You'd have to be very specific.
If your site has a pay service, I'm okay with that. Now, one last thing. What ever is going on, seems to happened once and then computer runs fine after, all day!!

Thanks,

JMKile