Author Topic: Error message From Registery Backup on a UEFI system. (Read 51856 times)

streetwolf · « **on:** December 10, 2012, 05:22:01 am »

After I did a clean install of Windows 8 Pro X64 under a UEFI environment and formatting my boot/system drive as GPT I always get a message after RB runs as an auto backup, when I first start up my machine, stating that an error was encountered. Examining my backup folder it appears everything was backed up. I do not get any error message if I run RB manually. Prior to converting to UEFI I had no problems.

Here's what I have in the Event Log:

Faulting application name: TweakingRegistryBackup.exe, version: 1.4.0.3, time stamp: 0x5071e5f1
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x770
Faulting application start time: 0x01cdd6d791f65069
Faulting application path: C:\Program Files (x86)\Tweaking.com\Registry Backup\TweakingRegistryBackup.exe
Faulting module path: unknown
Report Id: d90fd982-42ca-11e2-bed1-c86000a0a026
Faulting package full name:
Faulting package-relative application ID:

Shane · « **Reply #1 on:** December 10, 2012, 10:53:53 am »

Doesn't happen when you do it manually, only happens at startup?

And check the backup logs. If the logs are complete and everything back ups then it looks like the program is crashing when it closes itself.

I am on Windows 8 and have it set at startup but I am not using UEFI, and I have no crashes.

But why at startup? I guess that is where we should look first. When you run manually it is running under your account, what account do you have it set to run as from the task scheduler?

Shane

streetwolf · « **Reply #2 on:** December 11, 2012, 04:19:18 am »

Happens only at auto startup, never manually. I run both under my account which has Admin privileges. I also have added a delay of 4 minutes to the startup task so that my disk image program, which also uses VSS, has time to complete first at startup. I've always done this with no problems until I went UEFI.

I've attached two log files for you to look at.

Shane · « **Reply #3 on:** December 12, 2012, 11:02:03 am »

Yeah the backup totally finishes, it looks like when the program is closing down that it is crashing.

Try this, I want to see if it is something witht he task scheduler. Go to the task scheduler and run the backup from there instead.

Does it still crash?

Shane

streetwolf · « **Reply #4 on:** December 12, 2012, 12:05:48 pm »

I ran it from the Task Scheduler and didn't get the error message this time. However, I got the same error in my Event Log. Why no error message this time is anyone's guess.

Shane · « **Reply #5 on:** December 12, 2012, 01:41:36 pm »

OK but there was an error in the event viewer.

Ok now lets see if it is the task scheduler or perhaps how the program is shutting down from the command line.

If you look at the task for it you will see the command it uses to run the program. Like /silent and and such.

So lets try manually running the program with that same command from a shortcut instead.

Shane

streetwolf · « **Reply #6 on:** December 12, 2012, 03:53:57 pm »

I created a shortcut, which btw, I use /supersilent. I got the error message as well as the Event Log entry.

I then ran the shortcut as Administrator and it worked perfectly, no error message or Event Log error.

I did setup the job in the scheduler to run under the SYSTEM account but that didn't work either. Maybe I need to run it under something else?

Shane · « **Reply #7 on:** December 12, 2012, 04:00:00 pm »

But the odd thing is it is completing the backup. So now the hard part, trying to find at what point is it crashing

Shane

streetwolf · « **Reply #8 on:** December 12, 2012, 04:11:05 pm »

I also setup the shortcut to run as Administrator under the Advanced tab and that also worked fine. I think I'll just add it to my startup folder and see what happens when I start my machine tomorrow.

The reason a manual run works might be because I also have that shortcut setup to run as Admin.

Shane · « **Reply #9 on:** December 12, 2012, 04:25:39 pm »

The manifest file tells Windows it needs to be ran as admin. Very odd.

Shane

streetwolf · « **Reply #10 on:** December 12, 2012, 04:43:02 pm »

If my memory serves me correctly I recall that after I switched over to UEFI I ran a manual backup and that also failed with some kind of error. That is what led me to make the shortcut run as Admin.

Shane · « **Reply #11 on:** December 14, 2012, 09:33:52 am »

Is the manifest file in the folder with the program?

My machine supports UEFI but I would have to do a reinstall and dont want to do that lol. SO I cant test it myself yet.

Shane

streetwolf · « **Reply #12 on:** December 14, 2012, 12:52:59 pm »

Yes, the Manifest file is in the folder with the program. Since UEFI requires the volume to be GPT perhaps GPT is the problem. I also hesitated going UEFI as a full install of W8 is required along with everything else but I wanted to take advantage of UEFI which so far I haven't seen any.

For some reason the shortcut I placed in my startup folder didn't start up when Windows loaded in the morning for the first time. I then manually ran it and got the error message and Event Log error. Seems marking the shortcut as Admin doesn't always work for some reason.

Shane · « **Reply #13 on:** December 14, 2012, 12:57:46 pm »

UEFI isnt required for Windows 8. It is just one of the new options, suppose to protect against some viruses
http://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface

Quote

Secure boot

The UEFI 2.2 specification adds a protocol known as Secure boot, which can secure the boot process by preventing the loading of drivers or OS loaders that are not signed with an acceptable digital signature. When secure boot is enabled, it is initially placed in "Setup" mode, which allows a public key known as the "Platform key" (PK) to be written to the firmware. Once the key is written, secure boot enters "User" mode, where only drivers and loaders signed with the platform key can be loaded by the firmware. Additional "Key Exchange Keys" (KEK) can be added to a database stored in memory to allow other certificates to be used, but they must still have a connection to the private portion of the Platform key.[23] Secure boot can also be placed in "Custom" mode, where additional public keys can be added to the system that do not match the private key.[24]

Again though, the oddest part is that the program does the backup, even finishes the log. I think the crash is coming when the program tries to close itself. I wonder if there is a problem with any of the controls in the program closing out when the form isnt visible.

Shane

Tomas_Sweden · « **Reply #14 on:** December 14, 2012, 11:21:19 pm »

Shane, if you look at http://www.tweaking.com/forums/index.php/topic,278.msg3112.html#msg3112 you see that I have a similar crash on my brothers computer(Win xp Sp3) and the crash is still there!

Tomas

streetwolf · « **Reply #15 on:** December 15, 2012, 06:51:14 am »

I might have discovered the cause of my error. I had the main program run as Administrator under the Compatibility tab. I removed that and when my backup kicked off this morning after turning on my machine I didn't get any error at all. Fingers crossed.

Shane · « **Reply #16 on:** December 15, 2012, 10:55:30 am »

Yeah you dont need to have the admin set int he compatibility tab. The manifest file tells windows it needs admin rights

Let me know how it goes after a few days.

Quote

Shane, if you look at http://www.tweaking.com/forums/index.php/topic,278.msg3112.html#msg3112 you see that I have a similar crash on my brothers computer(Win xp Sp3) and the crash is still there!

Even the new version is crashing on his XP? Does it finish the backups before the crash?

Shane

Tomas_Sweden · « **Reply #17 on:** December 15, 2012, 10:58:11 am »

Quote from: Shane on December 15, 2012, 10:55:30 am

Even the new version is crashing on his XP? Does it finish the backups before the crash?

Yes even the latest version(1.4.3) and Yes the backup finish before the crash.

Tomas

Shane · « **Reply #18 on:** December 15, 2012, 11:01:08 am »

Has to be something with the custom controls and when it shuts down.

Hit me up in a new thread in the next day or so. I will make some test exe's that will have message boxes during the closing of the program. This way you can tell me what the last message box you see is before the crash. That is how I try and locate bugs LOL

Shane

Tomas_Sweden · « **Reply #19 on:** December 15, 2012, 11:20:48 am »

Ok!

I will go to my brother in the beginning of next week!

Tomas

streetwolf · « **Reply #20 on:** December 16, 2012, 06:31:54 am »

Sorry to say the error came back this morning. As usual the backup was taken successfully. I also got the error message when I had to reboot my machine. No backup was taken as I use the once a day auto option.

Shane · « **Reply #21 on:** December 17, 2012, 11:42:09 am »

Yeah I dont think this is a Windows 8 problem. I think it has something to do with the shutdown process of the program and it cleaning up the custom controls that I use.

I will do more testing in a bit and see if I can at least fig out which control it is. The thing that bugs me is that it doesnt happen every time. So going to be a hard one to find.

Shane

streetwolf · « **Reply #22 on:** December 17, 2012, 12:01:40 pm »

Thinking that maybe by unchecking run at highest privileges for the RB task in the task scheduler might fix the problem it didn't. RB didn't backup this morning and the message in Event Log clearly stated I needed elevated privileges. So I checked the box, saved the task, and ran it manually. It ran perfect. You are right about it being intermittent.

If you can code some sort of debug routine in RB to see what's happening I'll gladly try it out. I could also run Process Monitor and see what that produces when the task get's the error. Let me know.

Shane · « **Reply #23 on:** December 17, 2012, 12:07:47 pm »

I have seen this problem is some of my other programs.

In the shutdown process you have 2 way to close a VB app.

1. When all the Windows are closed it closes the exe
2. You can call "End" which will close itself even if other things are open in the program.

The odd bug I run into is this. When I do #1 sometimes the program will never close, even though I clean up after everything, for some reason something doesn't close all the way, normally it is a control on the form.

So I use #2 after I am done cleaning up and closing everything. What is happening is a control or form isnt closing properly at random times and the end command is killing it, thus giving us the random error.

2 hard things about trying to fix this. Is the fact that it doesn't happen every time and finding which control is doing it. In my CleanMem mini monitor program I had this problem as well. I found a few tricks that worked on fixing it, such as giving it more time to close and better cleanup. I need to see what I did different there and see if I did or didnt do the same close down process in the reg backup.

When I have had programs do it every time I could code and test till it is fixed. These random ones are a pain, I can try a few things then wait and see if it keeps happening.

Shane

Shane · « **Reply #24 on:** December 20, 2012, 05:03:12 pm »

Working on the program now.

Quick question, do you have the program set to remove old backups?

Reason why I ask is it removes the old backups when you do a backup. I am wondering if the removing the old backups is still working when the program tries to close. That might explain the crash.

If you do have it enabled does it still crash if you turn it off?

Shane