Have had my laptop for almost 3 years and have been using Norton 360 for at least that long without problems. Starting a little less than 3 weeks ago started having BSOD's on an irregular basis. Sometimes a few days apart, sometimes 2 or 3 times a day and as long as 6 days apart.
Finally found how to view the issues and they mentioned two Windows Systems files so I googled those and appeared to need driver updates which I did but, no joy. Then found Who Crashed which pointed me to the symefa64.sys driver as the cause. Checked out that driver and it had been modified by Symantec on 10/3/12 just about the time the problems arose so am thinking this is a Symantec issue and I need resolution.
Following is the information from Who Crashed and their pointing at your driver and asking for a update to that file:
System Information (local)
computer name: DAVESDELLLAPTOP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4254035968 total
VM: 2147352576, free: 1938432000
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 10/20/2012 6:06:40 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102012-62275-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001B2FA1D)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 10/20/2012 6:06:40 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netio.sys (NETIO!NetioUpdateNetBufferListContext+0xBCD)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001B2FA1D)
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 which cannot be identified at this time.
On Tue 10/16/2012 3:30:29 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101612-26270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8009221050, 0xFFFFF80000B9C4D8, 0xFFFFFA800C2597D0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
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 which cannot be identified at this time.
On Mon 10/15/2012 10:41:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101512-39327-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001B8FA1D)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 10/15/2012 7:48:58 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101512-34320-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001BA5A1D)
Error: DRIVER_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 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 10/14/2012 12:49:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101412-98733-01.dmp
This was probably caused by the following module: symefa64.sys (SYMEFA64+0x28B54)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800C722B54, 0xFFFFF880033AF838, 0xFFFFF880033AF090)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\N360x64\1402000.013\SYMEFA64.SYS
product: EFA
company: Symantec Corporation
description: Symantec Extended File Attributes
Bug check description: This indicates that a system thread 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: symefa64.sys (Symantec Extended File Attributes, Symantec Corporation).
Google query: symefa64.sys Symantec Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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:
symefa64.sys (Symantec Extended File Attributes, 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.
Only 6 crashes are shown as I tried to revert the laptop to an earlier time a week or so ago thus losing the other dumps but, they were identical to the latest one at the top of this copy and paste.
Have found a potential solution elsewhere to uninstall then reinstall Norton 360 which I kind of had to do when I reverted the system and V6 wouldn't work so I deleted it and then downloaded and installed the latest version using cloud 20.2.0.19.
Didn't go in and delete any reference to Norton but, did use the Norton removal tool and the problems continue. Have updated my network drivers and that seemed to extend the time between BSOD's but, they continue.
Please provide a solution for that driver which appears to be the cause of my issues.
Thanks,
David Weiman
rallydave@pobox.com