Имя пользователя:
Пароль:  
Помощь | Регистрация | Забыли пароль?  

Показать сообщение отдельно

Новый участник


Сообщения: 23
Благодарности: 0

Профиль | Отправить PM | Цитировать


поставил все это
Изменений нет
зато есть новый дамп:
Код: Выделить весь код
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: a54e20b1, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: a54e20b1, address which referenced memory

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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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+                                    *
*********************************************************************

MODULE_NAME: NDIS

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  41107ec3

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 a54e20b1 

CURRENT_IRQL:  1c

FAULTING_IP: 
+ffffffffa54e20b1
a54e20b1 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from 00000000 to a54e20b1

FAILED_INSTRUCTION_ADDRESS: 
+ffffffffa54e20b1
a54e20b1 ??              ???

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb060bde8

STACK_COMMAND:  dds B060BDE8-0x20 ; kb

STACK_TEXT:  
b060bdc8  00000000
b060bdcc  7c90eb94
b060bdd0  0000001b
b060bdd4  00200202
b060bdd8  0012f708
b060bddc  00000023
b060bde0  804ec791 nt+0x15791
b060bde4  f7411b85 NDIS+0x6b85
b060bde8  8897d400
b060bdec  00000000
b060bdf0  0020027f
b060bdf4  7c910000
b060bdf8  00000000
b060bdfc  00000000
b060be00  00000000
b060be04  00000000
b060be08  00001fa0
b060be0c  0000ffff
b060be10  895ebb00
b060be14  e35771f0
b060be18  0000ba34
b060be1c  00000000
b060be20  e35771f0
b060be24  00000004
b060be28  00003af2
b060be2c  00000000
b060be30  bf82327c win32k+0x2327c
b060be34  bc69e548
b060be38  000078a8
b060be3c  00000000
b060be40  0000038c
b060be44  e3bb0848


FOLLOWUP_IP: 
NDIS+6b85
f7411b85 ??              ???

SYMBOL_NAME:  NDIS+6b85

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  NDIS.sys

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner
---------

-------
моя проблема:
http://forum.oszone.net/thread-114248.html


Отправлено: 08:54, 17-04-2008 | #14