progressively worse bsods after working fine for 6 months.

Page 1 of 9 123 ... LastLast

  1. Posts : 41
    windows 10
       #1

    progressively worse bsods after working fine for 6 months.


    hi, i built my pc about 10 months ago and it was fine from the beginning. then one day it crashed in game. then after a few weeks it started crashing on the desktop or chrome. sounds like a hardware issue to me but it seems to be perfectly fine if i turn off all non microsoft services. i made a reddit post to see if someone could help me but i figured i should probably just post here. ill link to the reddit post as it may have some useful info about behavior with services on or off. basically i can turn either one service on or another and they both make it crash, and its fine with nothing on, it hasn't crashed for two whole days now. but im also having another problem in that it no longer makes any dump files. memory.dmp or anything in minidump. so in the onedrive is the only dumps i have. but they are relevant.
    Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
    Why would win10 stop making dump logs? : techsupport

    - - - Updated - - -

    update, it just crashed while all services were off while slicing a model to 3d print. so im back to thinking its memory related even though it passed 6 passes of memtest86+.
      My Computer


  2. Posts : 38,545
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Hi nicklindenmuth,

    Welcome to the Ten Forums BSOD forum.

    The logs displayed drive problems and misbehaving drivers.

    1) Use safe mode as needed to reduce the frequency of BSOD as needed:
    Boot into Safe Mode on Windows 10

    2) Temporarily remove all non-windows drives (except backup image drive) or disconnect cables

    3) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    4) Create a brand new restore point.
    Create System Restore Point in Windows 10

    5) Tests will be ran to evaluate the drives

    6) Drivers will be uninstalled and reinstalled

    Steps to follow.
      My Computer


  3. Posts : 38,545
    windows 10 professional version 1607 build 14393.969 64 bit
       #3

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    7) wmic recoveros set autoreboot = false
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) bcdedit /enum {badmemory}

    12) 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

    13) Make sure that there is no over clocking while troubleshooting.

    14) Sometimes there are problems in the bios that produce BSOD.

    15) To ensure that there are no improper bios settings please reset the bios.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computer’s CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow
    3 Easy Ways to Clear CMOS (Reset BIOS)
    How to Clear CMOS (AKA Reset BIOS Settings)


    16) 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


    17) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    18) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    19) Open administrative command prompt and type or copy and paste:
    chkdsk /r /v
    This may take hours to run so plan to run overnight.
    Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

    C:\Windows\system32>chkdsk /r /v
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y
    reboot


    20) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
    Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
    Read Chkdsk Log in Event Viewer in Windows 10


    21) For any BSOD:

    a) run the V2 log collector to collect new log files

    b) 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 > post a separate share link into the thread using one drive, drop box, or google drive

    When all drives are reattched:
    22) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
    Disk Management - How to Post a Screenshot of

    23) Download and install Minitool Partition Wizard > post an image of the results into this thread
    MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download.com



    24) Uninstall and reinstall: bcmwl63a.sys
    Code:
    bcmwl63a.sys	Broadcom 802.11 Network Adapter wireless driver	OEM - no wireless drivers available at
    http://www.broadcom.com/support/


    25) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)
    26) re-install the Nvidia GPU driver from the Nvidia website
    27) make sure that you check the clean install box and if available install the physx driver.

    Display Driver Uninstaller Download version 18.0.1.5 (or newer version if available)
    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller: How to use - Windows 7 Help Forums
    https://www.sevenforums.com/tutorial...r-how-use.html

    Download Drivers | NVIDIA
    https://www.nvidia.com/Download/index.aspx


    Code:
    bcmwl63a.sys Wed Feb  5 02:25:42 2014 (52F211A6)
    Code:
    nvlddmkm.sys Fri Dec  6 17:28:35 2019 (5DEB0043)


    Please post images of all steps / tests into the thread:

    Take Screenshot in Windows 10

    How to Upload and Post Screenshots and Files at Ten Forums
      My Computer


  4. Posts : 41
    windows 10
    Thread Starter
       #4

    Microsoft Windows [Version 10.0.18363.592]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>sfc scannow

    Microsoft (R) Windows (R) Resource Checker Version 6.0
    Copyright (C) Microsoft Corporation. All rights reserved.

    Scans the integrity of all protected system files and replaces incorrect versions with
    correct Microsoft versions.

    SFC [/SCANNOW] [/VERIFYONLY] [/SCANFILE=<file>] [/VERIFYFILE=<file>]
    [/OFFWINDIR=<offline windows directory> /OFFBOOTDIR=<offline boot directory> [/OFFLOGFILE=<log file path>]]

    /SCANNOW Scans integrity of all protected system files and repairs files with
    problems when possible.
    /VERIFYONLY Scans integrity of all protected system files. No repair operation is
    performed.
    /SCANFILE Scans integrity of the referenced file, repairs file if problems are
    identified. Specify full path <file>
    /VERIFYFILE Verifies the integrity of the file with full path <file>. No repair
    operation is performed.
    /OFFBOOTDIR For offline repair, specify the location of the offline boot directory
    /OFFWINDIR For offline repair, specify the location of the offline windows directory
    /OFFLOGFILE For offline repair, optionally enable logging by specifying a log file path

    e.g.

    sfc /SCANNOW
    sfc /VERIFYFILE=c:\windows\system32\kernel32.dll
    sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows
    sfc /SCANFILE=d:\windows\system32\kernel32.dll /OFFBOOTDIR=d:\ /OFFWINDIR=d:\windows /OFFLOGFILE=c:\log.txt
    sfc /VERIFYONLY

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 94% complete.

    Windows Resource Protection could not perform the requested operation.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.592

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18363.592

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    658688 file records processed.
    File verification completed.
    6203 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    550 reparse records processed.
    861554 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    550 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    101434 data files processed.
    CHKDSK is verifying Usn Journal...
    33726944 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    243001645 KB total disk space.
    158511256 KB in 454021 files.
    296412 KB in 101435 indexes.
    0 KB in bad sectors.
    772025 KB in use by the system.
    65536 KB occupied by the log file.
    83421952 KB available on disk.

    4096 bytes in each allocation unit.
    60750411 total allocation units on disk.
    20855488 allocation units available on disk.

    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-0A9PFM9\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\DESKTOP-0A9PFM9\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\WINDOWS\system32>
    C:\WINDOWS\system32>bcdedit /enum {badmemory}

    RAM Defects
    -----------
    identifier {badmemory}

    C:\WINDOWS\system32>

    - - - Updated - - -

    tenforums wouldent let me upload my pictures, so i put them in the onedrive in the folder disk checks. it blue screened while error checking the 1tb and 2tb drives. i can redo them in safe mode if need be. and i ran seatools a few days ago and all disk passed on long generic. working on step 19.
    edit, idk i guess it uploaded some of the pictures anyways.
      My Computer


  5. Posts : 38,545
    windows 10 professional version 1607 build 14393.969 64 bit
       #5

    For the Samsung drive test with Samsung Magician > post images for each category
    Samsung Magician Software | Samsung V-NAND SSD | Samsung Semiconductor Global Website

    Run HD Sentinel: (free or trial edition)
    Hard Disk Sentinel - HDD health and temperature monitoring
    Hard Disk Sentinel - HDD health and temperature monitoring
    Post images of each of these tabs into the thread:
    Overview tab
    Temperature
    SMART
    Disk performance
      My Computer

  6.   My Computer


  7. Posts : 38,545
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    Please post images of Sea Tools for Windows results when available.
    The testing can be performed overnight.

    Was Samsung Magician able to display SMART results?

    Run Crystal Disk standard edition: (all drives)
    CrystalDiskInfo – Crystal Dew World



    Code:
    Event[1601]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:51:00.079
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x600838 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    Code:
    Event[1606]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:00.206
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x2e85e8 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    Code:
    Event[1659]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x60b0c8 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1660]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x600d38 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1661]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x60a2e0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1662]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x60a2e0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1663]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x6009d0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1664]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x6009d0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1665]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x60a2e0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1666]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x6009d0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1667]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x60a2e0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1668]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x60a2e0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1669]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x6009d0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1670]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x6009d0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1671]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x6009d0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1672]:
      Log Name: System
      Source: disk
      Date: 2020-01-18T03:52:41.243
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x6009d0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    Code:
    Event[1837]:
      Log Name: System
      Source: disk
      Date: 2020-01-19T01:58:52.787
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    
    Event[1839]:
      Log Name: System
      Source: disk
      Date: 2020-01-19T01:59:17.884
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1840]:
      Log Name: System
      Source: disk
      Date: 2020-01-19T02:00:19.135
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
    
    Event[1841]:
      Log Name: System
      Source: disk
      Date: 2020-01-19T02:00:21.455
      Event ID: 154
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-0A9PFM9
      Description: 
    The IO operation at logical block address 0x0 for Disk 3 (PDO name: \Device\00000055) failed due to a hardware error.
      My Computer


  8. Posts : 41
    windows 10
    Thread Starter
       #8

    i exported the smart data to the onedrive, its named smart 970 evo.csv.
    which one is drive 3? Attachment 263951Attachment 263952Attachment 263953Attachment 263954

    - - - Updated - - -

    and i also added a second logv2 zip in the one drive. it blue screened when i was doing nothing.
      My Computer


  9. Posts : 38,545
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    For the crystal disk images there are scroll bars on the right.
    Please re-post images so that all rows can be viewed.

    When available please post HD Tune, Sea Tools, HD Sentinel, and chkdsk /r /v results for each drive.
      My Computer


  10. Posts : 41
    windows 10
    Thread Starter
       #10

    Attachment 264009Attachment 264010Attachment 264011Attachment 264012Attachment 264013

    - - - Updated - - -

    when i try to upload picture sometimes it gives me an error here say its not a valid image. so ive put them in the folder disk check on the onedrive.

    - - - Updated - - -

    just added folder chkdsk log to onedrive. i ran it for c drive, do you want me to run it for each drive?

    - - - Updated - - -

    Attachment 264020

    - - - Updated - - -

    finished steps 24-27. bcmwl63a.sys is no longer on my pc, i got a new wifi card a few weeks ago. and i just updated the GPU to 441.87. although what results do you want from minitool partition?

    - - - Updated - - -

    just reread youre message to do all drives for chkdsk, they are running now for G F and H
      My Computer


 
Page 1 of 9 123 ... LastLast

  Related Discussions
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 03:15.
Find Us




Windows 10 Forums