Repeatedly Getting Blue Screen

Hello everyone,

I am getting the Blue Screen followed by a physical memory dump every time I turn on my laptop. Sometimes it happens immediately after start up, other times within 5 minutes, and sometimes after working on it for 30+ minutes. I have tried to restore it to earlier settings several times.

I have access to another laptop but there is software that I want to keep using on the one that is getting the Blue Screen. How I can start figuring out what's wrong? What information should I post?

Thank you for your help!

 

If you can, download and install WhoCrashed.

http://www.majorgeeks.com/files/details/whocrashed_free_home_edition.html

The program will show what caused the laptop to crash. Copy and paste that info in your next post.

 

Thank you Eldon.

Unfortunately, the laptop won't stay on long enough (when started up in regular mode) for me to download anything. I managed to take a few pictures of the error messages just now. It's shut down 3 times. Within a few minutes each time.

 

Sorry Eldon. I started it in safe mode with networking enabled and I downloaded it. Here is the message:

System Information (local)
computer name: KAT-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Satellite M500, TOSHIBA,
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T6500 @ 2.10GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4256354304 total



Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 24/05/2015 2:47:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052415-26566-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032890CF)
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 Sun 24/05/2015 2:47:43 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, 0xFFFFF800032890CF)
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: symnets.sys .
Google query: symnets.sys IRQL_NOT_LESS_OR_EQUAL



On Sun 24/05/2015 2:44:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052415-35646-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032CD0CF)
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 Sun 24/05/2015 2:40:57 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052415-36441-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032970CF)
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 Sat 16/05/2015 4:22:08 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\051615-38485-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800032880CF)
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
5 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

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.

 

It's a driver that's causing the problem, your BSOD screenshot doesn't tell us which.

Can you carefully read and follow these instructions: http://www.sysnative.com/forums/bso...d-posting-instructions-windows-8-7-vista.html

Once you have the required data, can you attach it with a Reply back here, please?

 

Hello,
I was able to get the sysnative zip file. However, the perfmon isn't working. I get an error message: An error occured while attempting to generate the report. The system cannot find the path specified. Could this be because I'm running in safe mode with networking enabled?
Thank you!

 

Don't fret about the PerfMon report, I might not need it.

 

As per the WhoCrashed report.

symnets.sys is part of Symantec Security Drivers and developed by Symantec Corporation.

Here's more info at the Norton Community.

http://community.norton.com/en/forums/bsod-caused-symnetsys

 

All 4 crash dumps indicated some kind of issue with a standard Windows networking driver (Netio.sys) and a problem with a Symantec/Norton driver (SYMNETS.sys).

Let's begin by fully removing Norton and installing Microsoft Security Essentials during troubleshooting:

From Safe Mode, you cannot use the Windows Installer for removing certain programs, here's a workaround: http://www.symantec.com/connect/blogs/windows-installer-safe-mode < do this first.

http://www.majorgeeks.com/files/details/norton_removal_tool.html Download this ready to remove any Norton remnants after the usual uninstall routine.

Download MSE installer: http://www.majorgeeks.com/files/details/microsoft_security_essentials_for_windows.html

Enable the Windows Installer for Safe Mode, uninstall Norton (Control Panel > Remove Programs), after a reboot, run the SymNRT tool and reboot again, install MSE and check that the Windows Firewall has been re-enabled.

At this point (after any default MSE scan) you should be able to work safely in normal Windows mode. I'm hopeful that this will cure the BSOD but if another crash/Blue Screen happens, please re-run the Sysnative collection app again - from within normal Windows mode - it should give us a little more detail.

Code:

Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Debug session time: Sat May 16 17:22:08.441 2015 (UTC + 1:00)
System Uptime: 0 days 0:02:53.204
BugCheck A, {0, 2, 1, fffff800032880cf}
*** 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 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Debug session time: Sun May 24 15:44:04.284 2015 (UTC + 1:00)
System Uptime: 0 days 0:02:32.923
BugCheck A, {0, 2, 1, fffff800032cd0cf}
*** 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 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Debug session time: Sun May 24 15:40:57.024 2015 (UTC + 1:00)
System Uptime: 0 days 0:03:34.788
BugCheck A, {0, 2, 1, fffff800032970cf}
*** 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 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18741.amd64fre.win7sp1_gdr.150202-1526
Debug session time: Sun May 24 15:47:43.782 2015 (UTC + 1:00)
System Uptime: 0 days 0:02:40.546
BugCheck A, {0, 2, 1, fffff800032890cf}
*** 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 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System

 

Thank you very much Satrow! I just went through all the steps and it is no longer crashing

Now that I do not have Norton installed, is there another (less problematic) anti-virus, anti-malware software you would recommend?

Thank you!

 

Best to stay with MSE for a week - 10 days, until we're sure that the computer is stable.

 

Thank you Satrow for your help! It has been a few weeks now and there have been no further errors.

 

Excellent news :major

At this point, it's time for you to decide whether to install the latest version of Norton (I guess you've paid for it) or to tighten up your security by using some select Freeware to plug any holes and protect against most current threats - or just stick with MSE + the Windows firewall.

Without knowing your PC usage and your backup/recovery regime, it's very hard to make relevant suggestions.

A good read: http://forums.majorgeeks.com/showthread.php?t=44525

 

If you do choose a paid A/V software, I'll take Kaspersky over Norton or McAfee any day.

 

Thank you both. I have stuck with the MSE + Windows firewall for now and things seem to be going okay. Take care!