- Сообщения
- 24,710
- Реакции
- 13,565
Никак. Только пожаловаться модератору.И все-таки -- как редактировать свои сообщения на форуме?
Смотрите видео ниже, чтобы узнать, как установить наш сайт в качестве веб-приложения на домашнем экране.
Примечание: Эта возможность может быть недоступна в некоторых браузерах.
Никак. Только пожаловаться модератору.И все-таки -- как редактировать свои сообщения на форуме?
В Вашем случае нет.Насколько я понял из вывода команды, BSOD был из-за ошибки в Firefox 4 или не так?
Проблема в драйвере ULCDRHlp.sys.*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000046, The exception code that was not handled
Arg2: 82a829a0, The address that the exception occurred at
Arg3: abceb16c, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for ULCDRHlp.sys
*** ERROR: Module load completed but symbols could not be loaded for ULCDRHlp.sys
*** WARNING: Unable to verify timestamp for PxHelp20.sys
*** ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
*** WARNING: Unable to verify timestamp for Wdf01000.sys
*** ERROR: Module load completed but symbols could not be loaded for Wdf01000.sys
*** WARNING: Unable to verify timestamp for cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
*** WARNING: Unable to verify timestamp for mountmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for mountmgr.sys
***** 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+ *
*********************************************************************
FAULTING_MODULE: 82a01000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41c9dd4d
EXCEPTION_CODE: (NTSTATUS) 0xc0000046 - <Unable to get error code text>
FAULTING_IP:
nt+819a0
82a829a0 cc int 3
TRAP_FRAME: abceb16c -- (.trap 0xffffffffabceb16c)
ESP EDITED! New esp=abceb51c
ErrCode = 00000000
eax=c0000046 ebx=878af030 ecx=871e2500 edx=00000000 esi=871e25e4 edi=00000000
eip=82a829a0 esp=abceb1e0 ebp=abceb554 iopl=0 nv up ei ng nz na po nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000282
nt+0x819a0:
82a829a0 cc int 3
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 82a82782 to 82a829a0
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
abceb554 82a82782 871e25e4 00000001 00000000 nt+0x819a0
abceb56c 9a1f413c 871e25e4 00000000 871f3018 nt+0x81782
abceb58c 9a1f1a7f 005eb008 82a38593 871e24e0 ULCDRHlp+0x313c
abceb5ac 8b85f48c 8b86067c 871f3018 855eb008 ULCDRHlp+0xa7f
abceb5cc 82a38593 871f3018 855eb008 88284aa8 PxHelp20+0x448c
abceb5e4 8b62049c 78e1b860 abceb670 00000000 nt+0x37593
abceb628 8b62bffe 00284aa8 abceb670 abceb654 Wdf01000+0xa49c
abceb64c 8bee249a 00000020 88284aa8 871e4798 Wdf01000+0x15ffe
abceb680 8bee226d 78e199f0 88284b80 00000000 cdrom+0xf49a
abceb6a0 8b644fe8 871e67d0 77d7b550 88284aa8 cdrom+0xf26d
abceb6b8 8b6465e6 78e05490 77d7b550 88284aa8 Wdf01000+0x2efe8
abceb6dc 8b6489ac 77d7b550 88284aa8 871fab68 Wdf01000+0x305e6
abceb6f8 8b649a36 871fab00 00000000 855eb008 Wdf01000+0x329ac
abceb718 8b643ff4 88284aa8 855eb12c 86049918 Wdf01000+0x33a36
abceb74c 8b6441f0 855eb008 871fb0d8 871e4ac0 Wdf01000+0x2dff4
abceb768 8b63aa3f 855eb008 abceb78c 82a38593 Wdf01000+0x2e1f0
abceb774 82a38593 871e4ac0 855eb008 855eb12c Wdf01000+0x24a3f
abceb78c 9a1f882a 88152330 871fb020 855eb008 nt+0x37593
abceb7a8 82a38593 001fb020 005eb008 8815238c GEARAspiWDM+0x82a
abceb7c0 82c482a9 84c708a1 abceb968 00000000 nt+0x37593
abceb898 82c27ac5 871e4ac0 8d174698 856e9330 nt+0x2472a9
abceb914 82c37ed6 00000000 abceb968 00000240 nt+0x226ac5
abceb974 82c2e9b4 abcebb00 85174698 abceb900 nt+0x236ed6
abceb9f0 82c34b3a abcebaf0 00000080 abcebb00 nt+0x22d9b4
abceba38 82a3f1ea abcebaf0 00000080 abcebb00 nt+0x233b3a
abceba58 82a3d561 badb0d00 abcebad0 82008593 nt+0x3e1ea
abcebb1c 8b7ab3da abcebbb8 00000080 abcebb44 nt+0x3c561
abcebb4c 8b7abb51 85a9fe58 abcebbb8 abcebb80 mountmgr+0x93da
abcebb8c 8b7b1be7 85a9fe58 abcebbb8 00000000 mountmgr+0x9b51
abcebbe0 8b7b35df 85a9fe58 8797be38 85710260 mountmgr+0xfbe7
abcebbfc 82a38593 85a9fe74 006d0034 8797be38 mountmgr+0x115df
abcebc14 82c2c99f 85710260 8797be38 8797bea8 nt+0x37593
abcebc34 82c2fb71 85a9fda0 85710260 00000000 nt+0x22b99f
abcebcd0 82c763f4 85a9fda0 8797be38 00000000 nt+0x22eb71
abcebd04 82a3f1ea 00000148 00000000 00000000 nt+0x2753f4
abcebd34 779d70b4 badb0d00 0574f82c 00000000 nt+0x3e1ea
abcebd38 badb0d00 0574f82c 00000000 00000000 0x779d70b4
abcebd3c 0574f82c 00000000 00000000 00000000 0xbadb0d00
abcebd40 00000000 00000000 00000000 00000000 0x574f82c
STACK_COMMAND: kb
FOLLOWUP_IP:
ULCDRHlp+313c
9a1f413c ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: ULCDRHlp+313c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ULCDRHlp
IMAGE_NAME: ULCDRHlp.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
0: kd> lmvm ULCDRHlp
start end module name
9a1f1000 9a1f7b00 ULCDRHlp T (no symbols)
Loaded symbol image file: ULCDRHlp.sys
Image path: \SystemRoot\System32\Drivers\ULCDRHlp.sys
Image name: ULCDRHlp.sys
Timestamp: Thu Dec 23 01:47:09 2004 (41C9DD4D)
CheckSum: 000081C3
ImageSize: 00006B00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Скорее всего, даже не в нем, а в ссылке на него, которая продолжала оставаться в ключе LowerFilters раздела реестра, отвечавшего за класс CD/DVD-ROM.Получается, таки-да, проблема была в этом драйвере ULCDRHlp.sys, в новой системе его нет сейчас.
rulet, 0x8E ошибки почти всегда вызваны с аппаратными проблемами совместимости...
это верно.Причиной критических ошибок Windows, сопровождаемых синими экранами (BSOD), часто является драйвер - вновь установленный или поврежденный. Определив, какой именно драйвер служит причиной ошибки, можно приступать к устранению проблемы: обновить драйвер, откатиться к более ранней версии, переустановить или удалить приложение, установившее драйвер и т. д. Не всегда название драйвера отображается на синем экране. Однако существует очень простой способ, позволяющий с помощью дампа памяти определить проблемный драйвер за пару минут.