Blue Screens Notebook mit Win 7

  • Ersteller Ersteller Ichbraucheeinpc
  • Erstellt am Erstellt am
I

Ichbraucheeinpc

Gast
Hallo Computerbase Forum,

ich habe ein Problem mit meinem Notebook, weil ich des öfteren Blue Screens habe, ich habe daraufhon mal WhoCrashed runtergeladen und folgende Infos bekommen...
Wäre froh wenn mir einer beantworten könnte was der Auslöser ist.

Die Hardware:
500 GB Seagate HDD
4GB RAM
HD5470
i5 460m
OS: Win 7 64 BIT

Hardware läuft seit 3,5 Jahren fast jeden Tag.

Wenn was nicht klar ist einfach nochmal fragen....



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 29.01.2014 18:06:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012914-19609-01.dmp
This was probably caused by the following module: cdd.dll (cdd+0x10A85)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000630A85, 0xFFFFF880029C1AF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 29.01.2014 18:06:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cdd.dll (cdd+0x10A85)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF96000630A85, 0xFFFFF880029C1AF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sat 25.01.2014 19:41:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012514-22994-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22CA45)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600022CA45, 0xFFFFF8800A032150, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Fri 17.01.2014 12:32:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-21528-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22CA45)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600022CA45, 0xFFFFF88006C3F150, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Mehrbenutzer-Win32-Treiber
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 23.12.2013 18:58:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122313-41761-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70600)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8006213B30, 0xFFFFFA8006213E10, 0xFFFFF80002DDC540)
Error: CRITICAL_OBJECT_TERMINATION
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 process or thread crucial to system operation has unexpectedly exited or been terminated.
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.



On Fri 18.10.2013 18:32:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101813-52993-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xAE84)
Bugcheck code: 0x116 (0xFFFFFA80062A44E0, 0xFFFFF88006221E84, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
 
check mal deine Festplatte und den Ram, danach mach mal Prime an, oder auch umgekehrt, ist dir überlassen.. :)
 
Hab ihn schon mit Benchmarks gequält, dabei war das System stabil...
 
Zurück
Oben