BSOD at least twice a month - uncertain cause

When using google search iobit bsod or iobit blue there are many hits.
IObit can be a confounding factor when troubleshooting BSOD and uninstalling the software can make it easier to establish cause and effect.
Philc43 may have a preference.

@zbook
that's fine - I uninstalled iobit unlocker with the iobit uninstaller, and then uninstalled the iobit uninstaller with the revo uninstaller I had previously installed. I have changed to "automatic memory dump" and disabled automatic restart

Thank you

I had taken out two RAM sticks (#2 & #4) of the four I usually have in place and ran Memtest with 22 passes and no fails. My computer seemed to be running fine for 51 days with no BSODs (as opposed to a BSOD once every 2 to 3 weeks). This BSOD (MEMORY_MANAGEMENT) occurred immediately after waking up the computer from standby.

I will be swapping out the two sticks for the other two sticks (#2 & #4) + a Memtest overnight, and will run those to see how it fares

Link to the BSOD log + Minidump (Dropbox) below

Please let me know if you have any other suggestions

Attachment 218588
Dropbox - BSOD - Simplify your life

There are two log collectors: DM and BETA
At sometime the BETA will replace or become the DM log collector.
The DM log colletor collects more useful files and folders.
Please run the BETA log collector and post a new zip into the thread;
BSOD - Posting Instructions - Windows 10 Forums
https://www.tenforums.com/attachment...-v2-beta15.zip
(extract all > open)

Open file explorer > this PC > C: > in the right upper corner search for: C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a separate share link into the thread using one drive, drop box, or google drive

See attached beta collector log

I do not have a "memory.dmp" file in that directory. I also have to copy the minidump file back to the minidump directory since Windows 10 automatically deleted it. I do not use CCleaner

Sticks #2 and #4 went through Memtest over the last 16 hours with 17 passes and no errors

The event viewer displayed:

Code:

Event[1207]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2018-12-25T21:24:10.909
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: PICKLESDESKTOP
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000041201, 0xffff8000002b0600, 0x810000005c112805, 0xffff860fcaad3bc0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 50921df2-d014-4347-9301-c7e457220d8a.

The Memory.dmp file was created during the crash.

For the next BSOD immediately use search to find the file and if the size is < 1.5 GB then zip and post a share link into the thread.

At the present time you are working on the paired RAM testing in different DIMM.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) Powercfg -h off
6) bcdedit /enum all
7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Code:

Event[1152]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2018-12-25T21:23:57.025
  Event ID: 16
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: PICKLESDESKTOP
  Description: 
Windows failed to resume from hibernate with error status 0xC0000001.

See attached

In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread.

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

See attached screencaps

The settings are fine.
For any BSOD you should see a BSOD window with bugcheck and : (
Sometimes you may see a misbehaving driver in the form *.sys
At the very beginning of a BSOD you may see a % counter.
If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file.

Immediately after any BSOD:
a) Run the BETA log collector
b) Search for C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a share link into the thread using one drive, drop box, or google drive