BSOD File

Page 1 of 3 123 LastLast

  1. Anpippin
    Posts : 128
    Windows 7 Ultimate 64-Bit
       New #1

    BSOD File


    Can anyone analyze this BSOD file for me please?
    Attachment 77676
      My Computer
    Quote Quote

  3. richc46
    Posts : 17,796
    Windows 10, Home Clean Install
       New #2

    According to your dump report the problem is caused by ntkrnlnp.exe. The potential reasons for this situation is as follows:
    This problem occurs if one or more of the processors in the computer:
    •Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
    •Are damaged or defective.
    •Are operating outside their specified ranges for temperature, power, or other conditions.


    Test processors to insure that they are not damaged
    Make sure that your computer is not overheating

    In light of the many causes that can result in a BSOD, it is suggested that you take the following course of action:

    Test your memory using memtest86
    http://memtest.org/

    Although none of your drivers appeard to be suspect due to age, it might be a good time to check them for efficiency, using the driver verifier. THIS IS IMPORTANT
    Using Driver Verifier to identify issues with Drivers


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_060810-20888-01[1].zip\060810-20888-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02804000 PsLoadedModuleList = 0xfffff800`02a41e50
Debug session time: Tue Jun  8 12:37:52.856 2010 (GMT-4)
System Uptime: 0 days 0:00:20.963
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002b58fe0, fffff88002fce4e8, fffff88002fcdd40}
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+78 )
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: fffff80002b58fe0, The address that the exception occurred at
Arg3: fffff88002fce4e8, Exception Record Address
Arg4: fffff88002fcdd40, 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!ObpQueryNameString+78
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h]
EXCEPTION_RECORD:  fffff88002fce4e8 -- (.exr 0xfffff88002fce4e8)
ExceptionAddress: fffff80002b58fe0 (nt!ObpQueryNameString+0x0000000000000078)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000bad0b150
Attempt to read from address 00000000bad0b150
CONTEXT:  fffff88002fcdd40 -- (.cxr 0xfffff88002fcdd40)
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8002f81d20
rdx=fffffa8004006000 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002b58fe0 rsp=fffff88002fce720 rbp=0000000000001404
 r8=0000000000002000  r9=fffff88002fce878 r10=00000000bad0b0b0
r11=fffffa8002cdda38 r12=fffffa8003dceb30 r13=fffff80002804000
r14=fffffa8004006000 r15=fffffa8002f81cf0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ObpQueryNameString+0x78:
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h] ds:002b:00000000`bad0b150=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  winlogon.exe
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  00000000bad0b150
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aac0e0
 00000000bad0b150 
FOLLOWUP_IP: 
nt!ObpQueryNameString+78
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h]
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff80002c51fdd to fffff80002b58fe0
STACK_TEXT:  
fffff880`02fce720 fffff800`02c51fdd : fffffa80`02f81d20 fffffa80`04006000 fffffa80`00002000 fffff880`02fce878 : nt!ObpQueryNameString+0x78
fffff880`02fce820 fffff800`02c52224 : fffffa80`03dceb30 fffff800`0000007a fffff800`02c52000 fffff880`02fce940 : nt!EtwpEnumerateImages+0x7d
fffff880`02fce870 fffff800`02c098d6 : fffffa80`03dd0b30 fffffa80`03dceb30 fffff800`02c52050 fffff880`02fce940 : nt!EtwpProcessEnumCallback+0x1d4
fffff880`02fce8f0 fffff800`02c52371 : fffff880`02fcea28 fffffa80`01f66e01 fffffa80`01f66b00 fffffa80`01f66b00 : nt!PsEnumProcesses+0x26
fffff880`02fce920 fffff800`02c523c7 : 00000000`00000000 00000000`00000002 fffff800`02a18470 fffffa80`01f66b80 : nt!EtwpProcessThreadImageRundown+0x51
fffff880`02fce970 fffff800`02cbd4dc : 00000000`00401802 fffffa80`01f66e28 fffffa80`01f66b80 fffff800`029ea320 : nt!EtwpKernelTraceRundown+0x47
fffff880`02fce9a0 fffff800`02cbd9cc : 00000000`00000000 fffff8a0`00bac670 00000000`00000080 fffffa80`01544b30 : nt!EtwpUpdateLoggerGroupMasks+0x22c
fffff880`02fceaa0 fffff800`02bd95f2 : 00000000`00000000 fffffa80`01f66b80 fffff800`02a220c8 fffff800`029eee80 : nt!EtwpUpdateTrace+0x36c
fffff880`02fceb20 fffff800`02ce4706 : 00000000`00000008 00000000`00000001 00000000`000000d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x593fe
fffff880`02fceb90 fffff800`02ce490a : fffffa80`00000010 ffffffff`80000438 ffffffff`ffffffff fffff800`02a214a0 : nt!PerfDiagpUpdateCKCLEnableFlags+0xe6
fffff880`02fcec70 fffff800`02883161 : fffff880`01095e00 fffff800`02ce4720 fffff800`02a195f8 fffffa80`015d6b60 : nt!PerfDiagpProxyWorker+0x1ea
fffff880`02fcecb0 fffff800`02b19166 : 00000000`00001040 fffffa80`015d6b60 00000000`00000080 fffffa80`01544b30 : nt!ExpWorkerThread+0x111
fffff880`02fced40 fffff800`02854486 : fffff880`009e6180 fffffa80`015d6b60 fffff880`009f0f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fced80 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`02fce0c0 00000000`00000000 : nt!KxStartSystemThread+0x16
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!ObpQueryNameString+78
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
STACK_COMMAND:  .cxr 0xfffff88002fcdd40 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_nt!ObpQueryNameString+78
BUCKET_ID:  X64_0x7E_nt!ObpQueryNameString+78
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: fffff80002b58fe0, The address that the exception occurred at
Arg3: fffff88002fce4e8, Exception Record Address
Arg4: fffff88002fcdd40, 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!ObpQueryNameString+78
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h]
EXCEPTION_RECORD:  fffff88002fce4e8 -- (.exr 0xfffff88002fce4e8)
ExceptionAddress: fffff80002b58fe0 (nt!ObpQueryNameString+0x0000000000000078)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000bad0b150
Attempt to read from address 00000000bad0b150
CONTEXT:  fffff88002fcdd40 -- (.cxr 0xfffff88002fcdd40)
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8002f81d20
rdx=fffffa8004006000 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002b58fe0 rsp=fffff88002fce720 rbp=0000000000001404
 r8=0000000000002000  r9=fffff88002fce878 r10=00000000bad0b0b0
r11=fffffa8002cdda38 r12=fffffa8003dceb30 r13=fffff80002804000
r14=fffffa8004006000 r15=fffffa8002f81cf0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ObpQueryNameString+0x78:
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h] ds:002b:00000000`bad0b150=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  winlogon.exe
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  00000000bad0b150
READ_ADDRESS:  00000000bad0b150 
FOLLOWUP_IP: 
nt!ObpQueryNameString+78
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h]
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff80002c51fdd to fffff80002b58fe0
STACK_TEXT:  
fffff880`02fce720 fffff800`02c51fdd : fffffa80`02f81d20 fffffa80`04006000 fffffa80`00002000 fffff880`02fce878 : nt!ObpQueryNameString+0x78
fffff880`02fce820 fffff800`02c52224 : fffffa80`03dceb30 fffff800`0000007a fffff800`02c52000 fffff880`02fce940 : nt!EtwpEnumerateImages+0x7d
fffff880`02fce870 fffff800`02c098d6 : fffffa80`03dd0b30 fffffa80`03dceb30 fffff800`02c52050 fffff880`02fce940 : nt!EtwpProcessEnumCallback+0x1d4
fffff880`02fce8f0 fffff800`02c52371 : fffff880`02fcea28 fffffa80`01f66e01 fffffa80`01f66b00 fffffa80`01f66b00 : nt!PsEnumProcesses+0x26
fffff880`02fce920 fffff800`02c523c7 : 00000000`00000000 00000000`00000002 fffff800`02a18470 fffffa80`01f66b80 : nt!EtwpProcessThreadImageRundown+0x51
fffff880`02fce970 fffff800`02cbd4dc : 00000000`00401802 fffffa80`01f66e28 fffffa80`01f66b80 fffff800`029ea320 : nt!EtwpKernelTraceRundown+0x47
fffff880`02fce9a0 fffff800`02cbd9cc : 00000000`00000000 fffff8a0`00bac670 00000000`00000080 fffffa80`01544b30 : nt!EtwpUpdateLoggerGroupMasks+0x22c
fffff880`02fceaa0 fffff800`02bd95f2 : 00000000`00000000 fffffa80`01f66b80 fffff800`02a220c8 fffff800`029eee80 : nt!EtwpUpdateTrace+0x36c
fffff880`02fceb20 fffff800`02ce4706 : 00000000`00000008 00000000`00000001 00000000`000000d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x593fe
fffff880`02fceb90 fffff800`02ce490a : fffffa80`00000010 ffffffff`80000438 ffffffff`ffffffff fffff800`02a214a0 : nt!PerfDiagpUpdateCKCLEnableFlags+0xe6
fffff880`02fcec70 fffff800`02883161 : fffff880`01095e00 fffff800`02ce4720 fffff800`02a195f8 fffffa80`015d6b60 : nt!PerfDiagpProxyWorker+0x1ea
fffff880`02fcecb0 fffff800`02b19166 : 00000000`00001040 fffffa80`015d6b60 00000000`00000080 fffffa80`01544b30 : nt!ExpWorkerThread+0x111
fffff880`02fced40 fffff800`02854486 : fffff880`009e6180 fffffa80`015d6b60 fffff880`009f0f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fced80 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`02fce0c0 00000000`00000000 : nt!KxStartSystemThread+0x16
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!ObpQueryNameString+78
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
STACK_COMMAND:  .cxr 0xfffff88002fcdd40 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_nt!ObpQueryNameString+78
BUCKET_ID:  X64_0x7E_nt!ObpQueryNameString+78
Followup: MachineOwner
---------
    Last edited by richc46; 09 Jun 2010 at 15:30.
      My Computer
    Quote Quote

  4. Anpippin
    Posts : 128
    Windows 7 Ultimate 64-Bit
    Thread Starter
       New #3

    richc46 said:
    According to your dump report the problem is caused by ntkrnlnp.exe. The potential reasons for this situation is as follows:
    This problem occurs if one or more of the processors in the computer:
    •Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
    •Are damaged or defective.
    •Are operating outside their specified ranges for temperature, power, or other conditions.


    Test processors to insure that they are not damaged
    Make sure that your computer is not overheating

    In light of the many causes that can result in a BSOD, it is suggested that you take the following course of action:

    Test your memory using memtest86
    Memtest86+ - Advanced Memory Diagnostic Tool

    Although none of your drivers appeard to be suspect due to age, it might be a good time to check them for efficiency, using the driver verifier
    Using Driver Verifier to identify issues with Drivers


    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_060810-20888-01[1].zip\060810-20888-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02804000 PsLoadedModuleList = 0xfffff800`02a41e50
Debug session time: Tue Jun  8 12:37:52.856 2010 (GMT-4)
System Uptime: 0 days 0:00:20.963
Loading Kernel Symbols
...............................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002b58fe0, fffff88002fce4e8, fffff88002fcdd40}
Probably caused by : ntkrnlmp.exe ( nt!ObpQueryNameString+78 )
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: fffff80002b58fe0, The address that the exception occurred at
Arg3: fffff88002fce4e8, Exception Record Address
Arg4: fffff88002fcdd40, 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!ObpQueryNameString+78
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h]
EXCEPTION_RECORD:  fffff88002fce4e8 -- (.exr 0xfffff88002fce4e8)
ExceptionAddress: fffff80002b58fe0 (nt!ObpQueryNameString+0x0000000000000078)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000bad0b150
Attempt to read from address 00000000bad0b150
CONTEXT:  fffff88002fcdd40 -- (.cxr 0xfffff88002fcdd40)
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8002f81d20
rdx=fffffa8004006000 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002b58fe0 rsp=fffff88002fce720 rbp=0000000000001404
 r8=0000000000002000  r9=fffff88002fce878 r10=00000000bad0b0b0
r11=fffffa8002cdda38 r12=fffffa8003dceb30 r13=fffff80002804000
r14=fffffa8004006000 r15=fffffa8002f81cf0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ObpQueryNameString+0x78:
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h] ds:002b:00000000`bad0b150=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  winlogon.exe
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  00000000bad0b150
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002aac0e0
 00000000bad0b150 
FOLLOWUP_IP: 
nt!ObpQueryNameString+78
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h]
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff80002c51fdd to fffff80002b58fe0
STACK_TEXT:  
fffff880`02fce720 fffff800`02c51fdd : fffffa80`02f81d20 fffffa80`04006000 fffffa80`00002000 fffff880`02fce878 : nt!ObpQueryNameString+0x78
fffff880`02fce820 fffff800`02c52224 : fffffa80`03dceb30 fffff800`0000007a fffff800`02c52000 fffff880`02fce940 : nt!EtwpEnumerateImages+0x7d
fffff880`02fce870 fffff800`02c098d6 : fffffa80`03dd0b30 fffffa80`03dceb30 fffff800`02c52050 fffff880`02fce940 : nt!EtwpProcessEnumCallback+0x1d4
fffff880`02fce8f0 fffff800`02c52371 : fffff880`02fcea28 fffffa80`01f66e01 fffffa80`01f66b00 fffffa80`01f66b00 : nt!PsEnumProcesses+0x26
fffff880`02fce920 fffff800`02c523c7 : 00000000`00000000 00000000`00000002 fffff800`02a18470 fffffa80`01f66b80 : nt!EtwpProcessThreadImageRundown+0x51
fffff880`02fce970 fffff800`02cbd4dc : 00000000`00401802 fffffa80`01f66e28 fffffa80`01f66b80 fffff800`029ea320 : nt!EtwpKernelTraceRundown+0x47
fffff880`02fce9a0 fffff800`02cbd9cc : 00000000`00000000 fffff8a0`00bac670 00000000`00000080 fffffa80`01544b30 : nt!EtwpUpdateLoggerGroupMasks+0x22c
fffff880`02fceaa0 fffff800`02bd95f2 : 00000000`00000000 fffffa80`01f66b80 fffff800`02a220c8 fffff800`029eee80 : nt!EtwpUpdateTrace+0x36c
fffff880`02fceb20 fffff800`02ce4706 : 00000000`00000008 00000000`00000001 00000000`000000d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x593fe
fffff880`02fceb90 fffff800`02ce490a : fffffa80`00000010 ffffffff`80000438 ffffffff`ffffffff fffff800`02a214a0 : nt!PerfDiagpUpdateCKCLEnableFlags+0xe6
fffff880`02fcec70 fffff800`02883161 : fffff880`01095e00 fffff800`02ce4720 fffff800`02a195f8 fffffa80`015d6b60 : nt!PerfDiagpProxyWorker+0x1ea
fffff880`02fcecb0 fffff800`02b19166 : 00000000`00001040 fffffa80`015d6b60 00000000`00000080 fffffa80`01544b30 : nt!ExpWorkerThread+0x111
fffff880`02fced40 fffff800`02854486 : fffff880`009e6180 fffffa80`015d6b60 fffff880`009f0f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fced80 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`02fce0c0 00000000`00000000 : nt!KxStartSystemThread+0x16
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!ObpQueryNameString+78
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
STACK_COMMAND:  .cxr 0xfffff88002fcdd40 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_nt!ObpQueryNameString+78
BUCKET_ID:  X64_0x7E_nt!ObpQueryNameString+78
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: fffff80002b58fe0, The address that the exception occurred at
Arg3: fffff88002fce4e8, Exception Record Address
Arg4: fffff88002fcdd40, 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!ObpQueryNameString+78
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h]
EXCEPTION_RECORD:  fffff88002fce4e8 -- (.exr 0xfffff88002fce4e8)
ExceptionAddress: fffff80002b58fe0 (nt!ObpQueryNameString+0x0000000000000078)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000bad0b150
Attempt to read from address 00000000bad0b150
CONTEXT:  fffff88002fcdd40 -- (.cxr 0xfffff88002fcdd40)
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa8002f81d20
rdx=fffffa8004006000 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80002b58fe0 rsp=fffff88002fce720 rbp=0000000000001404
 r8=0000000000002000  r9=fffff88002fce878 r10=00000000bad0b0b0
r11=fffffa8002cdda38 r12=fffffa8003dceb30 r13=fffff80002804000
r14=fffffa8004006000 r15=fffffa8002f81cf0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ObpQueryNameString+0x78:
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h] ds:002b:00000000`bad0b150=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  winlogon.exe
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000000
EXCEPTION_PARAMETER2:  00000000bad0b150
READ_ADDRESS:  00000000bad0b150 
FOLLOWUP_IP: 
nt!ObpQueryNameString+78
fffff800`02b58fe0 4d8b92a0000000  mov     r10,qword ptr [r10+0A0h]
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from fffff80002c51fdd to fffff80002b58fe0
STACK_TEXT:  
fffff880`02fce720 fffff800`02c51fdd : fffffa80`02f81d20 fffffa80`04006000 fffffa80`00002000 fffff880`02fce878 : nt!ObpQueryNameString+0x78
fffff880`02fce820 fffff800`02c52224 : fffffa80`03dceb30 fffff800`0000007a fffff800`02c52000 fffff880`02fce940 : nt!EtwpEnumerateImages+0x7d
fffff880`02fce870 fffff800`02c098d6 : fffffa80`03dd0b30 fffffa80`03dceb30 fffff800`02c52050 fffff880`02fce940 : nt!EtwpProcessEnumCallback+0x1d4
fffff880`02fce8f0 fffff800`02c52371 : fffff880`02fcea28 fffffa80`01f66e01 fffffa80`01f66b00 fffffa80`01f66b00 : nt!PsEnumProcesses+0x26
fffff880`02fce920 fffff800`02c523c7 : 00000000`00000000 00000000`00000002 fffff800`02a18470 fffffa80`01f66b80 : nt!EtwpProcessThreadImageRundown+0x51
fffff880`02fce970 fffff800`02cbd4dc : 00000000`00401802 fffffa80`01f66e28 fffffa80`01f66b80 fffff800`029ea320 : nt!EtwpKernelTraceRundown+0x47
fffff880`02fce9a0 fffff800`02cbd9cc : 00000000`00000000 fffff8a0`00bac670 00000000`00000080 fffffa80`01544b30 : nt!EtwpUpdateLoggerGroupMasks+0x22c
fffff880`02fceaa0 fffff800`02bd95f2 : 00000000`00000000 fffffa80`01f66b80 fffff800`02a220c8 fffff800`029eee80 : nt!EtwpUpdateTrace+0x36c
fffff880`02fceb20 fffff800`02ce4706 : 00000000`00000008 00000000`00000001 00000000`000000d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x593fe
fffff880`02fceb90 fffff800`02ce490a : fffffa80`00000010 ffffffff`80000438 ffffffff`ffffffff fffff800`02a214a0 : nt!PerfDiagpUpdateCKCLEnableFlags+0xe6
fffff880`02fcec70 fffff800`02883161 : fffff880`01095e00 fffff800`02ce4720 fffff800`02a195f8 fffffa80`015d6b60 : nt!PerfDiagpProxyWorker+0x1ea
fffff880`02fcecb0 fffff800`02b19166 : 00000000`00001040 fffffa80`015d6b60 00000000`00000080 fffffa80`01544b30 : nt!ExpWorkerThread+0x111
fffff880`02fced40 fffff800`02854486 : fffff880`009e6180 fffffa80`015d6b60 fffff880`009f0f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fced80 00000000`00000000 : fffff880`02fcf000 fffff880`02fc9000 fffff880`02fce0c0 00000000`00000000 : nt!KxStartSystemThread+0x16
 
SYMBOL_STACK_INDEX:  0
SYMBOL_NAME:  nt!ObpQueryNameString+78
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
STACK_COMMAND:  .cxr 0xfffff88002fcdd40 ; kb
FAILURE_BUCKET_ID:  X64_0x7E_nt!ObpQueryNameString+78
BUCKET_ID:  X64_0x7E_nt!ObpQueryNameString+78
Followup: MachineOwner
---------
    Well this was a new custom install of Windows 7, and the coprocessor driver wasn't installed at the time I got the BSOD. But now I installed my motherboard drivers which includes the coprocessor driver.
      My Computer
    Quote Quote

  6. richc46
    Posts : 17,796
    Windows 10, Home Clean Install
       New #4

    You gave us one mini dmp report. Use the computer if it ahppens again, we may get a new reading. This is not 100% precise, it may take a few attempts to fix the problem.
      My Computer
    Quote Quote

  7. Anpippin
    Posts : 128
    Windows 7 Ultimate 64-Bit
    Thread Starter
       New #5

    Computer Not Starting


    Ok I was playing Counter Strike Source, and then all of a sudden my computer froze, so I turned it off but now when I turn it on it gets a blue screen of death at the starting windows screen.
      My Computer
    Quote Quote

  8. richc46
    Posts : 17,796
    Windows 10, Home Clean Install
       New #6

    Please follow these instructions, so that we may help

    https://www.sevenforums.com/tutorials...en-forums.html
      My Computer
    Quote Quote

  10. Anpippin
    Posts : 128
    Windows 7 Ultimate 64-Bit
    Thread Starter
       New #7

    richc46 said:
    Please follow these instructions, so that we may help

    https://www.sevenforums.com/tutorials...en-forums.html
    I can't login to windows to get the dump files.
      My Computer
    Quote Quote

  11. richc46
    Posts : 17,796
    Windows 10, Home Clean Install
       New #8

    Can you try in safe mode?
      My Computer
    Quote Quote

  12. Anpippin
    Posts : 128
    Windows 7 Ultimate 64-Bit
    Thread Starter
       New #9

    richc46 said:
    Can you try in safe mode?
    I can't get into safe mode either. The screen stops at loading CLASSPNP.SYS
      My Computer
    Quote Quote

  13. richc46
    Posts : 17,796
    Windows 10, Home Clean Install
       New #10

    Read ekkehert

    PLEASE HELP!! classpnp.sys bsod!!!

    Illl try my best to get you out of this.
    You can try the repair disc. too.
      My Computer
    Quote Quote

 
Page 1 of 3 123 LastLast

  Related Discussions
397088 I am using Windows 10 64 bit.At first the .sdf was not associated to any file type association like notepad etc.It was coming look for an app in store.I accidentally clicked on a file type association now can't find a solution to change it back to the default one(i.e pick an app from...
http://i.imgur.com/FXNZL1l.jpg
Hi all, Any idea how to write Batch File .bat to copy file from File Sharing & FTP Hosting to local directory. Current the File Sharing & FTP Hosting is SMARTFILE. I don't want to use WINSCP as the connector. Thanks
God bless you, I am not a computer person please help me to fix the problem I have. Every time I open a word, power point and note pad program another file is opens with that (with a infinity sign in the front with the same extension ) is that a thread or how can I stop this thank you...
I am having a BSOD problem whenever I try to open a file in MS Word or MS Excel using the "File Open" menu. This problem also occurs when I try to attach a file to a memo (in email using Internet Explorer) and use the "Browse" button and try to choose a file. I have attached the zip file using the...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 18:45.
Find Us