Dziwne Bsod'y

[Xanagaz]

Występują ich tylko dwa rodzaje, z końcówkami "D1" i "A"

Tutaj wyciąg z dump'a:

Microsoft (R) Windows Debugger  Version 6.5.0003.7Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini070305-05.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSKernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20Debug session time: Sun Jul  3 21:54:15.416 2005 (GMT+2)System Uptime: 0 days 0:21:45.013********************************************************************** 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 ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols..........................................................................................................................................Loading unloaded module list.............Loading User Symbols********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1000000A, {7ffd5000, 2, 1, 8057f7f0}***** Kernel symbols are WRONG. Please fix symbols to do analysis.*** WARNING: Unable to verify timestamp for mrxsmb.sys*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sysProbably caused by : mrxsmb.sys ( mrxsmb+23d00 )Followup: MachineOwner---------

Jak już wiemy prawdopodobnie to przez plik "mrxsmb.sys". Jak miałem system z SP1a to nie było tego. Teraz jestem na WinXP Pro SP2 i BSOD'y występują. Od czego jest ten plik? Format robiłem już z 5 razy, za każdym razem z zerowym skutkiem.

[Nyny]

Nic mi nie przychodzi do glowy poza supportem microsoftu.

Jesli to nie pomoze to nie mam zielonego pojecia co to moze byc.

czy debugger w kazdym przypadku wskazuje na ten plik mrxsmb.sys ?

 

Tutaj masz linka do tematów:

http://search.microsoft.com/search/results...2&qu=mrxsmb.sys

 

i sproboj zainstalowac ta auktualizacje o ktorej tam pisza:

http://www.microsoft.com/downloads/details...&displaylang=pl

 

Wszystkie najnowsze laty z windows update tez beda wskazane.

Sproboj tez poszukac cos na ten temat na google

[alcapone]

a w jakich momentach miales te restarty?

 

znalazlem jeszcze dwa przypadki:

klik! i klik!

[Xanagaz]

Zawsze winny jest ten plik. Zainstalowałem "WindowsXP-KB885250-x86-PLK.exe" i nie pomogło, nadal BSOD'y. Jutro zobaczę czy na samym Windows XP Pro jest taka sytuacja, potem zintegruje instalkę Win XP z SP1a i zobaczę na tym, następnie zobaczę znowy na zintegrowanym SP2. Zdam relację jak poszło ;)

 

Windows na nowo. C sformatowany, najpierw instalowałem samego Win XP Pro, następnie na niego SP2 (wcześniej to było zintegrowane ze sobą za pomocą nLite), sterowniki, aktualizacje i inne programy. Wystąpił mi BSOD z końcówką "A" lub "A1", nie pamiętam za bardzo. Co dziwne BSOD wystąpił po tym jak wszystkie pliki podczas instalacji WMP10 zdążyły sie skopiować na dysk... To tak jakby oprogramowanie MSoftu same sobie BSDA spowodowało... Myślałem wcześniej, że to właśnie nLite coś miesza ale się okzało, że to nie on. Zaaplikowałem sobie różne tweaki poprzez rejestr (czyszczenie pliku wymiany podczas zamykania sie systemu, unload dlli itd.). Może to być przyczyną BSOD'ów?

 

Pierwszy BSOD (opisany):

Microsoft (R) Windows Debugger  Version 6.5.0003.7Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini070705-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSKernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420Debug session time: Thu Jul  7 13:02:14.885 2005 (GMT+2)System Uptime: 0 days 0:23:21.478********************************************************************** 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 ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols......................................................................................................................................Loading unloaded module list..................Loading User Symbols********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 1000000A, {7ffd9000, 2, 1, 8057b753}***** Kernel symbols are WRONG. Please fix symbols to do analysis.Followup: MachineOwner---------

Drugi BSOD - nic nie robiłem, sam się spowodował...:

Microsoft (R) Windows Debugger  Version 6.5.0003.7Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\WINDOWS\Minidump\Mini070705-02.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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 ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeWindows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSKernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420Debug session time: Thu Jul  7 13:14:39.783 2005 (GMT+2)System Uptime: 0 days 0:10:28.373********************************************************************** 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 ntoskrnl.exe, Win32 error 2*** WARNING: Unable to verify timestamp for ntoskrnl.exe*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exeLoading Kernel Symbols.......................................................................................................................................Loading unloaded module list...........Loading User Symbols********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 100000D1, {7c837d4a, 2, 0, 7c837d4a}***** Kernel symbols are WRONG. Please fix symbols to do analysis.Followup: MachineOwner---------

Edytowane 7 Lipca 2005 przez Xanagaz