Guten Tag erstmal. Habe mich extra hier angemeldet, weil ich im Internet nirgendwo mein Problem finde.

Schon seit einiger Zeit, wenn ich auf dem PC spiele, haut mir dieser nach vielleicht 1 oder 2 Stunden einen Bluescreen rein. Ich bin jetzt kein Hardcore-Gamer, spiele nur Spiele wie Final Fantasy: A Realm Reborn, Sims 3/4, AION, TERA - also kein CoD oder sonstiges.

Habe mir gerade auch BlueScreenView runtergeladen, aber da ich keinen Schimmer von PCs habe, weiß ich auch nicht, was das alles bedeutet. (Screens füge ich an.)

Die Fehlermeldung, die jedes Mal kommt, habe ich natürlich auch abgespeichert und poste sie sogleich:

Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7601.2.1.0.768.3
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 1a
BCP1: 0000000000000403
BCP2: FFFFF68000006028
BCP3: 92B0000001B93867
BCP4: FFFFF60000006028
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Ob das hier noch hilft, weiß ich nicht, packe es aber trotzdem mal rein:

Betriebssystem
Windows 7 Home Premium 64-bit SP1

CPU
Intel Core i5 4570 @ 3.20GHz 39 °C
Haswell 22nm Technologie

RAM
8,00GB Dual Kanal DDR3 @ 800MHz (11-11-11-28)

Motherboard
MSI H81M-P33 (MS-7817) (SOCKET 0) 46 °C

Grafik
PHL 223V5 (1920x1080@60Hz)
2047 MBNVIDIA GeForce GTX 650 Ti (Undefined) 36 °C

Speicher
931GB Western Digital WDC WD10EZEX-00BN5A0 ATA Device (SATA) 29 °C

Optische Laufwerke
HL-DT-ST DVDRAM GH24NSB0 ATA Device
Audio
Realtek High Definition Audio

Ich wollte mir gerade noch Memtest86 runterladen, aber ich weiß nicht, ob es mir beim Problem helfen wird. Hoffentlich könnt ihr mir helfen

Bitte lade dir die neuste Version von WhoCrashed auf deinen Computer: WhoCrashed Download

• Installiere es
• Starte es als Administrator
• Klicke oben links auf den Button "Analyze"
• Scrolle herunter, die Bereiche Crash Dump Analysis und Conclusion bitte ins Forum kopieren

Bitte poste dein Ergebnis zwischen Code-Tags

Wenn ein Log zu lange ist, teile ihn bitte auf mehrere Antworten.

Code-Tags?

Drücke einfach die # in Antwortfenster und füge den Log dazwischen ein

#
On Sat 06.09.2014 15:35:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-11497-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFAA0098202F0, 0x1, 0xFFFFF80003488CC4, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 06.09.2014 15:35:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mobk.sys (MOBK+0x4695)
Bugcheck code: 0x50 (0xFFFFFAA0098202F0, 0x1, 0xFFFFF80003488CC4, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\mobk.sys
product: Mozy
company: Mozy, Inc.
description: Mozy Change Monitor Filter Driver
Bug check description: This indicates that invalid system memory has been referenced.
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: mobk.sys (Mozy Change Monitor Filter Driver, Mozy, Inc.).
Google query: Mozy, Inc. PAGE_FAULT_IN_NONPAGED_AREA



On Sat 06.09.2014 08:25:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090614-11746-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFA8065F8B76B, 0x0, 0xFFFFF800034757AF, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 05.09.2014 19:15:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090514-11871-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x41201, 0xFFFFF68000003390, 0x1310000170CE6847, 0xFFFFFA8006811EB0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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.

#
4 crash dumps have been found and analyzed. A third party driver has 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:

mobk.sys (Mozy Change Monitor Filter Driver, Mozy, Inc.)

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 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.
#

Mozy Change Monitor Filter Driver

Das bitte neuinstallieren und aktualisieren

Weiters aktualisiere bitte deine Treiber für Grafikkarte und Chipsatz. Lade sie bitte von der NVIDA Website bzw. der Website von MSI herunter.