Hilfe
Neues Thema
Antworten
geschrieben Ich bekomme seit ca 2 tagen ein und den selben Bluescreen, den ersten wo ich nach hause kam war er schon da,
das andere mal war ich einen Film am gucken (ton blieb stehen und bluescreen kam)
in dem Bluesceen Stand Folgendes:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Ich habe wie geschrieben schon überall mal goggle suchen lassen , aber da kommt soviel unterschiedliches raus , von CPU ecken kaputt bis Ram oder treiber defekt.
Habe diese mit dem Windows Debugger tool Angesehen und da kam diese bei raus :
Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dokumente und Einstellungen\Snake\Desktop\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
**************************************************
*******************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Feb 13 11:20:05.500 2008 (GMT+1)
System Uptime: 0 days 1:22:04.257
**************************************************
*******************
* 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+ *
**************************************************
*******************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Loading Kernel Symbols
..................................................
..................................................
.
............................
Loading User Symbols
Loading unloaded module list
................
*** ERROR: Module load completed but symbols could not be loaded for DrvFltIp
**************************************************
*****************************
* *
* Bugcheck Analysis *
* *
**************************************************
*****************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {880020, 2, 0, bac7aa29}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for tcpip.sys -
*** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for NDIS.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for psched.sys -
*** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
*** ERROR: Module load completed but symbols could not be loaded for RMSPPPOE.SYS
*** ERROR: Module load completed but symbols could not be loaded for NVENETFD.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 : DrvFltIp ( DrvFltIp+2a29 )
Followup: MachineOwner
---------
1: 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: 00880020, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: bac7aa29, 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+ *
**************************************************
*******************
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4589e4bb
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00880020
CURRENT_IRQL: 2
FAULTING_IP:
DrvFltIp+2a29
bac7aa29 8b08 mov ecx,dword ptr [eax]
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from bac7aa29 to 80543a70
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
bacd36bc bac7aa29 badb0d00 899f7600 bacd3704 nt!Kei386EoiHelper+0x2834
bacd3748 b7262733 86ebf028 89723be0 00000e20 DrvFltIp+0x2a29
bacd37a8 b72573a2 89723be0 00001850 8988cfdc tcpip!ARPRcv+0xa493
bacd3830 b7254ef5 86f198a8 e87b8b54 4a58b255 tcpip!IPTransmit+0x1764
bacd3890 b7254b19 00000020 86f198a8 b7257076 tcpip!IPFreeBuff+0x634
bacd390c b7254836 b72944f0 86f198a8 86d8d072 tcpip!IPFreeBuff+0x258
bacd39c4 ba9ad232 86f198a8 86d8d086 00000528 tcpip!IPRcvPacket+0x296
bacd3a08 ba9ad2cc 0cabb1e5 8784b058 86d8d064 wanarp+0x5232
bacd3a40 ba527b9f 0cabb1e5 00000000 b9accb40 wanarp+0x52cc
bacd3a94 b9ac701d 00d70278 896bef60 00000001 NDIS!FddiFilterDprIndicateReceive+0xaa8
bacd3aa8 b9ac71b4 897f8130 896bef60 00000001 psched!RegisterPsComponent+0x6cef
bacd3acc b9ac75f9 8979bb30 00000000 897f8130 psched!RegisterPsComponent+0x6e86
bacd3ae4 ba527c40 8979bb28 86f17550 86ecf008 psched!RegisterPsComponent+0x72cb
bacd3b34 b9b05c66 00d70278 bacd3b74 00000001 NDIS!FddiFilterDprIndicateReceive+0xb49
bacd3b68 b9b05f22 02ecf008 8784b058 86ecf008 ndiswan+0xdc66
bacd3b9c b9b063cf 86ecf008 86d8d008 00000540 ndiswan+0xdf22
bacd3bb8 b9b03e51 879c29b8 86d8d008 88a4e730 ndiswan+0xe3cf
bacd3bdc ba522888 00000001 88c56a1c 00000540 ndiswan+0xbe51
bacd3c00 bac73535 bacd3c28 027b4818 00000001 NDIS!NdisMWanIndicateReceive+0x54
bacd3c34 bac763e8 00000000 88c56a1e 00000552 RMSPPPOE+0x3535
bacd3c5c ba527e45 00000552 88c56a0a 8053fd10 RMSPPPOE+0x63e8
bacd3cb0 ba96e14a 00dcc848 894535d0 00000001 NDIS!FddiFilterDprIndicateReceive+0xd4e
00000000 00000000 00000000 00000000 00000000 NVENETFD+0x614a
STACK_COMMAND: kb
FOLLOWUP_IP:
DrvFltIp+2a29
bac7aa29 8b08 mov ecx,dword ptr [eax]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: DrvFltIp+2a29
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: DrvFltIp
IMAGE_NAME: DrvFltIp
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> lmvm DrvFltIp
start end module name
bac78000 bac7f200 DrvFltIp (no symbols)
Loaded symbol image file: DrvFltIp
Image path: \?\C:\Dokumente und Einstellungen\Snake\Lokale Einstellungen\TEMP\DrvFltIp
Image name: DrvFltIp
Timestamp: Thu Dec 21 02:34:51 2006 (4589E4BB)
CheckSum: 0000EE55
ImageSize: 00007200
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
Könnt ihr mir weiterhelfen , ich stehe somit vor einem leeren Loch^^
Nach oben
