[Win 10] Multiple BSODs, cannot identify the cause

[acole]

Hi there guys,


I was recommended to this site from bleepingcomputer dot com.

[Win 10] [Cbs.log][Error running sfc /scannow] - Windows 10 Support

Basically this computer (my brothers) is having a lot of issues. My brother is out of the country at the moment and I would like to have this long time issue fixed for him as a surprise by the time he gets back. There is no rush however, please do not see this as me asking for swift replies, I just am stating that I have good intentions at heart and I just wanna be there for my bro.

The cbs log is on the first page of the link above, I still get the same error every time I try to run sfc /scannow. I am happy to re-run any tests you all require.

I also replaced the RAM which fixed the issue for a week or so and then I am getting blue screens again. My guess would be that the "fix" was just incidental, and that the same problem was never fixed and just didn't happen by chance during this time.

I have updated drivers and still have issues with trying to check Windows.

This pc was completely installed on a fresh install of windows 10 about a month or so ago. It was bluescreening and having the SAME sfc /scannow issues even prior to this new install - but that was on Windows 7. A long with the random blue screens and the obvious issues with running sfc /scannow, I also have problems trying to run DISM.

As stated, RAM is not the issue because I totally replaced ALL the ram and I get the same bsod's. I removed my brothers overclocking and still the same problem. I checked temperatures and they are fine and also ran Prime95 for about 8 hours with no errors.

All of my problem solving attempts are logged in the thread I linked above.

My goal?

To fix the sfc /scannow so that it runs properly, same as DISM and that I can fix windows so those commands run properly with no errors (ie they find no errors when I finally run them). I would also like to fix the blue screen issue - or at least know what component is broken so that I can fix it for my bro by the time he gets back - around 2 and 1/2 weeks time. My brother is very ill and he has been stressing over this pc for about 3-4 months now. He is a games tester and basically he took some personal time off of reflection and to get away from the stresses of life for a while - and to get away from this pc that turns him into a raging inferno most of the time! Ha Ha. :grin1:

I would really appreciate any help here and would love to finally come to a conclusion. If I really have to, I will even buy the new pc parts required so that my bro can enjoy his pc again.


Many thanks,

Joe

 

[Aura]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Hi Joe :)

My name is Aura and I'll be assisting you with your issue. Do you still need help?

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Hi,

Sorry for the delay.

Yes I do. The computer has been very unstable so I haven't been using it much.

The same errors (the link I supplied, first page has the cbs log errors) still apply.

Look forward to a reply.

Joe.

 

[Aura]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Sorry for the delay. Here, follow the instructions below to replace one of the 2 corrupt files flagged by SFC.

SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.

• Download SFCFix and move the executable on your Desktop;
• Download the attached SFCFix.zip and move the archive to your Desktop;
  Note: Make sure that the file is named SFCFix.zip, do not rename it.
• Save any work you have open, and close every programs;
• Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it;
  
  
• SFCFix will launch, let it complete;
• Once done, a file will appear on your Desktop, called SFCFix.txt;
• Open the file, then copy and paste its content in your next reply;

SFCFix.zip

For the second file, please follow the instructions in the thread below.

https://www.sysnative.com/forums/wi...tion-sfc-dism-windows-10-update-1511-th2.html

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

SFCFix version 2.4.8.0 by niemiro.
Start time: 2016-01-27 19:22:43.521
Microsoft Windows 10 Build 10586 - amd64
Using .zip script file at C:\Users\a_col\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_microsoft-windows-font-truetype-simsunb_31bf3856ad364e35_10.0.10586.0_none_1d80224ec6470747\simsunb.ttf

Successfully copied file C:\Users\a_col\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-font-truetype-simsunb_31bf3856ad364e35_10.0.10586.0_none_1d80224ec6470747\simsunb.ttf to C:\WINDOWS\winsxs\amd64_microsoft-windows-font-truetype-simsunb_31bf3856ad364e35_10.0.10586.0_none_1d80224ec6470747\simsunb.ttf.

Successfully restored ownership for C:\WINDOWS\winsxs\amd64_microsoft-windows-font-truetype-simsunb_31bf3856ad364e35_10.0.10586.0_none_1d80224ec6470747\simsunb.ttf
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_microsoft-windows-font-truetype-simsunb_31bf3856ad364e35_10.0.10586.0_none_1d80224ec6470747\simsunb.ttf
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.8.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-01-27 19:22:44.074
Script hash: o0cgjF3jJnOAomXM+RKIa+ReCClXmPPgRUvMwmTdRUQ=
----------------------EOF-----------------------

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

SFCFix version 2.4.8.0 by niemiro.
Start time: 2016-01-27 19:25:49.482
Microsoft Windows 10 Build 10586 - amd64
Using .zip script file at C:\Users\a_col\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll

Successfully copied file C:\Users\a_col\AppData\Local\niemiro\Archive\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll to C:\WINDOWS\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll.

Successfully restored ownership for C:\WINDOWS\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
Successfully restored permissions on C:\WINDOWS\winsxs\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.8.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-01-27 19:25:49.583
Script hash: SPhJgk57HkoTrdMLtWrtMfeOccJRwa6Z8fwFua8SZKg=
----------------------EOF-----------------------

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Hi,

I ran sfc /scannow after doing those two steps and I still got "corrupt files found".

Did I do something wrong?

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Hi,

I rebooted my machine and re-ran sfc /scannow and this time it did not find any violations!

Hooray!

I only have one other issue that just popped up and it seems odd - but the Razer Ultimate keyboard no longer is recognized via the Razer control panel. No matter how many times I reboot it won't show up.

Could it be the keyboard causing blue screens?

I haven't had a BSOD for about two days, but I haven't been using the pc much, so I am not sure if the problem is solved or not.

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

The keyboard has finally returned. I had to uninstall and reinstall the drivers for it - no idea why it went haywire.

 

[Aura]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Sorry I was asleep.

According to your CBS.log, the only corrupt file left was opencl.dll, but it got repaired using the clean copy from the store (which we replaced). So on that side, you're good :) Let's see if DISM returns clean logs as well.

DISM - Fixing Component Store Corruption
Follow the instructions below to run a DISM operation on your system.

• On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
• On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
• Enter the command below and press on Enter;
  

  DISM /Online /Cleanup-Image /RestoreHealth

• Let the scan run until the end (100%). Depending on your system, it can take some time;
• Copy the C:\Windows\Logs\DISM folder and C:\Windows\Logs\CBS\CBS.log file on your Desktop, then right-click on it, go to Send to... and select Compressed .zip archive;
• Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;

Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the DISM scan is completed, it won't contains the information from the scan anymore. So archive it and upload it as soon as you can.

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Okay I ran DISM and it said "restore ended successfully".

Here is the log for CBS and DISM

https://drive.google.com/open?id=0B1y77xplXXLOUXZUNE81R1RRdm8

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

(double post sorry, but I will add...)

What should I do about the Blue Screen crashes, is there a way to find out what is causing it? I know it's not the RAM or the Video card as both were replaced and they still occur. Also it even happened a few months back when the system was on Windows 7.

Anyway thanks for your help so far, it's been great!

 

[Aura]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

It seems that I need to ask for your permission to download that file. Is it possible to have a public download URL for it? Also, if DISM returned a success message, it means that it did what it had to do :)

As for BSODs, I suggest you to head in the BSOD, Crashes, Kernel Debugging for that kind of assistance. Simply follow the instructions in the preparation guide and create a new thread :)

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Oh I have never used Google Drive before, sorry for that inconvenience. I will try and find a better way to upload it for you.

Could you possibly have this moved to the BSOD crashes forum. I have started this thread about my BSOD a number of times and I would hate to have to restart all my troubleshooting again from the start. At least this thread and the one from bleeping computer has the trouble shooting trail.

Anyway let me upload those logs somewhere else.

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Here you go.

Mega File Upload - Logs.7z

I hope this works!

 

[Aura]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

I can move this thread in the BSOD section, however I'll have to change the thread title to something that reflects your BSOD issues. Is that okay with you? If you start a new thread, you can just copy/paste the part about your BSODs in the first post, and follow the instructions in the procedure guide to get the required logs, or get them from your thread on BleepingComputer.

 

[acole]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

Sure,

Feel free to change the title as you see fit.

Did the upload work for you in the link I provided?

Cheers,

Joe

P.s My brother is going to be over the moon when he sees the Windows files are no longer corrupt, he has been wallowing over that for over 3 months! Also if you guys can save the pc from it's BSOD woes, it will save my brother a lot of money. He told me he want's to buy another pc when he comes back from his trip overseas, and he really doesn't want to - mainly because hes a pensioner (he is ill) and also because he doesn't see much of a benefit or bang-for-buck worth. The only reason he has made plans to do so is because he works with some games testing and the new (volunteer) job is coming up in February and he needs his pc working properly and he hasn't been able to solve this BSOD problem or pinpoint what hardware is the issue and he has basically given up. Alas I want to surprise him when he comes home. (fingers crossed).

 

[Aura]

Re: [Win 10] [Cbs.log][Error running sfc /scannow]

It did and the logs are clean, so my job here is done :) Moving your thread to the BSOD section now.

 

[acole]

Thanks so much,

I am really impressed with your work!

Thanks again and happy new year to you! (It's still January so I think I am allowed to still say that right?)

Cheers,

Joe

 

[acole]

Hi to the next person who will work on this thread,

A simple synopsis of what has happened so far.

This machine has a lot of random BSOD, and I am not sure why.

So I ran things like sfc /scannow to see if it was because of windows and I did find some errors I couldn't fix with that command and with DISM which Aura has kindly fixed. I haven't had a BSOD for the last couple of days because I haven't used the system much as it has been very randomly volatile...I know I put a redundant word there, but the crashes are truly random.

They usually have the error STOP 1a Memory Management.

The Video card and RAM have been completely swapped and the BSOD persist - so it can't be the RAM or the GPU. Windows was installed cleanly to see if it was Windows, but same issue - we tried Win 7 and Win 10...without luck.

All drivers were updated countless times. We tried the system with "optimized" settings, with and without my brothers overclock. We checked temperatures and they have always been well within limits, even when Prime95 was run for 6 hours or so straight. The system has a closed unit water cooler from Corsair for both the CPU and GPU.

We also ran chkdisk and I don't think it reported errors, but I am not 100% sure.

Anyhow,

I am willing to do any tests, but my brother does not want me to update the BIOS. He stated he updated the BIOS (to F8 version I think) when the manufacturer advised him to do so when the motherboard was repaired (I think the video card slot or something was fixed). He was advised that the BIOS version was fine and there was no reason to update it and that updating it could cause more problems, especially with the RAID 0.

I hope this info helps.

Thanks again guys!

Joe.