Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD Error: IRQL_NOT_LESS_OR_EQUAL


  • Please log in to reply
No replies to this topic

#1 Youredoingitwrong

Youredoingitwrong

  • Members
  • 15 posts
  • OFFLINE
  •  
  • Local time:12:49 PM

Posted 13 April 2015 - 05:27 AM

A couple months ago I built my own PC which is an MSI set up running Windows 7. Recently I noticed that I got a BSOD when I was away from my computer. So I scanned my computer with WhoCrashed and got the results below. I know the crashes from an earlier date were because I had Panda Security installed and WoW installed, and I found out that Panda and WoW don't run well together on a Pc, so then I uninstalled Panda Security. But I don't know how to fix the more recent crashes on 4/13/2015 and 3/10/2015. Could anyone help me fix these issues with the more recent crashes?

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 4/13/2015 9:17:14 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041315-12651-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800034908AC)
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 3/10/2015 3:14:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030915-6723-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800034D98AC)
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 12/25/2014 7:29:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122514-7082-01.dmp
This was probably caused by the following module: nnsstrm.sys (0xFFFFF88003A80BE0)
Bugcheck code: 0x50 (0xFFFFF8A00F3A502C, 0x0, 0xFFFFF88003A80BE0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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: nnsstrm.sys .
Google query: nnsstrm.sys PAGE_FAULT_IN_NONPAGED_AREA



On Thu 12/25/2014 7:22:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122514-7020-01.dmp
This was probably caused by the following module: nnsstrm.sys (0xFFFFF88003EF7BE0)
Bugcheck code: 0x50 (0xFFFFF8A01025702C, 0x0, 0xFFFFF88003EF7BE0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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: nnsstrm.sys .
Google query: nnsstrm.sys PAGE_FAULT_IN_NONPAGED_AREA



On Thu 12/25/2014 5:43:36 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122514-7035-01.dmp
This was probably caused by the following module: nnsstrm.sys (0xFFFFF88003F77B90)
Bugcheck code: 0x50 (0xFFFFF8A00BE7A038, 0x0, 0xFFFFF88003F77B90, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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: nnsstrm.sys .
Google query: nnsstrm.sys PAGE_FAULT_IN_NONPAGED_AREA



 

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:

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



 



BC AdBot (Login to Remove)

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users