• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2k blue screen error. Please Help.

datalink7

datalink7

Lifer
Hi all,

So I bought a new game (*note: I know that I could post this in the software forum, but I think that the info I need is more relevent to this forum): Independence War 2. I played through the tutorial fine, but during the first mission, I get these blue screens all the time. I'll be flying along, and all of a sudden I get a blue screen (this seems to happen pretty soon after starting the mission). It says "Process_Has_Locked_Pages," then reboots the computer. It flashes some stuff right before reboot, and I think it says somewhere in there "administrator."

What is this error? What does it mean? Is this something to do with win2k, or do you think the game (if so, I'll move this on down to the software forums).

Thanks a bunch for your help. This is really annoying me.

Some specs:

1.33ghz Athlon
MSI K7 Master
Leadtek GeForce 3 w 12.90 nvidia drivers (had 10.80 and switched to 12.90 to see if that would fix it, but it didn't)
512mb PC2100 DDR RAM
Hercules Game Theatre XP
 
Ok try this out and see if it helps you:


A Windows 2000-based computer may display one of the following error messages on a blue screen:
<BLOCKQUOTE>
<DIV class=ERRORMESSAGE>STOP: 0x00000076 (0x<I>Y</I>,0x<I>Y</I>,0x<I>Y</I>,0x<I>Y</I>) PROCESS_HAS_LOCKED_PAGES </DIV></BLOCKQUOTE>
<BLOCKQUOTE>-or- </BLOCKQUOTE>
<BLOCKQUOTE>
<DIV class=ERRORMESSAGE>STOP: 0x000000CB (0x<I>Y</I>,0x<I>Y</I>,0x<I>Y</I>,0x<I>Y</I>) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS </DIV></BLOCKQUOTE>The parameters in these error messages vary, depending on the programs in use and the system configuration.


<B>WARNING</B>: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT or Windows 2000, you should also update your Emergency Repair Disk (ERD).

The "STOP: 0x00000076 (0x<I>Y</I>,0x<I>Y</I>,0x<I>Y</I>,0x<I>Y</I>) PROCESS_HAS_LOCKED_PAGES" error message is caused by a driver not cleaning up completely after an I/O operation.
<BLOCKQUOTE>Parameter 1 - 0
Parameter 2 - process address
Parameter 3 - number of locked pages
Parameter 4 - pointer to driver stacks (if enabled) or 0 if not </BLOCKQUOTE>Windows 2000 includes a registry value that you can use to save stack traces that enable you to identify the problem driver. Use Registry Editor (Regedt32.exe) to view the following registry key:
<BLOCKQUOTE>HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management </BLOCKQUOTE>Add the following registry value, and then restart your computer:
<BLOCKQUOTE>Value Name: TrackLockedPages
Value Type: REG_DWORD
Value Data: 1
Radix: hexadecimal </BLOCKQUOTE>After you make this change, Windows saves stack traces so that you can identify the problem driver. There is no other way to determine which driver is neglecting to clean up the I/O operations. After you enable this flag, if the driver commits the error again, you see the following error message:
<BLOCKQUOTE>
<DIV class=ERRORMESSAGE>STOP: 0x000000CB (0x<I>Y</I>,0x<I>Y</I>,0x<I>Y</I>,0x<I>Y</I>) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS </DIV></BLOCKQUOTE>
<BLOCKQUOTE>Parameter 1 - The calling address in the driver that locked the pages
Parameter 2 - The caller of the calling address in the driver that locked the pages
Parameter 3 - A pointer to the MDL containing the locked pages
Parameter 4 - The problem driver's name (Unicode string) </BLOCKQUOTE>The problem driver's name is listed on the blue "Stop" screen and is available for dumping again as the fourth parameter in the "Stop" data.

After you identify and update or remove the problem driver, you should remove the TrackLockedPages value from the registry
 
ok, thanks. I sucessfully put in the new registry setting, but the blue screen still reboots too fast. I know that there is a way to make it so that there is no automatic reboot, but I can't remember how to set that up. Someone want to tell me real quick?

Thanks!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top