Author Topic: 0x80070005 error (Read 29343 times)

ruggb · « **on:** October 08, 2014, 09:38:05 am »

I can't create restore points - QRM Plus says SR is not enabled - it is.
SR gives me this error (0x80070005) = some indication that it is a reg permission issue.
I have used the reset permission utility but no fix. (both tweakling.com and win resource kit versions)

firewall/AV turned off. (Vipre)
set and reset SR config a couple times.

Where might the issue be????????

Shane · « **Reply #1 on:** October 08, 2014, 12:24:23 pm »

Did you also run the file permissions and serviced permissions repair from the program as well?

Use my Windows Repair and when you get to the repairs uncheck them all and only do the 3 permissions (Registry, File, Services) and then reboot and see how that does.

Shane

ruggb · « **Reply #2 on:** October 09, 2014, 03:12:19 pm »

loaded and ran 2.9.2 - unselected all but 3 repairs - run - rebooted.
same issue -- same symptoms.
QRM plus does not return an error - it just says SR is turned off -- which it is on drives D & E. It always worked that way before.
SR is the one showing the error.
I don't seem to be having other operational issues - except from CasISmBIOS showing various errors in the Event Viewer
that don't correspond to times running SR.

Shane · « **Reply #3 on:** October 13, 2014, 03:24:53 am »

Then I am very curious to why it would be getting a access denied error even after we made sure it does have access.

Windows would be a lot more easier to fix if the dang error messages would at least say where or what it had permissions denied on lol

The repairs for the permissions dont touch the system volume information folder, and that is where system restore does its work and keeps the data. Perhaps it is that folder it is having trouble accessing.

Shane

ruggb · « **Reply #4 on:** October 13, 2014, 12:01:14 pm »

well maybe, but looking at PROPERTIES on my desktop (works) and laptop (not working) they r the same for C:, which is the only one SR is turned on for.
Any suggestions as to where to go from here?

Yeah, wouldn't u think W could be a little more verbose about its errors?

Shane · « **Reply #5 on:** October 13, 2014, 12:19:10 pm »

The beta repair in my program (On the repair window at the bottom) if for trying to fix SR, only had a hand full of success because SR is so easy to break and MS gives zero info on how to fix it or what it needs. Not sure why they do that.

But one of the steps it does is reset the permissions on the system volume information folder. it is the only repair that does. Might be worth a shot running.

Shane

Boggin · « **Reply #6 on:** October 13, 2014, 01:30:21 pm »

Could QRM Plus be the problem - have you tried the restore points with that uninstalled ?

ruggb · « **Reply #7 on:** October 15, 2014, 09:01:13 pm »

I ran beta and rebooted --- BSOD
Stop C000021a (Fatal System Error)
The session manager initialization system process terminated unexpectedly with a status of 0xc000002 (0x00000000 0x00000000)
The system has been shut down.

Now what?

I ran System repair but it can't fix it.
Problem detail
Problem Signature:
Problem event name----StarupRepairOffline
Problem Signature 01:--6.1.7600.16385
Problem Signature 02:--6.1.7600.16385
Problem Signature 03:--unknown
Problem Signature 04:--383
Problem Signature 05:--AutoFailover
Problem Signature 06:--1
Problem Signature 07:--BadPatch
OS Version:---------------6.1.7601.2.1.0.256.1
LocaleID:------------------1033

Diagnostic and repair detail
All test were successful to.......

Root cause found:
A patch is preventing the system from starting.

Repair action: System Restore
Result: Failed. Error code = 0x1f
Time taken: 5191ms

Repair action: System files integrity check and repair
Result: Failed. Error code 0x4005
Time take: = 2886ms

Safe mode yields same error

ruggb · « **Reply #8 on:** October 15, 2014, 09:23:32 pm »

Quote from: Boggin on October 13, 2014, 01:30:21 pm

Could QRM Plus be the problem - have you tried the restore points with that uninstalled ?

QRM is pretty passive. When 'installed' it only changed a context menu.
Installing is just a matter of copying the files to a desired location.

Let's see if Shane can find an answer to the newest issue.

Boggin · « **Reply #9 on:** October 16, 2014, 07:36:52 am »

When you get the same error in Safe Mode then I think you are looking at a reinstall - either Repair, Clean or a factory reset.

http://www.sevenforums.com/tutorials/3413-repair-install.html

You could also try running a Kaspersky Rescue Disk over it should it be due to an infection. http://support.kaspersky.co.uk/viruses/rescuedisk/main

Shane · « **Reply #10 on:** October 16, 2014, 11:37:39 am »

I cant believe I didnt ask this yet, but what version of Windows? And what service pack is installed?

If XP I found this that should have a fix for the blue screen error
http://support2.microsoft.com/kb/156669

Shane

Boggin · « **Reply #11 on:** October 16, 2014, 01:15:49 pm »

In the last error report it gives the OS version as 6.1.7601 which is Win 7 SP1 although I don't know what variety the other digits refer to, as the Hardware Abstraction Layer for my Win 7 SP1 Home Premium 64 bit is .17514

Edit - @ ruggb - did you run the Startup Repair from within Windows or after you'd booted up with an install disk ?

Shane · « **Reply #12 on:** October 16, 2014, 01:48:04 pm »

Quote

In the last error report it gives the OS version as 6.1.7601 which is Win 7 SP1 although I don't know what variety the other digits refer to, as the Hardware Abstraction Layer for my Win 7 SP1 Home Premium 64 bit is .17514

Ah good catch, I didnt notice the OS version in the error log.

Shane

Boggin · « **Reply #13 on:** October 16, 2014, 01:54:27 pm »

I've just added an Edit to my last post for ruggb.

I've found this http://www.brighthub.com/computing/windows-platform/articles/105995.aspx but I don't think it will be of much use to ruggb, unless he can get in.

The patch the error message refers to could be anything but why now after the initial access denied error code ?

Shane · « **Reply #14 on:** October 16, 2014, 02:05:20 pm »

If he made a registry backup with my program he can restore the registry and see if that gets him up and going, if it does then we know it is something in the registry causing the problem.

I show a couple of different ways on how to restore the registry when you cant get into windows
http://www.tweaking.com/articles/pages/tweaking_com_registry_backup_online_help,3.html

Shane

ruggb · « **Reply #15 on:** October 17, 2014, 02:52:02 pm »

I backed up the registry BUT I can't get to that repair screen - it is always going straight to startup repair and not asking fo any login

Boggin · « **Reply #16 on:** October 17, 2014, 03:06:14 pm »

Do you have a Win 7 SP1 install disk that you could boot up with and run the Startup Repair from there after selecting Repair your Computer and navigating to the Recovery Environment ?

You can also select the Command Prompt and run an offboot sfc /scannow.

At the cmd prompt enter bcdedit |find "osdevice" and using whichever partition letter it gives, enter (assuming C: )

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows and see what that reports - that's a Pipe symbol before find.

ruggb · « **Reply #17 on:** October 17, 2014, 03:08:16 pm »

Yes I do, BUT FORTUNATELY, I had JUST made an image of my SSD drive C - and D
I would have tried that but I didn't wait long enough for ur reply.

It looks like I can't get to anything except system repair which can't fix the issue so I am restoring the image.

I guess the question is why did ur fix totally mess it up and is that pointing to the original problem?

Boggin · « **Reply #18 on:** October 17, 2014, 03:12:44 pm »

Quote from: ruggb on October 17, 2014, 03:08:16 pm

Yes I do, BUT FORTUNATELY, I had JUST made an image of my SSD drive C - and D
I would have tried that but I didn't wait long enough for ur reply.

It looks like I can't get to anything except system repair which can't fix the issue so I am restoring the image.

I guess the question is why did ur fix totally mess it up and is that pointing to the original problem?

Which fix are you referring to that messed it up ?

ruggb · « **Reply #19 on:** October 17, 2014, 04:47:25 pm »

the beta fix -- But my CRS disease prevents me from remembering if I did anything prior to that and did not reboot and maybe imaged a bad drive.

Well, I don't know what happened but, I reimaged all drives and it is doing the same thing.
Time for a clean install.................

my C: is an SSD
my profiles r moved to D:
That is an issue with windows in terms of doing a repair.
So I am changing this to only move the moveable folders to D and leave the system stuff on C.

Don't know if that had anything to do with it but I am surprised the image restore did not fix it.
more to come.

Boggin · « **Reply #20 on:** October 18, 2014, 05:39:24 am »

You must be talking about Shane's WR program which has nothing to do with me as I'm just a member as you are.

Your system image must have been corrupt as well.

You've probably done the clean install by now but you could have run the offboot sfc to check the system files before going for what should be the final solution.

Shane · « **Reply #21 on:** October 20, 2014, 11:59:00 am »

The video link I posted would have showed you how to restore the registry when windows wont boot, you can do it from the cmd window in the repair windows section that boots up.

But I am glad you got i back up and running. The only difference in the beta repair is that it sets the permissions on the system volume information folder, ran it on tons of machines and never had the problem you did, which makes me think there is something else going on and because of that there was a side effect of the error you got after running the beat repair.

I just answered so many forum posts so I cant remember if I asked this yet, but did you check the drive for bad sectors yet?

shane

ruggb · « **Reply #22 on:** October 20, 2014, 04:42:14 pm »

yes i ran chkdsk - it is also an ssd
probably somehting to do with profiles on D:

Now I have an issue with battery not charging - i think it has something to do with firmware on the intel devices.

It doesn't charge even with hard drives removed

Shane · « **Reply #23 on:** October 21, 2014, 09:39:33 am »

Is it possible the cord is bad or the soldering where the power cord plugin is on the system has come lose?

Shane

ruggb · « **Reply #24 on:** October 21, 2014, 11:25:46 am »

i wish it were that simple - none of my problems are.
The hard ones r easy for me - so i am left with the impossible ones that no one else has a clue about.
It runs fine on AC - just doesn't chg.

when I run hp batt test (either plugged in or not) it says the batt is OK and the chg light comes on during the test, but not otherwise.
So I must surmise that the chg ckt is functional and the battery is good, and the adapter is obviously working.
So why isn't it charging? It remains below 30% chg.

I wish I had a schematic.

Maybe it is a new feature that only charges the battery when it gets below 10% or something.
No, that would have been developed in the NiCd era.