Zurück   Trojaner-Board > Web/PC > Alles rund um Windows

Alles rund um Windows: Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL

Windows 7 Hilfe zu allen Windows-Betriebssystemen: Windows XP, Windows Vista, Windows 7, Windows 8(.1) und Windows 10 - als auch zu sämtlicher Windows-Software. Alles zu Windows 10 ist auch gerne willkommen. Bitte benenne etwaige Fehler oder Bluescreens unter Windows mit dem Wortlaut der Fehlermeldung und Fehlercode. Erste Schritte für Hilfe unter Windows.

Antwort
Alt 09.08.2015, 09:39   #1
markus_bs
 
Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL - Beitrag

Problem: Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL



Hallo zusammen,

mich plagen seit geraumer Zeit regelmässige Komplettabstürze meines PCs. Den Grafikkartentreiber habe ich gestern geupdated, das Problem besteht aber weiter. Aus der Recherche in anderen Beiträgen vermute ich, dass ich weitere Treiber updaten sollte. Leider weiss ich aber nicht welche und wie ich am geschicktesten vorgehe.

Vielen Dank im Voraus für eure Unterstützung
Markus


Anliegend die Zusammenfassung aus WhoCrashed:

System Information (local)
--------------------------------------------------------------------------------

computer name: MARKUS-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: MS-7713, MEDIONPC
CPU: AuthenticAMD AMD Athlon(tm) II X4 640 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4294221824 total
VM: 2147352576, free: 1913434112



Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 09.08.2015 07:03:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080915-43383-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x33, 0x2, 0x1, 0xFFFFF800034E6A15)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 09.08.2015 07:03:44 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0xFDF4)
Bugcheck code: 0xA (0x33, 0x2, 0x1, 0xFFFFF800034E6A15)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Kernelmodustreiber-Frameworklaufzeit
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sun 02.08.2015 10:06:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080215-26847-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800034B8B05, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 01.08.2015 15:21:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080115-31839-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000004.sys (Unloaded_Unknown_Module_00000000`00000004+0xC)
Bugcheck code: 0x3B (0xC0000047, 0xFFFFF800034BF7FC, 0xFFFFF880077535A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`00000004.sys .
Google query: unknown_module_00000000`00000004.sys SYSTEM_SERVICE_EXCEPTION



On Fri 24.07.2015 18:42:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072415-28454-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D27D)
Bugcheck code: 0xFE (0x6, 0xFFFFFA80056C9FF0, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
file path: C:\Windows\system32\drivers\usbport.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: USB 1.1 & 2.0-Porttreiber
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 16.06.2015 05:39:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061615-29452-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x20, 0xFFFFF900C21FF000, 0xFFFFF900C21FF1D0, 0x251D0000)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 02.06.2015 05:30:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060215-30404-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF880009AE520, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 29.05.2015 18:34:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052915-27440-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x1)
Bugcheck code: 0xFE (0x6, 0xFFFFFA80059CC020, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: unknown_module_00000000`00000000.sys .
Google query: unknown_module_00000000`00000000.sys BUGCODE_USB_DRIVER




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

8 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

unknown_module_00000000`00000000.sys
unknown_module_00000000`00000004.sys

Alt 09.08.2015, 14:37   #2
Alois S
 
Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL - Standard

Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL Anleitung / Hilfe



Hallo markus_bs und ,

zunächst würde ich dir raten, den RAM und die Festplatten auf Fehler zu überprüfen (dazu gibt es hier im Anleitungsbereich ausgezeichnete Vorschläge).

Was die Treiber betrifft, so sind vor allem die des Chipsatzes wichtig (aber "unwichtig" sind leider gar keine.....)

Liebe Grüße, Alois

Post © Alois 2015 – Alle Rechte vorbehalten – kein Teil darf in irgendeiner Form ohne schriftliche Genehmigung des Autors kritisiert werden!
__________________

__________________

Alt 09.08.2015, 15:36   #3
markus_bs
 
Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL - Standard

Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL Details



Hallo Alois,

vielen Dank für die schnelle Antwort. Den RAM habe ich bereits vor ein paar Tagen ergebnislos auf Fehler überprüft, die Festplatte werde ich mir deinem Rat folgend als nächstes anschauen. Ich würde das jetzt über die Windows eigene Fehlerprüfung über C: - Eigenschaften - Tools - Fehlerprüfung angehen und das Ergebnis dann hier posten.

Viele Grüsse,
Markus
__________________

Alt 09.08.2015, 15:44   #4
Malwarepro
/// Android Expert
 

Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL - Standard

Lösung: Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL



Hi,

ja die eigene kannst du machen, oder diese:

Chkdsk ausführen lassen (kommandozeile)

Antwort

Themen zu Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL
abstürze, betriebssystem, bluescreen, code, driver, file, free, grafikkarte, hallo zusammen, irql, irql_not_less_or_equal, links, not, ntoskrnl.exe, opera, problem, software, system, system32, treiber, updaten, updates, version, windows, windows 7



Ähnliche Themen: Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL


  1. Bluescreen: IRQL_NOT_LESS_OR_EQUAL
    Alles rund um Windows - 11.07.2015 (9)
  2. Windows Bluescreen x00000116 durch dxgkrnl.sys
    Alles rund um Windows - 28.04.2015 (8)
  3. Bluescreen Win 7 - IRQL_NOT_LESS_OR_EQUAL BCCode 0x0000000a
    Alles rund um Windows - 23.01.2015 (7)
  4. Bluescreen mit Fehlermeldung , verwirrt durch andere Googleergebnisse
    Plagegeister aller Art und deren Bekämpfung - 02.01.2014 (5)
  5. Bluescreen durch Virus/Trojaner verursacht?
    Plagegeister aller Art und deren Bekämpfung - 15.02.2013 (3)
  6. Bluescreen: STOP: 0x0A IRQL_NOT_LESS_OR_EQUAL
    Alles rund um Windows - 23.09.2012 (2)
  7. bluescreen-fehlermeldung durch trojaner verursacht?
    Plagegeister aller Art und deren Bekämpfung - 02.02.2012 (3)
  8. Bluescreen durch Flashplayer; Malwarefund durch MBAM
    Plagegeister aller Art und deren Bekämpfung - 19.01.2012 (11)
  9. Bluescreen BCCode: 3b durch Grafikkartentreiber
    Netzwerk und Hardware - 13.12.2011 (5)
  10. Irql_not_less_or_equal
    Mülltonne - 28.10.2011 (1)
  11. Bluescreen/Einfrieren+Fehlermeldung: IRQL_not_less_or_equal
    Alles rund um Windows - 07.08.2011 (17)
  12. Windows 7 Bluescreen: Bad_Pool_Caller, Bad_Pool_Header, Memory_Management, IRQL_NOT_LESS_OR_EQUAL..
    Alles rund um Windows - 01.09.2010 (0)
  13. Windows XP startet nicht - IRQL_NOT_LESS_OR_EQUAL
    Alles rund um Windows - 13.03.2010 (14)
  14. Bluescreen beim Öffnen von Dateien durch Fehler 0x0000008E
    Log-Analyse und Auswertung - 05.02.2010 (8)
  15. BlueScreen durch AntiVir
    Antiviren-, Firewall- und andere Schutzprogramme - 25.03.2009 (24)
  16. Bluescreen durch smit fraud, einen tag später wieder bluescreen
    Log-Analyse und Auswertung - 04.02.2008 (3)
  17. IRQL_Not_Less_or_equal
    Log-Analyse und Auswertung - 02.12.2005 (1)

Zum Thema Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL - Hallo zusammen, mich plagen seit geraumer Zeit regelmässige Komplettabstürze meines PCs. Den Grafikkartentreiber habe ich gestern geupdated, das Problem besteht aber weiter. Aus der Recherche in anderen Beiträgen vermute ich, - Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL...
Archiv
Du betrachtest: Windows Bluescreen durch IRQL_NOT_LESS_OR_EQUAL auf Trojaner-Board

Search Engine Optimization by vBSEO ©2011, Crawlability, Inc.