Hi Leute, hab seit neustem ein unangenehmes Problem. :O
Ab und zu wenn ich YouTube Videos schaue, startet mein PC neu. Mir nichts, dir nichts. Kein BSOD daher auch kein Minidump, was die Problemsuche natürlich erschwert.
Das einizige was ich im Event Viewer finden konnte hab ich unten reinkopiert. Wie gesagt, bis jetzt 3 mal passiert, immer wenn ich YouTube gucke.
Mein System ist Win7 64 bit, i7-4770k @4.6Ghz/1.300V, R9 290X, Crucial Ballistix Tactical LP 16GB, Samung SSD 128gb, Gigabyte Z87X-UD3H, NT ist ein Seasonic G550, also ein gutes eigentlich.
CPU war seit November wo ich den Takt zuletzt gesetzt habe 100% stabil beim Zocken (BF3 + BF4) und rendern.
Das einzige was sich bei mir neulich geändert hat, war der neue AMD Treiber 14.1. Ich hab ihn aber wieder deinstalliert. Also Absturz passierte jetzt mit neuem und altem Treiber.
Verstehe nicht woran es liegen könnte. Hat einer Rat? Ich meine was kann den PC so krass böse wegreißen? :O
<sp>
Source: Service Control Manager
Date: 06.02.2014 19:56:18
Event ID: 7026
Description:
The following boot-start or system-start driver(s) failed to load:
cdrom
Log Name: System
Source: Microsoft-Windows-SharedAccess_NAT
Date: 06.02.2014 19:56:18
Event ID: 34005
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Gero-PC
Description:
The ICS_IPV6 was unable to allocate bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.
Event Xml:
Log Name: Application
Source: ISCT Agent
Date: 06.02.2014 19:56:17
Event ID: 1003
Task Category: (1)
Level: Error
Keywords: Classic
User: N/A
Computer: Gero-PC
Description:
The description for Event ID 1003 from source ISCT Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Log Name: Application
Source: ISCT Agent
Date: 06.02.2014 19:56:17
Event ID: 1003
Task Category: (1)
Level: Error
Keywords: Classic
User: N/A
Computer: Gero-PC
Description:
The description for Event ID 1003 from source ISCT Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
CISCTPnpDriverApi::CreateInstance *****Unable to open the ISCT device driver
the message resource is present but the message is not found in the string/message table
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 06.02.2014 19:56:12
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Gero-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Ab und zu wenn ich YouTube Videos schaue, startet mein PC neu. Mir nichts, dir nichts. Kein BSOD daher auch kein Minidump, was die Problemsuche natürlich erschwert.
Das einizige was ich im Event Viewer finden konnte hab ich unten reinkopiert. Wie gesagt, bis jetzt 3 mal passiert, immer wenn ich YouTube gucke.
Mein System ist Win7 64 bit, i7-4770k @4.6Ghz/1.300V, R9 290X, Crucial Ballistix Tactical LP 16GB, Samung SSD 128gb, Gigabyte Z87X-UD3H, NT ist ein Seasonic G550, also ein gutes eigentlich.
CPU war seit November wo ich den Takt zuletzt gesetzt habe 100% stabil beim Zocken (BF3 + BF4) und rendern.
Das einzige was sich bei mir neulich geändert hat, war der neue AMD Treiber 14.1. Ich hab ihn aber wieder deinstalliert. Also Absturz passierte jetzt mit neuem und altem Treiber.
Verstehe nicht woran es liegen könnte. Hat einer Rat? Ich meine was kann den PC so krass böse wegreißen? :O
<sp>
Source: Service Control Manager
Date: 06.02.2014 19:56:18
Event ID: 7026
Description:
The following boot-start or system-start driver(s) failed to load:
cdrom
Log Name: System
Source: Microsoft-Windows-SharedAccess_NAT
Date: 06.02.2014 19:56:18
Event ID: 34005
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Gero-PC
Description:
The ICS_IPV6 was unable to allocate bytes of memory. This may indicate that the system is low on virtual memory, or that the memory manager has encountered an internal error.
Event Xml:
Log Name: Application
Source: ISCT Agent
Date: 06.02.2014 19:56:17
Event ID: 1003
Task Category: (1)
Level: Error
Keywords: Classic
User: N/A
Computer: Gero-PC
Description:
The description for Event ID 1003 from source ISCT Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Log Name: Application
Source: ISCT Agent
Date: 06.02.2014 19:56:17
Event ID: 1003
Task Category: (1)
Level: Error
Keywords: Classic
User: N/A
Computer: Gero-PC
Description:
The description for Event ID 1003 from source ISCT Agent cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
CISCTPnpDriverApi::CreateInstance *****Unable to open the ISCT device driver
the message resource is present but the message is not found in the string/message table
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 06.02.2014 19:56:12
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: Gero-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Zuletzt bearbeitet:
