Posiadam dwa ostatnio kupione komputery o bardzo podobnych parametrach ze sklonowanym Windowsem 7 64bit Enterprise.
# Komputer A:
- zasilacz: Tracer Highlander 500W
- płyta główna: Asus M4N68T-M Le v2
- procesor: AMD Phenom II X4 955
- pamięć: 4GB DDR3
- karta graficzna: (wbudowana) NVIDIA GeForce 7025 / NVIDIA nForce 630a + Zotac Geforce 8600GT
- dysk - WDC Black 1TB (kupiony jakiś czas temu)
# Komputer B:
- zasilacz: Qoltec Silent Line 425W
- płyta główna: Asus M4N68T-M Le v2
- procesor: AMD Athlon II X2 250
- pamięć: 2GB DDR3
- karta graficzna: (wbudowana) NVIDIA GeForce 7025 / NVIDIA nForce 630a
- dysk - WDC Green 1TB (nowy)
-> Wykluczam uszkodzenia dysku ze względu na to, że są to dwa różne dyski, kupowane w różnym czasie i skanowane z pozytywnym rezultatem za pomocą MHDD.
-> Wykluczam problem z pamięcią, gdyż skanowałem memtestem (1,5h, 2 razy success).
-> Wykluczam usterkę techniczną karty graficznej, gdyż dzieje się tak na dwóch komputerach z tą samą (wbudowaną) kartą graficzną, oraz po podłączeniu zewnętrznej karty graficznej (działającej na tych samych sterownikach).
-> Wykluczam (raczej) zasilacz, gdyż testowałem na dwóch komputerac z dwoma różnymi zasilaczami a problem pojawia się nie przypadkowo, lecz regularnie przy identycznych czynnościach.
-> System został zaktulanizowany za pomocą Microsoft Update.
Problem pojawia się w momencie przejścia w tryb eksploratora z poziomu programu. Pierwszy raz zauważyłem to chyba przy próbie otwarcia napisów za pomocą VLC. Dzisiaj próbowałem otworzyć pliki dmp za pomocą WinDbg i efekt był identyczny. W trybie awaryjnym nie pojawia się ten problem. Póki co nie zauważyłem innych okoliczności BSOD.
Mam zainstalowaną najnowszą wersję sterowników ze strony nvidii na architekturę 64bit. Instalowałem również na wszelki wypadek najnowsze sterowniki ze strony Asusa do płyty głównej. Poniżej załączam paczkę z plikami dmp, zdjęcie bluescreena oraz przykładową treść pliku dmp (odpalone z innego komputera).
# Informacja po ponownym uruchomieniu systemu Windows:
Kod:
Podpis problemu:
Nazwa zdarzenia problemu: BlueScreen
Wersja systemu operacyjnego: 6.1.7600.2.0.0.256.4
Identyfikator ustawień regionalnych: 1045
Dodatkowe informacje o problemie:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800267ACD0
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
# Jeden z plików *.dmp:
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [K: \minidm\021511-16660-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a67000 PsLoadedModuleList = 0xfffff800`02ca4e50
Debug session time: Tue Feb 15 14: 26: 55.824 2011 (UTC + 1: 00)
System Uptime: 0 days 0: 21: 50.759
*********************************************************************
* 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 1E, {ffffffffc0000005, fffff8800606bcd0, 0, 0}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+70740 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800606bcd0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
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: fffff80002a67000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
FAULTING_IP:
+2902faf015edfc0
fffff880`0606bcd0 e8cb060680 call fffff87f`860cc3a0
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002b69bdb to fffff80002ad7740
STACK_TEXT:
fffff880`0606bc18 fffff800`02b69bdb : 00000000`0000001e ffffffff`c0000005 fffff880`0606bcd0 00000000`00000000 : nt+0x70740
fffff880`0606bc20 00000000`0000001e : ffffffff`c0000005 fffff880`0606bcd0 00000000`00000000 00000000`00000000 : nt+0x102bdb
fffff880`0606bc28 ffffffff`c0000005 : fffff880`0606bcd0 00000000`00000000 00000000`00000000 fffffa80`06ce1940 : 0x1e
fffff880`0606bc30 fffff880`0606bcd0 : 00000000`00000000 00000000`00000000 fffffa80`06ce1940 fffffa80`05562000 : 0xffffffff`c0000005
fffff880`0606bc38 00000000`00000000 : 00000000`00000000 fffffa80`06ce1940 fffffa80`05562000 fffff800`02b28d30 : 0xfffff880`0606bcd0
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+70740
fffff800`02ad7740 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+70740
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> lmvm nt
start end module name
fffff800`02a67000 fffff800`03044000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: \SystemRoot\system32\ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Wed Oct 27 04: 43: 09 2010 (4CC791BD)
CheckSum: 00550986
ImageSize: 005DD000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> lmvm nt
start end module name
fffff800`02a67000 fffff800`03044000 nt T (no symbols)
Loaded symbol image file: ntoskrnl.exe
Image path: \SystemRoot\system32\ntoskrnl.exe
Image name: ntoskrnl.exe
Timestamp: Wed Oct 27 04: 43: 09 2010 (4CC791BD)
CheckSum: 00550986
ImageSize: 005DD000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
# Paczka plików *.dmp:
[url]http://rapidshare.com/files/448114611/minidmp.zip"]http://rapidshare.com/files/448114611/minidmp.zip[/url]
# Zdjęcie Bluescreena:
Uploaded with
ImageShack.us
Post: #1
