Re: Black screen of death and SYSTEM_SERVICE_EXCEPTION (3b) nt!CmpGetNameControlBlock+108

Tech-Archive recommends: Fix windows errors by optimizing your registry

Replace your system memory. Run Vista memory test upon boot (press F8)

"P." <alias@xxxxxxxxxxxxxxxx> wrote in message
news:0CC0A77E-9DD5-4462-99FF-AAC939F0EFBE@xxxxxxxxxxxxxxxx
A more complete analysis of the full dump on the same machine:


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


Loading Dump File [\\Server\Archive\3b.1.f.dmp]
Kernel Complete Dump File: Full address space is available

Symbol search path is:
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free
x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
Kernel base = 0xfffff800`0281a000 PsLoadedModuleList = 0xfffff800`029dfdb0
Debug session time: Fri May 30 15:41:11.086 2008 (GMT-7)
System Uptime: 0 days 0:00:45.836
Loading Kernel Symbols
......................................................................................................................................................
Loading User Symbols
.........................................................................................................
Loading unloaded module list
...................

A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.

A fatal system error has occurred.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002ad2e50, fffffa6006b18d20, 0}

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!CmpGetNameControlBlock+108 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ad2e50, Address of the exception record for the exception
that caused the bugcheck
Arg3: fffffa6006b18d20, Address of the context record for the exception
that caused the bugcheck
Arg4: 0000000000000000, zero.

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: kernel32!pNlsUserInfo ***
*** ***
*************************************************************************

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

FAULTING_IP:
nt!CmpGetNameControlBlock+108
fffff800`02ad2e50 443b3e cmp r15d,dword ptr [rsi]

CONTEXT: fffffa6006b18d20 -- (.cxr 0xfffffa6006b18d20)
rax=fffff88000021000 rbx=0000000000000000 rcx=fffff88000022dd0
rdx=0000000004c6fe36 rsi=0000400000000000 rdi=00000000000001dd
rip=fffff80002ad2e50 rsp=fffffa6006b19580 rbp=fffff88000021000
r8=000000000000000d r9=000000000000007d r10=000000000000004c
r11=fffff88009dee81c r12=0000000000000026 r13=0000000000001dd0
r14=fffffa6006b19618 r15=0000000070c3d314
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!CmpGetNameControlBlock+0x108:
fffff800`02ad2e50 443b3e cmp r15d,dword ptr [rsi]
ds:002b:00004000`00000000=????????
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80002ad2080 to fffff80002ad2e50

STACK_TEXT:
fffffa60`06b19580 fffff800`02ad2080 : 00000000`00000001 00000000`00001dd0
00000000`00001dd0 00000000`00000000 : nt!CmpGetNameControlBlock+0x108
fffffa60`06b195e0 fffff800`02ae0198 : fffff880`009ac010 00000000`00ec1850
fffff880`009ac010 00000000`00002160 : nt!CmpCreateKeyControlBlock+0x220
fffffa60`06b19670 fffff800`02af067e : 00000000`00000040 fffff800`00000000
fffffa80`08866010 fffffa60`06b19c01 : nt!CmpParseKey+0xd08
fffffa60`06b19910 fffff800`02af4884 : 00000000`00000694 fffffa80`06c43b01
00000000`00000040 fffffa80`039ae080 : nt!ObpLookupObjectName+0x2ce
fffffa60`06b19a20 fffff800`02ada86f : 00000000`00020019 00000000`00020000
00000000`00000001 00000000`00000000 : nt!ObOpenObjectByName+0x2f4
fffffa60`06b19af0 fffff800`0286ee33 : 00000000`067eede8 fffffa60`00020019
00000000`067eec60 00000000`00000000 : nt!CmOpenKey+0x25d
fffffa60`06b19c20 00000000`76e05b9a : 000007fe`fefe96fe 00000000`c0000034
00000000`00000000 7ec4cc8d`00000001 : nt!KiSystemServiceCopyEnd+0x13
00000000`067eec18 000007fe`fefe96fe : 00000000`c0000034 00000000`00000000
7ec4cc8d`00000001 00000003`00000020 : ntdll!NtOpenKey+0xa
00000000`067eec20 000007fe`fefe98c4 : 00000000`00000694 00000000`067eed38
00000000`00000000 00000000`00020019 : ADVAPI32!LocalBaseRegOpenKey+0x153
00000000`067eece0 000007fe`fefe9921 : 00000000`00000000 00000000`00000000
000007fe`fe0a31b4 00000000`00000001 : ADVAPI32!RegOpenKeyExInternalW+0x1f2
00000000`067eed70 000007fe`fe0311e1 : 00000000`00000000 00000000`040264b0
000007fe`fe0a31b4 00000000`067eeee8 : ADVAPI32!RegOpenKeyExW+0x19
00000000`067eedb0 000007fe`fe039651 : 00000000`0607bfc0 00000000`067ef2e8
00000000`0607bfc0 00000000`00000026 :
ole32!CComCat::IsClassOfCategoriesEx+0x171
00000000`067ef290 000007fe`f9232b49 : 00000000`067ef5d8 00000000`00000000
00000000`76ed64e0 00000000`76d02af4 :
ole32!CEnumClassesOfCategories::Next+0xc1
00000000`067ef540 000007fe`f9232dae : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`04097000 : BROWSEUI!_EnumerateGuids+0x8b
00000000`067ef590 000007fe`f9232cfd : 00000000`00000000 00000000`04045ac0
00000000`0607bfc0 00000000`02f89b18 :
BROWSEUI!SHWriteImplementingClassesOfCategory+0x76
00000000`067ef5d0 000007fe`f9232c98 : 00000000`040045d0 00000000`00000000
00000000`00000000 00000000`00000000 :
BROWSEUI!_WriteClassesOfCategories+0x4a
00000000`067ef600 000007fe`f923286b : 00000000`040045d0 00000000`00000938
00000000`00000003 00000000`0000000b :
BROWSEUI!CComCatCacheTask::InternalResumeRT+0x28
00000000`067ef640 000007fe`f923afd3 : 00000000`040b5330 00000000`02f16a20
00000000`00000000 00000000`00000000 : BROWSEUI!CRunnableTask::Run+0xd0
00000000`067ef670 000007fe`f923b213 : 00000000`02f15210 00000000`02f15200
00000000`00000000 00000000`00000000 :
BROWSEUI!CShellTaskThread::ThreadProc+0x2c7
00000000`067ef750 000007fe`fd75fc63 : 00000000`02f15210 00000000`00000000
00000000`0044d560 00000000`0044d560 :
BROWSEUI!CShellTaskThread::s_ThreadProc+0x33
00000000`067ef780 00000000`76dc5a73 : 00000000`0409c340 00000000`0409c340
000007fe`f8707080 000007ff`fff9a000 :
SHLWAPI!ExecuteWorkItemThreadProc+0xf
00000000`067ef7b0 00000000`76e01220 : 00000000`0042fac0 00000000`02fb7a98
00000000`003e1188 00000000`0044d560 : ntdll!RtlpTpWorkCallback+0xf0
00000000`067ef860 00000000`76be495d : 00000000`0042fac0 00000001`00010002
00000000`0042fac0 00000000`0409c340 : ntdll!TppWorkerThread+0x3d6
00000000`067efae0 00000000`76de8791 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`067efb10 00000000`00000000 : 00000000`00000000 00000000`00000000
00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d


FOLLOWUP_IP:
nt!CmpGetNameControlBlock+108
fffff800`02ad2e50 443b3e cmp r15d,dword ptr [rsi]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!CmpGetNameControlBlock+108

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 479192b7

STACK_COMMAND: .cxr 0xfffffa6006b18d20 ; kb

FAILURE_BUCKET_ID: X64_0x3B_nt!CmpGetNameControlBlock+108

BUCKET_ID: X64_0x3B_nt!CmpGetNameControlBlock+108

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




.

Relevant Pages

  • Intermitent Screen Dump
    ... i have a dell computer where i installed a new hard drive and new memory. ... Loading Kernel Symbols ... parameters are the exception record and context record. ... STACK_COMMAND: .cxr 0xffffffffbad13688; kb ...
    (microsoft.public.windowsxp.help_and_support)
  • BugCheck A0 INTERNAL_POWER_ERROR Reboot Loop
    ... Microsoft Windows Debugger Version 6.6.0007.5 ... Loading Kernel Symbols ... Unhandled exception occured while processing a system ...
    (microsoft.public.windowsxp.help_and_support)
  • Does anyone know what this bugcheck is ? WdfDeviceInitSetRequestAt
    ... my driver loads the very first thing it does is break into the debugger, ... of an exception, but the bugcheck code is 0. ... Loading Kernel Symbols ... total locks, 1 locks currently held ...
    (microsoft.public.development.device.drivers)
  • Re: Exception occurs only when run outside the debugger *confused*
    ... > I have a very strange problem here: ... > My program throws an exception coming from the glibmm library when I ... However, when I run it with the debugger, it ... Debuggers can use different memory management than the ...
    (comp.programming)
  • Re: lazy loading of a shared library
    ... >> Somebody needs to run a debugger over this. ... Because "loading" a file into memory is different from mapping it. ...
    (comp.os.linux.misc)