Going quite mad

M

misterz

Member
Having random BSOD's. Have tried cleaning interior and removed dust. Reseated peripherals. Have tried analyzing using debugging sw (which is brand new for me). But, the output is not telling me what I need to do to repair. Moreover, I can't seem to successfulyy dl symbols. Here is the output (as well a zipped file with more info, as per the instructions of this forum regarding posting queries for BSOD's):


WARNING: Whitespace at end of path element
WARNING: Whitespace at end of path element


Code: 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
WARNING: Whitespace at end of path element
Symbol search path is: .sympath[+] srv*c:\symbolfiles*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]

;.sympath[+] srv*C:/symbolfiles*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]


Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0xfffff800`02646000 PsLoadedModuleList = 0xfffff800`0280add0
Debug session time: Thu Oct 14 08:41:55.354 2010 (UTC - 4:00)
System Uptime: 0 days 5:53:16.170
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdb018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffd5ef03c8160, 2, 1, fffff800026ba78f}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 8037a not present in the dump file. Type ".hh dbgerr004" for 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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!PsGetCurrentProcess+40ff )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffd5ef03c8160, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800026ba78f, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 8037a not present in the dump file. Type ".hh dbgerr004" for 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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002646000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c0e5ae3

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 fffffd5ef03c8160 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!PsGetCurrentProcess+40ff
fffff800`026ba78f 498160201ffcffff and     qword ptr [r8+20h],0FFFFFFFFFFFFFC1Fh

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff800026a026e to fffff800026a04d0

STACK_TEXT:  
fffffa60`08f5f298 fffff800`026a026e : 00000000`0000000a fffffd5e`f03c8160 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`08f5f2a0 fffff800`0269f14b : 00000000`00000001 00000000`0001007c fffff900`c09a6a70 fffff680`0003fd88 : nt!ZwUnloadKeyEx+0x23ce
fffffa60`08f5f3e0 fffff800`026ba78f : 000003a1`000003ae 000003c0`00000486 00000000`00010088 00000000`00000440 : nt!ZwUnloadKeyEx+0x12ab
fffffa60`08f5f570 fffff800`026b6c16 : 00000000`00000000 fffff960`000beb2e fffff900`c0c05ef0 fffff900`c0c05ef0 : nt!PsGetCurrentProcess+0x40ff
fffffa60`08f5f5a0 fffff800`0269f059 : 00000000`00000000 fffffa60`08f5f648 00000000`07fb1401 00000000`03497da0 : nt!PsGetCurrentProcess+0x586
fffffa60`08f5f680 000007fe`fc265124 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ZwUnloadKeyEx+0x11b9
00000000`0389e880 fffff800`0269a0c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fc265124
fffffa60`08f5fa60 fffff900`c0936450 : fffff900`00000000 00000000`00000000 fffff960`0011bbaf 00000000`00040000 : nt!KiCpuId+0x30
fffffa60`08f5fa68 fffff900`00000000 : 00000000`00000000 fffff960`0011bbaf 00000000`00040000 fffffa60`08f600e0 : 0xfffff900`c0936450
fffffa60`08f5fa70 00000000`00000000 : fffff960`0011bbaf 00000000`00040000 fffffa60`08f600e0 00000000`00000000 : 0xfffff900`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PsGetCurrentProcess+40ff
fffff800`026ba78f 498160201ffcffff and     qword ptr [r8+20h],0FFFFFFFFFFFFFC1Fh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PsGetCurrentProcess+40ff

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID:  WRONG_SYMBOLS

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

Attachments

My Computer

System One

  • Manufacturer/Model
    Dell
    CPU
    2.80 gigahertz Intel Core2 Duo
    Motherboard
    Dell Inc. 0RY007 A01
    Memory
    4086 Megabytes Usable Installed Memory
    Graphics card(s)
    NVIDIA GeForce FX 5200 Intel(R) G33/G31 Ex
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Acer V173 NEC LCD72V
    Hard Drives
    ST3750630AS [Hard drive] (750.16 GB)
Blue screen crashes

Having random BSOD's. Have tried cleaning interior and removed dust. Reseated peripherals. Have tried analyzing using debugging sw (which is brand new for me). But, the output is not telling me what I need to do to repair. Moreover, I can't seem to successfulyy dl symbols. Here is the output (as well a zipped file with more info, as per the instructions of this forum regarding posting queries for BSOD's):


WARNING: Whitespace at end of path element
WARNING: Whitespace at end of path element

Code: 
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
WARNING: Whitespace at end of path element
Symbol search path is: .sympath[+] srv*c:\symbolfiles*Symbol information

;.sympath[+] srv*C:/symbolfiles*Symbol information


Executable search path is: 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.amd64fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0xfffff800`02646000 PsLoadedModuleList = 0xfffff800`0280add0
Debug session time: Thu Oct 14 08:41:55.354 2010 (UTC - 4:00)
System Uptime: 0 days 5:53:16.170
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffdb018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffd5ef03c8160, 2, 1, fffff800026ba78f}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 8037a not present in the dump file. Type ".hh dbgerr004" for 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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!PsGetCurrentProcess+40ff )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffd5ef03c8160, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800026ba78f, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Page 8037a not present in the dump file. Type ".hh dbgerr004" for 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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:  
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002646000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c0e5ae3

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 fffffd5ef03c8160 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!PsGetCurrentProcess+40ff
fffff800`026ba78f 498160201ffcffff and     qword ptr [r8+20h],0FFFFFFFFFFFFFC1Fh

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff800026a026e to fffff800026a04d0

STACK_TEXT:  
fffffa60`08f5f298 fffff800`026a026e : 00000000`0000000a fffffd5e`f03c8160 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffffa60`08f5f2a0 fffff800`0269f14b : 00000000`00000001 00000000`0001007c fffff900`c09a6a70 fffff680`0003fd88 : nt!ZwUnloadKeyEx+0x23ce
fffffa60`08f5f3e0 fffff800`026ba78f : 000003a1`000003ae 000003c0`00000486 00000000`00010088 00000000`00000440 : nt!ZwUnloadKeyEx+0x12ab
fffffa60`08f5f570 fffff800`026b6c16 : 00000000`00000000 fffff960`000beb2e fffff900`c0c05ef0 fffff900`c0c05ef0 : nt!PsGetCurrentProcess+0x40ff
fffffa60`08f5f5a0 fffff800`0269f059 : 00000000`00000000 fffffa60`08f5f648 00000000`07fb1401 00000000`03497da0 : nt!PsGetCurrentProcess+0x586
fffffa60`08f5f680 000007fe`fc265124 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ZwUnloadKeyEx+0x11b9
00000000`0389e880 fffff800`0269a0c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fc265124
fffffa60`08f5fa60 fffff900`c0936450 : fffff900`00000000 00000000`00000000 fffff960`0011bbaf 00000000`00040000 : nt!KiCpuId+0x30
fffffa60`08f5fa68 fffff900`00000000 : 00000000`00000000 fffff960`0011bbaf 00000000`00040000 fffffa60`08f600e0 : 0xfffff900`c0936450
fffffa60`08f5fa70 00000000`00000000 : fffff960`0011bbaf 00000000`00040000 fffffa60`08f600e0 00000000`00000000 : 0xfffff900`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PsGetCurrentProcess+40ff
fffff800`026ba78f 498160201ffcffff and     qword ptr [r8+20h],0FFFFFFFFFFFFFC1Fh

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!PsGetCurrentProcess+40ff

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID:  WRONG_SYMBOLS

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

Attachments

My Computer

System One

  • Manufacturer/Model
    Dell
    CPU
    2.80 gigahertz Intel Core2 Duo
    Motherboard
    Dell Inc. 0RY007 A01
    Memory
    4086 Megabytes Usable Installed Memory
    Graphics card(s)
    NVIDIA GeForce FX 5200 Intel(R) G33/G31 Ex
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Acer V173 NEC LCD72V
    Hard Drives
    ST3750630AS [Hard drive] (750.16 GB)
How to set your symbols:
Symbol File Path:
FYI - Open WinDbg, go to File...Symbol File Path
Delete anything in the box.
Then copy the stuff in the Code box below and paste it into the box.
Code: 
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Then click on OK to exit the dialog.
Then close WinDbg and answer Yes when it asks you if you want to "Save information for workspace"
Click to expand...

The program that generated the stuff in the Windows_NT6_BSOD_jcgriff2.zip folder was interrupted before it finished. Please run it again and let it run until it completes.

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)
Click to expand...

Also, from the above memory dump, please run Driver Verifier according to these directions:
Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
Code: 
Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
Click to expand...
 

My Computer

System One

Thank you for helping me with getting the symbols. I ran the debugger of the most recent BSOD and enclosed the report in the attached zip ("October 15, 2010.txt"). I ran the program again that generated "Windows_NT6_BSOD_jcgriff2". The results are in a folder of the same name within the zip. I ran the memory test throughout the night and it was negative. I ran several malware programs and they all came back negative. A report from one is within the zip ("Report 2010-1-14 23.27.37.txt"). I didn't run the HD Diagnostic as I don't think that's anything to do with the issue. I also ran a "System Diagnostics Report" and the results are within the zip as "perfmon-report.html". I didn't use Driver Verifier as it sounds very dangerous and I can't afford to be totally without this machine.

Anything you, or anyone, can advise on how I can fix this problem will be greatly appreciated.
 

My Computer

System One

  • Manufacturer/Model
    Dell
    CPU
    2.80 gigahertz Intel Core2 Duo
    Motherboard
    Dell Inc. 0RY007 A01
    Memory
    4086 Megabytes Usable Installed Memory
    Graphics card(s)
    NVIDIA GeForce FX 5200 Intel(R) G33/G31 Ex
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Acer V173 NEC LCD72V
    Hard Drives
    ST3750630AS [Hard drive] (750.16 GB)
What causes you to think that the hard drive has nothing to do with the issues you're experiencing?

If you choose not to run Driver Verifier, that's your choice.

Good luck
 

My Computer

System One

Seems inconsistent with HD troubles. However, I did run the HD test last PM and it was negative. Have you looked at any of the data I sent within the last zip? Can you deduce anything from that? Before, I risk the pitfalls that your message warns about for drive verifier, I'd prefer to see if the answer is knowable from the submitted data. That would be helpful to me. Can you help me? If I run DV, have you a contact # that I can consult with you on to walk me out of the trouble?
 

My Computer

System One

  • Manufacturer/Model
    Dell
    CPU
    2.80 gigahertz Intel Core2 Duo
    Motherboard
    Dell Inc. 0RY007 A01
    Memory
    4086 Megabytes Usable Installed Memory
    Graphics card(s)
    NVIDIA GeForce FX 5200 Intel(R) G33/G31 Ex
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Acer V173 NEC LCD72V
    Hard Drives
    ST3750630AS [Hard drive] (750.16 GB)
I am still unresolved in this issue. If anyone cares to jump in, I'd be appreciative. Alternatively, please refer me to another site.
 

My Computer

System One

  • Manufacturer/Model
    Dell
    CPU
    2.80 gigahertz Intel Core2 Duo
    Motherboard
    Dell Inc. 0RY007 A01
    Memory
    4086 Megabytes Usable Installed Memory
    Graphics card(s)
    NVIDIA GeForce FX 5200 Intel(R) G33/G31 Ex
    Sound Card
    Realtek High Definition Audio
    Monitor(s) Displays
    Acer V173 NEC LCD72V
    Hard Drives
    ST3750630AS [Hard drive] (750.16 GB)
You must log in or register to reply here.
Back
Top