You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

On Sun 12/14/2014 9:47:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121414-32495-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001408665)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001408665)
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.

BC AdBot (Login to Remove)

Please post that Speccy link in the box below, then try to understand follow the advice.

SYS errors, such as those associated with netio.sys, most often occur during computer startup, program startup, or while trying to use a specific function in your program (eg. printing).SYS file errors are typically caused by faulty hardware or corrupt device driver files. Because of the importance of Netio.sys in the functionality of Windows 7 Professional SP1 32-bit and other Windows functions, any corruption or damage to this file can create critical system errors in the form of a (BSOD).I may be wrong, but I believe it was part of a major update ....................................