Windows Vista Tips
Home Register Members Search Windows Vista Tips File Database Links
Member Login:

Windows Vista Tips > Newsgroups > Windows 64 Bit > Minidumps available !

Reply
Page 2 of 2 1 2
Thread Tools Display Modes

Minidumps available !

 
 
Skybuck Flying
Guest
Posts: n/a

 
      08-28-2007
It is not my job to fixes these bugs.

Somebody made a bug somewhere.

These minidumps can provide hints.

That's why I am providing these minidumps, in case some developer is reading
or happens to read this message and finds it interesting and thinks hmmm I
am gonna look into the mentioned code to see if there is something that
could have caused it.

Alternatively recreate the situation debug it and see what happens.

Might be difficult to recreate this problem, or maybe not... time will tell.

Bye,
Skybuck.
 
Reply With Quote
 
 
 
 
Skybuck Flying
Guest
Posts: n/a

 
      08-28-2007
What if they don't have the time for it, or are not interested ?

When they get fired at least somebody else can continue thanks to these
posts in history !

Bye,
Skybuck.
 
Reply With Quote
 
Tony Sperling
Guest
Posts: n/a

 
      08-28-2007

"Skybuck Flying" <> wrote in message
news:fb0ldc$385$...
> It is not my job to fixes these bugs.
>

Sure, it is.
Unless you give them your machine and pay them to solve it - it's nobody
else's job.

> Somebody made a bug somewhere.
>

So far, I've seen nothing that suggest this has to be a bug, just as I've
seen nothing to suggest it couldn't be your own doing.

> These minidumps can provide hints.
>

Sure, they can.

> That's why I am providing these minidumps, in case some developer is
reading
> or happens to read this message and finds it interesting and thinks hmmm I
> am gonna look into the mentioned code to see if there is something that
> could have caused it.
>

Developers usually aren't allowed to debug code, because they write code and
they are pre-determined to believe the code. Debugging is handed over to
people who can think like an analytical archeologist, and unless anything
essential on your system is Open Source - there is no code to look at. If it
is OS then this is not the forum anyway.

> Alternatively recreate the situation debug it and see what happens.
>

Wonderfull! They would have to do this on the actual machine - publishing a
memory dump is practically useless for anything other than guess-work,
unless you happen to draw attention to someone who studied a near duplicate
yesterday! In which case it would still contain a lot of guess-work.

> Might be difficult to recreate this problem, or maybe not... time will
tell.
>

If for nothing else - it will depend on how much learning you pick up from
the event. If you don't care - nobody else will, too.


Tony. . .
 
Reply With Quote
 
Homer J. Simpson
Guest
Posts: n/a

 
      08-29-2007
It's not the job of anyone *here* either to hunt down bugs you're seeing on
your system. Besides, what do you expect any of *us* here to do about them?
Nobody here has the source or can release a hotfix.

Submit your dumps to MS. If it's somebody's job at all to look after these
submissions, they won't claim they don't have time or inclination. It's not
up to the individual developers at MS to make those kind of decisions.
 
Reply With Quote
 
Don Burn
Guest
Posts: n/a

 
      08-29-2007

"Skybuck Flying" <> wrote in message
news:fb1dtu$ddm$...
> What if they don't have the time for it, or are not interested ?
>
> When they get fired at least somebody else can continue thanks to these
> posts in history !
>

Sorry, but this is not how it works. You can submit the dumps to
Microsoft, IIRC the cost is $250 per dump. This is a newsgroup where
people try to help one another, but not do their work.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
 
Reply With Quote
 
Skybuck Flying
Guest
Posts: n/a

 
      08-29-2007
Very strange,

This is a newsgroup hosted by microsoft ?

Bye,
Skybuck.
 
Reply With Quote
 
R. C. White
Guest
Posts: n/a

 
      08-30-2007
Hi, Skybuck.

"Hosted" is the key word. Microsoft just makes it easy (possible?) for us
users to communicate with each other. With rare exceptions, Softies don't
hang out in these newsgroups, or do so quietly on their own time. Unless
you see something like [MS] or [MSFT] in their Sig, they probably are not
posting in any official capacity. MVPs are NOT Microsoft employees; we are
just volunteers who enjoy helping when we can.

It's just us, talking among ourselves, trying to help each other. Like
reminding each other when it is time to contact the official Tech Support
staff, who ARE paid to help us solve problems with Microsoft products.

RC
--
R. C. White, CPA
San Marcos, TX

Microsoft Windows MVP
(Running Windows Live Mail beta in Vista Ultimate x64)

"Skybuck Flying" <> wrote in message
news:fb4jb4$bsc$...
> Very strange,
>
> This is a newsgroup hosted by microsoft ?
>
> Bye,
> Skybuck.
 
Reply With Quote
 
Tiletron
Guest
Posts: n/a

 
      10-09-2007
I am experiencing a similar error, but the crash occurs whenever various,
unconnected folders crash the Windows Explorer. I have just recently
installed an upgrade to Windows Vista Business and this was not occuring
before then.

"Skybuck Flying" wrote:

> Make that 28 !
>
> System just crashed again while using internet explorer and surfing to the
> weblog of the guy that wrote the themed delphi stuff ?!
>
> The irony ?! Coincendence ?! or this guy one serious bug !? Me think
> coincedence !
>
> Latest crash analysis:
>
> Microsoft (R) Windows Debugger Version 6.6.0007.5
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini082707-02.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is:
> SRV*c:\Tools\WinDbg\WebSymbols*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free
> x64
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 3790.srv03_sp2_rtm.070216-1710
> Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100
> Debug session time: Mon Aug 27 17:39:39.484 2007 (GMT+2)
> System Uptime: 0 days 2:21:02.411
> Loading Kernel Symbols
> .................................................. .................................................. ........................................
> Loading User Symbols
> Loading unloaded module list
> .................................................. .
> ************************************************** *****************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** *****************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 1000007E, {ffffffffc0000005, fffff80001011ebd, fffffadfc9086a90,
> fffffadfc90864a0}
>
> Probably caused by : ntkrnlmp.exe ( nt!CmpDelayCloseWorker+494 )
>
> Followup: MachineOwner
> ---------
>
> 1: kd> !analyze -v
> ************************************************** *****************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** *****************************
>
> SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
> 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: ffffffffc0000005, The exception code that was not handled
> Arg2: fffff80001011ebd, The address that the exception occurred at
> Arg3: fffffadfc9086a90, Exception Record Address
> Arg4: fffffadfc90864a0, Context Record Address
>
> 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!CmpDelayCloseWorker+494
> fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8]
>
> EXCEPTION_RECORD: fffffadfc9086a90 -- (.exr fffffadfc9086a90)
> ExceptionAddress: fffff80001011ebd
> (nt!CmpDelayCloseWorker+0x0000000000000494)
> ExceptionCode: c0000005 (Access violation)
> ExceptionFlags: 00000000
> NumberParameters: 2
> Parameter[0]: 0000000000000000
> Parameter[1]: 0000000000000008
> Attempt to read from address 0000000000000008
>
> CONTEXT: fffffadfc90864a0 -- (.cxr fffffadfc90864a0)
> rax=0000000000000000 rbx=fffffa8003281c68 rcx=000000000000132f
> rdx=0000000000000008 rsi=00000000ffffffff rdi=fffffa80028bd588
> rip=fffff80001011ebd rsp=fffffadfc9086cb0 rbp=fffffa800412b920
> r8=00000000da81d47a r9=fffffa80028bd590 r10=0000000000000000
> r11=00000000000007ff r12=000000000000132f r13=00000000000001c1
> r14=0000000000000000 r15=0000000000000001
> iopl=0 nv up ei pl nz na pe cy
> cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b
> efl=00010203
> nt!CmpDelayCloseWorker+0x494:
> fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8]
> ds:002b:00000000`00000008=0000000000000000
> Resetting default scope
>
> CUSTOMER_CRASH_COUNT: 2
>
> CURRENT_IRQL: 0
>
> ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced
> memory at "0x%08lx". The memory could not be "%s".
>
> READ_ADDRESS: 0000000000000008
>
> BUGCHECK_STR: 0x7E
>
> DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
>
> EXCEPTION_STR: 0x0
>
> LAST_CONTROL_TRANSFER: from fffff8000103768a to fffff80001011ebd
>
> STACK_TEXT:
> fffffadf`c9086cb0 fffff800`0103768a : 00000000`00000000 fffff800`011defe0
> fffff800`01012070 fffffadf`cecd3bf0 : nt!CmpDelayCloseWorker+0x494
> fffffadf`c9086d00 fffff800`0124b972 : fffffadf`cecd3bf0 00000000`00000080
> fffffadf`cecd3bf0 fffffadf`c8c83680 : nt!ExpWorkerThread+0x13b
> fffffadf`c9086d70 fffff800`010202d6 : fffffadf`c8c7b180 fffffadf`cecd3bf0
> fffffadf`c8c83680 fffff800`011b5dc0 : nt!PspSystemThreadStartup+0x3e
> fffffadf`c9086dd0 00000000`00000000 : 00000000`00000000 00000000`00000000
> 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
>
>
> FOLLOWUP_IP:
> nt!CmpDelayCloseWorker+494
> fffff800`01011ebd 488b4008 mov rax,qword ptr [rax+8]
>
> SYMBOL_STACK_INDEX: 0
>
> FOLLOWUP_NAME: MachineOwner
>
> MODULE_NAME: nt
>
> IMAGE_NAME: ntkrnlmp.exe
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 45d69ab4
>
> SYMBOL_NAME: nt!CmpDelayCloseWorker+494
>
> STACK_COMMAND: .cxr 0xfffffadfc90864a0 ; kb
>
> FAILURE_BUCKET_ID: X64_0x7E_nt!CmpDelayCloseWorker+494
>
> BUCKET_ID: X64_0x7E_nt!CmpDelayCloseWorker+494
>
> Followup: MachineOwner
> ---------
>
> 1: kd> ml
> *** WARNING: Unable to verify timestamp for nv4_disp.dll
> *** ERROR: Module load completed but symbols could not be loaded for
> nv4_disp.dll
> *** WARNING: Unable to verify timestamp for CTEDSPSY.DLL
> *** ERROR: Module load completed but symbols could not be loaded for
> CTEDSPSY.DLL
> *** WARNING: Unable to verify timestamp for dump_nvata64.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> dump_nvata64.sys
> *** WARNING: Unable to verify timestamp for vmm.sys
> *** ERROR: Module load completed but symbols could not be loaded for vmm.sys
> *** WARNING: Unable to verify timestamp for kl1.sys
> *** ERROR: Module load completed but symbols could not be loaded for kl1.sys
> *** WARNING: Unable to verify timestamp for klif.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> klif.sys
> *** WARNING: Unable to verify timestamp for CTEXFIFX.DLL
> *** ERROR: Module load completed but symbols could not be loaded for
> CTEXFIFX.DLL
> *** WARNING: Unable to verify timestamp for CT20XUT.DLL
> *** ERROR: Module load completed but symbols could not be loaded for
> CT20XUT.DLL
> *** WARNING: Unable to verify timestamp for ctac32k.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> ctac32k.sys
> *** WARNING: Unable to verify timestamp for ctsfm2k.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> ctsfm2k.sys
> *** WARNING: Unable to verify timestamp for emupia2k.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> emupia2k.sys
> *** WARNING: Unable to verify timestamp for ha20x2k.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> ha20x2k.sys
> *** WARNING: Unable to verify timestamp for AmdTools64.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> AmdTools64.sys
> *** WARNING: Unable to verify timestamp for usbccgp.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> usbccgp.sys
> *** WARNING: Unable to verify timestamp for dtscsi.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> dtscsi.sys
> *** WARNING: Unable to verify timestamp for NVSNPU.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> NVSNPU.SYS
> *** WARNING: Unable to verify timestamp for NVNRM.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> NVNRM.SYS
> *** WARNING: Unable to verify timestamp for ctoss2k.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> ctoss2k.sys
> *** WARNING: Unable to verify timestamp for ctaud2k.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> ctaud2k.sys
> *** WARNING: Unable to verify timestamp for nv4_mini.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> nv4_mini.sys
> *** WARNING: Unable to verify timestamp for yk51x64.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> yk51x64.sys
> *** WARNING: Unable to verify timestamp for speedfan.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> speedfan.sys
> *** WARNING: Unable to verify timestamp for nvata64.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> nvata64.sys
> *** WARNING: Unable to verify timestamp for SI3132.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> SI3132.sys
> *** WARNING: Unable to verify timestamp for Si3132r5.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> Si3132r5.sys
> *** WARNING: Unable to verify timestamp for SPTD2221.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> SPTD2221.SYS
> *** WARNING: Unable to verify timestamp for sptd.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> sptd.sys
> *** WARNING: Unable to verify timestamp for amdk8.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> amdk8.sys
> *** WARNING: Unable to verify timestamp for LHidFilt.Sys
> *** ERROR: Module load completed but symbols could not be loaded for
> LHidFilt.Sys
> *** WARNING: Unable to verify timestamp for LMouFilt.Sys
> *** ERROR: Module load completed but symbols could not be loaded for
> LMouFilt.Sys
> *** WARNING: Unable to verify timestamp for SiWinAcc.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> SiWinAcc.sys
> *** WARNING: Unable to verify timestamp for ptilink.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> ptilink.sys
> *** WARNING: Unable to verify timestamp for NVENETFD.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> NVENETFD.sys
> *** WARNING: Unable to verify timestamp for nvnetbus.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> nvnetbus.sys
> *** WARNING: Unable to verify timestamp for klim5.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> klim5.sys
> *** WARNING: Unable to verify timestamp for SiRemFil.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> SiRemFil.sys
> *** WARNING: Unable to verify timestamp for CdaC15BA.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> CdaC15BA.sys
> *** WARNING: Unable to verify timestamp for secdrv.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> secdrv.sys
> *** WARNING: Unable to verify timestamp for CdaD10BA.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> CdaD10BA.sys
> *** WARNING: Unable to verify timestamp for ctprxy2k.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> ctprxy2k.sys
> *** WARNING: Unable to verify timestamp for ASACPI.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> ASACPI.sys
> *** WARNING: Unable to verify timestamp for FileDisk.SYS
> *** ERROR: Module load completed but symbols could not be loaded for
> FileDisk.SYS
> *** WARNING: Unable to verify timestamp for AmdAcpi.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> AmdAcpi.sys
> *** WARNING: Unable to verify timestamp for PxHlpa64.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> PxHlpa64.sys
> *** WARNING: Unable to verify timestamp for AsIO.sys
> *** ERROR: Module load completed but symbols could not be loaded for
 
Reply With Quote
 
Tiletron
Guest
Posts: n/a

 
      10-09-2007
Opened log file 'c:\debuglog.txt'

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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

************************************************** **********
WARNING: Dump file has been truncated. Data may be missing.
************************************************** **********
Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
C:\Windows;C:\Windows\system32;C:\Windows\system32 \drivers
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
Unable to read PsLoadedModuleList
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
KdDebuggerData.KernBase < SystemRangeStart
Windows XP Kernel Version 2600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x00000000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Sep 18 06:34:07.937 2007 (GMT+1)
System Uptime: 0 days 2:59:32.620
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
Unable to read PsLoadedModuleList
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
CS descriptor lookup failed
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get program counter
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 804ef15f, acfe6b54, 0}

***** Debugger could not find nt in module list, module list might be
corrupt, error 0x80070057.

GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

?: kd> !analyze -v;r;kv;lmtn;.logclose;q
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get program counter
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
************************************************** *****************************
*
*
* Bugcheck Analysis
*
*
*
************************************************** *****************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 804ef15f, The address that the exception occurred at
Arg3: acfe6b54, Trap Frame
Arg4: 00000000

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

***** Debugger could not find nt in module list, module list might be
corrupt, error 0x80070057.

GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002

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

FAULTING_IP:
+ffffffff804ef15f
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
804ef15f ?? ???

TRAP_FRAME: acfe6b54 -- (.trap 0xffffffffacfe6b54)
..trap 0xffffffffacfe6b54
Unable to read trap frame at acfe6b54
..trap

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

STACK_TEXT:
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

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

GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
^ Unable to get program counter '!analyze
-v;r;kv;lmtn;.logclose;q'
 
Reply With Quote
 
 
 
Reply
Page 2 of 2 1 2

« Installing windows 2003 64 bits standard server without R2 | Missing User Profile! »
Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Forum Software Powered by vBulletin®, Copyright Jelsoft Enterprises Ltd.
SEO by vBSEO 3.3.2 ©2009, Crawlability, Inc.
Contact Us - Windows Vista Tips - Archive - Privacy Statement - Top

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59