Bluescreen

schmiddi2106

Software-Overclocker(in)
Hallo !

Heute ist beim Battlefield 3 spielen mein Rechner mit dem Bluescreen im Anhang abgeschmiert.
Muss ich mir iwelche Gedanken machen ?

Grüße
 

Anhänge

  • bluescreen 1.jpg
    bluescreen 1.jpg
    58,7 KB · Aufrufe: 129
  • bluescreen 2.jpg
    bluescreen 2.jpg
    62,2 KB · Aufrufe: 127
Lad dir mal das Programm "whocrashed" runter und lass es drüberlaufen. Das kann dir vllt genaueres Auskunft geben, was hier der Auslöser war
 
"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."

Scheint nichts schlimmes zu sein... Danke !
 
Gerade wieder BF3 gespielt und wieder Bluescreen.
Hier die Analyse von 'whocrashed'

"[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Mon 12.08.2013 10:11:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081213-11419-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT] (nt+0x75C00)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003965180, 0x2)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Mon 12.08.2013 10:11:57 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]hal.dll[/FONT] (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88003965180, 0x2)
Error: [FONT=Segoe UI, Arial]CLOCK_WATCHDOG_TIMEOUT[/FONT]
file path: C:\Windows\system32\hal.dll
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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.
"

[/FONT]
 
Leute ich brauche wirklich dringend eure Hilfe, der nächste Bluescreen, dieses mal in Arma 3.............

"[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]

[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Tue 13.08.2013 18:44:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081313-11700-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k+0xC639B)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF9600011639B, 0x0, 0x43800000700)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Betriebssystem Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Mehrbenutzer-Win32-Treiber
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 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.


[/FONT]
[FONT=Segoe UI, Arial]On Tue 13.08.2013 18:44:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]win32k.sys[/FONT] (win32k!memset+0x6BB)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF9600011639B, 0x0, 0x43800000700)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\win32k.sys
product: [FONT=Segoe UI, Arial]Betriebssystem Microsoft® Windows®[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Mehrbenutzer-Win32-Treiber
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 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.
"

[/FONT]
 
Ne, meinste daran kanns liegen ? kann ich mir eigentlich nicht vorstellen. Wie teste ich den ? Hab das vor paar Jahren mal mit ner CD gemacht..
 
Okay, werd ich dann mal machen....

Was mir noch eingefallen ist: Der Bluescreen kommt nur in Games, und auch nur in Arma 3 und Battlefield 3. Beides CPU lastige Spiele. Kann es sein das ich meine Übertaktung ein wenig reduzieren muss ? Mein 3570k läuft auf 4,1 Ghz auf Standartspannung (1,175V) ??
 
Bekomme das mit dem Memtest nicht hin. Wenn ich auf Booten von USB stick klicke, dann sucht er ne sekunde und bootet wieder windows von meiner ssd...
 
Da kannst das für den Anfang auch einfach in Windows laufen lassen....

Ansonsten muss du den Stick bootfähig machen.
 
Zurück