BSOD cause by ntoskrnl.exe error 0x0000000a

david21094 · 17 Jul 2014

Here's what I got:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 7/17/2014 1:49:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071714-23462-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030DAC3F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Thu 7/17/2014 1:49:32 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: symnets.sys (SYMNETS+0x1E7BB)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030DAC3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\N360x64\1501000.012\SYMNETS.SYS
product: Symantec Security Drivers
company: Symantec Corporation
description: Network Security Driver
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: symnets.sys (Network Security Driver, Symantec Corporation).
Google query: Symantec Corporation IRQL_NOT_LESS_OR_EQUAL

On Thu 7/17/2014 1:40:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071714-22869-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030DDC3F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Wed 7/16/2014 1:04:30 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071714-13104-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80003086C3F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Tue 7/15/2014 7:29:01 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071614-17784-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80003088C3F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Tue 7/15/2014 6:55:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071514-16692-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030DEC3F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 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:

symnets.sys (Network Security Driver, Symantec 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.

I also have the dump file here.

I really want to know how to get this fixed.

Boozad · 17 Jul 2014

It's Norton, every one of your dumps points it out:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff800030dec3f}

*** WARNING: Unable to verify timestamp for SYMNETS.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMNETS.SYS
Probably caused by : NETIO.SYS ( NETIO!WfpExpireEntryLru+17 )

Followup: MachineOwner

Code:

fffff880`035085c8  fffff880`04588900Unable to load image \SystemRoot\system32\DRIVERS\SymIMv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SymIMv.sys
*** ERROR: Module load completed but symbols could not be loaded for SymIMv.sys
 SymIMv+0xc900

Uninstall Norton and install MS Security Essentials and MalwareBytes.

Note

Make sure you uncheck the 'Enable Free Trial' box when installing.

david21094 · 18 Jul 2014

Okay so I got rid of norton and I installed Malwarebytes and Microsoft Security Essentials. Now what?

Boozad · 18 Jul 2014

Test and report back.

david21094 · 18 Jul 2014

So far there is no blue screen. No malware was encounterd, there was no encounter in virus and everything seems okay. Does this mean the BSoD will occur if I install Norton Anti-Virus?

Boozad · 18 Jul 2014

It means Norton was causing them. It's possible it will cause them again, stick with MSE and MalwareBytes.

david21094 · 18 Jul 2014

okay then, I will test it out again later in the future to see if it won't happen. Thank you very much. I couldn't have done it without your help!

Boozad · 18 Jul 2014

No problem, you're welcome. Just to be clear, MSE is now your Antivirus program and Malwarebytes is for antimalware and should be run on demand (I run a scan once a week) as opposed to having realtime protection enabled. These two are more than adequate to keep your PC safe from nasties and won't cause BSODs. If you do have any more issues don't hesitate to come back and come back and let us know, we'll be here to help.