admin account in Vista

dg2008 · Aug 14, 2008

I am debuging my memory dump and have installed Windbg but I can't open a file as I'm told 'I don't have access, I need to contact admin' etc

My account has full access so I don't understand why I have this problem. I have to log into my laptop each time could that be it?

EDIT: I'm on VISTA

Adrynalyne · Aug 14, 2008

What file?

dg2008 · Aug 14, 2008

a memory dump file

Adrynalyne · Aug 14, 2008

What is the file name?

dg2008 · Aug 14, 2008

don't know off the top of head as I'm as work now

something like - Minixxxxx-03.dmp

Adrynalyne · Aug 14, 2008

Well, my thoughts would be that either the file is corrupt, or is in use.

Whats the specific message?

dg2008 · Aug 14, 2008

it says

minixxx.dmp
You don't have permission to access this file
Contact the file owner or administrator to obtain permission
Click to expand...

dg2008 · Aug 14, 2008

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\Mini081308-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*DownstreamStore*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x82000000 PsLoadedModuleList = 0x82111e10
Debug session time: Wed Aug 13 00:28:59.447 2008 (GMT+1)
System Uptime: 0 days 0:31:24.126
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82076029, a4f40908, 0}

Probably caused by : ntkrpamp.exe ( nt!ExAcquireFastMutex+12 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82076029, The address that the exception occurred at
Arg3: a4f40908, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!ExAcquireFastMutex+12
82076029 f00fba3000 lock btr dword ptr [eax],0

TRAP_FRAME: a4f40908 -- (.trap 0xffffffffa4f40908)
ErrCode = 00000002
eax=20c7fed1 ebx=00000000 ecx=20c7fe01 edx=00000000 esi=20c7fed1 edi=00000000
eip=82076029 esp=a4f4097c ebp=a4f40994 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!ExAcquireFastMutex+0x12:
82076029 f00fba3000 lock btr dword ptr [eax],0 ds:0023:20c7fed1=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

BUGCHECK_STR: 0x8E

PROCESS_NAME: Awcl.exe

CURRENT_IRQL: 1

LAST_CONTROL_TRANSFER: from 820b5180 to 82076029

STACK_TEXT:
a4f40980 820b5180 00000000 840ffd20 a4f409e8 nt!ExAcquireFastMutex+0x12
a4f40994 807228a5 20c7fed1 83934f38 00000000 nt!FsRtlLookupPerFileObjectContext+0x31
a4f409b0 8071e7bc 840ffd20 a4f409e8 00000005 fltmgr!FltpGetStartingCallbackNode+0x3b
a4f409d0 8071ec07 a4f409e8 83ab0e80 840ffd20 fltmgr!FltpPassThrough+0x16a
a4f40a00 82027f83 83ab0e80 8fac9008 8f702fa4 fltmgr!FltpDispatch+0xb1
a4f40a18 821880e9 8d493014 a7bb2440 000000be nt!IofCallDriver+0x63
a4f40a54 8219797f 840ffd20 00000009 00000000 nt!IopQueryXxxInformation+0x17e
a4f40ab4 821854a6 840ffd20 00000001 8d493008 nt!IopQueryNameInternal+0x1d7
a4f40ae4 8221438d 840ffd20 a4f40cf0 a4f4b608 nt!IoQueryFileDosDeviceName+0x2e
a4f40d48 8208caaa 0000071c 0000002b 0a0d33a0 nt!NtQueryInformationProcess+0x1b9
a4f40d48 770b0f34 0000071c 0000002b 0a0d33a0 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0983f18c 00000000 00000000 00000000 00000000 0x770b0f34

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExAcquireFastMutex+12
82076029 f00fba3000 lock btr dword ptr [eax],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExAcquireFastMutex+12

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 471ea39c

FAILURE_BUCKET_ID: 0x8E_nt!ExAcquireFastMutex+12

BUCKET_ID: 0x8E_nt!ExAcquireFastMutex+12

Followup: MachineOwner
Click to expand...

the above is my file, any help would be great

Log in or Sign up

admin account in Vista

dg2008 Private E-2

Adrynalyne Guest

dg2008 Private E-2

Adrynalyne Guest

dg2008 Private E-2

Adrynalyne Guest

dg2008 Private E-2

dg2008 Private E-2