May have found an issue? [auto-deletion of .dmp files]

usasma · May 11, 2013

Running the latest dumps from this post: Help with a BSOD problem! (I only ran May 4 and later - 5 dumps total)

The app found one size mismatch - and that's the one that was left in the directory after the app finished it's business.
We had discussed in a previous post that the app wasn't deleting all the .dmp files when done.

I'm still using the old version of the app, haven't had time to upgrade to the latest one.

writhziden · May 12, 2013

If you received the error that there was a size mismatch, the file with size 0 should have been deleted automatically before even giving that message. If that file was not deleted at that time, there is something (perhaps a 3rd party app?) interfering with the app's ability to delete the size 0 .dmp. I will check the logic in the app to make sure there is not something internal to it that is interfering.

Thanks for letting me know.

usasma · May 13, 2013

I also get problems when trying to install the latest versions of the apps.
Hmmm ... I've also had issues with Microsoft Visual Studio Express 2012 (it hijacked the .dmp file association)
Uninstalling it now.

Ran into an issue yesterday/the day before where the app would crash on a full memory dump. But was uncertain about the integrity of the dump as it was downloaded from one of the free online file-hosting services (and I had the minidump from it, so I didn't need the full dump).

niemiro · May 13, 2013

usasma said:
Hmmm ... I've also had issues with Microsoft Visual Studio Express 2012 (it hijacked the .dmp file association)
Uninstalling it now.

Yes...it will do that. You need to go back in a Command Prompt (shift > right click > Open Command Window here is very convenient) to your normal windbg.exe and run it with -IA (IIRC) to restore the dump association.

Richard

writhziden · May 13, 2013

usasma said:
I also get problems when trying to install the latest versions of the apps.

Was there an error message during installation? If so, what was it?

A screenshot might help determine what is causing the installation issue.

usasma · May 14, 2013

No, no error messages. Usually the first attempt doesn't even put the new executable in the folder.
After renaming the folder it usually works.
Also, the installation usually takes 10 to 20 minutes (I haven't actually timed it, but I have gone downstairs to get coffee and have come back to it still working).

I haven't attempted to use the alternate version as I'm able to get the new one working eventually.
I suspect my system, but just don't have the time to reinstall in order to find out.

I'll get screenshots and a Process Monitor log when I try to install the latest version. It should be in the next 3 days (those are my days off).
Also will get Event Viewer logs and the BSOD collection app logs - for starters :0)

jcgriff2 · May 14, 2013

I installed 2.15.3.0 a few hours ago - no issues to report.

writhziden · May 14, 2013

Sounds like some kind of permissions issue with the folder; I suspected that as a possibility with the size 0 files not being deleted and now the description of installation issues points to that too. Check your permissions and ownership for your SysnativeBSODApps installation directory.

usasma · May 15, 2013

SysnativeBSODApps directory:

Owner is the Administrators group
Owner/Administrators/System all have Full Control
Inherited from C:\Users\Owner and inherits to all folders, sub-folders, and files below it

Permissions for Owner/Administrator/System are:

Full control - Allow
Modify - Allow
Read & execute - Allow
List folder contents - Allow
Read - Allow
Write - Allow

Haven't checked the actual directory that it installs from (as I deleted it).
I tried running it straight out of the .zip
Then I tried extracting it to my C:\Users\Owner\Downloads directory (which has the same ownership/permissions as the SysnativeBSODApps directory) - but that's the one that I deleted.

Will try installing the latest version late today or tomorrow (I've gotta go on a road trip today).

writhziden · May 16, 2013

Does your user profile also have full permissions?

The Administrators group should be enough for the installer, so that shouldn't be an issue there. For the apps themselves, the user running the apps needs full permissions.

usasma · May 16, 2013

Yes it does. User profile is named "Owner"
It's the installation that's a PITA.
Once installed I have no issues.

usasma · May 18, 2013

Tried installing 3 times, system crashed (unrelated) after last attemp - so I lost my notes.
Installation takes 10 minutes and does not add the new executable to the folder
Renamed the folder with a zzz prefix and then the installer installed the new executable.

writhziden · May 18, 2013

Very strange behavior. Everything sounds like it should work fine, but your system is being contrary. ;-}

You could try installing to another directory within your user profile and see how it behaves for a while. Just save your settings before installing and then load them after installing again.

usasma · May 18, 2013

When I have time, I'll try installing in another, fresh profile

I'm booked solid for free time in the next few weeks - the wife got delivery of her new computers and the proprietary software is going to be installed in mid-June. Before then I've gotta reset her network so it (and the computers) will last for another 10 years (she'll be retired by then).

writhziden · May 18, 2013

Not a problem. As far as I know, you are the only one experiencing the current problem with installation, so we can fix it when you have time.

If anyone else reports similar issues, or if I find a solution to the long install time during my testing, I'll post here and let you know.

EDIT: Sorry, I edited this instead of my own post.

usasma · May 18, 2013

The installer restores my 3 gB of files in the outputDmp folder each time I install the app
It appears that it is responsible for most of the time that's consumed.

I haven't had time to check, but if I delete the contents of the folder will the app auto-save the folder without anything in it (for the next install?)

writhziden · May 18, 2013

Ah, that explains it. I will fix that feature in the installer and it will work correctly in the next update. Thanks for the info. :-}

The only way to prevent that would be to delete the folder and also delete the backup from the %TEMP% directory at present: SysnativeBSODApps.zdnbak

In the future, I will have the installer do less when updating than when doing a fresh install.

Search

Search

May have found an issue? [auto-deletion of .dmp files]

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer, BSOD Academy Instructor

usasma

Retired Admin

niemiro

Senior Administrator, Windows Update Expert

writhziden

Administrator, .NET/UWP Developer, BSOD Academy Instructor

usasma

Retired Admin

jcgriff2

Site Administrator, General Manager, BSOD Academy Instructor, Microsoft MVP (Ret.)

writhziden

Administrator, .NET/UWP Developer, BSOD Academy Instructor

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer, BSOD Academy Instructor

usasma

Retired Admin

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer, BSOD Academy Instructor

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer, BSOD Academy Instructor

usasma

Retired Admin

writhziden

Administrator, .NET/UWP Developer, BSOD Academy Instructor