Witamy na forum PC Format Zapraszamy do REJESTRACJI


U┼╝ytkownicy przegl─ůdaj─ůcy ten w─ůtek: 1 go┼Ťci

BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

#1
BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Witam

Mam taki problem jak u┼╝ywam programu utorrent to wiesza mi sie caly komputer ponizej daje log z debugera moze ktos bedzie umial mi pomoc bo nie mam pojecia co mam zrobic

Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini011808-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbole*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri Jan 18 04:13:16.031 2008 (GMT+1)
System Uptime: 0 days 1:58:47.498
Loading Kernel Symbols
.................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {f1f53d, 2, 1, 7c9114b6}



Probably caused by : Unknown_Image ( INVALID_CONTEXT )

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: 00f1f53d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c9114b6, address which referenced memory

Debugging Details:
------------------




CURRENT_IRQL: 2

FAULTING_IP:
+7c9114b6
7c9114b6 884f05 mov byte ptr [edi+5],cl

PROCESS_NAME: utorrent.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

SYMBOL_NAME: INVALID_CONTEXT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

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: 00f1f53d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c9114b6, address which referenced memory

Debugging Details:
------------------




CURRENT_IRQL: 2

FAULTING_IP:
+7c9114b6
7c9114b6 884f05 mov byte ptr [edi+5],cl

PROCESS_NAME: utorrent.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

SYMBOL_NAME: INVALID_CONTEXT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

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: 00f1f53d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c9114b6, address which referenced memory

Debugging Details:
------------------




CURRENT_IRQL: 2

FAULTING_IP:
+7c9114b6
7c9114b6 884f05 mov byte ptr [edi+5],cl

PROCESS_NAME: utorrent.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

SYMBOL_NAME: INVALID_CONTEXT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

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: 00f1f53d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c9114b6, address which referenced memory

Debugging Details:
------------------




CURRENT_IRQL: 2

FAULTING_IP:
+7c9114b6
7c9114b6 884f05 mov byte ptr [edi+5],cl

PROCESS_NAME: utorrent.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

SYMBOL_NAME: INVALID_CONTEXT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

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: 00f1f53d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c9114b6, address which referenced memory

Debugging Details:
------------------




CURRENT_IRQL: 2

FAULTING_IP:
+7c9114b6
7c9114b6 884f05 mov byte ptr [edi+5],cl

PROCESS_NAME: utorrent.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

SYMBOL_NAME: INVALID_CONTEXT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

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: 00f1f53d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c9114b6, address which referenced memory

Debugging Details:
------------------




CURRENT_IRQL: 2

FAULTING_IP:
+7c9114b6
7c9114b6 884f05 mov byte ptr [edi+5],cl

PROCESS_NAME: utorrent.exe

BUGCHECK_STR: RAISED_IRQL_FAULT

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

SYMBOL_NAME: INVALID_CONTEXT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

FAILURE_BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

BUCKET_ID: RAISED_IRQL_FAULT_utorrent.exe_INVALID_CONTEXT

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

1: kd> !pte
VA 00000000
PDE at C0300000 PTE at C0000000
Unable to get PDE FFFFFFFFC0300000
 System operacyjny: windows_xp_2003 Przegl─ůdarka: firefox
#2
RE: BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Spisz sobie kody b┼é─Öd├│w z bluescreena i zapoznaj sie z tre┼Ťci─ů przyklejonego na temat b┼é─Öd├│w krytycznych.Najprawdopodobniej co┼Ť jest nie tak z pami─Öci─ů ram,poniewa┼╝ w tym chodzi o to ze chce uzyska─ç dost─Öp do autoryzacji
 Przegl─ůdarka: opera
#3
RE: BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Chinka d to b┼é─ůd w obliczeniach procesora a (a) to b┼é─ůd w module RAM do autora operacja nie mo┼╝e zosta─ç wykonana bo procesor mo┼╝e by─ç przeci─ů┼╝ony co jest powodem BSODA.
 System operacyjny: windows_xp_2003 Przegl─ůdarka: firefox
#4
RE: BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Witam to znowu ja niestety dalej nie uporałem się z tym problemem tym razem mam dumpa z utorrenta

Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Program Files\uTorrent\7859-utorrent.9449.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: SRV*c:\symbole*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Version 2600 (Service Pack 3, v.3244) MP (2 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Tue Jan 22 03:19:18.000 2008 (GMT+1)
System Uptime: not available
Process Uptime: 0 days 8:14:32.000
............
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(a1c.544): Access violation - code c0000005 (first/second chance not available)
eax=05b30000 ebx=00bc4b30 ecx=00000007 edx=7c90e4f4 esi=00bc4b08 edi=00bc4b60
eip=7c90e4f4 esp=010eee68 ebp=010eee78 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
ntdll!KiFastSystemCallRet:
7c90e4f4 c3 ret

Procesor mam pentiuma duo 2x 2.8ghz i zostawiam w┼é─ůczony komputer z odpalonym tylko u torrentem wi─Öc raczej przeci─ů┼╝ony procek odpada
 System operacyjny: windows_xp_2003 Przegl─ůdarka: firefox
#5
RE: BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
~Anonim napisał(a):[...]Windows XP Version 2600 (Service Pack 3, v.3244) MP (2 procs) Free x86 compatible [...]
Witam, Moim zdaniem cytowanie ca┼éego dumpa tutaj mija si─Ö z sensem. 90% tych informacji jest zb─Ödnych nawet zaawansowanemu u┼╝ytkownikowi-programi┼Ťcie.
Moj─ů uwag─Ö zwr├│ci┼éa jedynie Beta SP3. Mo┼╝e trzeba zaczeka─ç do Final, chwilowo rezygnuj─ůc z tego dodatku?
--
Pozdrawiam
 System operacyjny: windows_vista Przegl─ůdarka: ie
#6
RE: BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
To samo dzia┼éo si─Ö z service packiem 2 ten sp3 zainstalowa┼éem bo mia┼éem nadzieje ┼╝e to co┼Ť pomo┼╝e ale dalej jest tak samo
 System operacyjny: windows_xp_2003 Przegl─ůdarka: firefox
Programy: Polecane / Nowe / Inne



U┼╝ytkownicy forum szukali:
driver_irql_not_less_or_equal d1windows xp 7C9114B6

Podobne w─ůtki (BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1))
W─ůtek: Autor Odpowiedzi: Wy┼Ťwietle┼ä: Ostatni post
  Windows 10 BSOD Prolax0990 4 4666 27.06.2018, 03:10
Ostatni post: Illidan
Ściana BsoD po instalacji Win7 HeraldOfRuin 1 4184 19.02.2018, 15:02
Ostatni post: pytam32
  BSOD 0x00000116 w Windows 7 Szymeg 1 4015 29.12.2017, 19:01
Ostatni post: broda99

Skocz do:


Wybrane w─ůtki (BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1))
W─ůtek: Autor Odpowiedzi: Wy┼Ťwietle┼ä: Ostatni post
  Sterowniki po zainstalowaniu systemu GierO 2 2505 11.09.2019 08:57
Ostatni post: Arczi7
  Jak Doda─ç Fabryczn─ů partycje Recovery? Igor Miko┼éajczyk 3 3016 06.09.2019 17:42
Ostatni post: Armo
Question Programy darmowe, alternatywne dla SlimDrivers i Snaildriver do sterownik├│w Illidan 0 2096 05.09.2019 23:14
Ostatni post: Illidan
  Czy w konsoli CMD jest mo┼╝liwe kopiownie kilku plik├│w do folderu witnow 5 3136 03.09.2019 19:45
Ostatni post: witnow
  Poszukuj─Ö dobrego systemu ERP Gregor56 5 4304 02.09.2019 15:47
Ostatni post: rysiek77
  Problem z Win10 edgarx 0 2186 02.09.2019 08:40
Ostatni post: edgarx
  Zacinanie si─Ö muzyki podczas s┼éuchania ShaintoS 0 2330 29.08.2019 11:32
Ostatni post: ShaintoS
  Wy┼é─ůczenie zb─Ödnych funkcji Windows 10 Home/Pro adiq1033 6 3077 28.08.2019 17:46
Ostatni post: Fix00ser
  Jak zmieni─ç nawiasy na jeden w cytatach w wordzie? natalkowata10 0 2164 27.08.2019 20:54
Ostatni post: natalkowata10
  Bios nie zapami─Ötuje ustawie┼ä bootowania smialy1 1 789 27.08.2019 11:23
Ostatni post: umiejead
  System Recovery Options nie dzia┼éa mysz klawiatura Bartek94 4 2495 22.08.2019 20:37
Ostatni post: Bartek94
  Windows 10 ci─ůg┼ée skupienie Jarek1104 1 2347 20.08.2019 16:11
Ostatni post: Michu_PL
  Zu┼╝ycie procesora 40-50% ntoskrnl.exe po w┼é─ůczeniu qbitorrent,utorrent komarzycho 0 585 19.08.2019 16:59
Ostatni post: komarzycho
  Problem Z ASUS BackTracker Igor Miko┼éajczyk 0 2133 18.08.2019 15:17
Ostatni post: Igor Mikołajczyk
  Klucz przypisany do p┼éyty g┼é├│wnej, kt├│r─ů chce sprzeda─ç - mo┼╝na go "wyci─ůgn─ůc"? adiq1033 8 3863 15.08.2019 23:09
Ostatni post: Officer Crabtree