New
#1
Random BSOD error
I kept having random BSODs at random times, doing different thing, including doing nothing, laptop would BSOD. Ran WhoCrashed and report is as follows:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 21/10/2013 3:00:24 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF880033F1640)
Bugcheck code: 0x109 (0xA3A039D8A1A88782, 0xB3B7465EF426C4CC, 0xFFFFF880033F1640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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.
Google query: CRITICAL_STRUCTURE_CORRUPTION
On Fri 18/10/2013 3:09:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101813-34803-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D8A11A75C7, 0xB3B7465EF398B321, 0xFFFFF880033F1640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 15/10/2013 8:22:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101513-40856-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D8A2A8B6D4, 0xB3B7465EF526F29E, 0xFFFFF8800334D640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Sat 12/10/2013 1:49:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101213-34803-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x109 (0xA3A039D8A21BF5D8, 0xB3B7465EF49A31A2, 0xFFFFF8800334D640, 0x3)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 the kernel has detected critical kernel code or data corruption.
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 Fri 11/10/2013 10:57:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101113-29140-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001ACB6FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001ACB6FD)
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 Fri 4/10/2013 11:52:07 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-33992-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880018106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880018106FD)
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 Fri 4/10/2013 10:26:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-22354-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880019AE6FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880019AE6FD)
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 Fri 4/10/2013 9:50:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-24726-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001AA96FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001AA96FD)
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 Fri 4/10/2013 8:58:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100413-25334-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001A106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001A106FD)
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 30/9/2013 11:57:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\093013-23790-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001B766FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001B766FD)
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 Sat 28/9/2013 2:04:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-142397-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8800198A6FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF8800198A6FD)
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 Wed 25/9/2013 7:11:03 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092513-225374-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001A246FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001A246FD)
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 2/9/2013 9:09:10 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\090213-37596-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880019286FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880019286FD)
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 Fri 31/5/2013 3:04:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053113-24476-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF880018106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF880018106FD)
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 Wed 29/5/2013 6:53:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052913-35006-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF88001A106FD)
Bugcheck code: 0xD1 (0x28, 0x2, 0x0, 0xFFFFF88001A106FD)
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.
.rar file attached with SF files inside.
Please help asap, need my laptop in top working condition!
Thanks in advance for your help