| Schorle2 | 31.03.2017 00:06 |
Bluescreen
Hallo,
Ich habe am Sonntag mein Laptop neu aufgesetzt und seit dem lief eigentlich alles gut.
Doch heute habe ich bereits 2 mal einen Bluescreen gehabt.
Das einzige Programm das ich heute Installiert habe ist Bluetooth, kann es vielleicht daran liegen ?
Ich habe in einem anderem Thread von dem Programm "Whocrashed" gelesen und dieses direkt auch mal runtergeladen. Hier ist die Auswertung : Zitat:
On Fri 3/31/2017 12:37:57 AM your computer crashed
crash dump file: C:\Windows\Minidump\033117-31808-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F440)
Bugcheck code: 0x1A (0x5001, 0xFFFFF70001080000, 0x3172, 0xEFDF0000000020C0)
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. This problem might also be caused because of overheating (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 3/31/2017 12:37:57 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x5001, 0xFFFFF70001080000, 0x3172, 0xEFDF0000000020C0)
Error: MEMORY_MANAGEMENT
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. This problem might also be caused because of overheating (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 Thu 3/30/2017 7:17:27 PM your computer crashed
crash dump file: C:\Windows\Minidump\033017-46550-01.dmp
This was probably caused by the following module: btath_flt.sys (Unloaded_btath_flt.sy+0x12C0)
Bugcheck code: 0xCE (0xFFFFF8800C13A2C0, 0x8, 0xFFFFF8800C13A2C0, 0x0)
Error: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
file path: C:\Windows\system32\drivers\btath_flt.sys
product: Blue Manager
company: Atheros
description: Atheros FILTER driver
Bug check description: This indicates that a driver failed to cancel pending operations before unloading.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: btath_flt.sys (Atheros FILTER driver, Atheros).
Google query: Atheros DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 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:
btath_flt.sys (Atheros FILTER driver, Atheros)
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.
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.
| | 