Bsod - Irql Not Less Or Equal

[m4z!]

witam, jak w temacie mam ów problem na drugim kompie. zrobilem debbugerem zrzut ->

 

 

Microsoft ® Windows Debugger Version 6.8.0004.0 X86

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini031008-13.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 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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20

Debug session time: Mon Mar 10 20:35:25.975 2008 (GMT+1)

System Uptime: 0 days 0:00:52.635

*********************************************************************

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

..

Unable to load image psched.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for psched.sys

*** ERROR: Module load completed but symbols could not be loaded for psched.sys

Unable to load image NDIS.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for NDIS.sys

*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 100000D1, {0, 2, 0, f794cb2a}

 

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004

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

 

*** WARNING: Unable to verify timestamp for sisnic.sys

*** ERROR: Module load completed but symbols could not be loaded for sisnic.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 ***

*** ***

*************************************************************************

*********************************************************************

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

*********************************************************************

Probably caused by : sisnic.sys ( sisnic+125c )

 

Followup: MachineOwner

---------

 

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: 00000000, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: f794cb2a, address which referenced memory

 

Debugging Details:

------------------

 

ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.

ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004

***** 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: sisnic

 

FAULTING_MODULE: 804d7000 nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 3d2bf2c4

 

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

00000000

 

CURRENT_IRQL: 2

 

FAULTING_IP:

psched+8b2a

f794cb2a 8b18 mov ebx,dword ptr [eax]

 

CUSTOMER_CRASH_COUNT: 13

 

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

 

BUGCHECK_STR: 0xD1

 

LAST_CONTROL_TRANSFER: from f828bc0a to f794cb2a

 

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

f8951efc f828bc0a 82070c08 00bc3ef8 00000000 psched+0x8b2a

f8951f1c 81db2e82 8213b8b8 821bf4b8 00000000 NDIS+0x17c0a

f8951f5c f884f25c 8213b8b8 81bc3ef8 00000000 0x81db2e82

f8951f80 f885249a 821877b0 81bc3ef8 820f9c38 sisnic+0x125c

f8951fd0 804dc179 8219eac0 8219eaac 00000000 sisnic+0x449a

f8951fd4 8219eac0 8219eaac 00000000 00000000 nt+0x5179

f8951fd8 8219eaac 00000000 00000000 ef17547f 0x8219eac0

f8951fdc 00000000 00000000 ef17547f cf179b75 0x8219eaac

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

sisnic+125c

f884f25c ?? ???

 

SYMBOL_STACK_INDEX: 3

 

SYMBOL_NAME: sisnic+125c

 

FOLLOWUP_NAME: MachineOwner

 

IMAGE_NAME: sisnic.sys

 

BUCKET_ID: WRONG_SYMBOLS

 

Followup: MachineOwner

---------

 

 

ram jest sprawny, mam dwie kostki i sprawdzone nie ma problemu. po wywaleniu pliku psched.sys nie ma ów bledu jednak nie dziala net.. gdyz plik psched.sys zarzadza pakietami QoS. przeinstalowalem stery do zintegrowanej sieciowki sis 900 fast ethernet jednak nadal to samo. proszeeeeeee o poomoc :)

[m4z!]

anybody?