Hey bekomme komischerweise einen Bluescrenn WENN ich unter GOOGLE CHROME - Einstellung klicke....dann fährt er jedesmal runter und zeigt mir einen Bluescreen an! Siehe Bild!

Lade Dir das Programm von Filepony und poste das Ergebnis. Bad_Pool_Header kann erst mal alles sein.

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: DJRISOW-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASRock, Z68 Extreme4
CPU: GenuineIntel Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17088217088 total
VM: 2147352576, free: 1927622656



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 13.09.2016 09:32:08 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091316-59607-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F400) 
Bugcheck code: 0x19 (0x20, 0xFFFFFA800D80BB80, 0xFFFFFA800D80BC00, 0xC080001)
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 Tue 13.09.2016 09:32:08 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: etronhub3.sys (EtronHub3+0x598E) 
Bugcheck code: 0x19 (0x20, 0xFFFFFA800D80BB80, 0xFFFFFA800D80BC00, 0xC080001)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\etronhub3.sys
product: Etron HUB2/HUB3 Driver.
company: Etron Technology Inc
description: Etron eXtensible Hub Driver.
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. 
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: etronhub3.sys (Etron eXtensible Hub Driver., Etron Technology Inc). 
Google query: Etron Technology Inc BAD_POOL_HEADER



On Tue 13.09.2016 09:25:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091316-24492-01.dmp
This was probably caused by the following module: etronxhci.sys (EtronXHCI+0x4A94) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88006604A94, 0xFFFFF88008B5C408, 0xFFFFF88008B5BC60)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
Bug check description: This indicates that a system thread 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. 
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc). 
Google query: Etron Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Mon 12.09.2016 11:33:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091216-20061-01.dmp
This was probably caused by the following module: etronxhci.sys (EtronXHCI+0xA3A1) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880071F83A1, 0xFFFFF880030A4838, 0xFFFFF880030A4090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
Bug check description: This indicates that a system thread 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. 
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc). 
Google query: Etron Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sun 11.09.2016 10:57:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091116-21886-01.dmp
This was probably caused by the following module: etronxhci.sys (EtronXHCI+0xA3A1) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800660A3A1, 0xFFFFF88003077838, 0xFFFFF88003077090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
Bug check description: This indicates that a system thread 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. 
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc). 
Google query: Etron Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Sat 10.09.2016 12:29:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091016-24585-01.dmp
This was probably caused by the following module: etronxhci.sys (EtronXHCI+0xA3A1) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800660A3A1, 0xFFFFF8800305E838, 0xFFFFF8800305E090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
Bug check description: This indicates that a system thread 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. 
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc). 
Google query: Etron Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Fri 09.09.2016 09:57:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090916-26036-01.dmp
This was probably caused by the following module: etronxhci.sys (0xFFFFF8800660A3A1) 
Bugcheck code: 0xD1 (0xFFFF, 0x2, 0x0, 0xFFFFF8800660A3A1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc). 
Google query: Etron Technology Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 08.09.2016 20:08:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090816-21918-01.dmp
This was probably caused by the following module: etronxhci.sys (0xFFFFF880071E33A1) 
Bugcheck code: 0xD1 (0xFFFF, 0x2, 0x0, 0xFFFFF880071E33A1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc). 
Google query: Etron Technology Inc DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 08.09.2016 12:25:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090816-23150-01.dmp
This was probably caused by the following module: etronxhci.sys (EtronXHCI+0xA3A1) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800661C3A1, 0xFFFFF8800309D838, 0xFFFFF8800309D090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
Bug check description: This indicates that a system thread 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. 
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc). 
Google query: Etron Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Wed 07.09.2016 21:37:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090716-23618-01.dmp
This was probably caused by the following module: etronxhci.sys (EtronXHCI+0xA3A1) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800662D3A1, 0xFFFFF8800305E838, 0xFFFFF8800305E090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\etronxhci.sys
product: Etron xHCI Driver.
company: Etron Technology Inc
description: Etron eXtensible Host Controller Driver.
Bug check description: This indicates that a system thread 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. 
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: etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc). 
Google query: Etron Technology Inc SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



Conclusion

51 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: 

etronxhci.sys (Etron eXtensible Host Controller Driver., Etron Technology Inc)
etronhub3.sys (Etron eXtensible Hub Driver., Etron Technology 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 actually 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.
         

In den Schlussfolgerungen kannst Du nachlesen, wo der Fehler liegt und was Du machen kannst. Folge erst mal den Anweisungen. Dann kannst Du die Minidumps erst mal löschen. Wenn wieder BSODs auftreten, kannst Du das Programm ja nochmal laufen lassen und das Ergebnis posten.

GL