Win10 Many BSOD issues

Question

Hello Microsoft Community,
My customers having a lot of trouble with Win10 Pro product lately

As far as I know I had around 10 of these issues for the last 2 days
All I know that the PC's installed this update:

Please advise

Answer 1

The BSOD says there is corrupted memory so the list of causes is pretty standard:

• Bad memory DIMMs, replace them and see if the problem goes away
• Corrupt driver, probably a third party one
• Virus, malware is impacting machine so run a scan

Personally I would recommend you take one of the crash dumps that is generated and load it up in windbg and use the standard BSOD debugging steps as discussed here to analyze where the failure is. If you consistently see a specific driver in the call stack then it is likely the driver. If the crashes occur all over the place then it is more likely bad memory.

If you still cannot figure it out then I would contact MS Support and get their engineers to help you diagnose the problem.

Answer 2

Take a look at:
https://support.microsoft.com/en-us/sbs/windows/troubleshoot-blue-screen-errors-5c62726c-6489-52da-a372-3f73142c14ad
Open start and search for feedback and open the Feedback Hub app and report this issue.

Answer 3

Please run the V2 log collector > post a share link into this thread using one drive, drop box, or google drive:

https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

Answer 4

@QmarkIT
Hi,
When did this issue start to occur?
Did it happen after installing the KB 5004945?

The KERNEL_SECURITY_CHECK_FAILURE bug check has a value of 0x00000139. This bug check indicates that the kernel has detected the corruption of a critical data structure.

Determining the cause of this issues typically requires the use of the debugger to gather additional information.
These general troubleshooting tips may be helpful.
-If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
-If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
-Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.
-Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.
-Run a virus detection program. Viruses can infect all types of hard disks formatted for Windows, and resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.

Due to security policy, community support cannot download and save user’s personal data such as dump or log files, please install WinDbg from Microsoft website and analyze crash dump files.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools
If you really need crash dump files analysis support, open a support ticket with Microsoft.

Hope above information can help you.

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.