Trojaner-Board - Windows 7: Regelmäßig Absturz -> Bluescreen -> Neustart. Fehlercode: 0x000000d1

Vielen Dank! Hier die Logs

Betriebssystem ist WIN 7, 64 Bit
Code:
Crash Dump Analysis

--------------------------------------------------------------------------------
 

Crash dump directory: C:\Windows\Minidump
 

Crash dumps are enabled on your computer.
 

On Mon 04.04.2016 12:41:31 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040416-20638-01.dmp

This was probably caused by the following module: netwsw02.sys (0xFFFFF88005B1BF1E) 

Bugcheck code: 0xD1 (0xFFFFFA8407ADCB70, 0x2, 0x0, 0xFFFFF88005B1BF1E)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\netwsw02.sys

product: Intel® Wireless WiFi Link Adapter

company: Intel Corporation

description: Intel® Wireless WiFi Link 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: netwsw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation). 

Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 

On Mon 04.04.2016 12:41:31 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: netwsw02.sys (Netwsw02+0x90F1E) 

Bugcheck code: 0xD1 (0xFFFFFA8407ADCB70, 0x2, 0x0, 0xFFFFF88005B1BF1E)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\netwsw02.sys

product: Intel® Wireless WiFi Link Adapter

company: Intel Corporation

description: Intel® Wireless WiFi Link 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: netwsw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation). 

Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 

On Mon 04.04.2016 12:28:01 GMT your computer crashed

crash dump file: C:\Windows\Minidump\040416-34460-01.dmp

This was probably caused by the following module: netwsw02.sys (0xFFFFF8800531DF1E) 

Bugcheck code: 0xD1 (0xFFFFFA8407BF6B70, 0x2, 0x0, 0xFFFFF8800531DF1E)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\drivers\netwsw02.sys

product: Intel® Wireless WiFi Link Adapter

company: Intel Corporation

description: Intel® Wireless WiFi Link 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: netwsw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation). 

Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
 

--------------------------------------------------------------------------------

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: 
 

netwsw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)
 

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.