Bsod irql_not_less_or_equal

Greetings All:

Been some time, too much work these days.....

After a Windows update I restarted and cant get past IRQL_NOT_LESS_OR_EQUAL .

Working in safe mode with networking, can't open anything in Office 2010, Word, Outlook, Excel, etc..

Here is the Windows info:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF800030DD96F
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070115-28828-01.dmp
C:\Users\NewHP\AppData\Local\Temp\WER-46129-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


I attempted to upload the files, I can find the .dmp file but it won't let me upload it. The .xml file can't be found.

Thanks in advance for the assistance

Crapgame

 

I suggest you download WhoCrashed Free Home Edition and post the log.

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

 

Thanks for your prompt response, here is the log:

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 7/1/2015 6:17:54 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070115-28828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030DD96F)
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/1/2015 6:17:54 AM 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, 0xFFFFF800030DD96F)
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 Wed 7/1/2015 5:26:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070115-15756-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030D496F)
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/1/2015 5:23:45 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070115-30638-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000308596F)
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 6/30/2015 2:10:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-61121-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000308796F)
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 6/30/2015 2:06:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-60216-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000309996F)
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 6/30/2015 2:02:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-59389-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000309B96F)
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 6/30/2015 1:58:07 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-56753-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800030E096F)
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 6/30/2015 1:54:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-60403-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000308296F)
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 6/30/2015 1:50:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\063015-44600-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000308F96F)
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
--------------------------------------------------------------------------------

51 crash dumps have been found and analyzed. Only 10 are included in this report. 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.


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 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.

 

Try and do a System Restore to just before the problem occurred. If you can't, or it doesn't fix the problem, run the System File Checker tool.

https://support.microsoft.com/en-gb/kb/929833

 

System restore, would that remove the windows update? This happened just after I did a windows update, I restarted it and left for the day (wasn't here when it restarted, I got on the computer and put in password then got the BSOD).

 

symnets.sys is flagged, uninstall Norton/Symantec and use their removal tool: http://www.majorgeeks.com/files/details/norton_removal_tool.html

Ensure that the Windows firewall is enabled and install MSE during testing: http://www.majorgeeks.com/files/details/microsoft_security_essentials_for_windows.html

 

Thanks all......

No more BSOD.......

One last question, Norton was a free copy provided by Comcast and I was able to retain use after switching to Verizon. I will be unable to obtain a new "Free" copy, recommendations for Anti-Virus software or is the Security Essentials good enough?

Thanks again.....

 

Stick with MSE for 7-10 days, if it's still stable then, you've probably fixed it.

Which free AV you use after that really depends on what suits your PC usage/style and works well with any other security tools you use. I'd suggest trying a limited install of Avast!, install just the File protection and Web 'shields' and see how you get along with it.

 

Thanks, will keep you posted.....

 

OK, good luck :major