Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

mind of its own

Status
Not open for further replies.

skyblade

Technical User
May 21, 2002
9
US
ive got XP pro and it turns itself off every few hours or so. i disabled the automatic reboot option and now i get the blue screen of death instead. it says that there is an error in the win32k.sys file. how do i fix it? am i gonna have to reinstall XP? thanks for any insight.
 
Try running the System File Checker program use SFC /Scannow typed in the Run Box and see if that clears up your problem.

Description of the Windows System File Checker Tool (Q310747)

When did this start happening. If recently you might be able to use System Restore to go back to a restore point before the trouble.

If none of the above help post back with your exact error details.
 
well i tried that and it helped for like 2 days. then it has since gone back to normal. here is the exact error i recieve when my computer freezes on me

win32k.sys
Page_Fault_in_nonpaged_area

stop: oxoooooo50 (0xE044DC18, 0x00000000, 0xBF876BCL, 0x0000000)

win32k.sys - address BF876BC1 base at BF800000 Datestamp 3B7de698

then it goes on to begin dump of physical memory and the normal blue screen of death process ect.

i hope that means something to someone because its just numbers and letters to me. thanks in advance for any help.
 
See if these two sites help you out with their information on this Stop Error.




Error Message:
STOP: 0x00000050 (parameter, parameter, parameter, parameter) PAGE_FAULT_IN_NONPAGED_AREA

Explanation:
This is a Windows 2000 Executive character-mode STOP message. It indicates a page fault in the address space reserved for nonpaged data.

User Action:
If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.






STOP 0x00000050 Errors

"Stop 0x00000050" Error Message During Copy from OS/2 Clients
Microsoft Knowledge Base Article Q281546 - When you copy files from an OS/2-based client computer to a Windows 2000-based computer, you may receive the following error message: STOP 0x00000050 (0xXXXXXXXX 0x00000000 0xXXXXXXXX 0x00000001 in Srv.sys (updated 2/22/2001)

"Stop 0x00000050" Error Message When You Are Using a CD-ROM
Microsoft Knowledge Base Article Q302827 - When you are using a CD-ROM, you may receive a "Stop 0x00000050" error message. (updated 7/12/2001)

"Stop 0x50" Error Message While Installing Windows NT 4.0
Microsoft Knowledge Base Article Q171003 - While you are installing Windows NT 4.0, your computer may stop responding (hang) while displaying the following error message on a blue screen: (updated 1/17/2000)

"Stop 0x00000050" in Ntfs.sys Under Stress Accessing Freed FCB
Microsoft Knowledge Base Article Q252192 - A Windows 2000-based computer that is under stress in Ntfs.sys may display the following error message on a blue screen; (updated 8/2/2000)

STOP 0x50 in Usbhub.sys with Surprise Removal of Plug and Play USB Hub
Microsoft Knowledge Base Article Q261199 - When you unplug a Plug and Play Universal Serial Bus (USB) hub (a surprise removal) several times, the following error message may be displayed: (updated 7/27/2000)

Stop 0x00000050 in Udfs.sys Viewing Files on DVD
Microsoft Knowledge Base Article Q282870 - When you are using Windows Explorer to view files on a DVD, you may receive the following error message on a blue screen: Stop 0x00000050 (0xd1e3ffd7, 0x00000000, 0xbef54b74, 0x00000000) (updated 1/8/2001)

"Stop 0x00000050" in Ntfs.sys Under Stress Accessing Freed FCB
Microsoft Knowledge Base Article Q252192 - A Windows 2000-based computer that is under stress in Ntfs.sys may display the following error message on a blue screen: (updated 7/27/2000)

Stop 0x50 Error Message Printing to Windows NT 4.0 Print Server
Microsoft Knowledge Base Article Q199118 - When you attempt to print to a Microsoft Windows NT 4.0 print server, you may receive the following error message: (updated 12/29/1999)

"Stop 0x1E" or "Stop 0x50" with Terminal Services Client Print Session
Microsoft Knowledge Base Article Q279343 - A Windows 2000-based Terminal Services server may generate a "Stop 0x1E" or "Stop 0x50" error message during a Terminal Services client print session. This may be caused by selecting a particular font in the document that is being printed. (updated 1/10/2001)

"Stop 0x50" in ObReferenceObjectByPointer with Terminal Services in Windows 2000
Microsoft Knowledge Base Article Q295462 - Under certain conditions, a heavily loaded Windows 2000-based server that is using Terminal Services may experience a "Stop 0x50" (fffffff0,0,8044d24d,0) error in ObReferenceObjectByPointer. (7823 updated 4/11/2001 10:30:00 AM GMT)

"Stop 0x50 in Win32k.sys" Error Message
Microsoft Knowledge Base Article Q281132 - When you are running Terminal Services with multiple clients (for example, you may have Citrix clients with Citrix Serverfarm), you may receive multiple error messages on blue screens that are related to Win32k.sys. The following error message may be displayed: STOP: 0x00000050 (0xf7f7f7fb, 0x00000000, 0xa0033dd0, 0x00000000) PAGE_FAULT_IN_NONPAGED_AREA address 0xa0033dd0 in Win32K.sys (updated 2/7/2001)

"Stop 0x00000050" Error Message When USB Device Is Connected
Microsoft Knowledge Base Article Q291284 - If you connect a Universal Serial Bus (USB - device to the USB port, your computer may stop responding (hang - with the following error message: (updated 8/15/2001)

Stop 0x50 Error Message When You Rename a Large Number of Files on Windows 2000
Microsoft Knowledge Base Article Q323256 - After a you create and then rename a large number of files, you may receive a stop 0x00000050 error message on a blue screen. If special pool memory is turned on (as is described in Q188831), you may receive a stop 0x000000CD error message (updated 6/12/2002)

"Stop 0x00000050" Error Message When You View Files on a DVD
Microsoft Knowledge Base Article Q290321 - When you are use Windows Explorer to view files on a DVD, you may receive the following error message on a blue screen: (updated 6/20/2001)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top