Hallo zusammen,

seit einiger Zeit habe ich regelmäßig Bluescreens.
Sei es beim Schauen eines Twitch - Streams, beim Starten eines
Spiels (in dem Fall "Ark"), auch mal beim einfachen Hören von
Musik über iTunes.

Um mal den Fall auszumerzen, dass es falsche Soundtreiber sind, habe ich diese gestern mal neu installiert (über ASUS), aber Fehlanzeige, PC stürzt bei Server Connect zu "ARK" ab.

Habe Hardware technisch nichts verändert und mein Virenscanner von Emsisoft hat auch jüngst keine Funde gehabt.

Vielen Dank im Voraus.

Was erwartest Du hier für eine Antwort?
Du postest keinerlei relevante Fakten, die es jemanden ermöglichen würden, Dir irgendwie zu Helfen.
Genauso wenn ich zum Tierarzt gehe und sage: "Mein Hund bellt".

Zitat von felix1

Genauso wenn ich zum Tierarzt gehe und sage: "Mein Hund bellt".

Dein Tierarzt würde jetzt systematisch vorgehen und alles mögliche beim Hund untersuchen

Zitat von cosinus

Dein Tierarzt würde jetzt systematisch vorgehen und alles mögliche beim Hund untersuchen

Eigentlich hat der Tierarzt ja schon gesagt, was er wissen will

Die Fakten erhoffte ich hier zu finden, Fehlanzeige, stattdessen: Bullshit
Mein System ist im sysP ersichtlich.

Ich kann nur angeben, dass es immer die Meldung ist: driver not less or equal.

Edit: nachdem ich die Auslagerungsdatei vor 2 Tagen manuell auf das 1,5- fache des RAM's gesetzt habe, blieb
ich von Bluescreens verschont.

Zitat von Martin Gore

Die Fakten erhoffte ich hier zu finden, Fehlanzeige, stattdessen: Bullshit
Mein System ist im sysP ersichtlich.

Du postest Bullshit und in Rätseln. Was ist sysP?

Zitat von Martin Gore

Ich kann nur angeben, dass es immer die Meldung ist: driver not less or equal.

Das hast Du bisher nicht gepostet.

Zitat von Martin Gore

Edit: nachdem ich die Auslagerungsdatei vor 2 Tagen manuell auf das 1,5- fache des RAM's gesetzt habe, blieb
ich von Bluescreens verschont.

Bereite Dich bei Deiner nächsten Anfrage besser vor. Lese dazu die entsprechenden Hinweise, welche Angaben erforderlich sind. Wir haben etwas gegen solche Aussagen wie in #1

Zitat von felix1

Du postest Bullshit und in Rätseln. Was ist sysP?

Schau dir mal dieses sysP Schildchen unter seinem Benutzernamen an...

Zitat von cosinus

Schau dir mal dieses sysP Schildchen unter seinem Benutzernamen an...

So ist es !
WIe kann ein langjähriger Nutzer dieses Boards keinen Blassen
von sysP haben? Merkwürdiger Bullshit.

Der Bluescreen, der bei mir immer auftaucht, wirft tcpip.sys in den Raum.
Ich habe die Grafikkarte, die seit letztem Dezember verbaut ist, einem Belastungstest unterworfen- keine Fehler.
Speicher (DDR3 12800er von Kingston), ebenfalls von Dezember, auch ohne Fehler.

Langsam gehen mir die Ideen aus.

Bei diesem Ton hat vermutlich jeder sehr viel Lust dir zu helfen.

Wahrscheinlich genauso wie ich hier weiter zu schreiben, bei der warmen Begrüßung / "Antwort" auf meine Eröffnung.

Lade dir doch mal dieses Tool runter => WhoCrashed - Download - Filepony

Erstelle damit ein Log und poste es hier in CODE-Tags

Danke für deine Antwort, allerdings habe ich keine Log Funktion bei WhoCrashed gefunden.
Hier der Téxt:


"Welcome to WhoCrashed (HOME EDITION) v 5.01
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


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

computer name: CHRILU
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., CROSSHAIR V FORMULA-Z
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 17072640000 total
VM: 2147352576, free: 1896656896




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 10.07.2016 17:22:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88001646393)
Bugcheck code: 0xD1 (0x7, 0x2, 0x0, 0xFFFFF88001646393)
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 Sat 09.07.2016 14:17:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070916-31371-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646393)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646393)
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 07.07.2016 09:44:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070716-23852-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646393)
Bugcheck code: 0xD1 (0x7, 0x2, 0x0, 0xFFFFF88001646393)
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 06.07.2016 18:09:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070616-24928-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800164618C)
Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF8800164618C)
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 Mon 04.07.2016 11:15:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070416-31512-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001645393)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001645393)
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 Mon 04.07.2016 11:07:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070416-29312-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646393)
Bugcheck code: 0xD1 (0x7, 0x2, 0x0, 0xFFFFF88001646393)
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 03.07.2016 15:19:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070316-31871-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001645393)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001645393)
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 03.07.2016 15:11:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070316-32307-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF80002E8E400)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646393)
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 Fri 01.07.2016 20:48:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070116-32682-01.dmp
This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1B990)
Bugcheck code: 0xD1 (0x68, 0x2, 0x1, 0xFFFFF880063AB990)
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 Fri 01.07.2016 11:46:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070116-27440-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001646393)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001646393)
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.




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

50 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.39 , NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further."

windows version: Windows 7 Service Pack 1, 6.1, build: 7601

Warum bist du noch bei Windows 7?

50 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 368.39 , NVIDIA Corporation)

whocrahed hat zwei Treiber identifiziert, die für den Crash verantwortlich sein können...

Danke für deine Antwort!
Ja, das habe ich auch gesehen.

Na gut, da für WIN 7 ja noch immer Updates erscheinen, ist das Betriebssystem ja wirklich eine Geschmacksfrage. Kommt hinzu, dass ich mich vor dem Upgrade scheue.
Aber wahrscheinlich werde ich mich noch in diesem Monat damit beschäftigen.

Kannst du mir bei der Herangehensweise bzgl. dieser Treiber assistieren?

Hallo ?