Windows 10: win 10 pro 64 stop code 0x0000007b 0xffffffffc0000034

win 10 pro 64
SSD 500gb samsung 850 pro

stop code : inaccessible boot device (probably 0x0000007b)
0xffff----------1810 <--the middle numbers keep changing with each restart
0xffffffffc0000034
0x0000000000
0x0000000000

same result with safe mode

I am quite sure it is a hard drive or partition driver issue that causes the windows to lose connection with the partiotion once loaded so I could not even get a minidump or log of the issue...
windows starts loading drivers and logging but loses touch with the partition and crashes and can not save the crash log since it has no access to the partition.

This came about after a bad install of acronis trueimage 2017 NG (upgrade from 2016)
per acronis I have removed traces of acronis drivers from regedit (snapman.sys etc) but removing that did not help, probably there is a disconnect or missing driver now that snapman acronis driver is gone.

anyway I need a way to log the boot or safemode boot to see at what point the system crashes.

I have tried remaking the boot etc... that is not the issue
DISM can not access the image of c:\windows log dism can not access image error 2 - Pastebin.com
Sfc offline does not work either
chkdsk done and all is good
hardware tests all are okay
bios was untouched so that could not be the issue but in case I have tried to disable and enable virtual drive and also factory reset the bios it is not UEIF (it is older HP envy 17t 3200 that was shipped with windows 7 originaly)

:)

 

Memory_Management Stop Code on Win 10 Pro 64

You need to place copies of the files in your OneDrive NOT shortcuts to the files!

 

Memory_Management Stop Code on Win 10 Pro 64

New link; I hope:

Shared items 12-16-2016

 

Attachment 138466Attachment 138467Attachment 138468Attachment 138469Attachment 138470Attachment 138471Attachment 138472

System restore failed again makes sense since there is no access to the partition
startup recovery ran 20 times with no fix
do not have a back up to restore
installed apps are important to me so I would like to do all possible to avoid reinstalling everything

the blue screen code changes slightly after each restart as you can see in the images but some parts of it stau the same that are noted in the post above

 

What hard drive tests did you run?

 

HP boot test
smasung magician test for the SSD
chkdsk
etc

 

You may be able to fix your boot to get back to the desktop.
Creating a bootable windows 10 iso can enable you to get back to windows 10.
Download Windows 10

 

Sorry, but I need you to be specific in what hard drive tests you ran.
Some don't check everything on the hard drive (is the hard drive failing in regards to speed, too many bad sectors or the overall health)

The 0x7B has causes where a clean install won't fix the problem, since we are not aware of the health of your laptop we need specific information.

 

as I said this is NOT a hardware issue.
I made an image backup and installed a new windows on the SSD
seams to be a permission issue with the old windows folder. it does not let dism or other windows repair to touch it even when online from another windows on the same SSD

dism /image:c:\windows.old\windows \cleanup-image
gives me the same error
can not access the image

at this point I need 1) a way to fix the permission on the windows.old from new windows
or perhaps an easy way to transfer most my apps and settings and files from the old windows to the new one

chrome, firefox sessions, open links, passwords. windows setting etc

 

Please allow me to explain the boot process with MBR.
When you power on the system, the BIOS is initialized to execute the POST (Power On Self Test) to ensure the hardware works.
Then the BIOS selects a boot device, reads the MBR of the device to the memory and handsover control to the MBR. The MBR scans for a partition that is marked as active which gives the signal that the partition is bootable. MBR reads the first sectors of the partition which contains executable code to which control is given to handle the rest.

The most usual causes for this error are

• Hard drive,
• File system,
• Boot sequence errors,
• Device driver,
• Virus infection (in particular check the MBR)

If you don't think the file system and hard drive are the cause, then I'd suggest to make sure the boot order in the BIOS is proper so the hard drive is first in the list.
You may be able to fix boot problems with MBR using Macrium Reflect preinstalled in the WinPE at Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums

 

The STOP 0x0000007B errors are caused by device driver problems, viruses, data corruption, and sometimes even hardware failures. You have tried update your drivers. If the problem still persist, try the steps:

• Run chkdsk on your hard drive. ...
• Perform an extensive test of your hard drive. ...
• Run the fixmbr command to create a new master boot record. ...
• Clear the CMOS. ...
• Update your BIOS. ...
• Update the hard drive controller's firmware if possible. ...
• Repair your Windows installation. ...
• Perform basic STOP error troubleshooting.

 

thanks for your help guys but this not an oridinary problem

it has to do with a permission that was assigned to my files by acronis

After installing a new windows 10 , I brought over some files from the old system in program files etc
the files I brought I can not delete easily , I have to use apps to override their permissions.
looked at the properties> security and the administrator is under a name I have not seen and can not change..

 

Those folders are protected by Windows, once moving files into the folders the files are automatically protected and many cannot be accessed at all.

My first question is why you moved old system files to the new system folder, but that doesn't help us. The easiest way I can think of that solves this kind of issues is a clean install.
A more difficult way, use a WinPE (see my previous post) and open a file manager. From there you may be able to change what you want to change, Windows cannot interfere then. If something goes wrong the risk exists that you're further gone into this problem.

 

The operating system may be able to be fixed. However this would be without boot logging. Let us know whether you want to attempt to fix the os.

 

how can I fix the OS

I can access it with WinPE..