Windows 10: BSOD Random times when computer unattended.

Page 2 of 5 FirstFirst 1234 ... LastLast

  1. Posts : 19,915
    windows 10 professional version 1607 build 14393.969 64 bit
       13 Apr 2018 #11

    Please post images of these post clean install results into the thread:

    1) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    2) 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 into the thread.
    b) > on the advanced tab under performance > click on settings > under performance options > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory tab into the thread

    3) Memtest86+ version 5.01: 8 or more passes with 12 GB RAM

    4) HD Sentinel: (run on each drive)
    a) click disk > surface test > post image into the thread
    (this may take several hours to complete)
    b) Post images of each of these tabs into the thread:
    Overview tab
    Temperature
    SMART
    Disk performance

    5) chkdsk /x /f /r on each partition
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Tutorials

    6) The BETA log collector can display more information than the DM log collector.
    All of the posts so far have had the DM log collector.
    Please use the BETA log collector for posting.
    open this thread > DM Log tool problem Solved - Windows 10 Forums > post #5 > follow the text and images to run the BETA log collector > post a new zip into the thread after the in place upgrade repair:

    Log collector BETA on the bottom of this web page:
    BSOD - Posting Instructions - Windows 10 Forums

    If you are unable to perform any of the above steps please post information in the thread so that each of the above can be troubleshooted.
    Last edited by zbook; 13 Apr 2018 at 08:48.
      My ComputerSystem Spec

  2.    13 Apr 2018 #12

    update: it seems like crashes only happen when I try to wake up my computer. Its not waking up after coming back to use it after an hour or so. (TV is saying no HDM signal), the only way to use it is to restart it. maybe its something to do wiht my video card?
      My ComputerSystem Spec

  3.    14 Apr 2018 #13

    Sorry, missed your post zbook, I couldntdownload the dm beta, when i clicked on link i get:Invalid Attachment specified. If you followed a valid link, please notify the administrator
      My ComputerSystem Spec

  4.    14 Apr 2018 #14

    Hi Zbook
    I have ran the all the tests but the memory test, I ran that last time and went past 8 passes and didnt take a photo, will run it again now, in the meantime, I took all the pics in the zip file, everything should be here even the DM beta (finally managed to find it). But please keep in mind that I found out my comp does not do memory dumps for some reason. I used who crashed and crashed my PC but nothing came out. in the event viewer i get:
    Volmrg: Dump file creation failed due to error during dump creation.

    I have pics of all the attached above :) Thank you once again
    BSOD Random times when computer unattended. Attached Files
      My ComputerSystem Spec


  5. Posts : 19,915
    windows 10 professional version 1607 build 14393.969 64 bit
       14 Apr 2018 #15

    1) Chkdsk /x /f /r C: displayed:

    Correcting errors in the master file table's (MFT) BITMAP attribute.

    Windows has made corrections to the file system.

    2) When available post chkdsk /x /f /r on the other partitions.

    3) Open device manager > click view > click show hidden devices > expand all rows > post images of any row with a yellow triangle and black exclamation mark or unknown device

    4) Check and re-seat cables for all drives.

    5) Read these links on Windows driver verifier: (do not use the tool until it is communicated in the thread)
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials

    6) Create a brand new restore point
    7) Backup any important files to another drive or to the cloud

    8) Run Sea tools for windows on each drive using SMART, and long generic tests:

    How to use SeaTools for Windows
    http://www.seagate.com/support/downl...ls-win-master/
    How to use SeaTools for Windows | Seagate Support
    http://www.seagate.com/support/downloads/seatools/
    Boot SeaTools off of a USB Drive | nowhereLAN

    Report the results into the thread.

    9) The upper portion of the Virtual Memory windows was cut off. Please re-post displaying the uppermost box.
      My ComputerSystem Spec

  6.    14 Apr 2018 #16

    Hi Zbook

    Thank you for being patient with me, and thank you for all your help so far:

    1) Do i need to do anything for this step or is this for my own information ? Is that a good thing?
    2) I have disconnected all other drives yesterday, and the BSOD still happens, do i still need to do chkdsk on my other drives?
    3) I have completed this step, do i need to show you screenshot, no yellow triangle and black exclamation marks or unknown devices.
    4) I have opened my PC, took apart my graphics card, cleaned it, cleaned PCI slot, added new thermal paste, reseated all cables, nothing seems loose. But it was good to do it.
    5) Will read those now, I will not use them until you tell me too
    6) created restore point (14/4/18 12:28pm NZD time)
    7) have nothing to backup as this is a new installation (ready to do anything at this stage)
    8) have installed seatools, will start running it now, do i need to do it for all the drives as I can disconnect the others.
    Edit: Ran the smart test - passed Long generic test - passed :) 1:10pm NZD Time

    9) Apologies, have attached a pic for virtual memory now,

    Edit: Shall i run the driver verfier now?
    Also, googling the error in eventviewer right before my critical error:
    File System Filter 'npsvctrig' (10.0, ‎2070‎-‎05‎-‎06T02:38:28.000000000Z) has successfully loaded and registered with Filter Manager.
    People are saying its a hardware error.
    I have changed powersupply, still same error, I will change videocardtonight with my mate, all else fails then it must be either CPU or Motherboard. (positive that the ram passed but will run it again tonight).

    I am really hoping its a driver error

    Again, thank you so much for your time.
    Attached Thumbnails Attached Thumbnails virtual memory.jpg  
    Last edited by aymanibousi; 14 Apr 2018 at 20:14.
      My ComputerSystem Spec


  7. Posts : 19,915
    windows 10 professional version 1607 build 14393.969 64 bit
       15 Apr 2018 #17

    Chkdsk /x /f /r corrected problems with the drive file system. If these types of problems are not fixed there can be problems related to the problematic files. This can include problems with booting.

    When possible, especially on HD it is your best interest to perform chkdsk /x /f /r on all drives to scan, fix and restore any drive file system problems. This can be accomplished is most cases by running the command overnight.

    Windows driver verifier will repetitively produce BSOD until all misbehaving drivers are fixed or until the tool is turned off.
    After each BSOD run the beta log collector to collect new files.
    And search for a memory dump file: C:\Windows\memory.dmp > zip > post a share link into the thread

    For each dump you should see a windows with : ( and bugcheck. Sometimes a misbehaving driver may displayed in the form *.sys. If you see a misbehaving driver please record it and post it into the thread.

    To turn off or recover from Windows driver verifier you will need to use the Windows advanced troubleshooting menu. There are 3 different methods:
    1) startup options (not startup repair) > restart > select #6 safe mode with command prompt > type:
    verifier /reset
    2) command prompt > administrator: X:\windows\system32\cmd.exe > X:\Sources> type:
    verifier /bootmode resetonbootfail
    3) system restore

    The methods to be used to turn off Windows driver verifier should be used in the order above and only advance to the next step if the prior step failed. Using system restore often leads to a loss of the dump file and little progress is made in the troubleshooting.

    There may be computer sluggishness or slow boots when using Windows driver verifier. If there are significant problems the test settings can be modified.

    Use this link for the customized test settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Use this link for the methods to turn off Windows driver verifier:
    Enable and Disable Driver Verifier in Windows 10 Windows 10 Tutorials


    Code:
    Event[790]:  Log Name: System
      Source: volmgr
      Date: 2018-04-13T22:35:54.462
      Event ID: 161
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    Dump file creation failed due to error during dump creation.
    
    
    Event[1259]:
      Log Name: System
      Source: volmgr
      Date: 2018-04-14T16:21:16.259
      Event ID: 161
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    Dump file creation failed due to error during dump creation.
    
    
    Event[1329]:
      Log Name: System
      Source: volmgr
      Date: 2018-04-14T18:11:14.680
      Event ID: 161
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    Dump file creation failed due to error during dump creation.
    
    
    Event[1628]:
      Log Name: System
      Source: volmgr
      Date: 2018-04-14T21:01:35.712
      Event ID: 161
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    Dump file creation failed due to error during dump creation.
    
    
    
    
    Event[1697]:
      Log Name: System
      Source: volmgr
      Date: 2018-04-15T00:26:25.212
      Event ID: 161
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    Dump file creation failed due to error during dump creation.
    
    
    Event[1784]:
      Log Name: System
      Source: volmgr
      Date: 2018-04-15T08:32:51.290
      Event ID: 161
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    Dump file creation failed due to error during dump creation.
    
    
    Event[756]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:04.761
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[757]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:04.761
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[758]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:04.761
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[759]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:08.767
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[760]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:08.767
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[761]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:08.767
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[762]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:12.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[763]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:12.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[764]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:12.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[765]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:16.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[766]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:16.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[767]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:16.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    
    
    Event[845]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:27.923
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk7\DR7, is not ready for access yet.
    
    
    Event[846]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:27.941
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk8\DR8, is not ready for access yet.
    
    
    Event[847]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:33.009
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk7\DR7, is not ready for access yet.
    
    
    Event[848]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:33.026
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk8\DR8, is not ready for access yet.
    
    
    Event[849]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:38.072
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk7\DR7, is not ready for access yet.
    
    
    Event[850]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:38.088
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk8\DR8, is not ready for access yet.
    
    
    Event[851]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:43.137
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk7\DR7, is not ready for access yet.
    
    
    Event[852]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:43.153
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk8\DR8, is not ready for access yet.
    
    
    Event[853]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:48.196
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk7\DR7, is not ready for access yet.
    
    
    Event[854]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:48.212
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk8\DR8, is not ready for access yet.
    
    
    Event[855]:
      Log Name: System
      Source: atapi
      Date: 2018-04-14T00:18:53.259
      Event ID: 143
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The storage device produced an internal dump.
    
    
    Event[856]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:53.259
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk7\DR7, is not ready for access yet.
    
    
    
    
    Event[857]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:53.260
      Event ID: 157
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    Disk 7 has been surprise removed.
    
    
    Event[858]:
      Log Name: System
      Source: atapi
      Date: 2018-04-14T00:18:53.276
      Event ID: 143
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The storage device produced an internal dump.
    
    
    Event[859]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:53.276
      Event ID: 15
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The device, \Device\Harddisk8\DR8, is not ready for access yet.
    
    
    Event[860]:
      Log Name: System
      Source: Disk
      Date: 2018-04-14T00:18:53.709
      Event ID: 157
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    Disk 8 has been surprise removed.
    
    
    Event[756]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:04.761
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[757]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:04.761
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[758]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:04.761
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[759]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:08.767
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[760]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:08.767
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[761]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:08.767
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[762]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:12.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[763]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:12.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[764]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:12.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[765]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:16.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x1 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[766]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:16.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x11 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[767]:
      Log Name: System
      Source: Disk
      Date: 2018-04-13T21:38:16.806
      Event ID: 153
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: Ayman-PC
      Description: 
    The IO operation at logical block address 0x21 for Disk 12 (PDO name: \Device\00000066) was retried.
    
    
    Event[991]:
      Log Name: System
      Source: Microsoft-Windows-WHEA-Logger
      Date: 2018-04-14T08:39:26.730
      Event ID: 21
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-19
      User Name: NT AUTHORITY\LOCAL SERVICE
      Computer: Ayman-PC
      Description: 
    A corrected hardware error has occurred.
    
    
    Component: AMD Northbridge
    Error Source: Corrected Machine Check
    Error Type: 28
    Processor APIC ID: 0
    
    
    The details view of this entry contains further information.
      My ComputerSystem Spec

  8.    16 Apr 2018 #18

    Hey mate, good news, its been 2 days without any freezes. I have no idea what might of sorted it out, will keep this post open for now and mark it when its 1 week steady. It might be the "Correcting errors in the master file table's (MFT) BITMAP attribute."
      My ComputerSystem Spec


  9. Posts : 19,915
    windows 10 professional version 1607 build 14393.969 64 bit
       16 Apr 2018 #19

    There were problems creating dump files.
    Using Windows driver verifier may create BSOD dump files and find misbehaving drivers.
    If there are no BSOD with Windows driver verifier in use for 48 hours that would be useful in evaluating the drivers.
    It would be useful to have some mini dumps or memory dump files to debug as there were driver problems reported in the logs.
      My ComputerSystem Spec

  10.    16 Apr 2018 #20

    I will use driver verifier, spoke too soon too. Was watching an anime online and comp just froze (with a weird buzzing noise from the sound coming from the PC speakers), no BSOD as well, had to restart so got an error 41. Its frustrating, I have no idea why my computer is not creating a minidump or a dump or why there is no BSOD.
      My ComputerSystem Spec


 
Page 2 of 5 FirstFirst 1234 ... LastLast

Related Threads
My computer keeps randomly freezing and it is driving me nuts! Sometimes I can be playing for hours and nothing happens or I have had it also freeze when it is starting up or once windows has loaded. I can't remember when I bought it but for a...
BSOD at very random times, no specific times. in BSOD Crashes and Debugging
Hi guys, I keep on getting BSOD screens when using my laptop. It is very random, sometimes it happens whilst I am working in Adobe Photoshop or Illustrator or even just when I am browsing the web. At first I thought it might be the display...
I have a brand new HP convertible laptop that came to me with Windows 10 installed. Have had frequent blue screen/restarts since buying 2 weeks ago. No apparent single application or activity that is the cause - it can happen just browsing for a...
Hi guys I have been having a bit of problem with my computer - I have windows 10 installed It feels like approximately every second night my computer is turning off by itself at night and I have no reason why - I was wondering if any one...
BSOD at random times doing random things. in BSOD Crashes and Debugging
Hi, I am getting BSODs at random times, while doing different things each time. Been getting them for 5 days trying to narrow down what could be causing it. Searching lead me here. I did the posting instructions. Also did sfc/scannow 2 times that...

Tags for this Thread

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 21:28.
Find Us