-Здравствуйте Андрей! У меня такая проблема... Переодически вылетает BSOD.
При сложном анализе выдает вот что:
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090310-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: srv*C:\symbols*http://msdl.microsoft.com/download/symbols
Unable to load image 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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Fri Sep 3 00:25:38.609 2010 (GMT+4)
System Uptime: 0 days 0:24:04.205
Unable to load image 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 10000050, {e58ede2d, 1, 805662ed, 2}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** WARNING: Unable to verify timestamp for cmuda.sys
*** ERROR: Module load completed but symbols could not be loaded for cmuda.sys
*************************************************************************
*** ***
*** ***
*** 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 : hardware ( cmuda+35d00 )
Followup: MachineOwner
---------
kd> kd: Reading initial command '!analyze -v; q'
*******************************************************************************
* *
* 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: e58ede2d, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 805662ed, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000002, (reserved)
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 ***
*** ***
*************************************************************************
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.
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 0
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
e58ede2d
FAULTING_IP:
nt+8f2ed
805662ed 018b4d108d04 add dword ptr [ebx+48D104Dh],ecx
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
MISALIGNED_IP:
nt+8f2ed
805662ed 018b4d108d04 add dword ptr [ebx+48D104Dh],ecx
LAST_CONTROL_TRANSFER: from 8056627f to 805662ed
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b8d589f0 8056627f 00000004 00000000 00000010 nt+0x8f2ed
b8d58a14 8056499f e1e19840 e101cd70 00000001 nt+0x8f27f
b8d58a34 8057ccfa e101cd70 88fea354 00000001 nt+0x8d99f
b8d58b3c 80563fec 8961e030 00000000 88fea338 nt+0xa5cfa
b8d58bc4 8056866a 00000000 b8d58c04 00000040 nt+0x8cfec
b8d58c18 8056f42b 00000000 00000000 00000801 nt+0x9166a
b8d58c94 8056f4fa 00b2f14c 00120080 00b2f0ec nt+0x9842b
b8d58cf0 8056f630 00b2f14c 00120080 00b2f0ec nt+0x984fa
b8d58d30 804de7ec 00b2f14c 00120080 00b2f0ec nt+0x98630
b8d58d64 7c90e514 badb0d00 00b2f0b4 00000000 nt+0x77ec
b8d58d68 badb0d00 00b2f0b4 00000000 00000000 0x7c90e514
b8d58d6c 00b2f0b4 00000000 00000000 00000000 cmuda+0x35d00
b8d58d70 00000000 00000000 00000000 00000000 0xb2f0b4
STACK_COMMAND: kb
FOLLOWUP_IP:
cmuda+35d00
badb0d00 ?? ???
SYMBOL_STACK_INDEX: b
SYMBOL_NAME: cmuda+35d00
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
---------
![[Изображение: c204d4ffbccc.jpg]](http://s52.radikal.ru/i135/1009/2d/c204d4ffbccc.jpg)