BSOD at least twice a month - uncertain cause

Page 2 of 8 FirstFirst 1234 ... LastLast

  1. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #11

    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.
      My ComputerSystem Spec


  2. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #12

    @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
      My ComputerSystem Spec


  3. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #13

    new BSOD after 51 days


    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

    PICKLESDESKTOP-Tue_12_25_2018_213144_59.zip
    Dropbox - BSOD - Simplify your life
      My ComputerSystem Spec


  4. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #14

    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
      My ComputerSystem Spec


  5. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #15

    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
    BSOD at least twice a month - uncertain cause Attached Files
      My ComputerSystem Spec


  6. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #16

    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.
      My ComputerSystem Spec


  7. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #17

    See attached
    BSOD at least twice a month - uncertain cause Attached Files
      My ComputerSystem Spec


  8. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #18

    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
      My ComputerSystem Spec


  9. Posts : 58
    Windows 10 Pro 64 bit v1809
    Thread Starter
       #19

    See attached screencaps
    Attached Thumbnails Attached Thumbnails VM window.jpg   S&R window.jpg  
      My ComputerSystem Spec


  10. Posts : 25,509
    windows 10 professional version 1607 build 14393.969 64 bit
       #20

    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
      My ComputerSystem Spec


 
Page 2 of 8 FirstFirst 1234 ... LastLast

Related Threads
Random BSOD for the last month in BSOD Crashes and Debugging
Hey Guys, My PC keeps randomly BSODing mainly from DRIVER_IRQL_NOT_LESS_OR_EQUAL 00000000`00000000. Have tried different GPU & RAM. Have even done a fresh install to no avail any help would be much appreciated. Thanks in advance.
4 BSOD's on 2-month old PC in BSOD Crashes and Debugging
Recently built a new PC, and it works excellently well however over the last 3 weeks I've had 4 BSOD's all with the same bugcheck error code from Event Log I don't know how it starts or what triggers it. It simply runs into the issue every few...
3rd BSOD in a month in BSOD Crashes and Debugging
Hello. Last night I received my 3rd blue screen error in about a month. That one and the previous one said "system service exception (netio.sys)." I forget if the first time this happened the error listed the same. Anyway, here's my log file...
Multiple bsod's in last month in BSOD Crashes and Debugging
Hello, I have had multiple bsod's in the last month. they seem to occur when pc is not doing anything. When im working on it it bsod's sometimes, but when i walk away it will in a matter of minutes. 61517 i hope someone can tell me what is...
Keep getting BSOD for the pass 2 month in BSOD Crashes and Debugging
BlueScreenView says that its ntoskrnl.exe driver error.
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 14:22.
Find Us