Bluescreen, analiza mini-dump


(Reinsx) #1

Witam.

 

W różnych odstępach czasowych (czasami 2x w godzinę czasami 1x na dzień - w różnych momentach - czasami stoi bez używania wyświetlając pulpit a czasem modeluje 3D) pojawiają mi się BSODy i minidump zawsze to samo co zaraz zacytuje.

 

Początkowo myślałem że grafika - podmieniłem i myślałem że jest dobrze bo prawie 24 godziny baz zawieszki - ale jednak dalej to samo.

 

Plik dmp w załączniku. Narzędzie Microsoftu  mówi

 

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



	Loading Dump File [D:\072916-7737-01.dmp]
	Mini Kernel Dump File: Only registers and stack trace are available


	Symbol search path is: ***Invalid***
	****************************************************************************
	* Symbol loading may be unreliable without a symbol search path.           *
	* Use .symfix to have the debugger choose a symbol path.                   *
	* After setting your symbol path, use .reload to refresh symbol locations. *
	****************************************************************************
	Executable search path is:
	*********************************************************************
	* Symbols can not be loaded because symbol path is not initialized. *
	*                                                                   *
	* The Symbol Path can be set by:                                    *
	*   using the _NT_SYMBOL_PATH environment variable.                 *
	*   using the -y <symbol_path> argument when starting the debugger. *
	*   using .sympath and .sympath+                                    *
	*********************************************************************
	Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
	*** WARNING: Unable to verify timestamp for ntoskrnl.exe
	*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
	Windows 7 Kernel Version 7600 MP (8 procs) Free x64
	Product: WinNt, suite: TerminalServer SingleUserTS
	Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
	Machine Name:
	Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a2e50
	Debug session time: Fri Jul 29 11:14:38.679 2016 (GMT+2)
	System Uptime: 0 days 3:09:01.600
	*********************************************************************
	* Symbols can not be loaded because symbol path is not initialized. *
	*                                                                   *
	* The Symbol Path can be set by:                                    *
	*   using the _NT_SYMBOL_PATH environment variable.                 *
	*   using the -y <symbol_path> argument when starting the debugger. *
	*   using .sympath and .sympath+                                    *
	*********************************************************************
	Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
	*** WARNING: Unable to verify timestamp for ntoskrnl.exe
	*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
	Loading Kernel Symbols
	...............................................................
	................................................................
	.....................
	Loading User Symbols
	Loading unloaded module list
	......
	*******************************************************************************
	*                                                                             *
	*                        Bugcheck Analysis                                    *
	*                                                                             *
	*******************************************************************************


	Use !analyze -v to get detailed debugging information.


	BugCheck 50, {fffffa80c8a37158, 0, fffff80002eeadab, 5}


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


	*************************************************************************
	***                                                                  ***
	***                                                                  ***
	***    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                                    ***
	***                                                                  ***
	*************************************************************************
	*********************************************************************
	* Symbols can not be loaded because symbol path is not initialized. *
	*                                                                   *
	* The Symbol Path can be set by:                                    *
	*   using the _NT_SYMBOL_PATH environment variable.                 *
	*   using the -y <symbol_path> argument when starting the debugger. *
	*   using .sympath and .sympath+                                    *
	*********************************************************************
	*********************************************************************
	* Symbols can not be loaded because symbol path is not initialized. *
	*                                                                   *
	* The Symbol Path can be set by:                                    *
	*   using the _NT_SYMBOL_PATH environment variable.                 *
	*   using the -y <symbol_path> argument when starting the debugger. *
	*   using .sympath and .sympath+                                    *
	*********************************************************************
	Probably caused by : ntoskrnl.exe ( nt+85dab )


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

 

Konfiguracja komputera

Intel Xeon E3-1231v3

Asus Z97-K, Z97

Grafika docelowo Quadro 5000 chwilowo włożony do testów GTX 260.

Pamięć Crucial Ballistix 16GB (2x8GB)

Dysk Western Digital 2x1TB RAID0

Dysk SSD intel 535 system

Zasilacz XFX TS550W

Windows 7

072916-7737-01.dmp


(drunkula) #2

Nie wskazałeś symboli w WinDbg.


(Reinsx) #3

oki :slight_smile:

 

Jak dla mnie wygląda mi to na RAM (ale mogę się mylić).

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



	Loading Dump File [D:\072916-7737-01.dmp]
	Mini Kernel Dump File: Only registers and stack trace are available


	Symbol search path is: srv*c:\debugging\symbols*http://msdl.microsoft.com/download/symbols
	Executable search path is:
	Windows 7 Kernel Version 7600 MP (8 procs) Free x64
	Product: WinNt, suite: TerminalServer SingleUserTS
	Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
	Machine Name:
	Kernel base = 0xfffff800`02e65000 PsLoadedModuleList = 0xfffff800`030a2e50
	Debug session time: Fri Jul 29 11:14:38.679 2016 (GMT+2)
	System Uptime: 0 days 3:09:01.600
	Loading Kernel Symbols
	...............................................................
	................................................................
	.....................
	Loading User Symbols
	Loading unloaded module list
	......
	*******************************************************************************
	*                                                                             *
	*                        Bugcheck Analysis                                    *
	*                                                                             *
	*******************************************************************************


	Use !analyze -v to get detailed debugging information.


	BugCheck 50, {fffffa80c8a37158, 0, fffff80002eeadab, 5}



	Could not read faulting driver name
	Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+48b )


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


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


	PAGE_FAULT_IN_NONPAGED_AREA (50)
	Invalid system memory was referenced.  This cannot be protected by try-except,
	it must be protected by a Probe.  Typically the address is just plain bad or it
	is pointing at freed memory.
	Arguments:
	Arg1: fffffa80c8a37158, memory referenced.
	Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
	Arg3: fffff80002eeadab, If non-zero, the instruction address which referenced the bad memory
	    address.
	Arg4: 0000000000000005, (reserved)


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



	Could not read faulting driver name


	READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310d0e0
	 fffffa80c8a37158


	FAULTING_IP:
	nt!MiAgeWorkingSet+48b
	fffff800`02eeadab 6641837f1801    cmp     word ptr [r15+18h],1


	MM_INTERNAL_CODE:  5


	CUSTOMER_CRASH_COUNT:  1


	DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT


	BUGCHECK_STR:  0x50


	PROCESS_NAME:  System


	CURRENT_IRQL:  0


	TRAP_FRAME:  fffff88003932760 -- (.trap 0xfffff88003932760)
	NOTE: The trap frame does not contain all registers.
	Some register values may be zeroed or incorrect.
	rax=0000000000000003 rbx=0000000000000000 rcx=fffff6fc50098550
	rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
	rip=fffff80002eeadab rsp=fffff880039328f0 rbp=0000000000000007
	 r8=0000000000000001  r9=fffff80003061b40 r10=0000000000000005
	r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
	r14=0000000000000000 r15=0000000000000000
	iopl=0         nv up ei pl nz na pe nc
	nt!MiAgeWorkingSet+0x48b:
	fffff800`02eeadab 6641837f1801    cmp     word ptr [r15+18h],1 ds:00000000`00000018=????
	Resetting default scope


	LAST_CONTROL_TRANSFER:  from fffff80002f54b91 to fffff80002ed6f00


	STACK_TEXT:  
	fffff880`039325f8 fffff800`02f54b91 : 00000000`00000050 fffffa80`c8a37158 00000000`00000000 fffff880`03932760 : nt!KeBugCheckEx
	fffff880`03932600 fffff800`02ed4fee : 00000000`00000000 f1600042`e125c963 00000000`00000000 00000000`00000801 : nt! ?? ::FNODOBFM::`string'+0x40f5b
	fffff880`03932760 fffff800`02eeadab : 00000000`00000000 00000000`000003a1 00000000`00000000 00000000`0000004e : nt!KiPageFault+0x16e
	fffff880`039328f0 fffff800`02f57a0e : fffff800`03061b40 fffff880`00000001 00000000`00000001 fffff880`03932b70 : nt!MiAgeWorkingSet+0x48b
	fffff880`03932aa0 fffff800`02eeb6e2 : 00000000`00002c4e 00000000`00000000 fffffa80`00000000 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x49926
	fffff880`03932b40 fffff800`02eeb96f : 00000000`00000008 fffff880`03932bd0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
	fffff880`03932b90 fffff800`0317a166 : fffffa80`0c795040 00000000`00000080 fffffa80`0c763990 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
	fffff880`03932d00 fffff800`02eb5486 : fffff880`009ce180 fffffa80`0c795040 fffff880`009d90c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
	fffff880`03932d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16



	STACK_COMMAND:  kb


	FOLLOWUP_IP:
	nt!MiAgeWorkingSet+48b
	fffff800`02eeadab 6641837f1801    cmp     word ptr [r15+18h],1


	SYMBOL_STACK_INDEX:  3


	SYMBOL_NAME:  nt!MiAgeWorkingSet+48b


	FOLLOWUP_NAME:  MachineOwner


	MODULE_NAME: nt


	DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600


	IMAGE_NAME:  memory_corruption


	FAILURE_BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+48b


	BUCKET_ID:  X64_0x50_nt!MiAgeWorkingSet+48b


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

(drunkula) #4

Słusznie przypuszczasz… memtest, kilka przebiegów (zostaw na noc czy coś). Niestety, analiza nie identyfikuje sterownika powodującego błąd, a błąd 0x50 może dotyczyć zarówno RAM, VRAM, jak i L2 cache.

Kolejne możliwe przyczyny: antywirus (można tymczasowo wyłaczyć i testować), uszkodzona partycja NTFS oraz nieprawidłowy sterownik. Intrygujące jest też “VISTA_DRIVER_FAULT” - może nieprawidłowy driver chipsetu powoduje takie zachowanie pamięci? Masz wgrane od producenta? aktualizowałeś zanim BSOD zaczął się pojawiać?


(Reinsx) #5

Sterowniki od producenta - aczkolwiek mam problem z takim czymś ACPI\PNP0A0A (wykrzyknik - nieznane urządzenie - kilka sterowników próbowałem co na internecie znajdowałem ale problem występował od samego początku działania systemu).

 

Dzisiaj wsadziłem nową pamięc RAM a tamta chwilowo do pudła - poczekam zobaczę co się będzie działo.


(drunkula) #6

Sprawdź identyfikator sprzętu tego ustrojstwa z wykrzyknikiem.