Um ein 64Bit Betriebssystem und ich entschuldige, dass ich gestern so plötzlich offline war, hatte noch viel zu erledigen ![]()
Beiträge von Moshroom
-
-
Erfolgreich im abgesichterten Modus gestartet.
-
So, ich habe heute dienoriginal CD von Windows gefunden, jetzt einfach reinschmeißen und die Reperaturinstallation durführen?
-
Wir reden aneinander vorbei
Ich wollte eigentlich nur wissen ob ich die Reperaturinstallation vom Handy aus ausführen kann anstatt von der DVD. Da sich aus der Antwort trotzdem schließen lässt das dies nicht geht muss ich wohl oder übel eine CD/DVD mit genug Speicherplatz kaufen gehen
-
Dafür wird doch auch eine Windows CD benötigt....oder kann ich dafür das downloadete System vom Handy aus nutzen?
-
Das wär auf dem Handy kein Problem.
Jetzt bräucht ich nur ne gute Anleitung dafür
-
Wie viel Speicherplatz wird benötigt?
Und könnte ich die Dateien auch auf meinem Handy zwischenspeichern, habe keinen höchstwahrscheinlich keinen Datenträger zur Hand der groß genug ist -
Ah,Entschuldigung falsch verstanden
nein leider nicht
-
Soweit ich weiß nicht....
-
N'abend Community,
Seid einigen Tagen geht beim Hochfahren unter dem Punkt "Loading Operating System" mein Pc kurz aus und fährt dann automatisch neu hoch, allerdings ist er dann extrem langsam
Unter Google hab ich schon gesucht doch leider nichts gefunden was auf mein Problem passt, deswegen hab ich mich dazu entschieden einfach hier mal nachzufragen.
Ich würde mich über baldige Hilfe freuen,MfG. Moshroom

-
Nutze zur Zeit Avast, dann werde ich dabei bleiben.
Na gut dann ist ja erstmal alles in Ordnung, danke und bis zum nächsten Mal
-
Vergessen beizufügen, der Bluescreen war nach der Deinstallation des "ON_OFF Chargers" behoben.^^
Ich danke für die kompetente Hilfe und hätte noch zwei kleine Fragen..1.Wie check ich weiterhin am besten ob alle Treiber aktuell sind und ob keine inaktiven Treiber vorhanden sind?
2.Welches kostenlose Viren-Programm ist momentan zu empfehlen? -
-
"ON_OFF Charger" gefunden und erfolgreich deinstalliert.^^
Scanergebnis:
-
Ok, ich merk schon ist ein schwerwiegenderes Problem, Treiber einfach Deinstallieren ist wohl nicht

Scan Ergebnis:
http://www.file-upload.net/gal-92415/1ga95e/1.html -
4:0 Sieg! Was ein Spiel

Hört sich ja alles nicht so prächtig an. Hab den PC damals ohne groß nachzudenken zugemüllt, das sind wohl die Folgen

-
Entschuldigung für die kleine Verzögerung.
Hier sind alle Dateien aus dem PPF_Scan1 Ordner: -
Konnte nicht alles auf einmal posten (max 10000) Zeichen.
Hier der Rest:--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------15 crash dumps have been found and analyzed. Only 10 are included in this report. 3 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 337.88 , NVIDIA Corporation)
applecharger.sys
unknown_module_fffff880`012042ec.sysIf 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.
-
Erstmal ein dickes danke für die schnelle Antwort und den lieben Willkommensgruß.

Die Analyse ergab:
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------computer name: Home-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: P55A-UD4, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4285972480 total
VM: 2147352576, free: 1892450304--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 15.06.2014 21:24:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061614-18985-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003D686CA, 0x0, 0x4E)
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 Sun 15.06.2014 21:24:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: applecharger.sys (AppleCharger+0x270C)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003D686CA, 0x0, 0x4E)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\applecharger.sys
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.
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: applecharger.sys .
Google query: applecharger.sys KMODE_EXCEPTION_NOT_HANDLEDOn Sat 14.06.2014 19:07:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061514-19531-01.dmp
This was probably caused by the following module: unknown_module_fffff880`012042ec.sys (Unloaded_Unknown_Module_fffff880`012042ec+0x3D01975)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003D5F6CA, 0x0, 0x4E)
Error: KMODE_EXCEPTION_NOT_HANDLED
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.
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_fffff880`012042ec.sys .
Google query: unknown_module_fffff880`012042ec.sys KMODE_EXCEPTION_NOT_HANDLEDOn Sat 14.06.2014 10:23:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061414-26067-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003DB26CA, 0x0, 0x4E)
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 14.06.2014 01:47:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061414-30357-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003DA96CA, 0x0, 0x4E)
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 14.06.2014 01:40:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061414-30295-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003DA56CA, 0x0, 0x4E)
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 Thu 12.06.2014 17:44:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061214-31200-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003DAB6CA, 0x0, 0x4E)
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 Thu 12.06.2014 17:40:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061214-34242-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003D696CA, 0x0, 0x4E)
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 Mon 09.06.2014 18:01:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060914-21855-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003D756CA, 0x0, 0x4E)
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 Mon 09.06.2014 00:51:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060914-23275-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003DBB6CA, 0x0, 0x4E)
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. -
N'abend Community,
wie schon in der Überschrift steht, erscheint seid einigen tagen ein Bluescreen beim Herunterfahren meines Computers.
Nach einigen Sekunden geht der PC aus und startet Windows mit der Fehlermeldung "Windows wurde nach unerwartetem Herunterfahren wieder ausgeführt"In den Problemdetails steht:
Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.1.7601.2.1.0.768.3
Gebietsschema-ID: 1031Zusatzinformationen zum Problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF80003D5F6CA
BCP3: 0000000000000000
BCP4: 000000000000004E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\061514-19531-01.dmp
C:\Users\Gavin\AppData\Local\Temp\WER-43165-0.sysdata.xmlLesen Sie unsere Datenschutzbestimmungen online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline:
C:\Windows\system32\de-DE\erofflps.txtDa meine Kenntnisse über Computer da aufhören wo man Probleme nicht mehr simpel mit Google lösen kann, komm ich bei diesem Problem an meine Grenzen und würde mich über baldige Hilfe freuen

Ich bedanke mich im Voraus