I'm going to throw this thing off my balcony

[DKJones96]

This is the 9th time I've done a windows 2000 server SP4 install on this computer. In 2 days. It gets done with checking hardware and when I click next it blue screens...now here is the funny part. It's never the same reason. The only thing the same is that it is a page_fault_in_nonpaged_area...It was working fine until the powersupply went on the fritz and the computer wrote corrupted data for a couple days. Imagine my suprise when my file/print server starts printing random pages until the laser printer is out of paper and anything saved on it for the last few days was garbage...gotta love it.

this time it says ntoskrnl.exe did it. last time it was something32.sys that did it. who know what it was the last few times probably elvisisstillalive.dll or something.

This is a P166(nonMMX) with 196MBEDO memory 4HDDs@ 40GB each(slow as hell on the ATA-2) Has a controller that runs an external array that totals 2TB of storage and has a gigabit ethernet adaptor but I've taken everything out and even disabled all the ports I don't need to try and get the install done. Unfortunately it overwrote the full backup while it was messed up so that's out of the question.

Should I just retire this bad boy with a 100watt powersupply? Its run 24/7 for the past 6 years flawlessly I guess HP just didn't build it to hit the 10 year mark...too bad tho it was only a month and a half away...

[Sterling_Aug]

Page faults are ALWAYS the result of bad RAM.

Toss the system before you throw good money after bad.

You got your moneys worth out of the poor thing.

[DKJones96]

You know...I did just swap in the last set of 64MB chips a few weeks ago...I should take them out and see if that was the problem.

[Sterling_Aug]

An easy test and FREE.

[DKJones96]

Don't worry...I don't plan on putting real money into this thing for as little as 50 bucks I could get an athlon 900 going with double the ram...not really needed tho and it takes more power to run all the time so yeah.

[DKJones96]

what do you know...it was that stupid ram...thanks.

[Baddog]

Cruising on to the 10 year mark.:)

[GrefMofovich]

What have you done about the y2k though? Now might be a good time to upgrade your safety helmet! :eek:

-GM

[G]

From "More Than Just A Glossary" - Copyright


 PAGE_FAULT_IN_NOPAGES_AREA (symbolic name) (Stop 0x00000050 or Stop 0x50 (Stop error code)) (Parameter codes: 0xffffffe0, 0x00000001, 0xf30da010, 0x00000000):

 (Cause: This bug check indicates that requested data was not located in memory - invalid system memory has been referenced from which it is unable to recover from and is looked for in the paging file. However, if the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver. In this situation, however, the missing data is identified as being located within an area of memory that cannot be read to disk because of memory corruption is in an I/O Request Package (IRP) list. This fault can occur as a result of a variety of error conditions, such faulty hardware installed (in particular memory, e.g., physical memory L2 RAM cache, or video RAM), a system service bugs, corrupted NTFS volume or bugs in anti-virus software. This Stop error is a common at IRQL_NOT_LESS_OR_EQUAL. (Solution: Firstly, Use the Event Viewer, Control Panel > Administrative Tools > Event Viewer and check for SCSI or FASTFAT error messages in the System Log. Check for error messages from Autochk in the Application Log. Error messages may identify whether a device or a device driver is causing the Stop error. 1) Faulty hardware: Remove any recently installed hardware and determine whether this resolves the error. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics utilities downloadable from the manufacturer’s support webpage and seek further advice. 2) System service bug: Disable the service and determine whether this resolves the problem. Some software installations install system services; consult the manufacture for an update to resolve this problem. If the problem persists during booting into Windows use Safe Mode (SM), one of three Windows boot-problem recovery modes: the other two are the Recovery Console (RC) and the Last Known Good Configuration (LKGC). SM is available by pressing the F8 function key during startup: after the firmware POST process completes but before the operating system displays the graphical output. Once the operating system’s Advanced Option Menu is displayed, select the option to start the computer in SM. Once in SM disable the service. If this resolves the problem then the system service bug is the cause. Uninstall the application in SM, if possible, and reboot into Windows. If it is a recent driver, the simplest and most effective route to correcting this Stop error is to use the LKGC. Press the F8 function key during startup: after the firmware POST process completes but before the operating system displays the graphical output. Once the operating system’s Advanced Option Menu is displayed, select the option to start the computer in the LKGC. Note: Logging on to the computer in SM does not update the Last Known Good control set, so the LKGC remains an option even if SM is attempted first. Do not complete a normal logon if problems have been encountered, as logging on causes the LKGC control set to be overwritten. Instead, restart the computer and use the LKGC or SM unless it fails too to resolve the problem. If the current hardware settings, instability and startup problems prevent the computer from starting, the LKGC can allow the computer to be started and the configuration to be examined by reversing (rolling back) the most recent hardware profile consisting of system and driver changes, using the last known good control set to roll back the system’s registry configuration to a successful booting state. When the LKGC is used, restoring previous drivers and registry settings for the subkey HKLM\SYSTEM\CurrentControlSet loses all configuration changes that were made since the last successful logon. After a user logs on successfully, Windows updates the LKGC information to reflect the current configuration state. Report the driver problem so that the driver engineer will be able to avoid future Stop errors. If not already doing so, install using the latest driver. Alternatively, increase the quantity of non-paged pool memory available to the kernel. Corrupted NTFS volume: Run the chkdsk /r (locates bad sectors and recovers readable information (implies /f) and to resolve any file structure corruption). If Chkdsk.exe cannot lock the volume, it offers to check it the next time the computer restarts (boots). Because NTFS also identifies and remaps bad sectors during the course of normal operations, it is usually not necessary to use the /f parameter useless there is a suspicion that a hard disk drive has bad sectors to detect and correct filesystem damage, if any. Refer to the entry Recovery Console (RC) and run chkdsk /r if booting into Windows is not possible. If on booting, run Windows Setup or the RC, it will not be possible to determine the cause of the problems using the solutions aforementioned and 3) After the virus is activated, it stays in memory and passes the execution to the original boot sector so that the startup appears normal. Newer viruses have the power to make restoring an uninfected MBR more intractable. In this case the first port of call is to run a pre-Windows commercial anti-virus program. There is no guarantee that full or partial boot file disinfection will be possible. Also update the anti-virus program to fix program bug.


 FAT or FAT32 File System: Whether the system partition is a FAT or FAT32 filesystem, disconnect or turn off any data hard disk drive that contain NTFS volumes. This allows access back into the operating system to perform the following troubleshooting steps. If you can determine which NTFS volume that is causing the Stop error boot problem, use the following steps:

1 Disconnect the hard disk drive containing the corrupted NTFS volume, and start Windows in Safe Mode.
2 Rename the %SystemRoot%\System32\Drivers\Ntfs.sys file to Ntfs.old; thus preventing Ntfs.sys loading after rebooting.
3 Reconnect the hard disk drive containing the corrupted NTFS volume.
4 Reboot and run chkdsk d: /f (d signifying the corrupt NTFS volume).
5 Rename %SystemRoot%\System32\Drivers\Ntfs.old to Ntfs.sys.
6 Reboot and the Stop error should be resolved.

 Using the RC on a single hard disk drive computer: Assuming that the problem occurs on a computer with a single NTFS partition/volume, boot using the Windows Setup floppy diskettes. Run Chkdsk with the Ntfs.sys driver disabled and repair the corrupted NTFS volume using the RC as follows:

1 Using the first Windows Setup floppy diskette, modify the file called Txtsetup.sif using Notepad.

 Section [FileSystems.Load]; locate the line beginning ntfs.
 Insert a semicolon ( ; ) in front of ntfs ,as shown below:


 Save the changes made.

2 Using the Windows Setup floppy diskettes, at the “Welcome to Setup” message, press F10 to start the RC.
3 Run chkdsk d: /p to repair the corrupted NTFS partition (d signifying the corrupt NTFS volume).
4 Exit the RC, and reboot the computer.

There are occasions when the solutions described above to correct this Stop error relating to a corrupt NTFS volume will not be successful. The only option left is to delete, recreate, and format the corrupted NFTS partition.