Windows 10: Seemingly random BSOD, Memory? Solved

  1.    10 Jul 2017 #1

    Seemingly random BSOD, Memory?

    I recently tore down my PC to do some dusting, and noticed that one of the latches for my ram was broken. It still locks the ram in place, but it opens too far. I put the ram in and didn't think about it beyond that, but now I'm getting lots of random bluescreens.

    At first they were happening while playing games, so I assumed it was my graphics drivers at fault. I did a clean uninstall of those using DDU, and reinstalled them, but the crashing continues. The stop error is different every time, for the most part. One that happens somewhat frequently is "SYSTEM_SERVICE_EXCEPTION" from what I've read online, that's supposed to be followed with a driver ID, but it never is. I've run both SFC /SCANNOW as well as a CHKDSK and both came back clean.

    Could some dust have gotten in a ramslot and made it intermittently faulty? The ram is relatively old, but it's never been pushed hard, so I don't see why it would randomly fail. Seems taking it apart was the catalyst. I haven't run a MEMTEST, because I plan on removing the ram and blowing the slots clean, properly this time.

    Included is the zip that DM Log Collector created, boy the "generating msinfo report" portion seems to take forever.
      My ComputerSystem Spec

  2. Posts : 19,887
    windows 10 professional version 1607 build 14393.969 64 bit
       10 Jul 2017 #2

    {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Scott\AppData\Local\Microsoft\Windows\UsrClass.dat' was corrupted and it has been recovered. Some data might have been lost.
    The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume9.(A device which does not exist was specified.)
    Windows failed fast startup with error status 0xC000007B.
    VDS fails to write boot code on a disk during clean operation. Error code: 80070002@02070008
    Crash dump initialization failed!
    The IO operation at logical block address 0x722f882 for Disk 4 (PDO name: \Device\00000065) failed due to a hardware error.
    BugCheck 3B, {c0000005, fffff80135251d0e, ffff9880e18cc0e0, 0}Probably caused by : memory_corruption
    BugCheck 1E, {ffffffffc0000005, fffff802d2ee6db7, 0, ffffffffffffffff}Probably caused by : memory_corruption

    Open administrative command prompt and type or copy and paste:

    1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)

    2) sfc /scannow

    3) dism /online /cleanup-image /restorehealth

    4) chkdsk /scan

    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 copy > paste into the thread

    5) turn off windows fast startup:
    Turn On or Off Fast Startup in Windows 10 Windows 10 Performance Maintenance Tutorials

    6) Run memtest86+ version 5.01 for at least 8 runs.
    This may take many hours so plan to run it overnight.
    Memtest86+ - Advanced Memory Diagnostic Tool
    When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.
    Memory problems. - Microsoft Community
    MemTest86+ - Test RAM Windows 10 BSOD Tutorials

    7) run one of the SMART tests on your drives:CrystalDiskInfo - Software - Crystal Dew World: CrystalDiskMark - Software - Crystal Dew World
    Software - Crystal Dew World
    HD Tune:
    Hard Disk Sentinel - HDD health and temperature monitoring: Hard Disk Sentinel - HDD health and temperature monitoring

    When the SMART test has completed open the Microsoft snipping tool and make images of the results to post into the thread.
      My ComputerSystem Spec

  3.    10 Jul 2017 #3

    I'll run Memtest86 tonight, though I did run the built in windows version, and it came back with no errors.

    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.

    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 /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.14393.0

    Image Version: 10.0.14393.0

    [==========================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.


    Winver result: Version 1607 (OS Build 14393.1358)

    I had tried to turn fastboot off before, but for some reason checking it again, it's on again. I turned it off once more.

    P: I rarely access this drive, and it was a "salvage" from another PC. That error is likely very old.
      My ComputerSystem Spec

  4.    10 Jul 2017 #4

    two more BSOD's, different stop messages for both.
      My ComputerSystem Spec

  5. Posts : 19,887
    windows 10 professional version 1607 build 14393.969 64 bit
       10 Jul 2017 #5

    The above adobe file was not able to be opened.

    1) When you have bsod please post a new zip: BSOD - Posting Instructions - Windows 10 Forums

    2) Run Sea Tools for Windows in SMART, short, and long generic on your drives and post the results into the thread.
    How to use SeaTools for Windows

    How to use SeaTools for Windows

    3) update windows and post any failed KB# or error code into the thread
      My ComputerSystem Spec

  6.    11 Jul 2017 #6

    While I have no idea what "adobe" file you saw, I seem to have solved the issue. It was a bad stick of ram or a bad ram slot. Removing two sticks from their paired up slots, I've had no more BSODs.

    The minidumps file was a '.7z' format, basically a better version of a '.zip'. Surprised you didn't know that, as you presumably work on PCs all day.
      My ComputerSystem Spec

  7. Posts : 19,887
    windows 10 professional version 1607 build 14393.969 64 bit
       11 Jul 2017 #7

    Glad you got it fixed.

    Left clicking on a zip file uses the default 7zip.
    Multiple zip files can be opened without issues.
    These are the images when attempting to open the file in post #4:

    Attachment 143441

    Attachment 143439

    It was peculiar that it did not open like other zip files.
      My ComputerSystem Spec

  8.    11 Jul 2017 #8


    u have to reset the file type association for *.7z files:

    Choose Default Apps in Windows 10 Windows 10 Apps Features Tutorials
    Restore Default File Type Associations in Windows 10 Windows 10 Customization Tutorials

    i can normally extract this archive with 7zip
      My ComputerSystem Spec


Related Threads
I recently essentially built a new computer (old case and old ssd+hdd, everything else new) and have been getting BSODs. I did the build around a month ago and got a couple BSODs less than a week later but they stopped so it seemed fine. However,...
I have been having BSOD at random times, mostly while playing games, last few have been while i have been playing overwatch. The error it says is driver_irql_not_less_or equal (etd.sys), mini-dump files below
BSOD Watchdog on Windows 10, Seemingly Random in BSOD Crashes and Debugging
Hi everyone! This is my first post here. My computer has been fine until I updated it to windows 10 from win 8. I have been getting Watchdog violations randomly every 30 min to 3 hours since the update. One error report analyzed via WhoCrashed...
Hi everyone, I'm having an issue with my new laptop running Windows 10. After increasingly short periods of time, I am experiencing a BSOD seemingly at random, with the error message "DRIVER_POWER_STATE_FAILURE". I have looked into my minidump...
Hi, Over the past couple of days I have been having reasonably frequent BSODs. Some have not created a dump file. I cant pinpoint anything in particular but it seems to be pointing to a driver issue but never identifies the driver from what I can...
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:57.
Find Us