Random BSOD (probably) caused by graphical driver issue

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 19
    Windows 7 Home Premium 64 bit
    Thread Starter
       #11

    Thanks, I was a bit confused on how OneDrive works. I just saw it as some extra storage space on my PC that somehow synchronizes with the online service. Turns out I have lo log on the Live website to actually upload files to the folders there.

    I'm uploading the CBS.log file to OneDrive right now, which is gonna take a while since it's huge. So, if I store it in the online Public folder and post the link to the folder here, you can view it? Exactly which link do you need?

    The BSOD problem may be (partially) solved. My brother (who assembled this PC) reminded me about the way it used to crash back when it was new (5 or 6 years ago), which turned out to be caused by faulty BIOS settings. The crashes due to the (fixed) overheating caused Windows to suggest a system recovery (or something like that), which didn't completely succeed but may have reset the BIOS settings to default. So I looked up the stuff we marked in the motherboard manual, entered BIOS and manually changed the DRAM Bus Voltage to 1.65. That was yesterday, and so far today I haven't had any BSODs (though I haven't been doing a lot on the PC).

    So, the BSODs just might (partially) be history, but I'd still love to hear if there's something wrong with my drivers. At least, that's what BlueScreenView seems to suggest.
      My Computer


  2. Posts : 7,050
    Windows 10 Pro
       #12

    In onedrive, right click on the file/folder and click share.
    In the pop-up click on Create link/url (or whatever it is), choose what you want for the rights and click on create link/url.
    Copy the link and paste it in your post.
      My Computer


  3. Posts : 19
    Windows 7 Home Premium 64 bit
    Thread Starter
       #13
      My Computer


  4. Posts : 7,050
    Windows 10 Pro
       #14

    The file is 500MB+, too big to open for my notepad or any other program I use.
    If you have Ccleaner, run it to clear this file up, but without clearing dumps
    If you are using a program like Ccleaner please stop using it while troubleshooting.
    This because programs like Ccleaner remove dump files that are needed to troubleshoot.
    Or configure Ccleaner to not remove dump files:
      My Computer


  5. Posts : 19
    Windows 7 Home Premium 64 bit
    Thread Starter
       #15

    I just ran CCleaner for the first time in way too long, it removed like 2.5 GB of crap. Memory dumps were left alone as you instructed.

    Then I ran the "scannow" command again and looked for the cbs.log file, but it seems like it's still over 700 MB. Is it still "refreshing" or something, should I try again tomorrow?
      My Computer


  6. Posts : 7,050
    Windows 10 Pro
       #16

    Make sure in the System part Windows Log Files is checked.
      My Computer


  7. Posts : 19
    Windows 7 Home Premium 64 bit
    Thread Starter
       #17

    It was, and the file is still huge.

    I googled this problem and might have a solution:

    https://social.technet.microsoft.com...nservermanager

    Start/Stop Windows Modules Installer service in Windows 7 from Services, Regedit or CMD

    In short: temporarily disable the Windows Module Installer service, delete the CBS.log file and run "sfc/scannow" again to create a new one.

    Does that sound like a plan to you?
      My Computer


  8. Posts : 7,050
    Windows 10 Pro
       #18

    Are you able to delete the file manually?
    UAC will prompt, just allow.
      My Computer


  9. Posts : 19
    Windows 7 Home Premium 64 bit
    Thread Starter
       #19

    Deleted, recreated (only like 1 MB now), uploaded, posted:

    https://onedrive.live.com/redir?resi...int=file%2clog

    Hope you can find the driver problem if there actually is any. I'm calling it a day.
      My Computer


  10. Posts : 7,050
    Windows 10 Pro
       #20

    Repair install
    Code:
    2015-10-17 23:58:13, Info                  CSI    00000367 [SR] Cannot repair member file [l:18{9}]"ehres.dll" of Microsoft-Windows-ehome-ehres, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-10-17 23:58:13, Info                  CSI    00000368 [SR] This component was referenced by [l:176{88}]"Microsoft-Windows-MediaCenter-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.MediaCenter"
    2015-10-17 23:58:13, Info                  CSI    00000369 Hashes for file member \??\C:\Windows\ehome\ehres.dll do not match actual file [l:18{9}]"ehres.dll" :
      Found: {l:32 b:lhtTn3REVhB3MudeO6nKepJ6n8i6LAV4uMY25qTZFaw=} Expected: {l:32 b:GibbbuCnCqSVlIpo9jRTxqvNduH8zq6Qn5IvKNJ38Q0=}
    2015-10-17 23:58:13, Info                  CSI    0000036a Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-ehome-ehres_31bf3856ad364e35_6.1.7600.16385_none_ae00f59c6a2932c3\ehres.dll do not match actual file [l:18{9}]"ehres.dll" :
      Found: {l:32 b:lhtTn3REVhB3MudeO6nKepJ6n8i6LAV4uMY25qTZFaw=} Expected: {l:32 b:GibbbuCnCqSVlIpo9jRTxqvNduH8zq6Qn5IvKNJ38Q0=}
    2015-10-17 23:58:13, Info                  CSI    0000036b [SR] Could not reproject corrupted file [ml:520{260},l:40{20}]"\??\C:\Windows\ehome"\[l:18{9}]"ehres.dll"; source file in store is also corrupted
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  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 10:11.
Find Us