Wkur... BSOD'y

isbjorn

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.7
Copyright (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 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 ntoskrnl.exe, Win32 error 2
*** WARNING&#58; Unable to verify timestamp for ntoskrnl.exe
*** ERROR&#58; Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 &#40;Service Pack 2&#41; UP Free x86 compatible
Product&#58; WinNt, suite&#58; TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time&#58; Sun Jul  3 21&#58;54&#58;15.416 2005 &#40;GMT+2&#41;
System Uptime&#58; 0 days 0&#58;21&#58;45.013
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
*                                                                  *
* The Symbol Path can be set by&#58;                                    *
*  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&#58; Unable to verify timestamp for ntoskrnl.exe
*** ERROR&#58; Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
..........................................................................................................................................
Loading unloaded module list
.............
Loading User Symbols
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, &#123;7ffd5000, 2, 1, 8057f7f0&#125;

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

*** WARNING&#58; Unable to verify timestamp for mrxsmb.sys
*** ERROR&#58; Module load completed but symbols could not be loaded for mrxsmb.sys
Probably caused by &#58; mrxsmb.sys &#40; mrxsmb+23d00 &#41;

Followup&#58; 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.
  • zanotowane.pl
  • doc.pisz.pl
  • pdf.pisz.pl
  • jasekupa.opx.pl
  • Copyright (c) 2009 isbjorn | Powered by Wordpress. Fresh News Theme by WooThemes - Premium Wordpress Themes.