Windows 2000 Pro Problem

mastarecoil

Senior member
Dec 31, 2000
615
0
0
I am getting this problem every time I restart my computer. Sometimes I get threw with out a problem, this is a very rare occasion though, so for now my computer is staying on 24/7, but this is getting hard to sleep with. Here is what happens:

My computer boots to windows 2000 like normal, it looks like its all going well, then it starts going threw the loading procedures, starting computer, all that, but when it gets to applying personal settings the thing just stays there, and if I push a button or move my mouse it stops the blue/white bar scrolling. At that point all I can do is restart. It does this every time so I try to go into safe mode, where i get a stop screen with the error PAGE_FAULT_IN_NONPAGED_AREA 0x00000000(0xED06E5E0,0x00000000,0xED0652E1,0x00000000). Ive looked in the KB and found nothing on this.

Here is my system:
Celeron 533
2) 128mb pc100 cas2 Crucial ram
Abit BX133-RAID
Voodoo 3 2000 pci (I have played with all the win2k drivers for this)
Sound Blaster Live Value
2) WD 20.5gb 7.2krpm in RAID0 array
Dlink 10/100 nic
Dlink 10 usb nic
Memorex 48x cdrom
Plextor 12x10x32A CDRW
Logitech optical mouseman
Sidewinder game pad
2) generic 4 port usb hubs

Windows 2000 is the version that schools distribute cheaply. I also installed the service pack from windows a while back.

If anyone has any idea what is causing this or what I can try to solve this, please let me know.

Also, I am getting an Elsa Geforce2 gts, will I have problems installing it and overriding it as my primary video card in place of the v3, I intend to keep the v3.

Thank you,
Garrett Kaste.
 

Hecky

Banned
Dec 15, 2000
105
0
0
Have you added or changed anything at all? Or did this just start out of the blue? It sounds like an unresolved hardware issue. I got similar results when I added an old SCSI drive and the only way to fix win2k was to remove the drive. If you added something or changed your configuration you could try to put it back the way it was before the problem began....
I went back and read your problem again and it sounds like something is up with your page file. Have you tried to resize or move your paging file? You could put it on another drive and defrag the first one to see if that fixes it.
 

Dulanic

Diamond Member
Oct 27, 2000
9,951
570
136
Are you OCing? If my CPU is up too high thats what causes that stop error for me.
 

mastarecoil

Senior member
Dec 31, 2000
615
0
0
Nope. Havent added anything recentally. Im also not overclocking, this cele 533 cant oc for jack. System wont post if it oced, good thing its just temp til I get my p3 850.

Thanks
Garrett.
 

jaywallen

Golden Member
Sep 24, 2000
1,227
0
0
The only reference I can find with respect to this error (PAGE_FAULT_IN_NONPAGED_AREA) in the W2K Pro Resource Kit references the error number 0x00000050 rather than 0x00000000. Not sure what significance that might have.

At any rate it's supposed to happen when an entity requests data that isn't found in memory. The system should normally go to the pagefile when this occurs, but in this case the data has been identified as being located within an area of memory that can NOT be paged to disk. This is what causes the system fault, and the inability to recover. The most common causes are listed as faulty hardware, a buggy system service, antivirus software (sometimes the same thing as a "buggy system service"), and corruption of an NTFS volume.

Since you say you hadn't installed anything (hardware or software?) just before this mess started, this begs the question of incipient or intermittent hardware failure, though something as mundane as an anti-virus update could be causing it, too. I'd try swapping out components with known good ones or just removing components as appropriate, starting with portions of main memory, then moving on to L2 RAM cache, video cards / video RAM, and then any other hardware -- particularly if any of it seems flakey. For instance, what happens if you switch memory modules around in the slots? Or if you just remove half of your memory (assuming you have multiple memory modules)?

Other stuff to try: disabling the anti-virus (totally, including any services it runs), selectively disabling other non-essential non-Microsoft services, running chkdsk /f /r, disabling memory caching in the BIOS.

You might wish to alter the order of these suggestions, doing the easy stuff first. Most important thing is to make one change at a time with testing between changes. This can be a PIA, but it's definitely the best way to find the source of the problem. If the error occurs often enough it shouldn't take too long to find out what item, when disabled, causes the error to stop happening.

BTW, are you getting any error messages in the Applications Log or System Log in Event Viewer? Sometimes they'll give a clue about a screwed-up function that's either a cause or symptom of an NT Executive Stop.

Hope you get it pegged.

Regards,
Jim
 

Kappo

Platinum Member
Aug 18, 2000
2,381
0
0
I have a VERY similar setup as you...(bx133 raid) I have had the EXACT same problem.
it is actually one of two things that I have encountered...
try setting your ram back down to cas3...if that does not work try disabling the serial or parallel port to free up your IRQ's. I have a feeling that will solve the problem but, you probably want to use the serial or parallel ports...
you can try moving your PCI cards around...(try to leave the 2nd one from the bottom free...) and it may free up an irq for you..hope this helps and let us know! ;)