AW: Suche Gehäuselüfter 8 cm
Und hier was WhoCrashed über die BlueScreens anzeigt
gibt es dafür eine Lösung?Es kam wieder zu nem freeze obwohl der GL nich drin war.
Quelle: iaStor
Ereigniskennung: 9
Beschreibung : Das Gerät \Device\Ide\iaStor0 hat innerhalb der Fehlerwartezeit nicht geantwortet.
hab übrigens Keine SSD drin.
Und hier was WhoCrashed über die BlueScreens anzeigt
<font face="Segoe UI, Arial" size="4"><b><hr>Welcome to WhoCrashed (HOME EDITION) v 5.50</b><hr></b></font><br>
<font face="Segoe UI, Arial" size="2" color="000000">This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution. <br><br>Whenever a computer suddenly reboots without displaying any notice or blue (or black) 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. <br><br>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. <br></font><br>
<font face="Segoe UI, Arial" size="2" color="000000">To obtain technical support visit <a href="http://www.resplendence.com/support" target="_blank">www.resplendence.com/support</a><br><br></font>
<font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.resplendence.com/docs/rspupdate.dll/checkforupdate?product=WhoCrashed&ver=55030715&os=ntoskrnl.exe&osver=56eb24e65e7000&pdbname=ntkrnlmp.pdb&pdb7=97219F85530548958964A37DC485AF7E2&edition=home" target="_blank">Click here to check if you have the latest version or if an update is available. </a><br><br></font>
<font face="Segoe UI, Arial" size="2" color="000000">Just click the Analyze button for a comprehensible report ...<br><br><br></font>
<font face="Segoe UI, Arial" size="4"><b><hr>Home Edition Notice</b><hr></b></font><br>
<font face="Segoe UI, Arial" size="2" color="000000">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. <br><br><a href="http://www.resplendence.com/whocrashed_pro" target="_blank">Click here for more information on the professional edition.</a><br><a href="http://www.resplendence.com/buynow" target="_blank">Click here to buy the the professional edition of WhoCrashed.</a><br></font><br>
<font face="Segoe UI, Arial" size="4"><b><hr>System Information (local)</b><hr></b></font><br>
<font face="Segoe UI, Arial" size="2" color="000000">computer name: PC<br>windows version: Windows 7 Service Pack 1, 6.1, build: 7601<br>windows dir: C:\Windows<br>Hardware: Aspire M5810, Acer, FMP55<br>CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz Intel586, level: 6<br>4 logical processors, active mask: 15<br>RAM: 6433095680 total<br><br><br></font><br>
<font face="Segoe UI, Arial" size="4"><b><hr>Crash Dump Analysis</b><hr></b></font><br>
<font face="Segoe UI, Arial" size="2" color="000000">Crash dump directory: C:\Windows\Minidump</font><br>
<font face="Segoe UI, Arial" size="2" color="000000"></font><br>
<font face="Segoe UI, Arial" size="2" color="000000">Crash dumps are enabled on your computer.<br></font><br>
<font face="Segoe UI, Arial" size="2" color="000000"><b>On Mon 25.04.2016 18:01:50 GMT your computer crashed</b><br>crash dump file: C:\Windows\Minidump\042516-24710-01.dmp<br>This was probably caused by the following module: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=ntoskrnl.exe" target="_blank">ntoskrnl.exe</a></font> (nt+0x70380) <br>Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009F0180, 0x1)<br>Error: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=MSDN+bugcheck+CLOCK_WATCHDOG_TIMEOUT" target="_blank">CLOCK_WATCHDOG_TIMEOUT</a></font><br>file path: C:\Windows\system32\ntoskrnl.exe<br>product: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=Microsoft® Windows® Operating System" target="_blank">Microsoft® Windows® Operating System</a></font><br>company: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=Microsoft Corporation" target="_blank">Microsoft Corporation</a></font><br>description: NT Kernel & System<br>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. <br>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</a>. <br>The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. <br><br><br></font><br>
<font face="Segoe UI, Arial" size="2" color="000000"><b>On Mon 25.04.2016 18:01:50 GMT your computer crashed</b><br>crash dump file: C:\Windows\memory.dmp<br>This was probably caused by the following module: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=aswsp.sys" target="_blank">aswsp.sys</a></font> (aswSP+0x136C2) <br>Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009F0180, 0x1)<br>Error: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=MSDN+bugcheck+CLOCK_WATCHDOG_TIMEOUT" target="_blank">CLOCK_WATCHDOG_TIMEOUT</a></font><br>file path: C:\Windows\system32\drivers\aswsp.sys<br>product: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=Avast Antivirus " target="_blank">Avast Antivirus </a></font><br>company: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=AVAST Software" target="_blank">AVAST Software</a></font><br>description: avast! self protection module<br>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. <br>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</a>. <br>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: aswsp.sys (avast! self protection module, AVAST Software). <br>Google query: <font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=aswsp.sys+AVAST Software+CLOCK_WATCHDOG_TIMEOUT" target="_blank">AVAST Software CLOCK_WATCHDOG_TIMEOUT</a></font><br><br><br></font><br>
<font face="Segoe UI, Arial" size="2" color="000000"></font><br>
<font face="Segoe UI, Arial" size="4"><b><hr>Conclusion</b><hr></b></font><br>
<font face="Segoe UI, Arial" size="2" color="000000">2 crash dumps have been found and analyzed. A third party driver has 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: <br><br><font face="Segoe UI, Arial" size="2" color="000000"><a href="http://www.google.com/search?q=aswsp.sys+AVAST Software+Avast Antivirus " target="_blank">aswsp.sys (avast! self protection module, AVAST Software)</a></font><br><br>If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.<br><br><br>Read the topic <a href="http://www.resplendence.com/whocrashed_troubleshooting" target="_blank">general suggestions for troubleshooting system crashes</a> for more information. <br><br>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. <br><br><br><br></font><br>
