Project Reality Forums

PAGE_FAULT_IN_NONPAGED_AREA


That BSOD message occurs sometimes when I'm loading a map.

Windows 7 Home Premium 64 Bit
AMD Athlon 64 X2 6400+
nVidia GeForce 9600 GT OC
4 GB DDR2 Dual-Channel RAM at ~400 MHz
Creative Fata1ity Sound Card

When is the last tine you ran an error check on your HD?

not since I upgraded to Win 7. I'll do that now

I have this problem too. W7 64 bit 8gb ram. From a clean install, I get BSOD with a page fault in non paged error at random times when playing PR. Ive tried

DEP
UAC
Running as Admin
Updating PB
Using XP compat mode
Checking HD
Checking RAM
Using latest drivers

I have a GTX275 card, an intel core 2 chip, and a XF1 fatality gamer card.

Other than this game, everything else (all other games and apps) run fine and smooth. Its just this game.

Any help would be appreciated.

Found this with Google:
Error Message:

PAGE_FAULT_IN_NONPAGED_AREA

Explanation:

This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware(check your RAM), a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.

User Action:

This Stop message usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, either main memory, L2 RAM cache, or video RAM). If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owners manual for your computer. Another cause of this Stop message is the installation of a buggy system service. Disable the service and determine if this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time. Antivirus software can also trigger this Stop message. Disable the program and determine if this resolves the error. If it does, contact the manufacturer of the program about a possible update. A corrupted NTFS volume can also generate this Stop message. Run Chkdsk /f /r to detect and repair disk errors. Restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk. Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver causing the error. Disabling memory caching of the BIOS might also resolve it. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at Microsoft Support.

Good luck

Same here. Vista 64bit and win7 ultimate 64bit , 6 GB Ram , i920 , Xfire , HD4870 (512MB)
Same on both OS and different HDs. After some rounds and only when a new map starts.

I also have BSOD on map loading, ~ 1 from 50 is BSOD. BSOD is only in PR, only when a map loads. It is caused by Creative sound driver, but the problem is only in PR. My card is x-fi Titanium Fatal1ty.

Audio.con

I am getting pretty convinced this error is tied to a crappy driver for my Creative Fata1ity Sound Card in Win7 64.

I ran Memtest and Windows Memtest each all night and found no RAM errors.

When I downloaded another XFI driver (called XFI Sound Pack compiled on 05/15/2009 by Daniel Kawakami) and installed them insted over the Creative driver, it seems to have fixed it for me (fingers crossed). No BSODs in this game any more.

Before I found this driver, I was going to turn my sounds down from Ultra to High then Software mode to point more towards a sound card issue.

For those who have Win7 and an XFI card with frequent BSODs in PR, give this a try and report back here.

Well...bummer...got another BSOD even with this alternate driver.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: FFFFFFFF97140000
BCP2: 0000000000000000
BCP3: FFFFF80002AA8E60
BCP4: 0000000000000005
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

I think I will try to step down the sound quality from XFI to HIGH then LOW etc. to see if that fixes it.

Yeah it's the stupid X-Fi. Creative doesn't know how to write proper drivers. What is amazing is that they actually reference 0x0000000000000000, which you should never do.

I have the same problem...if you look in the event log it will show that it's a "ctoss2k.sys" related error. That's the X-Fi's driver.

These BSOD's will happen in pretty much an EAX game that utilizes the X-Fi, like LOTRO, BF2, 2142, etc.

Also, I recommend that if you want to get rid of the X-Fi BSOD, you go to Hardware and High; that should sound better than X-Fi at Low, if I'm not mistaken.

Snares wrote:Yeah it's the stupid X-Fi. Creative doesn't know how to write proper drivers.

Not only that ... they slap legal injunctions on people who fix them ... when they try to give them to the public, assuming it is in everyones best interest.

Apparently Creative feel that working drivers do not serve their best interests when they are written by a 3rd party.

We first found the bear back in 0.5. It was there, lurking, waiting, just daring anyone to go near. Lying in wait for those unlucky passers by who strayed too close to it's lair. We sent teams to trap it, to remove it from the mod. But they were never seen again. We lost many good developers and testers to that bear.

I also have a Creative Fata1ity card, but my BSOD problem is solved. A simple chkdsk solved it.

I have exactly the same problem here on Win Vista 64bit Business with the Creative X-FI Titanium Fatal1ty.
It's nearly everytime loading a map after playing one or two rounds.

Yesterday I tried it with the driver pack from daniel kawakami (reminds me dr. kawashima )...
Didn't work :/

So, what now?

I can't imagine that a chkdsk will solve the problem.

That's what i did and never had a problem since, give it a try, you never know.

So I tried chkdsk and it didn't help.

I found out that other people have the same problem in some other games like LOTR.

There is a reported issue on the creative site: here

(Created at 12/9/2008 8:48 AM)

And they still don't have a solution?! I really start to dislike creative very much...

What I tried now is the "Software" setting in audio options of PR instead of "X-FI" and played now one round and the next map was loaded succesfully without BSOD. I hope it stays so.

IceCube wrote:So I tried chkdsk and it didn't help.

I found out that other people have the same problem in some other games like LOTR.

There is a reported issue on the creative site: here

(Created at 12/9/2008 8:48 AM)

And they still don't have a solution?! I really start to dislike creative very much...

What I tried now is the "Software" setting in audio options of PR instead of "X-FI" and played now one round and the next map was loaded succesfully without BSOD. I hope it stays so.

Yes, I was also getting BSOD or crashes when loading maps with ctoss2k.sys as being the reason. Happens in both PR and FH2.

By setting sound from X-Fi - Ultra High to Hardware - High I was able to stop the BSODs, however I noticed I have no 3D Surround sound anymore! It only gives surround on X-Fi, how stupid is that? Any other possible fixes that don't make you lose Surround?

Fighter wrote:PAGE_FAULT_IN_NONPAGED_AREA

Driver issue with 99.999% probability. I'd say on sound card side.

I'm having the same issue with Win 7 and X-Fi, having run a memtest I was about to buy a new HDD til I saw this thread! I have sent a support message to creative regarding this issue. I'm not sure they'll be able to help but it's worth a shot. I'll post up their response when I recieve it.

I was able to enable 3D surround sound even on Hardware mode by using ALchemy and adding & activating Battlefield 2 on it.

So no more BSODs since it's not X-Fi mode but still have 3D surround sound on Hardware mode. However the sounds are glitchy... Tried Buffers to 4 and Duration 24 and last tried Buffers 5 and Duration 10, but still get glitched sounds...

Going to test a few more settings. If anyone has found a good combo do tell.

EDIT:

Tested LOADS of Buffers/Duration combos and the best I could find was 6/14, but EVEN STILL it GLITCHES sometimes damn! Even with number of voices lowered from 128 to 64.


I'm not sure which to choose now:

1. Ultra high quality surround sound with occasional BSODs

2. High quality stereo sound

3. Glitchy surround sound


I think I'll stick with BSODing :smileyindifferent:, unless Creative does something about this! I think I'll try messing with the ctoss2k.sys file on system32/drivers.

Would be great if they fixed this X-Fi BSOD issue though... I also get it on Windows Vista 64 bit SP2.

Hey guys

I have the same problem but i am using an Auzentech Xfi Forte 7.1.

Their is a fix that may work but it didn't work for me.

It is definitaly to do with the creative hardware and running it on ultra high, you can run it on high or do the fix in this link,

WIN 7 Ult 64 + XFI + Battlefield 2 = BSOD - Creative Labs

hope it works for you, does anyone else know another fix?

cheers Alex