Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management\
Name: TrackLockedPages
Type: REG_DWORD
Value: 1
- Admin KnowledgeBase
- Articles & Tutorials
- Authors
- Blogs
- Hardware
- Message Boards
- Newsletters
- RSS
- Software
- White Papers
- Admin Tips
- Windows Server 2008/2003/2000/XP/NT Administrator Knowledge Base
- Windows 2000
- Registry Tips
- Miscellaneous
- Windows 2000 PROCESS_HAS_LOCKED_PAGES BSOD
- Miscellaneous
- Registry Tips
- Windows 2000
- Windows Server 2008/2003/2000/XP/NT Administrator Knowledge Base
- Section(s): Miscellaneous
- Published on Apr 20, 2004.
- Last Modified on Apr 20, 2004.
- Last Modified by Wayne Maples.
- Rated 4.2 out of 5 based on 15 votes.
PROCESS_HAS_LOCKED_PAGES BSOD is caused by a driver leaving behind locked I/O
pages when a process is being cleaned up. If you add the following registry
entry, Windows 2000 will start instead of blue screening and will log extra
memory management information. The next time this event occurs, Windows 2000
will be able to track what process is leaving behind the allocated memory, and
instead of a BSOD with PROCESS_HAS_LOCKED_PAGES , you'll
get DRIVER_LEFT_LOCKED_PAGES which hopefully will
identify the culprit.
Latest tips by Wayne Maples
Article not looking right or info is missing? Let us know so that we can fix it: .
Featured Links*
Become a WindowsNetworking.com member!
Discuss your network issues with thousands of other network administrators. Click here to join!