"Access denied" to minidump files

[Willyw]

Hello, Brand new system here. Windows 7 x64. Have been getting an occasional blue screen. Sometimes many days can go by without one, then twice in one day. I would like to proceed with trying to track down the cause of the BSODs, but before I ask for help on that, I'd like to be able to see what is in the minidump files. They are being created in C:\Windows\Minidump , but if I try to open one with Wordpad or Notepad, I get "access denied". ( Using administrator account). On any given minidump file, when I do Properties->Security->Continue, I can see that Administrators have "Full control". "Special Permissions is the only one not checked to be On. Under Properties->Security->Advanced->Owner, current owner is "Unable to display current owner." I have tried experimenting with changing the owner to me. Result is the same. First, - what is causing this? I'm new to Windows 7, and am baffled. Next, what *should* Win7 be doing with these files... what should the permissions be? And , how do I adjust Win7 to do it? Thanks edit: Sorry... the post lost my paragraphs. Is there a trick to posting here? tnx.

 

[zigzag3143]

Hello, Brand new system here. Windows 7 x64. Have been getting an occasional blue screen. Sometimes many days can go by without one, then twice in one day. I would like to proceed with trying to track down the cause of the BSODs, but before I ask for help on that, I'd like to be able to see what is in the minidump files. They are being created in C:\Windows\Minidump , but if I try to open one with Wordpad or Notepad, I get "access denied". ( Using administrator account). On any given minidump file, when I do Properties->Security->Continue, I can see that Administrators have "Full control". "Special Permissions is the only one not checked to be On. Under Properties->Security->Advanced->Owner, current owner is "Unable to display current owner." I have tried experimenting with changing the owner to me. Result is the same. First, - what is causing this? I'm new to Windows 7, and am baffled. Next, what *should* Win7 be doing with these files... what should the permissions be? And , how do I adjust Win7 to do it? Thanks edit: Sorry... the post lost my paragraphs. Is there a trick to posting here? tnx.

Try dragging them to your desktop and zipping them there. Use these to help find and upload them. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Let us know if you need more help

Ken

 

[Willyw]

Hello, Brand new system here. Windows 7 x64. Have been getting an occasional blue screen. Sometimes many days can go by without one, then twice in one day. I would like to proceed with trying to track down the cause of the BSODs, but before I ask for help on that, I'd like to be able to see what is in the minidump files. They are being created in C:\Windows\Minidump , but if I try to open one with Wordpad or Notepad, I get "access denied". ( Using administrator account). On any given minidump file, when I do Properties->Security->Continue, I can see that Administrators have "Full control". "Special Permissions is the only one not checked to be On. Under Properties->Security->Advanced->Owner, current owner is "Unable to display current owner." I have tried experimenting with changing the owner to me. Result is the same. First, - what is causing this? I'm new to Windows 7, and am baffled. Next, what *should* Win7 be doing with these files... what should the permissions be? And , how do I adjust Win7 to do it? Thanks edit: Sorry... the post lost my paragraphs. Is there a trick to posting here? tnx.

Try dragging them to your desktop and zipping them there. Use these to help find and upload them. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Let us know if you need more help

Ken

Yes, I do.
You misunderstood my questions.
I need to know what is causing this, and how to fix it.

Thanks

 

[zigzag3143]

Hello, Brand new system here. Windows 7 x64. Have been getting an occasional blue screen. Sometimes many days can go by without one, then twice in one day. I would like to proceed with trying to track down the cause of the BSODs, but before I ask for help on that, I'd like to be able to see what is in the minidump files. They are being created in C:\Windows\Minidump , but if I try to open one with Wordpad or Notepad, I get "access denied". ( Using administrator account). On any given minidump file, when I do Properties->Security->Continue, I can see that Administrators have "Full control". "Special Permissions is the only one not checked to be On. Under Properties->Security->Advanced->Owner, current owner is "Unable to display current owner." I have tried experimenting with changing the owner to me. Result is the same. First, - what is causing this? I'm new to Windows 7, and am baffled. Next, what *should* Win7 be doing with these files... what should the permissions be? And , how do I adjust Win7 to do it? Thanks edit: Sorry... the post lost my paragraphs. Is there a trick to posting here? tnx.

Try dragging them to your desktop and zipping them there. Use these to help find and upload them. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Let us know if you need more help

Ken

Yes, I do.
You misunderstood my questions.
I need to know what is causing this, and how to fix it.

Thanks

If we are to tell you what is causing "this" we need the actual DMP file. You cant ope a DMP file with notepad or any word processor. What exactly are you trying to do?

Ken

 

[Willyw]

Try dragging them to your desktop and zipping them there. Use these to help find and upload them. http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

Let us know if you need more help

Ken

Yes, I do.
You misunderstood my questions.
I need to know what is causing this, and how to fix it.

Thanks

If we are to tell you what is causing "this" we need the actual DMP file. You cant ope a DMP file with notepad or any word processor. What exactly are you trying to do?

Ken

You misunderstand.
*First*, I want to know why I get "Access denied", when I am admin, and/or owner of the file.
Then, fix it, so it doesn't do this any more.
"this" is not the blue screens, yet. "this" is the denial of access to files.

Thanks

 

[zigzag3143]

Yes, I do.
You misunderstood my questions.
I need to know what is causing this, and how to fix it.

Thanks

If we are to tell you what is causing "this" we need the actual DMP file. You cant ope a DMP file with notepad or any word processor. What exactly are you trying to do?

Ken

You misunderstand.
*First*, I want to know why I get "Access denied", when I am admin, and/or owner of the file.
Then, fix it, so it doesn't do this any more.
"this" is not the blue screens, yet. "this" is the denial of access to files.

Thanks

You are getting access denied because in that folder those files are owned by someone else. You can take ownership, add yourself to the trusted installer group,etc.

Usually when an admin is denied the owner is usually "trusted INstaller" who installs all your apps.

Ken

 

[Willyw]

If we are to tell you what is causing "this" we need the actual DMP file. You cant ope a DMP file with notepad or any word processor. What exactly are you trying to do?

Ken

You misunderstand.
*First*, I want to know why I get "Access denied", when I am admin, and/or owner of the file.
Then, fix it, so it doesn't do this any more.
"this" is not the blue screens, yet. "this" is the denial of access to files.

Thanks

You are getting access denied because in that folder those files are owned by someone else.

No, they are not.

You can take ownership, add yourself to the trusted installer group,etc.

In my first post, I already said: "I have tried experimenting with changing the owner to me. Result is the same"

Usually when an admin is denied the owner is usually "trusted INstaller" who installs all your apps.

Ken

and that the current owner was not "trusted installer". I'd said, "current owner is "Unable to display current owner"." , before I changed it to me.

 

[jcgriff2]

Either the TrustedInstaller or NT AUTHORITY\SYSTEM is the owner of record for most found within \windows. You can copy files out of \windows\minidump, but cannot work with them in place unless you change file permission settings via the takeown & icacls commands first.

Add Take Ownership to your context menu. Download the attached REG file and allow merge with registry to occur. Then go to \windows\minidump, RIGHT-click on a dump file, "Take Ownership".

You chose to create this thread in the Crashes and Debugging Forum for BSOD help. If you do not want to attach the dump files as zigzag3143 has repeatedly requested and wish instead to obtain answers to general Windows 7 questions, I'll be glad to request this thread be moved to the appropriate SF Forum.

Regards. . .

jcgriff2

.

 

[Willyw]

Either the TrustedInstaller or NT AUTHORITY\SYSTEM is the owner of record for most found within \windows.

Neither TrustedInstaller or NT AUTHORITY\SYSTEM is listed as the owner of these files.
Is this unusual and/or significant?

Currrent Owner is: "Unable to display current owner"

You can copy files out of \windows\minidump, but cannot work with them in place unless you change file permission settings via the takeown & icacls commands first.

So... is it *normal* then, to get an 'access denied', even though I am admin?


As for those commands, I do not recognize them... sorry. ( I am new to Win7).
I took ownership using the gui.
I right clicked the file, from within Windows Explorer, then
Properties->Security->Advanced->Owner tab->Edit

Add Take Ownership to your context menu. Download the attached REG file and allow merge with registry to occur. Then go to \windows\minidump, RIGHT-click on a dump file, "Take Ownership".

What will this do different from the method I used?

You chose to create this thread in the Crashes and Debugging Forum for BSOD help. If you do not want to attach the dump files as zigzag3143 has repeatedly requested

Perhaps that is how he got so confused. He was on to the bsod, and as I'd posted, first I wanted to find out about the 'access denied' to the files.

and wish instead to obtain answers to general Windows 7 questions, I'll be glad to request this thread be moved to the appropriate SF Forum.

Is this a general Win 7 question?
If so, then by all means - please do. Whatever works best.

Regards. . .

jcgriff2

.

Thanks

 

[Willyw]

Any help?

 

[Tews]

Willy ... this is pretty straight forward and not difficult at all ... if you are not getting access to the .dmp file, you will need to take ownership of it .. http://www.sevenforums.com/tutorials/1911-take-ownership-shortcut.html?ltr=T ... follow the directions in this tutorial.... right click on the .dmp file and select take ownership...

 

[Willyw]

Willy ... this is pretty straight forward and not difficult at all ... if you are not getting access to the .dmp file, you will need to take ownership of it ..

I have done this.
And again... the results remain the same. Access denied.

http://www.sevenforums.com/tutorials/1911-take-ownership-shortcut.html?ltr=T ... follow the directions in this tutorial.... right click on the .dmp file and select take ownership...

That is some sort of edit to the registry, with no explanation of its details.

I'd asked if it results in anything different from the method that I used.
If I'm getting ownership properly without it, then I won't need a shortcut.


Thanks

 

[CarlTR6]

It is a very handy handy shortcut. It does modify the registry; however it is harmless and completely reversible. For more information, read this: Context Menu - Take Ownership - Vista Forums

 

[Willyw]

It is a very handy handy shortcut. It does modify the registry; however it is harmless and completely reversible. For more information, read this: Context Menu - Take Ownership - Vista Forums

I don't see the point of modifying the registry, if I can simply take ownership of files using the tools already built into Windows 7.
I believe this is what I've done.
No one has said anything yet about that method that I used.

 

[Tews]

Im sorry that you feel that you dont need to try what has been suggested.. it WILL fix your problem .. good luck..
Im 10-7

 

[CarlTR6]

I thought you just stated the method you used resulted in no access? If so, trying it again is not going to change the result.

The shortcut method is very safe in that you are not messing with permissions, which, if you do not know what your are doing, can necessitate a repair install.

So, if what you are doing is not working, try an approved method that is perfectly safe. If you choose not to follow advice, we cannot assist you. We would not suggest something that could harm your system.

 

[Willyw]

I thought you just stated the method you used resulted in no access?

I did.
So... I need some help in figuring out what is wrong. That's what I'm asking for.
I'm not asking for an alternate method.

If so, trying it again is not going to change the result.

Obviously. But... I haven't said that I was doing it repeatedly.

The shortcut method is very safe in that you are not messing with permissions, which, if you do not know what your are doing, can necessitate a repair install.

So, if what you are doing is not working, try an approved method that is perfectly safe. If you choose not to follow advice, we cannot assist you. We would not suggest something that could harm your system.

Again, I'm not asking for a work-around.
I'm explaining what I did. If it didn't work, then something is wrong, and I need some help from those that know Windows 7, in figuring it out.


Thanks

 

[CarlTR6]

Tews definitely knows windows and knows it very, very well. Just look at his reputation. He gave you the correct and easy way to solve your problem.

Please understand that Tews and everyone here are volunteers. No one here receives one penny for assisting others. We do it because we enjoy helping others. In my case, I enjoy passing along to others what someone helped me learn.

If you want to learn Windows in depth, there are some excellent books on the subject. And they can be found at Amazon. However, it will take you a while to read and understand even one. But if you want an in depth analysis of what you tried, you need to start reading.

You have a perfectly safe and easy solution presented to you. This method was written by Brink, one of the administrators here. Check his reputation.

Have a good day and happy computing.

 

[derekimo]

I thought you just stated the method you used resulted in no access?

I did.
So... I need some help in figuring out what is wrong. That's what I'm asking for.
I'm not asking for an alternate method.

If so, trying it again is not going to change the result.

Obviously. But... I haven't said that I was doing it repeatedly.

The shortcut method is very safe in that you are not messing with permissions, which, if you do not know what your are doing, can necessitate a repair install.

So, if what you are doing is not working, try an approved method that is perfectly safe. If you choose not to follow advice, we cannot assist you. We would not suggest something that could harm your system.

Again, I'm not asking for a work-around.
I'm explaining what I did. If it didn't work, then something is wrong, and I need some help from those that know Windows 7, in figuring it out.


Thanks

I would say you should pick which is the more important of your dilemma's, if it's the knowledge of why, then you have been given a suggestion for that.

If it is how to fix your access denied problem, you have been given a suggestion for that as well.

Pick the one you want most and let us know your results, but if you had just tried the original take ownership suggestion, you would be much farther along than you are now.

 

[Willyw]

Tews definitely knows windows and knows it very, very well.

?
I didn't say that he didn't.

Just look at his reputation. He gave you the correct and easy way to solve your problem.

No, he didn't.
Again, he gave me a work-around.
I appreciate that, but that is not what I'm asking for yet.

I don't see the need to modify the registry, when Windows apparently has the capability built right in, to take ownership of a file.
Am I misunderstanding this? ... it is built into Windows, correct?

Please understand that Tews and everyone here are volunteers. No one here receives one penny for assisting others.

I know this. I don't know why you are telling me.

We do it because we enjoy helping others. In my case, I enjoy passing along to others what someone helped me learn.

If you want to learn Windows in depth, there are some excellent books on the subject. And they can be found at Amazon. However, it will take you a while to read and understand even one. But if you want an in depth analysis of what you tried, you need to start reading.

Ok.
I thought that it was something simple, since I found it as described.
Why it is not working as I expected, is why I came here.... hoping somebody would know, or would have experienced it.

You have a perfectly safe and easy solution presented to you.

No, I don't.
Again... it is a work around.
I appreciate the effort, but that is not what I asked for.

This method was written by Brink, one of the administrators here. Check his reputation.

Have a good day and happy computing.