<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>win 2000 bluescreen: PROCESS HAS LOCKED PAGES</title>
    <link>http://forum.geizhals.at/feed.jsp?id=24361</link>
    <description>Geizhals-Forum</description>
    <item>
      <title>Re: win 2000 bluescreen: PROCESS HAS LOCKED PAGES</title>
      <link>http://forum.geizhals.at/t24361,96302.html#96302</link>
      <description>Hi!&lt;br&gt;&lt;br&gt;Irgendein Treiber spielt da nicht mit - hab ich auch ab und dann. &lt;br&gt;Befolg die Anweisungen unten, dann kannst du mal herausfinden, &lt;br&gt;welcher Treiber da Probleme macht.&lt;br&gt;&lt;br&gt;-----------------------------------------------------------&lt;br&gt;&lt;br&gt;Troubleshooting "STOP 0x00000076 - PROCESS_HAS_LOCKED_PAGES" Error &lt;br&gt;Messages in Windows 2000&lt;br&gt;&lt;br&gt;The information in this article applies to:&lt;br&gt;Microsoft Windows 2000 Advanced Server &lt;br&gt;Microsoft Windows 2000 Professional &lt;br&gt;Microsoft Windows 2000 Server&lt;br&gt;IMPORTANT: This article contains information about editing the &lt;br&gt;registry. Before you edit the registry, make sure you understand &lt;br&gt;how to restore it if a problem occurs. For information about how to &lt;br&gt;do this, view the "Restoring the Registry" Help topic in &lt;br&gt;Regedit.exe or the "Restoring a Registry Key" Help topic in &lt;br&gt;Regedt32.exe.&lt;br&gt;&lt;br&gt;SUMMARY&lt;br&gt;A Windows 2000-based computer may display one of the following &lt;br&gt;error messages on a blue screen: &lt;br&gt;STOP: 0x00000076 (0xY,0xY,0xY,0xY) PROCESS_HAS_LOCKED_PAGES &lt;br&gt;-or- &lt;br&gt;STOP: 0x000000CB (0xY,0xY,0xY,0xY) &lt;br&gt;DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS &lt;br&gt;The parameters in these error messages vary, depending on the &lt;br&gt;programs in use and the system configuration. &lt;br&gt;&lt;br&gt;MORE INFORMATION&lt;br&gt;WARNING: Using Registry Editor incorrectly can cause serious &lt;br&gt;problems that may require you to reinstall your operating system. &lt;br&gt;Microsoft cannot guarantee that problems resulting from the &lt;br&gt;incorrect use of Registry Editor can be solved. Use Registry Editor &lt;br&gt;at your own risk.&lt;br&gt;&lt;br&gt;For information about how to edit the registry, view the "Changing &lt;br&gt;Keys and Values" Help topic in Registry Editor (Regedit.exe) or &lt;br&gt;the "Add and Delete Information in the Registry" and "Edit Registry &lt;br&gt;Data" Help topics in Regedt32.exe. Note that you should back up the &lt;br&gt;registry before you edit it. If you are running Windows NT or &lt;br&gt;Windows 2000, you should also update your Emergency Repair Disk &lt;br&gt;(ERD).&lt;br&gt;&lt;br&gt;The "STOP: 0x00000076 (0xY,0xY,0xY,0xY) PROCESS_HAS_LOCKED_PAGES" &lt;br&gt;error message is caused by a driver not cleaning up completely &lt;br&gt;after an I/O operation. &lt;br&gt;Parameter 1 - 0&lt;br&gt;Parameter 2 - process address&lt;br&gt;Parameter 3 - number of locked pages&lt;br&gt;Parameter 4 - pointer to driver stacks (if enabled) or 0 if not &lt;br&gt;Windows 2000 includes a registry value that you can use to save &lt;br&gt;stack traces that enable you to identify the problem driver. Use &lt;br&gt;Registry Editor (Regedt32.exe) to view the following registry key: &lt;br&gt;HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory &lt;br&gt;Management &lt;br&gt;Add the following registry value, and then restart your computer: &lt;br&gt;Value Name: TrackLockedPages&lt;br&gt;Value Type: REG_DWORD&lt;br&gt;Value Data: 1&lt;br&gt;Radix: hexadecimal &lt;br&gt;After you make this change, Windows saves stack traces so that you &lt;br&gt;can identify the problem driver. There is no other way to determine &lt;br&gt;which driver is neglecting to clean up the I/O operations. After &lt;br&gt;you enable this flag, if the driver commits the error again, you &lt;br&gt;see the following error message: &lt;br&gt;STOP: 0x000000CB (0xY,0xY,0xY,0xY) &lt;br&gt;DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS &lt;br&gt;Parameter 1 - The calling address in the driver that locked the &lt;br&gt;pages&lt;br&gt;Parameter 2 - The caller of the calling address in the driver that &lt;br&gt;locked the pages&lt;br&gt;Parameter 3 - A pointer to the MDL containing the locked pages&lt;br&gt;Parameter 4 - The problem driver's name (Unicode string) &lt;br&gt;The problem driver's name is listed on the blue "Stop" screen and &lt;br&gt;is available for dumping again as the fourth parameter in &lt;br&gt;the "Stop" data. &lt;br&gt;&lt;br&gt;After you identify and update or remove the problem driver, you &lt;br&gt;should remove the TrackLockedPages value from the registry. &lt;br&gt;</description>
      <pubDate>Wed, 04 Jul 2001 06:58:47 GMT</pubDate>
      <guid>http://forum.geizhals.at/t24361,96302.html#96302</guid>
      <dc:creator>Anonym</dc:creator>
      <dc:date>2001-07-04T06:58:47Z</dc:date>
    </item>
    <item>
      <title>win 2000 bluescreen: PROCESS HAS LOCKED PAGES</title>
      <link>http://forum.geizhals.at/t24361,96222.html#96222</link>
      <description>was soll obige fehlermeldung bedeuten? &lt;br&gt;ich muss windows 2000 dann rebooten.&lt;br&gt;</description>
      <pubDate>Tue, 03 Jul 2001 21:22:06 GMT</pubDate>
      <guid>http://forum.geizhals.at/t24361,96222.html#96222</guid>
      <dc:creator>ernst</dc:creator>
      <dc:date>2001-07-03T21:22:06Z</dc:date>
    </item>
  </channel>
</rss>
