Colif :
update motherboard drivers , gpu drivers or any USB devices you have.
IRQL errors are mostly associated with drivers so one of your drivers is older than the bios I have to assume.
You can download and run this:
http://www.resplendence.com/whocrashed
it will scan error logs and may show name of driver responsible or just blame ntoskrnl like usual
Copy the summary page into here and we see if we can help
Can I have some help with my computer crashes?
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Tue 10/11/2016 4:06:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101116-37312-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8060F24E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8060F24E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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 Tue 10/11/2016 4:06:37 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: avgwfpa.sys (avgwfpa+0xA38E)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8060F24E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\avgwfpa.sys
product: AVG Internet Security
company: AVG Technologies CZ, s.r.o.
description: AVG Firewall 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: avgwfpa.sys (AVG Firewall driver, AVG Technologies CZ, s.r.o.).
Google query: AVG Technologies CZ, s.r.o. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Tue 10/11/2016 3:44:27 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101116-35796-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8090837E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8090837E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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 Tue 10/11/2016 3:09:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101016-32468-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF802DEF7E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF802DEF7E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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 Tue 10/11/2016 3:03:27 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101016-30531-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80BD174E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF80BD174E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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 Mon 10/10/2016 9:55:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101016-35703-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF808F737E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF808F737E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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 Mon 10/10/2016 9:49:48 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101016-34093-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80D7F70E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF80D7F70E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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 Mon 10/10/2016 9:18:00 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101016-27656-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8014604E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF8014604E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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 Mon 10/10/2016 8:05:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101016-27515-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF802A9F2E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF802A9F2E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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 Mon 10/10/2016 7:45:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101016-24421-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF80FC184E6D8)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF80FC184E6D8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
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.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
12 crash dumps have been found and analyzed. Only 10 are included in this report. 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:
avgwfpa.sys (AVG Firewall driver, AVG Technologies CZ, s.r.o.)
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.
Facebook
Twitter
Instagram