Multiple BSODs over the month, no clear root cause


  1. Posts : 2
    Windows 7 Home 64X
       #1

    Multiple BSODs over the month, no clear root cause


    I built this computer about a year ago, and I've had BSODs every one or two weeks for just as long. The problem is that I've never been able to tie them to one program, one driver, or one piece of hardware. All of the diagnostics and general health checks I've run on the system and its hardware come out clean.

    Usually the BSODs are far enough apart that I forget about them until the next one comes up, but I've had three or four in the last week alone. Virus scanner shows nothing, and the dump reports through BlueScreenView remain unhelpful because all of the drivers involved seem to be essential system drivers and processes. There's got to be something behind all this, but I can't figure out what. Any suggestions?
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2


       Note
    Do not start the trial version of MalwareBytes



    • System File Checker
      • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    • Run Disk Check in Windows 7
      • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log



    • Test and Diagnose RAM issues with MEMTEST86+
      • Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
        • Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. RAM - Test with Memtest86+

    Uninstall the software below:
    AsrAppCharger.sys Tue May 10 14:28:46 2011 (4DC8F73E)
    ASRock App Charger Likely BSOD cause.
    Driver Reference Table - AsrAppCharger.sys

    Let us know the results.
    Code:
    Code:
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Thu Oct 31 02:05:45.452 2013 (UTC + 6:00)
    System Uptime: 0 days 5:37:28.264
    BugCheck 1A, {5003, fffff70001080000, a4f27, 8fdc700149e5e}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45f7d )
    BUGCHECK_STR:  0x1a_5003
    PROCESS_NAME:  Photoshop.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Wed Oct 30 20:27:25.065 2013 (UTC + 6:00)
    System Uptime: 0 days 0:01:12.877
    BugCheck 3B, {c0000005, fffff88007272890, fffff8800aa1fb60, 0}
    Probably caused by : rdbss.sys ( rdbss!memset+80 )
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  svchost.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sun Oct 27 03:11:55.924 2013 (UTC + 6:00)
    System Uptime: 0 days 4:31:46.111
    BugCheck 27, {baad0073, fffff88014a11ef8, fffff88014a11750, fffff880073b90c9}
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0x27
    PROCESS_NAME:  Bridge.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
    Debug session time: Sat Oct 19 21:28:07.718 2013 (UTC + 6:00)
    System Uptime: 0 days 0:36:30.904
    BugCheck D1, {fffff8800e303762, 2, 1, fffff880073290c5}
    *** WARNING: Unable to verify timestamp for aswTdi.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswTdi.SYS
    Probably caused by : memory_corruption
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  AvastSvc.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer


  3. Posts : 2
    Windows 7 Home 64X
    Thread Starter
       #3

    Thanks! I'll run through all these steps in the morning and get back to you. One catches my eye, though-- why Microsoft Security over Avast? I've always heard Avast recommend over MS security because Avast offers greater levels of protection under its free plan.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd
All times are GMT -5. The time now is 04:56.
Find Us