Hallo zusammen,

seit cirka 2 Wochen stürzt jedesmal beim Aufstarten der Pc mehrmals hintereinander ab. Wenn er dann endlich läuft funktioniert er dann problemlos den ganzen Tag.

Welcome to WhoCrashed (HOME EDITION) v 5.02
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...


Home Edition Notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.

System Information (local)
computer name: MASTER-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Thurley, Intel, XFX, MB-X58I-CH19
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 3211976704 total



Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 30.11.2014 11:54:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113014-27562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000337068E, 0xFFFFF88001FCAB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 30.11.2014 11:54:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngSetLastError+0xD54D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000337068E, 0xFFFFF88001FCAB60, 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 Sun 30.11.2014 11:36:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113014-17187-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88003326238, 0xFFFFF88003325A90, 0xFFFFF800030E974E)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates a problem occurred in the NTFS file system.
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 21.11.2014 07:12:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112114-17437-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC53AE)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960001553AE, 0xFFFFF88001FFE0C0, 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 Thu 20.11.2014 07:55:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112014-17968-01.dmp
This was probably caused by the following module: ndis.sys (ndis+0x3758)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88001437758, 0xFFFFF880087CB350, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ndis.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NDIS 6.20-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 Sun 07.09.2014 17:05:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090714-58406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 04.08.2014 06:42:13 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080414-17890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1A (0x5100, 0xFFFFF6FC500219D8, 0x21CA, 0x1)
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.



On Thu 12.06.2014 11:55:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061214-18375-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8002432EE0, 0xF0FFFFFA8002432E, 0xFFFFFA8002432EE1)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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.



On Wed 04.06.2014 04:48:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060414-18421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Fri 27.12.2013 14:21:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122713-23984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x7F (0x8, 0x80050033, 0x6F8, 0xFFFFF80002EFD3CD)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Conclusion
14 crash dumps have been found and analyzed. Only 10 are included in this report. 2 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 340.52 , NVIDIA Corporation)
hcw73bda.sys (Hauppauge Computer Works Driver, Hauppauge Computer Work, 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.

Hallo roberto11,

ich schlage folgende Vorgangsweise vor:

1) RAM überprüfen

2) Treiber auf Aktualisierung prüfen (Chipsatz zuerst!)

3) Festplatte auf Fehler prüfen

Noch eine Frage: Du benutzt nicht zufällig ein Gerät mit "FireWire" - Schnittstelle?

Liebe Grüße, Alois

Post © Alois 2014 – Alle Rechte vorbehalten – kein Teil darf in irgendeiner Form ohne schriftliche Genehmigung des Autors kritisiert werden!

Hallo Alois ,

danke für die gut gemeinten Tips, leider bin ich kein Freak und brauche genaue Anweisungen
wie ich was machen muss.

Gruss roberto 11

Hi,

zuallererst solltest du mal einen RAM-Test machen:

Dazu gibst du bitte in das Suchfeld "mdsched.exe" ein und wählst "Neu starten und nach Problemen suchen aus" - danach sehen wir weiter (PS: Der Test dauert einige Zeit, kann übrigens mit "Escape" abgebrochen werden).

Liebe Grüße, Alois

Hallo Alois,

danke für deine Unterstützung. Habe den Test ausgeführt und das Resultat keine Fehler.
Beim Entstauben habe ich noch festgesellt,dass der PC Gehäuse Lüfter defekt ist. Habe in ersetzt.

Gruss roberto 11

Gut - als nächstes prüfen wir die Festplatte:

Diesmal gibst du bitte "CHKDSK c: /f /r" in das Feld ein, wobei "c" für deine Systemfestplatte steht und danach folgst du den Anweisungen.

Liebe Grüße, Alois

Bin zurück aus dem Wochenende. Habe CHKDSK ausgeführt. Dabei kam die Warnung " Der Parameter F wurde nicht angegeben. CHKDSK wird im Schreibgeschützten Modus aus-
geführt." Lief durch und das wars.

Gruss roberto11