Hello, I'm in a pinch right now and I need the help of this community, of possible. My Windows has been showing me that STOP error for the past 2 days (after reformatting). Everything went cool the first day. Installed everything correctly and went on with my business. But then, it just started to go downhill. I've looked up a couple of threads in this forum but I could not understand most of them, however I did download this WhoCrashed program and got the following:
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 10/6/2013 12:46:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-14352-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD0936)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E45990, 0xFFFFFFFF955B6B34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program 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.
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 Sun 10/6/2013 12:46:38 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngLpkInstalled+0xD1A5)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E45990, 0xFFFFFFFF955B6B34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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 Sun 10/6/2013 12:41:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-13759-01.dmp
This was probably caused by the following module: spsys.sys (spsys+0x1129B)
Bugcheck code: 0xD1 (0xFFFFFFFF96547020, 0x2, 0x1, 0xFFFFFFFF9454629B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\spsys.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: security processor
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 10/5/2013 9:32:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-13306-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1A84)
Bugcheck code: 0xA (0x1FFFFE8, 0x2, 0x1, 0xFFFFFFFF82CB4D7D)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 10/5/2013 7:59:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-15178-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3839)
Bugcheck code: 0xA (0x2000000, 0x2, 0x1, 0xFFFFFFFF83016839)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
On Sat 10/5/2013 6:39:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-19172-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x66D87)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF807C9750, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 10/5/2013 6:29:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-19266-01.dmp
This was probably caused by the following module: l1c62x86.sys (L1C62x86+0x2B6C)
Bugcheck code: 0xD1 (0x57, 0x2, 0x1, 0xFFFFFFFF8FBBCB6C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\l1c62x86.sys
product: Atheros L1c PCI-E Gigabit Ethernet Controller
company: Atheros Communications, Inc.
description: Atheros L1c PCI-E Gigabit Ethernet Controller
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: l1c62x86.sys (Atheros L1c PCI-E Gigabit Ethernet Controller, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 10/5/2013 5:45:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-18439-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
Bugcheck code: 0xA (0x2000018, 0x2, 0x1, 0xFFFFFFFF82C7A2BC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 10/5/2013 5:37:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-19718-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x524289)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF91134289, 0xFFFFFFFF9D01F218, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 259.19
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 259.19
Bug check description: This indicates that a kernel-mode program 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 259.19 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 10/5/2013 4:40:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-29702-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
Bugcheck code: 0xA (0xFFFFFFFF87A37020, 0x9, 0x1, 0xFFFFFFFF82C49783)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 10/5/2013 4:19:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-19999-01.dmp
This was probably caused by the following module: afd.sys (afd+0x259CB)
Bugcheck code: 0xD1 (0x4E0C0F8, 0x2, 0x0, 0xFFFFFFFF8D68A9CB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. 3 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:
l1c62x86.sys (Atheros L1c PCI-E Gigabit Ethernet Controller, Atheros Communications, Inc.)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 259.19 , NVIDIA Corporation)
hal.sys
I've uninstalled the Internet and Graphic Card drivers and then installed them again, the same thing happened. I just want to know, do I need to buy new stuff or is there something wrong in the registry? I'm not that good with computers so don't hesitate to ask me for information, because I feel like I left a lot out.
Thanks in advance~
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 10/6/2013 12:46:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-14352-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD0936)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E45990, 0xFFFFFFFF955B6B34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a kernel-mode program 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.
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 Sun 10/6/2013 12:46:38 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngLpkInstalled+0xD1A5)
Bugcheck code: 0x8E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E45990, 0xFFFFFFFF955B6B34, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.
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 Sun 10/6/2013 12:41:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-13759-01.dmp
This was probably caused by the following module: spsys.sys (spsys+0x1129B)
Bugcheck code: 0xD1 (0xFFFFFFFF96547020, 0x2, 0x1, 0xFFFFFFFF9454629B)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\spsys.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: security processor
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 10/5/2013 9:32:16 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-13306-01.dmp
This was probably caused by the following module: netio.sys (NETIO+0x1A84)
Bugcheck code: 0xA (0x1FFFFE8, 0x2, 0x1, 0xFFFFFFFF82CB4D7D)
Error: 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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 10/5/2013 7:59:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-15178-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3839)
Bugcheck code: 0xA (0x2000000, 0x2, 0x1, 0xFFFFFFFF83016839)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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: hal.sys .
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
On Sat 10/5/2013 6:39:31 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-19172-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x66D87)
Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF807C9750, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 10/5/2013 6:29:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-19266-01.dmp
This was probably caused by the following module: l1c62x86.sys (L1C62x86+0x2B6C)
Bugcheck code: 0xD1 (0x57, 0x2, 0x1, 0xFFFFFFFF8FBBCB6C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\l1c62x86.sys
product: Atheros L1c PCI-E Gigabit Ethernet Controller
company: Atheros Communications, Inc.
description: Atheros L1c PCI-E Gigabit Ethernet Controller
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: l1c62x86.sys (Atheros L1c PCI-E Gigabit Ethernet Controller, Atheros Communications, Inc.).
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Sat 10/5/2013 5:45:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-18439-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
Bugcheck code: 0xA (0x2000018, 0x2, 0x1, 0xFFFFFFFF82C7A2BC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 10/5/2013 5:37:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-19718-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x524289)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF91134289, 0xFFFFFFFF9D01F218, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 259.19
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 259.19
Bug check description: This indicates that a kernel-mode program 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 259.19 , NVIDIA Corporation).
Google query: NVIDIA Corporation KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
On Sat 10/5/2013 4:40:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-29702-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
Bugcheck code: 0xA (0xFFFFFFFF87A37020, 0x9, 0x1, 0xFFFFFFFF82C49783)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Sat 10/5/2013 4:19:26 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-19999-01.dmp
This was probably caused by the following module: afd.sys (afd+0x259CB)
Bugcheck code: 0xD1 (0x4E0C0F8, 0x2, 0x0, 0xFFFFFFFF8D68A9CB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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
--------------------------------------------------------------------------------
11 crash dumps have been found and analyzed. 3 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:
l1c62x86.sys (Atheros L1c PCI-E Gigabit Ethernet Controller, Atheros Communications, Inc.)
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 259.19 , NVIDIA Corporation)
hal.sys
I've uninstalled the Internet and Graphic Card drivers and then installed them again, the same thing happened. I just want to know, do I need to buy new stuff or is there something wrong in the registry? I'm not that good with computers so don't hesitate to ask me for information, because I feel like I left a lot out.
Thanks in advance~
Facebook
Twitter
Instagram