Crashes Sometimes/BSOD with different error messages.

Hello moregun.

Apparently the BSOD is caused by Tencent QQSYSMON (

Code:

fffff880`083c9648  fffff880`00dd2b7aUnable to load image \??\C:\Program Files (x86)\Tencent\QQPCMgr\8.0.9211.227\QQSysMonX64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for QQSysMonX64.sys
*** ERROR: Module load completed but symbols could not be loaded for QQSysMonX64.sys
 QQSysMonX64+0xab7a

I would suggest you to uninstall Tencent QQ and observe the situation.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Also test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Let us know the results.
__________________________________________________________________________________
BSOD ANALYSIS:

Code:

BugCheck 4E, {2, 86242, 21f5ff, 1}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )

Followup: MachineOwner
---------------------------------------------------------------------------------------
BugCheck 4E, {99, 1dff38, 2, be346}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
----------------------------------------------------------------------------------------
BugCheck C000021A, {fffff8a001f38420, ffffffffc0000005, 770be8b5, 8de680}

----- ETW minidump data unavailable-----
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )

Followup: MachineOwner
-----------------------------------------------------------------------------------------
BugCheck 1A, {5003, fffff70001080000, 2a8c, 48100205518}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+38936 )

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

One single error message (red line) is enough to rule out the RAM to be bad. Stop testing it now.

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

Otherwise, you may replace the entire RAM kit. If those are within warranty, send those to the vendor for RAM.

Let us know how the computer is running with the replacement RAM, when replaced :)

OK. Let the computer run now. If it crashes again, let us know.

I think you should follow post 4 again ....

The dumps are silent about any probable cause. As we noticed the RAM to fail, better we check it thoroughly.