- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- StoreEasy Storage
- >
- STOP ERROR 0x0000007f (0x00000008, 0x80042000, 0x0...
StoreEasy Storage
1820392
Members
3263
Online
109623
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2006 03:55 PM
тАО03-13-2006 03:55 PM
STOP ERROR 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000)
I keep getting this error a few hours after enabling Symantec AV autoprotect.
I have the latest Symantec version and HP NAS support pack 5.6 applied to my NAS 2000s.
Upon doing a debug of memory.dmp I get:
Probably caused by : NmSvFsf.sys ( NmSvFsf+6ac )
That looks like the quota driver. I do use my own quota management softeare (Tools4Ever SpaceGuard) and wonder if I can safely disable the Quota service and this driver.
appreciate your feedback.
I have the latest Symantec version and HP NAS support pack 5.6 applied to my NAS 2000s.
Upon doing a debug of memory.dmp I get:
Probably caused by : NmSvFsf.sys ( NmSvFsf+6ac )
That looks like the quota driver. I do use my own quota management softeare (Tools4Ever SpaceGuard) and wonder if I can safely disable the Quota service and this driver.
appreciate your feedback.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-15-2006 10:45 AM
тАО03-15-2006 10:45 AM
Re: STOP ERROR 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000)
Stop 7f is a fatal kernel-level bugcheck. The OS is unhappy about something at a pretty low level, such as a non-paged-pool memory leak, etc.
A quick Google search on NmSvFsf.sys shows there have been several known issues with StorageExec quota software leaking non-paged memmory. Veritas appears to have released several hotfixes for StorageExec.
Another point to note is that several anti-virus vendors' software has been known at various times to introduce such non-paged-pool leaks as well. Symantec is one of the big offenders in that regard, but even McAfee and Trend Micro have caused more than their fair share as well.
Plus, these are all filter drivers. Filter drivers tend to not get along very well with each other. The more of these types of applications that you load (i.e. anti-virus, IP replication, quota software, etc.), the greater your chances of such fatal conflicts. Loading two similar applications, such as two quotaing software applications, has seemed to almost guarantee problems.
Given that NmSvFsf.sys is a filter driver, merely disabling the software will not fix the problem. Filter drivers are always active and present in the driver stack, even if their handler (the application) is disabled or turned off.
The only way to remove a filter driver is to uninstall the software. That, and pray that the software vendor cleans up after themselves correctly during the uninstall.
Since the StorageExec software is part of the Windows Powered OS, uninstalling that software probably puts you outside the "supported configuration". Plus, you don't want to be mucking around with components that are integrated into the OS package, at the risk of introducing further complications...
I took a quick look through the release notes of the NAS Service Pack 5.6, and didn't see anything regarding hotfixes for StorageExec. You might want to call HP support and ask about what fixes, if any, are included or available (and supported!) for the StorageExec on your NAS.
In any case, I'd recommend calling HP support and reporting the problem. Once you get a case logged, HP will be made aware of the problem, and the support people can begin to research this and help you.
A quick Google search on NmSvFsf.sys shows there have been several known issues with StorageExec quota software leaking non-paged memmory. Veritas appears to have released several hotfixes for StorageExec.
Another point to note is that several anti-virus vendors' software has been known at various times to introduce such non-paged-pool leaks as well. Symantec is one of the big offenders in that regard, but even McAfee and Trend Micro have caused more than their fair share as well.
Plus, these are all filter drivers. Filter drivers tend to not get along very well with each other. The more of these types of applications that you load (i.e. anti-virus, IP replication, quota software, etc.), the greater your chances of such fatal conflicts. Loading two similar applications, such as two quotaing software applications, has seemed to almost guarantee problems.
Given that NmSvFsf.sys is a filter driver, merely disabling the software will not fix the problem. Filter drivers are always active and present in the driver stack, even if their handler (the application) is disabled or turned off.
The only way to remove a filter driver is to uninstall the software. That, and pray that the software vendor cleans up after themselves correctly during the uninstall.
Since the StorageExec software is part of the Windows Powered OS, uninstalling that software probably puts you outside the "supported configuration". Plus, you don't want to be mucking around with components that are integrated into the OS package, at the risk of introducing further complications...
I took a quick look through the release notes of the NAS Service Pack 5.6, and didn't see anything regarding hotfixes for StorageExec. You might want to call HP support and ask about what fixes, if any, are included or available (and supported!) for the StorageExec on your NAS.
In any case, I'd recommend calling HP support and reporting the problem. Once you get a case logged, HP will be made aware of the problem, and the support people can begin to research this and help you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2006 07:18 AM
тАО04-23-2006 07:18 AM
Re: STOP ERROR 0x0000007f (0x00000008, 0x80042000, 0x00000000, 0x00000000)
Hy,
I had this Error too on a HP DL380G4p Storage Server with Symantec AV.
In "SafeMode" I moved the Symantec Directory to another Folder, restarted the system in normal mode and found the following advices for this problem:
http://support.microsoft.com/kb/822789/en-us
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2002071208532048?Open&src=w
I think that could help you...
I had this Error too on a HP DL380G4p Storage Server with Symantec AV.
In "SafeMode" I moved the Symantec Directory to another Folder, restarted the system in normal mode and found the following advices for this problem:
http://support.microsoft.com/kb/822789/en-us
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2002071208532048?Open&src=w
I think that could help you...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP