bluescreen win 7 sp1

  • hallo ich habe seit mehreren wochen das problem das mein pc nicht mehr richtig funktioniert.
    zuerst war es nur bei videos und im chrome.
    diablo 3 läuft stundenlang ohne probleme.
    das system wurde vor ca 2 wochen neu aufgespielt und alle aktuellen treiber installiert.
    neuerdings schreibt er keine minidumb dateien mehr.
    wir wollen morgen ein neues netzteil einbauen
    ich bedanke mich schonmal im voraus
    ich habe who crashed installiert und hier das ergebnis :

    On Mon 02.09.2013 19:04:58 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: Unknown (0xFFFFF88001A4449C)
    Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001A4449C)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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.
    Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL


    On Sun 01.09.2013 11:44:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\090113-13899-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C4449C)
    Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001C4449C)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 01.09.2013 11:44:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\090113-13899-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C4449C)
    Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001C4449C)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 Thu 29.08.2013 20:38:53 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082913-13447-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 Thu 29.08.2013 20:38:53 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082913-13447-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 Thu 29.08.2013 13:41:02 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082913-13930-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 Thu 29.08.2013 13:41:02 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082913-13930-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 Wed 28.08.2013 11:50:30 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13400-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 Wed 28.08.2013 11:50:30 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-13400-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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 Wed 28.08.2013 11:10:58 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13743-02.dmp
    This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
    Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF8800461BA03)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\e1q62x64.sys
    product: Intel(R) Gigabit Adapter
    company: Intel Corporation
    description: Intel(R) Gigabit Adapter NDIS 6.x driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


    On Wed 28.08.2013 11:10:58 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-13743-02.dmp
    This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
    Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF8800461BA03)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\e1q62x64.sys
    product: Intel(R) Gigabit Adapter
    company: Intel Corporation
    description: Intel(R) Gigabit Adapter NDIS 6.x driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


    On Wed 28.08.2013 02:11:42 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13993-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
    Bugcheck code: 0x19 (0x22, 0xFFFFFA8000000000, 0x0, 0x0)
    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 Wed 28.08.2013 02:11:42 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-13993-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
    Bugcheck code: 0x19 (0x22, 0xFFFFFA8000000000, 0x0, 0x0)
    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 Wed 28.08.2013 02:05:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-12994-01.dmp
    This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
    Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88003EAFA03)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\e1q62x64.sys
    product: Intel(R) Gigabit Adapter
    company: Intel Corporation
    description: Intel(R) Gigabit Adapter NDIS 6.x driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


    On Wed 28.08.2013 02:05:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-12994-01.dmp
    This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
    Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88003EAFA03)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\e1q62x64.sys
    product: Intel(R) Gigabit Adapter
    company: Intel Corporation
    description: Intel(R) Gigabit Adapter NDIS 6.x driver
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

    • Anzeige

    Hallo!

    Wenn du gerade an deiner Website arbeitest oder dein aktuelles Hosting überdenkst: Wir betreiben mit NetzLiving eine Hosting-Plattform, die speziell auf Performance, Sicherheit und einfache Verwaltung ausgelegt ist.

    • ✔️ Schnelle Ladezeiten (optimiert für WordPress, WoltLab & Co.)
    • ✔️ Deutsche Server & DSGVO-konform
    • ✔️ Persönlicher Support (kein 0815-Ticket-System)

    Mehr erfahren

  • Das einmal tun:

    • Von hier den PPFScanner herunterladen und die ZIP in einen eigenen Ordner entpacken (zum Beispiel nach C:\PPFS).
    • Danach die PPFScan.exe starten.
    • Klicke im PPFScanner oben links auf den Menüpunkt Programm, es öffnet sich dann ein Untermenü.
    • Wähle im Untermenü Script laden und ausführen.
    • Du hast dann im daraufhin erscheinenden Dialog die Möglichkeit, durch die Ordner zu browsen und eine Datei auszuwählen. Wähle hier die Datei Erweiterter Scan.scp aus, die sich im PPFScanner Ordner befindet, klicke dann auf Öffnen und bestätige die erscheinende Messagebox mit Ja.
    • Nach dem Scan beendet sich der Scanner. Es befinden sich dann im Ordner C:\PPF_Scan1 einige Text-Dateien. Lade bitte alle Dateien, die du dort findest, bei File-Upload.net - Ihr kostenloser File Hoster! hoch und poste die Downloadlinks hier.
  • Desweiteren hattest du scheinbar einen Festplattencrash auf dem SSD Laufwerk:

    Code
    2.9.2013 18:35 Uhr 54s 
    Record #7891
    Computername->Uttokko-PC
    Ntfs:
    Error
    Die Dateisystemstruktur auf dem Datenträger ist beschädigt und unbrauchbar.
    Führen Sie auf dem Volume "SSD" den Befehl "chkdsk" aus.


    Das jetzt sofort tun, nicht mehr warten!

    • Computer
    • Rechtsklick auf Laufwerk das SSD-Laufwerk.
    • Eigenschaften
    • Registrierkarte Tools
    • Jetzt prüfen
    • Dateisystemfehler... und Fehlerhafte Sektoren... mit Häkchen versehen
    • Starten
    • Auf Nachfrage Prüfung planen lassen
    • rebooten
    • Festplattentest durchführen lassen!
  • ja ich habe es zwimal so gemacht und c: ist die ssd .dann den computer nach der datei suchen lassen und dann noch nach boot und .txt gesucht und in den ergebnissen nichts gefunden

  • OK, das reicht.
    Das tun:

    Einmal die Freeware von HDTune herunterladen und installieren: http://www.hdtune.com/files/hdtune_255.exe

    • Registrierkarte Health anklicken.
    • Ganz oben steht ein Thermometer mit der Gradzahl. Klicke mit der Maus auf den ersten kleinen Button rechts daneben. Zeigst du mit der Maus darauf, erscheint der Text "Copy information to clipboard".
    • Füge den Text hier ein (SMART Daten). So in der Art müsste dein LOG aussehen:
  • HD Tune: OCZ-OCTANE S2 Health

    ID Current Worst ThresholdData Status
    (01) Raw Read Error Rate 7 0 0 7 Ok
    (03) Spin Up Time 100 100 0 0 Ok
    (04) Start/Stop Count 100 100 0 0 Ok
    (05) Reallocated Sector Count 100 100 0 0 Ok
    (09) Power On Hours Count 100 100 0 599 Ok
    (0C) Power Cycle Count 100 100 0 1150 Ok
    (E8) (unknown attribute) 100 100 0 80 Ok
    (E9) (unknown attribute) 100 0 0 100 Ok

    Power On Time : 599
    Health Status : Ok

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!