Frequent BSODs, DISM

Toggle sidebar Toggle sidebar
E

evilcirc

Reputable
Aug 5, 2015
10
0
4,510
Hi, I've been having multiple frequent BSODs lately, I've attempted to resolve some of them through sfc.exe and DISM in an elevated console, however both fail. When I enter sfc.exe I receive the error "Windows Resource Protection found corrupt files but was unable to fix some of them," I also receive similar results while in safe mode. When I run DISM as such: DISM /Online /Cleanup-Image /RestoreHealth I receive error 0x800f081f and the text reads the source files could not be found.

Here is my CBS log: https://onedrive.live.com/redir?resid=2A698C6214CC190!365&authkey=!AL-za2BRgtvbpgg&ithint=file%2ctxt

I am currently running on Windows 10, however these BSODS and errors still occur just as they did on Windows 8.1.

Plus I think my RAM may be failing, I've received a few MEMORY_MANAGEMENT BSODS and when I run Windows Memory Diagnostic hardware problems are detected.
Can someone please help me with my PC?
Thanks
 
Sort by date Sort by votes
update BIOS to get new default RAM timings, then boot and run memtest86 on its own boot image to test your RAM to confirm your hardware is ok.

you might want to clear windows update cache also then update your ethernet drivers and rerun the update or dism command.
https://rahuldpatel.wordpress.com/2008/12/02/clearing-windows-update-cache-upon-update-failure/
 
Upvote 0 Downvote
Ok so I ran 2 passes of memtest86 and received results as such:
Test 1: 0 Errors
2:0
3:3
4:13
5:17
6:50
7:49
8:0
9:3
10:0

So if I'm correct on my interpretation it means I should replace my RAM stick yes? If so I would also like to know if there could be a problem with my motherboard.

By the way, my BIOS had already been updated, and I switched the RAM into the other slot of the MOBO earlier and still received MEMORY_MANAGEMENT BSOD

Also, I attempted to clear the windows update cache however the console said that it could not be stopped after the net stop wuauserv command.
 
Upvote 0 Downvote
Pull out ram and run on single sticks until you figure out which stick is bad.
run memtest86 on each stick. Also, and software you installed with bad memory settings is suspect.
(may be corrupted on disk or may get corrupted when copied from disk to memory during booting)

just make sure you reset the BIOS to defaults before you conclude the ram is bad. Some systems have automatic memory overclocking.





 
Upvote 0 Downvote
I only have one stick. Also what do you mean by software with bad memory settings? If you mean some software I've installed is messing with my RAM then I just reset this PC and upgraded to Windows 10, so all I have installed is Google Chrome and MSI Live Update 6.
 
Upvote 0 Downvote
overclocking drivers like msi overdrive can cause bugchecks



 
Upvote 0 Downvote
the /cleanup-image only works on windows 8.1 and it requires unblocked access to a windows update servers.

confirm you have window 8.x
confirm you have internet access at the time you run the command.
some hacked versions of windows have this blocked so windows update will not overwrite the hack and expose the invalid license.

confirm you have room on your drive to store the downloaded files.
 
Upvote 0 Downvote
no, the error would make sense if the winodow 10 update servers were getting hammered and just did not respond in time to prevent a loss of connection. I would just check for any current updates again.



 
Upvote 0 Downvote
just looked at my log, I get the same errors as in your log.
basically a warning that the same security descriptor is in a list twice for certain directories.
(i assume it has something to do with the fact that I ran the windows 10 prerelease)

it also complained about some .png files with incorrect file hashes. I think it would be a bug in the file hashes.

in your case it complains about the hash for "ChsPinyin.lm" https://support.microsoft.com/en-us/kb/2937781
and for "adcjavas.inc"
as far as the sfc.exe command it could not fix it because both the normal copy and the backup copy in the hidden driver store are "corrupted"

\C:\Program Files (x86)\Common Files\System\msadc"\[l:24{12}]"adcjavas.inc"; source file in store is also corrupted

generally, the only to get these fixed would be run CMD.exe as an admin, change directory to c:\windows\system32 and run
DISM.exe /Online /Cleanup-Image /RestoreHealth

But, who knows if it is a windows 10 bug or not. I would expect it is. I would not expect that error to be on my machine as it relates to "Chinese Pinyin IME"


Sorry if this is not much help, my guess it is a bug that went unnoticed because it is only in the log files. These type of errors would not be fixed in the late stages of shipping a new operating system. kind of a bummer sfc.exe always reports corruption though. I will check my wifes machine, she did not have the pre release installed.
----------
log shows a bunch of directories with duplicate security descriptors.
you have not taken ownership of some of the system directories ? or changed the startup method of the trusted installer service?
ie the "windows modules installer" service is running when you start cmd.exe as an admin then run the:
net.exe start


I will run the command on my windows 10 and see if it is a bug or in my log file.
 
Upvote 0 Downvote
Well that's pretty interesting, I actually haven't installed the Chinese Pinyin keyboard through windows on this version, however I did before I reset my PC. Also I have never done anything with the system directories or changed anything about trusted installer service as far as I know, however I'm unsure as to what that pertains to. Also, windows module installer is not on the list when i run net.exe start.
 
Upvote 0 Downvote
I looked at my wife's machine that was not in the prerelease but did do a windows 10 upgrade from a CD.
some of the same errors and a few more that I did not get.

I suspect it is just bugs related to the upgrade process. Maybe someone who does a clean install can run the
sfc.exe /scannow
command and see if they get errors.



 
Upvote 0 Downvote
Ok well thanks for all the help so far, I'm going to do a system reset and leave it on windows 8.1 for now.

------------------------------------------------------------------------------

Actually since I haven't received any BSODS since I changed RAM i'm going to use this for a while and see what happens.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom