I recently updated/changed from Windows ME to Windows 2000 Professional.
Every time I start up the computer, it "almost gets there", then stops, showing
a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
STOP number 0x00000050, which implies problems with the writing to memory
(swap file).

I then restart the computer, and it starts up fine. Ergo: I always need to start
the computer twice, the first time resulting in a blur screen, the second time
successfully. 

I have set aside a 766 MB swap file on the C: partition (min and max size), although
I previously had it on the D: partition. I have run chkdsk and service packs, and 
no
errors are found whatsoever, but the problems remains. My computer is formatted
in NTFS (but was FAT32 prior to Windows 2000.)

I have no new hardware besides an additional 256 MB RAM.

I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

Well, the rule of thumb for swapfile....or pagefile as it's called in NT/2000 is, amount of RAM plus 12 MB's. So if you have 256 MB RAM, your pagefile should be 268 MB's. Personally, I would let windows handle the size and location. I'm betting it was something you did that made the error happen so undo your changes and see if that doesn't cure the problem




On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

Do you have Norton Antivirus 2000 vs6.0 installed?


On Monday, August 20, 2001 at 7:22 am, Curt R wrote:
>

Well, the rule of thumb for swapfile....or pagefile as it's called in NT/2000
>is, amount of RAM plus 12 MB's. So if you have 256 MB RAM, your pagefile should
>be 268 MB's. Personally, I would let windows handle the size and location. I'm
>betting it was something you did that made the error happen so undo your changes
>and see if that doesn't cure the problem


>
>


>On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:
>

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.
>

[Reply or follow-up to this message]

On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

On Wednesday, October 17, 2001 at 3:46 am, Don Schmidt wrote:
>
>
>


>On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:
>

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.
>

[Reply or follow-up to this message]

For me it was Norton Antivirus 6.0 that caused this behavior. Good luck!


On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

I got the same error. I was running everquest when I got it. I also get the error when I run Dark Age of Camelot and Tribes 2. I believe the problem revolves around my video card and upgrading to windows XP. I have a Geforce 2 MX/400 and aparently it doesnt like windows XP. I have tried three of the drivers from the NVIDIA homepage, 2 of the drivers from Visionstek homepage, and the two drivers that Gateway sent to me. I have noticed a trend in tracking down this problem, alot of the people that are having it got there computers from gateway and are upgrading it to a new OS. I have formatted my computer twice and it hasnt helped. I have tested my RAM with a program. I have tried altering the BIOS setting (though it always made things worse so i switched it back to original) I have played with the amount of space set aside for memory and left it up to windows. The blue screens has blamed it on NV4_DISP and WIN32K.SYS AND FASTFAT.SYS. I have also gotten the message : DRIVER_IRQL_NOT_LESS_OR_EQUAL. if anyone has some clues, please write me at travismelvin@hotmail.com and make the title of the letter PC_HELP so i know its not just some virus. Thanks, Travis

[Reply or follow-up to this message]

I just started having this exact problem, as well as getting the "IRQL_NOT_LESS_OR_EQUAL" error. Everything worked fine on my XP system up until now. I did recently install the latest Norton Utilities, which includes the Antivirus software mentioned earlier in this thread. Only problem is, I can't get to my desktop to uninstall the software. The 2 times I managed to actually boot to the desktop, the mouse froze after 5 seconds. Any suggestions??


On Saturday, January 5, 2002 at 6:59 pm, Travis M wrote:
>
>I got the same error. I was running everquest when I got it. I also get the error
>when I run Dark Age of Camelot and Tribes 2.
>
>I believe the problem revolves around my video card and upgrading to windows XP.
> I have a Geforce 2 MX/400 and aparently it doesnt like windows XP.
>
>I have tried three of the drivers from the NVIDIA homepage, 2 of the drivers from
>Visionstek homepage, and the two drivers that Gateway sent to me. I have noticed
>a trend in tracking down this problem, alot of the people that are having it got
>there computers from gateway and are upgrading it to a new OS.
>
>I have formatted my computer twice and it hasnt helped. I have tested my RAM with
>a program. I have tried altering the BIOS setting (though it always made things
>worse so i switched it back to original) I have played with the amount of space
>set aside for memory and left it up to windows.
>
>The blue screens has blamed it on NV4_DISP and WIN32K.SYS AND FASTFAT.SYS.
>
>I have also gotten the message :
>
>DRIVER_IRQL_NOT_LESS_OR_EQUAL.
>
>if anyone has some clues, please write me at travismelvin@hotmail.com and make the
>title of the letter PC_HELP so i know its not just some virus. Thanks,
>
>Travis

[Reply or follow-up to this message]

your memory upgrade? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/bccodes_4qsn.asp


On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

I will go weeks without getting this message and then it happens several times. No changes in hardware, no bad hardware or corrupted NTFS, maybe software but like I said, it does not happen often which makes it difficult to know what is causing it. So far I have been living with rebooting a couple of times when it happens.


On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

Has anyone ever figured this out. I am starting to see this since I added a new hard drive. both the paged and IRQ errors at random.


On Wednesday, January 16, 2002 at 6:44 am, Jim Day wrote:
>I just started having this exact problem, as well as getting the "IRQL_NOT_LESS_OR_EQUAL"
>error. Everything worked fine on my XP system up until now. I did recently install
>the latest Norton Utilities, which includes the Antivirus software mentioned earlier
>in this thread.
>
>Only problem is, I can't get to my desktop to uninstall the software. The 2 times
>I managed to actually boot to the desktop, the mouse froze after 5 seconds.
>
>Any suggestions??
>

[Reply or follow-up to this message]

"I added more ram to my system and I got the same stop message. Gateway tells me the only way to fix it is to reformat and reinstall win2000 after adding the memory. " -How did you eventually correct this? I am having the same problems. I added ram, bios sees it, but when it tries to start w2k the blue screen comes up. Please any help will be appreciated. -Scott


On Wednesday, October 17, 2001 at 3:46 am, Don Schmidt wrote:
>
>

[Reply or follow-up to this message]

I have a DELL Inspiron3800 and recently purchased 256Mb (originally 64Mb). On installation Windows2000 did not want to recognise the additional memory, while the BIOS (A17) said it was there. I have since upgraded from SP2 to Version 5.0 SP3 (Build 2195), the fault has gone away and all the memory works a treat.


On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

I received this error message as well apon installing XP Pro on a new PC clean install, I changed the RAM, Hard Drive, Cables, CPU and everything else that I could and continued to get the error message. After much trail & error I discovered that if your system is overclocked you can & WILL get this message. I re-clocked the system, error message went away and XP installed! Just another thing you might want to check! Tom


On Friday, January 4, 2002 at 12:58 am, D wrote:
>For me it was Norton Antivirus 6.0 that caused this behavior. Good luck!
>

[Reply or follow-up to this message]

Overclocked? I assume you don't mean the time is ste too fast. The clock or CPU speed? Is this in the CMOS? Please explain, and thanks!


On Wednesday, June 25, 2003 at 9:39 am, Tom Scata wrote:
>I received this error message as well apon installing XP Pro on a new PC clean install,
>I changed the RAM, Hard Drive, Cables, CPU and everything else that I could and continued
>to get the error message. After much trail & error I discovered that if your system
>is overclocked you can & WILL get this message. I re-clocked the system, error message
>went away and XP installed!
>
>Just another thing you might want to check!
>
>Tom
>
>

[Reply or follow-up to this message]

I also had the same problem. I would get one of the two error messages half way through window2k and xp setup. I was able to stop this error by changing my bios settings to not overclock my CPU, as mentioned above. Some motherboards overclock the CPU through the CMOS and other do it through a jumper on the mother board. This seems to have solved my problem.


On Tuesday, July 1, 2003 at 3:05 pm, Roger Barker wrote:
>Overclocked? I assume you don't mean the time is ste too fast. The clock or CPU
>speed? Is this in the CMOS? Please explain, and thanks!
>

[Reply or follow-up to this message]

Hi, I am trying to reinstall my windows 2000 on the existing hard drive and I am getting similar message. Now whenever I reboot it comes back asking me to insert the win2 K CD and it starts the process of installing win2K and this error come up. I am not sure how to fix it. You mentioned that you changed the bios not to lock the the CPU. How do you do that. Can you help? Thanks,


On Sunday, August 17, 2003 at 3:07 pm, Dave D. wrote:
>I also had the same problem. I would get one of the two error messages half way
>through window2k and xp setup. I was able to stop this error by changing my bios
>settings to not overclock my CPU, as mentioned above. Some motherboards overclock
>the CPU through the CMOS and other do it through a jumper on the mother board. This
>seems to have solved my problem.
>
>

[Reply or follow-up to this message]

I had the same problem you did/do, but I have a clean install of Windows 2000. The PAGE_FAULT_IN_NONPAGED_AREA system fault would occur every time or nearly every time (can't remember) I started my computer but then a reboot would work fine (seemingly). Very strange. I tried to recall what I had changed as I had a perfectly running system until a few days previous to my analysis of the problem and after searching the internet and reading the suggested possible causes I recalled that I had recently changed the Bloodhound heuristics setting for my Norton Antivirus to high from normal. I changed the setting back to normal and have not had the problem since. If I get a recurrence I will post. I sure do like it when things work as they should. I'm running an Athlon XP 2500+ Barton on an Asus A7N8X with one 512mb stick of Crucial DDR ram, most stable BIOS settings, no overclocking at all, 766 mb swap file on the C: system drive. I haven't been going to church, however, but I am a Democrat (mostly). I haven't seen whether the moon is full, it's been cloudy. Best of luck.


On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

Dear all,

I have been plagued by these 2 IRQL/PAGE_FAULT errors for a while now.  I own a laptop 
computer and so changing hardware is not very feasible.

I generally experience the errors at set points whilst watching DivX encoded films 
in Windows Media Player 9 in fullscreen (generally it would be fine in a window). 
 The fact that the errors occur at the same point in the video (or after a certain 
time period) meant it's been easy to find out if i've fixed the problem I had.

Whilst it is still fresh in my mind, I felt I should post the fix somewhere so maybe 
others could follow what I did and perhaps come to a solution.

My system is an AMD Athlon 1600+ (1.4GHz) notebook with 384mb ram and an S3 Twister 
K video card.

here is what i've done:

1.  Downgraded from XP Pro to Home using image cds from supplier (still crashes with 
same error)
2.  Installed XP SP1
3.  Installed latest video drivers for S3 Twister K
4.  Installed every recommended update from WindowsUpdate (relating to QB articles 
- not things like DX9 etc..)
5.  Installed S3 Twister drivers from VIATech.com website
6.  Installed latest VIATech4-in-1 drivers
7.  I read on the DivX.com website that DivX5.0 is optimized for AMD processors, 
so I disabled post-processing in DivXConfig.

and to think... after all this it was still crashing at the same point of the film.

8.  I checked the bios.  Unfortunately the bios settings are not very advanced compared 
to desktop bios's, however I was able to alter "Shared Video Memory", between 8, 
16 and 32mb.  Current setting was on 16mb.  I changed it to 32mb, and now I am 30 
minutes into the film, fullscreen, and not even so much as a hiccup from the video.

I hope this has indeed fixed the problem for me, and also that it might help other 
sufferers (and doing a Google search tells me there's alot of you!)

Kieran

[Reply or follow-up to this message]

xp can't run when the usb disk is disconnetted. This is the error message that appear in the "blue screen" PAGE_FAULT_IN_NONPAGED_AREA Thanks Crocco


On Tuesday, October 21, 2003 at 9:30 pm, Kieran wrote:

>Dear all,
>
>I have been plagued by these 2 IRQL/PAGE_FAULT errors for a while now.  I own a 
laptop 
>computer and so changing hardware is not very feasible.
>
>I generally experience the errors at set points whilst watching DivX encoded films 
>in Windows Media Player 9 in fullscreen (generally it would be fine in a window). 
> The fact that the errors occur at the same point in the video (or after a certain 
>time period) meant it's been easy to find out if i've fixed the problem I had.
>
>Whilst it is still fresh in my mind, I felt I should post the fix somewhere so maybe 
>others could follow what I did and perhaps come to a solution.
>
>My system is an AMD Athlon 1600+ (1.4GHz) notebook with 384mb ram and an S3 Twister 
>K video card.
>
>here is what i've done:
>
>1.  Downgraded from XP Pro to Home using image cds from supplier (still crashes 
with 
>same error)
>2.  Installed XP SP1
>3.  Installed latest video drivers for S3 Twister K
>4.  Installed every recommended update from WindowsUpdate (relating to QB articles 
>- not things like DX9 etc..)
>5.  Installed S3 Twister drivers from VIATech.com website
>6.  Installed latest VIATech4-in-1 drivers
>7.  I read on the DivX.com website that DivX5.0 is optimized for AMD processors, 
>so I disabled post-processing in DivXConfig.
>
>and to think... after all this it was still crashing at the same point of the film.
>
>8.  I checked the bios.  Unfortunately the bios settings are not very advanced compared 
>to desktop bios's, however I was able to alter "Shared Video Memory", between 8, 
>16 and 32mb.  Current setting was on 16mb.  I changed it to 32mb, and now I am 30 
>minutes into the film, fullscreen, and not even so much as a hiccup from the video.
>
>I hope this has indeed fixed the problem for me, and also that it might help other 
>sufferers (and doing a Google search tells me there's alot of you!)
>
>Kieran

[Reply or follow-up to this message]

I'm getting the same message during the fresh install of xp... What interesting is that i've noticed from all the other posts that we all have a similar computer configuration... I have a AMD XP 2500, nvidia nforce2 mx and corsair 256mb ram. wonder if it's hadware related....


On Monday, August 20, 2001 at 12:08 am, Robert Eklund wrote:

>I recently updated/changed from Windows ME to Windows 2000 Professional.
>Every time I start up the computer, it "almost gets there", then stops, showing
>a blu screen with error message PAGE_FAULT_IN_NONPAGED_AREA, i.e.,
>STOP number 0x00000050, which implies problems with the writing to memory
>(swap file).
>
>I then restart the computer, and it starts up fine. Ergo: I always need to start
>the computer twice, the first time resulting in a blur screen, the second time
>successfully. 
>
>I have set aside a 766 MB swap file on the C: partition (min and max size), although
>I previously had it on the D: partition. I have run chkdsk and service packs, and 
>no
>errors are found whatsoever, but the problems remains. My computer is formatted
>in NTFS (but was FAT32 prior to Windows 2000.)
>
>I have no new hardware besides an additional 256 MB RAM.
>
>I have a few programs installed, but they are all normal, like Acrobat Reader 5.0
>and the like, and they all work fine, and installed OK.

[Reply or follow-up to this message]

About same config & same problems on clean XP install! AMD Athlon 2400, 512 MB ??, ATI Radeon ... Microsoft says it has to do w/ faulty memory on either video, main or cache ... Don't have the means to test this though .. and i'm not in the mood 2 buy new vid, memory AND motherboard :( Any ideas?


On Monday, December 1, 2003 at 11:18 am, Marko wrote:
>I'm getting the same message during the fresh install of xp... What interesting is
>that i've noticed from all the other posts that we all have a similar computer configuration...
>I have a AMD XP 2500, nvidia nforce2 mx and corsair 256mb ram. wonder if it's hadware
>related....
>
>

[Reply or follow-up to this message]

if it lists a display driver uninstall reboot then reinstall, also try getting one of the free memtest utilities available on the net and run it. it will test to see if you have a faulty RAM module. if you get the irq one this is most likely the case as for this page fault error it could be many things.


On Thursday, December 4, 2003 at 2:36 am, Rekamedar wrote:
>About same config & same problems on clean XP install!
>AMD Athlon 2400, 512 MB ??, ATI Radeon ...
>
>Microsoft says it has to do w/ faulty memory on either video, main or cache ... Don't
>have the means to test this though .. and i'm not in the mood 2 buy new vid, memory
>AND motherboard :(
>
>Any ideas?

[Reply or follow-up to this message]

I'm having a VERY similar problem to this. I have an ak77 600n board from Aopen and an athlon xp 2200+ a 512 mb stick of pc 2700 DDR 333 mhz ddr ram. FSB is set at 133 mhz and everything detects correctly during POST. I cannot get XP to install it constantly crashes with the blue screen. I've had IRQL, page_fault_in_nonpaged_area caused by ntfs.sys and another pfn_ error. I was using a geforce2 t200 card with tv out, but i've taken it out and put in an ati rage pro 128 32 mb card..and I still get it. Ive tried disabling USB, Built in NIC, built in Audio, unplugging CD roms ,etc Current hardware on the system is a: 13 gb Fujitsu HD, 56x cdrom and a 3 year old burner. All that hardware was running under xp corp fine prior to my upgrading hte motherboard CPU and ram. The ram has been moved to another pC and tested and another PCs ram put in that machine to see if it works and nada the ram is fine and the known working ram still crashes in the machine I'm trying to set up. I've tried changing everything I can think of in the bios ,etc... I'm at a complete loss. I can't even get the OS to install. I've tried resetting the bios as well. Heat is fine, CPU is running at 37 degrees system at 35


On Thursday, December 18, 2003 at 5:53 am, patrick wrote:
>if it lists a display driver uninstall reboot then reinstall, also try getting one
>of the free memtest utilities available on the net and run it. it will test to see
>if you have a faulty RAM module. if you get the irq one this is most likely the case
>as for this page fault error it could be many things.
>
>

[Reply or follow-up to this message]

hey try testing the HDs. sounds like an HD problem. also set eerything to Serial Presence Detection (SPD) and see if it runs. also try changing some of the BIOS settings since that was my problem. for example some HDs that have SMART capability need it to run correctly and vice versa. the thing about these windows errors is that they can stem from something as small as a little BIOS settings. and make sure your cables are all nice and in correctly. if you are using those old ribbon cables get round cables, they work for all HDs and CD roms even if they are not ATA 100 or above (most round cables support ATA 133) and it will improve airflow.


On Sunday, December 28, 2003 at 7:47 am, Matt C wrote:
>I'm having a VERY similar problem to this. I have an ak77 600n board from Aopen and
>an athlon xp 2200+
>a 512 mb stick of pc 2700 DDR 333 mhz ddr ram. FSB is set at 133 mhz and everything
>detects correctly during POST.
>I cannot get XP to install it constantly crashes with the blue screen. I've had IRQL,
>page_fault_in_nonpaged_area caused by ntfs.sys and another pfn_ error.
>I was using a geforce2 t200 card with tv out, but i've taken it out and put in an
>ati rage pro 128 32 mb card..and I still get it.
>Ive tried disabling USB, Built in NIC, built in Audio, unplugging CD roms ,etc
>Current hardware on the system is a: 13 gb Fujitsu HD, 56x cdrom and a 3 year old
>burner. All that hardware was running under xp corp fine prior to my upgrading hte
>motherboard CPU and ram.
>The ram has been moved to another pC and tested and another PCs ram put in that machine
>to see if it works and nada the ram is fine and the known working ram still crashes
>in the machine I'm trying to set up.
>I've tried changing everything I can think of in the bios ,etc...
>I'm at a complete loss. I can't even get the OS to install.
>I've tried resetting the bios as well.
>Heat is fine, CPU is running at 37 degrees system at 35
>
>
>
>

[Reply or follow-up to this message]

The HD I have is: a fujitsu MPD3130AT 12.9 GB interface is UDMA 66 5400 RPM I'm not sure if that helps. I KNOW The harddrive was just working fine with xp corp installed on it prior ot upgrading the harddrive.so I can't possibly imagine the harddrive dying (considering I didn't evne take it out, just unplugged it and plugged it back in) Is it possible the harddrive is not compatible with this new motherboard?


On Sunday, December 28, 2003 at 11:47 am, patrick wrote:
>hey try testing the HDs. sounds like an HD problem. also set eerything to Serial
>Presence Detection (SPD) and see if it runs. also try changing some of the BIOS settings
>since that was my problem. for example some HDs that have SMART capability need it
>to run correctly and vice versa. the thing about these windows errors is that they
>can stem from something as small as a little BIOS settings. and make sure your cables
>are all nice and in correctly. if you are using those old ribbon cables get round
>cables, they work for all HDs and CD roms even if they are not ATA 100 or above (most
>round cables support ATA 133) and it will improve airflow.
>
>

[Reply or follow-up to this message]

your motherboard is UDMA/ATA 100 and 13 compatible. that may be causing a problem, but not always. the backwards compatability feature may not work with some HDs. that could very well be the problem. also your BIOS may have a setting for this. i know i have to set it to either ATA/100 or lower or 100 and higher. also check for any assign IRQ options. aand what other hardware do you have installed? do you have the HD as the master drive and the jumpers (if any) set to apprpiate selection?


On Sunday, December 28, 2003 at 12:09 pm, Matt C wrote:
>The HD I have is:
>a fujitsu MPD3130AT
>12.9 GB interface is UDMA 66
>5400 RPM
>I'm not sure if that helps. I KNOW The harddrive was just working fine with xp corp
>installed on it prior ot upgrading the harddrive.so I can't possibly imagine the
>harddrive dying (considering I didn't evne take it out, just unplugged it and plugged
>it back in)
>Is it possible the harddrive is not compatible with this new motherboard?
>
>

[Reply or follow-up to this message]

it the master device on the primary IDE cable, the 2 CD drives are on the secondary IDE cable. Its on an 80 wire ribbon cable. I will check the udma accesss i think its set auto I will see if I can set it to 66 The only other hardware is what I listed in my original message 2 messagesa back. I have the option in the bios enabled to auto set irq's if it finds a conflict.


On Sunday, December 28, 2003 at 12:19 pm, patrick wrote:
>your motherboard is UDMA/ATA 100 and 13 compatible. that may be causing a problem,
>but not always. the backwards compatability feature may not work with some HDs. that
>could very well be the problem. also your BIOS may have a setting for this. i know
>i have to set it to either ATA/100 or lower or 100 and higher. also check for any
>assign IRQ options. aand what other hardware do you have installed? do you have the
>HD as the master drive and the jumpers (if any) set to apprpiate selection?
>
>

[Reply or follow-up to this message]

my only option is to enable or disable UDMA the drive... no option of 66 or ata 100 or anything like that. Also my MB is mainly a jumperless mobo I'll check see if there is any settings for the speed.................there does not appear to be. Disabling UDMA makes the drive EXTREMELY slow... if thats the only fix I think I may have to put a new drive in teh machine.


On Sunday, December 28, 2003 at 12:19 pm, patrick wrote:
>your motherboard is UDMA/ATA 100 and 13 compatible. that may be causing a problem,
>but not always. the backwards compatability feature may not work with some HDs. that
>could very well be the problem. also your BIOS may have a setting for this. i know
>i have to set it to either ATA/100 or lower or 100 and higher. also check for any
>assign IRQ options. aand what other hardware do you have installed? do you have the
>HD as the master drive and the jumpers (if any) set to apprpiate selection?
>
>

[Reply or follow-up to this message]

if it has that option then the drive should work fine unless there is a drive problem, the udam on off option is only if you are using an old (i mean OLD about 10 yearsor more) . when you disabled the UDMA drive did it crash? what causes the crash, running the computer in general, whenever you try something that writes to the drive ? any particular application ?


On Sunday, December 28, 2003 at 1:08 pm, Matt C wrote:
>
>my only option is to enable or disable UDMA the drive...
>no option of 66 or ata 100 or anything like that.
>Also my MB is mainly a jumperless mobo I'll check see if there is any settings for
>the speed.................there does not appear to be.
>Disabling UDMA makes the drive EXTREMELY slow...
>if thats the only fix I think I may have to put a new drive in teh machine.
>
>

[Reply or follow-up to this message]

also please check fo updates for your BIOS, before you do it though make sure you read the directions for doing so, because it can be disasterous if your computer fails or something else, but is simple in most cases. also check to see if there is anything on the HD manufacturer site about similiar errors, or more software such as with maxtor drives. also ensure that you have proper power and all that other basic BS.


On Sunday, December 28, 2003 at 1:08 pm, Matt C wrote:
>
>my only option is to enable or disable UDMA the drive...
>no option of 66 or ata 100 or anything like that.
>Also my MB is mainly a jumperless mobo I'll check see if there is any settings for
>the speed.................there does not appear to be.
>Disabling UDMA makes the drive EXTREMELY slow...
>if thats the only fix I think I may have to put a new drive in teh machine.
>
>

[Reply or follow-up to this message]

Well the harddrive worked fine on the old mobo. and I can't be certain that its not working fine right now its just the only thing that makes sense that would cause all the errors I'm getting. and like I said in my previous message I can't even get windows installed. I Formatted the harddrive and it will not install it gets near completion and crashes everytime with one of the errors I listed above. The ram has been tested and is fine. I've swapped video cards and tried disabling everything on the mobo the HD is the only thing left. twice so far the blue screen crash has mentioned ntfs.sys and it seems impossible that would be continually getting corrupted on fresh installs unless there was a problem with the access of hte HD and the mobo.


On Sunday, December 28, 2003 at 1:12 pm, patrick wrote:
>if it has that option then the drive should work fine unless there is a drive problem,
>the udam on off option is only if you are using an old (i mean OLD about 10 yearsor
>more) . when you disabled the UDMA drive did it crash? what causes the crash, running
>the computer in general, whenever you try something that writes to the drive ? any
>particular application ?
>
>

[Reply or follow-up to this message]

Bios is updated one of the first things i've done. As well there is lots of power its a 350w power supply and this system is pretty much bare bones so there is no way its a power issue.


On Sunday, December 28, 2003 at 3:52 pm, patrick wrote:
>
>also please check fo updates for your BIOS, before you do it though make sure you
>read the directions for doing so, because it can be disasterous if your computer
>fails or something else, but is simple in most cases. also check to see if there
>is anything on the HD manufacturer site about similiar errors, or more software such
>as with maxtor drives. also ensure that you have proper power and all that other
>basic BS.
>

[Reply or follow-up to this message]

ok try it with one stick of ram if using 2 or 2 instead of 3. try swapping the mem. if any probs try a new HDD. if no success then it would be mobo. also try a new installation of windows. try formatting fat32 or ntfs which ever you didnt do last time. if non of those work then you may need a new mobo.


On Sunday, December 28, 2003 at 5:18 pm, Matt C wrote:
>Well the harddrive worked fine on the old mobo. and I can't be certain that its not
>working fine right now its just the only thing that makes sense that would cause
>all the errors I'm getting.
>and like I said in my previous message I can't even get windows installed. I Formatted
>the harddrive and it will not install it gets near completion and crashes everytime
>with one of the errors I listed above.
>The ram has been tested and is fine. I've swapped video cards and tried disabling
>everything on the mobo the HD is the only thing left.
>twice so far the blue screen crash has mentioned ntfs.sys and it seems impossible
>that would be continually getting corrupted on fresh installs unless there was a
>problem with the access of hte HD and the mobo.
>
>
>

[Reply or follow-up to this message]

I've got a similar problem also. It happens when I try to run a clean install of 
Win 2k. I've gotten a 0x00000050 Page Fault In Nonpaged Area ntoskrnl.exe STOP screen 
(same one about three times now), an 0x00000026 CDFS File System cdrom.sys error 
(that stopped when I went from two cdrom drives to just one--a read only now, haven't 
got that one again), and 0x0000001E KMODE Exception Not Handled ntoskrnl.exe STOP 
screen, not exactly in that order, but close enough. I've researched the error numbers 
on Microsoft and found nothing usefull.

I'm on my second mother board. The last one was an ECS, and I attributed the problem 
to crappy hardware. However, the latest board is a DFI, and I can't see how it could 
be the board again. My memory is brand new, also. Barely been 14 days since I purchased 
it. The hard drive is one from my previous system, a Maxtor 7200rpm 30gb. It worked 
fine under my previous system, however now Win2k won't install what with the STOP 
screens interrupting the installation.

My new board has an nVidia chipset, the processor is an AMD Athlon 2500+, the memory 
is Centon pc2700 512mb, and my video card is a Geforce FX 5200 128mb PCI card with 
GPU (last computer didn't have an AGP slot, the card is new, only a few weeks old). 
I see a hardware connection with some of us, however who knows what is to blame. 
I'm going to give the previous "no overclocking on CPU" idea a try, see if that works 
for me. I doubt it will, however anything is worth a shot.

I'm at my wit's end. I've tried everything I can think of, all to no avail. It'll 
be my luck I'll go out and buy a new hard drive and STILL have the same problem. 
lol

If I solve it on my end, I'll post an update. If anyone has any ideas, please don't 
hesitate to jump in.


Anthony

[Reply or follow-up to this message]

Somethings you might try: It looks like you isolated the problem to something other than the motherboard - So lets start there: Fdisk and Format from DOS*** Copy the install files to newly created subdir on Drive*** Remove all unnecessary peripherals: Sound Card Network Card USB floppy driver extra drives CDrom's CDRW's Extra Memory Modems.... Leave only the bare necessities.*** Check your BIOS and set to FailSafe Settings if available. Otherwise configure and disable all the bells and whistles.**** Try the install: Good to go then some peripheral*** No good: Use different media ( W2K install media may be bad)*** No good: Use different memory stick*** No good: Check the powersupply*** Good luck


On Thursday, March 18, 2004 at 1:59 am, Anthony wrote:
>I've got a similar problem also. It happens when I try to run a clean install of
>Win 2k. I've gotten a 0x00000050 Page Fault In Nonpaged Area ntoskrnl.exe STOP screen
>(same one about three times now), an 0x00000026 CDFS File System cdrom.sys error
>(that stopped when I went from two cdrom drives to just one--a read only now, haven't
>got that one again), and 0x0000001E KMODE Exception Not Handled ntoskrnl.exe STOP
>screen, not exactly in that order, but close enough. I've researched the error numbers
>on Microsoft and found nothing usefull.
>
>I'm on my second mother board. The last one was an ECS, and I attributed the problem
>to crappy hardware. However, the latest board is a DFI, and I can't see how it could
>be the board again. My memory is brand new, also. Barely been 14 days since I purchased
>it. The hard drive is one from my previous system, a Maxtor 7200rpm 30gb. It worked
>fine under my previous system, however now Win2k won't install what with the STOP
>screens interrupting the installation.
>
>My new board has an nVidia chipset, the processor is an AMD Athlon 2500+, the memory
>is Centon pc2700 512mb, and my video card is a Geforce FX 5200 128mb PCI card with
>GPU (last computer didn't have an AGP slot, the card is new, only a few weeks old).
>I see a hardware connection with some of us, however who knows what is to blame.
>I'm going to give the previous "no overclocking on CPU" idea a try, see if that works
>for me. I doubt it will, however anything is worth a shot.
>
>I'm at my wit's end. I've tried everything I can think of, all to no avail. It'll
>be my luck I'll go out and buy a new hard drive and STILL have the same problem.
>lol
>
>If I solve it on my end, I'll post an update. If anyone has any ideas, please don't
>hesitate to jump in.
>
>
>Anthony

[Reply or follow-up to this message]

My case of this problem has been solved. Between myself and two others, we narrowed 
it down to either video or memory. I replaced both, and everything is happy. I suspected 
the memory was the problem, however it could have been the ram integrated into the 
video card. Who knows, I was running out of time to do trial and error, so I replaced 
both items and the problem is now solved.

After replacing the video and memory, I got a video card with a defective chipset 
(does it never end? lol). I took that back with no problems and got another one. 
So far, it works, so no complaints here. lol

Thanks for the suggestions.


Anthony

[Reply or follow-up to this message]

The problem is on hardware compatibility in this case according to my experience problem was in compatibility between motherboard and RAM memory. DDR400 memory is now the formal standard. Now that the Jedec committee has made its decision, RAM and motherboard makers finally have some guidelines on integration. DDR400, a.k.a. PC3200 RAM, had been plagued by incompatibility issues and an embarrassing lack of performance improvements. Without any official standard at all, trying to find a perfect match between RAM and the motherboard had been like playing poker blindfolded. Solution: change the RAM memory to a new one, for example if you have Asus P4V533, RAM memory must be 533 Hz thats all., or play with bios, adjust ram speed, END.

[Reply or follow-up to this message]

doOD!!! i cant believe this! im running almost the exact same specs as you... Windows XP Corp. Biostar M7NCD w/NForce 2 chipset Athlon XP 2600+ 768 MB DDR2700 (the 512mb chip is CENTON!!!) GeForce 4 MX440 ...and i keep getting those damn stop errors!!! i cant run any programs (other than IE6) for any useful amount of time before i get another error. it's driving me crazy, i've formatted, re-installed, updated, and i'm about to put my foot right thru my piece of crap computer! lol, not really, 'cause i cant afford to buy another... if anybody can help please do!


On Tuesday, July 13, 2004 at 1:15 pm, router0 wrote:
>
>The problem is on hardware compatibility in this case according to my experience
>problem was in compatibility between motherboard and RAM memory.
> DDR400 memory is now the formal standard. Now that the Jedec committee has made
>its decision, RAM and motherboard makers finally have some guidelines on integration.
>DDR400, a.k.a. PC3200 RAM, had been plagued by incompatibility issues and an embarrassing
>lack of performance improvements. Without any official standard at all, trying to
>find a perfect match between RAM and the motherboard had been like playing poker
>blindfolded.
>Solution: change the RAM memory to a new one, for example if you have Asus P4V533,
> RAM memory must be 533 Hz thats all., or play with bios, adjust ram speed, END.

[Reply or follow-up to this message]

It was so IRRITATING fixing this problem when I had it! It's most likely a memory 
problem (it was with me). Try running off of one card of memory at a time, instead 
of the combination you have going on there. If you keep getting the Fault screens, 
try swapping to a new card of memory. It could possibly be the memory integrated 
into your video card, however I doubt that. 

Follow the route of the memory. It may solve your prob. Post back here when you get 
the chance, let us know if it worked or not.


Anthony







On Saturday, September 4, 2004 at 8:36 pm, StEALth_[KTS] wrote:

>doOD!!!  i cant believe this! im running almost the exact same specs as you...

>

>Windows XP Corp.

>Biostar M7NCD w/NForce 2 chipset

>Athlon XP 2600+

>768 MB DDR2700 (the 512mb chip is CENTON!!!)

>GeForce 4 MX440

>

>...and i keep getting those damn stop errors!!!

>i cant run any programs (other than IE6) for any useful amount of time before i 
get 

>another error.

>it's driving me crazy, i've formatted, re-installed, updated, and i'm about to put 

>my foot right thru my piece of crap computer! lol, not really, 'cause i cant afford 

>to buy another...

>

>if anybody can help please do!

>

> 

[Reply or follow-up to this message]

ok, thanks Anthony! i did run windiag(approx. same as memtest86) overnight and it came up with 27 errors out of 54 complete passes...all errors were on the WMATS test. because all the errors happened so late into the testing, i just assumed it was with the ram in slot1, luckily my 512mb was in slot0! since removing the 256mb stick, i have had no errors and im already on day 2, so i believe that was the problem. thanks to you anthony!!!


On Tuesday, September 7, 2004 at 5:35 pm, Anthony wrote:
>It was so IRRITATING fixing this problem when I had it! It's most likely a memory
>problem (it was with me). Try running off of one card of memory at a time, instead
>of the combination you have going on there. If you keep getting the Fault screens,
>try swapping to a new card of memory. It could possibly be the memory integrated
>into your video card, however I doubt that.
>
>Follow the route of the memory. It may solve your prob. Post back here when you get
>the chance, let us know if it worked or not.
>
>
>Anthony
>
>
>

[Reply or follow-up to this message]

I'm glad you got it sorted out. Hope you don't have anymore probs.


Anthony







On Tuesday, September 7, 2004 at 10:10 pm, StEALth_[KTS] wrote:

>ok, thanks Anthony!

>

>i did run windiag(approx. same as memtest86) overnight and it came up with 27 errors 

>out of 54 complete passes...all errors were on the WMATS test.

>because all the errors happened so late into the testing, i just assumed it was 
with 

>the ram in slot1, luckily my 512mb was in slot0!

>

>since removing the 256mb stick, i have had no errors and im already on day 2, so 

>i believe that was the problem.

>

>thanks to you anthony!!!

>

>

> 

[Reply or follow-up to this message]

I have change the motherboard,Ram ,hard disk & reloaded windows but still heve the same messeage appear.

[Reply or follow-up to this message]

What hardware have you kept and not changed? Could you provide the system specs for 
the machine encountering the Stop screens? Write down the error number(s) you're 
getting and post them here with your system specs. If not I, surely someone may be 
able to find some info on those spacific error numbers.

I'm probably getting a bit ahead of myself, seeing as how I don't know more about 
the problem you are having, but here goes: The problem I was having was associated 
with either a bad card of ram (it happens with brand new memory, I've gotten a bad 
one before) or the ram on the video card. (I believe it was the former of the two, 
in my case)

When you're troubleshooting hardware, strip everything on the motherboard down to 
the bare essentials: memory, video, hard drive, CD-ROM drive, keyboard, mouse. If 
you have two cards of memory, try using one at a time--swap one out, try it, then 
try the other. Try using a backup video card if you have one. If you have more than 
one CD drive, try using one at a time.

Hope the above helps. In the meantime, good luck!


Anthony







On Tuesday, February 7, 2006 at 6:36 pm, Erollnamu wrote:

>I have change the motherboard,Ram ,hard disk & reloaded windows but still heve the 

>same messeage appear. 

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum