• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Stop ERROR Non pagefault

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

JASPER24

Registered
Joined
Jul 9, 2004
Can I get some advise?

I have been getting the BSOD for 2 months- and I can figure it out.

480w PSU
abit nf7-s 2.0
xp2500+ mobile
2(512 OCZ 3200 - which has been replaced and I get the same error)

BSOD is PAGE_FAULT_IN_NON_PAGED_AREA
Stop 0X00000050

0XFFFF00F8,0X00000000,0X8053434E,0X000000

I get this error running at all FSB speeds from stock to 220fsbx11

I can run prime 95 for 8-36 hours before the BSOD--- Memtest 86+ shows NO errors


I'm just lost-- any insight?

Jp
 

repo man11

Member
Joined
Dec 28, 2001
Jlin is on the right track. Boosting the CPU's core voltage has been effective at eliminating those errors for me. Make sure you have good enough cooling though.
 
OP
J

JASPER24

Registered
Joined
Jul 9, 2004
Thats weird-- I have also ran this at 1.775 and ran into the same problems
 
OP
J

JASPER24

Registered
Joined
Jul 9, 2004
I have thermatake silent boost heatsink fan---- What would you recomend that is better at cooling--- noise it not an issue to me.
 

repo man11

Member
Joined
Dec 28, 2001
Your present HSF is probably fine. I just meant for you to be aware that raising Vcore will raise your CPU's temperature.

When you ran it at 1.775, was that at default speed? An overclock generally requires at least some increase in Vcore, and it sounds as though your combination might require it at default speed for some reason.

I would recommend running it at default speed until you are sure you have elminated this error.

I'm running my 2500M at 1.85 @ 2.4 GHz. I had it set to 1.825 for a long time, but then I started getting the page fault error while running Lock On Modern Air Combat. Bumping it to 1.85 elminated the error in my case.
 
OP
J

JASPER24

Registered
Joined
Jul 9, 2004
I will give it a try
I have never went over 1.775 yet-- I'll see what happens
 
OP
J

JASPER24

Registered
Joined
Jul 9, 2004
Darn it!

I still get the same error---- How can I find out what is causing that error. I have searched everywhere but I can't find anyone that has had same error code that I'm getting


Jp
 

John G

Member
Joined
May 31, 2004
You could try overkilling on going with easy settings to try to see if anything helps. For example, if you set real easy timings and fairly low FSB to see if making things easy on the memory helps. Or, try running your CPU below 2gig and see if anything gets better then. If you haven't already. Might at least help you pinpoint a problem or know if it's even fixable in that way.

John G
 

repo man11

Member
Joined
Dec 28, 2001
Have you read the MS article, and has it helped you narrow it down at all?
As they mention, it can be a hardware, or software problem. We've been focusing on hardware (for me, that was the case), but it is beginning to seem as though it may be more likely a software problem, possibly drivers.

Can you remember changing anything before this happened the first time?
 
OP
J

JASPER24

Registered
Joined
Jul 9, 2004
This is a newely built system--- so everything has been changed---

Wacom graphics tablet
joystick
scanner
printer
(all drivers reinstalled)


all new parts hd,video card,memory

so you can see where I have no idea where to start looking
 
OP
J

JASPER24

Registered
Joined
Jul 9, 2004
OMG-- I just changed the voltage to my video card-- 9200se from 1.6 to 1.5v and it has ran for 3 days without the BSOD--- I have no idea-- I feel so dumb I hope it continues to work
 
OP
J

JASPER24

Registered
Joined
Jul 9, 2004
Scratch that after running prime95 for app 36 hours and sitting idle for 12 hours it just gave me the same BSOD back to tweaking

darn it
 
OP
J

JASPER24

Registered
Joined
Jul 9, 2004
does this mean anything to anyone?

this is the last entry in my event viewer under the applications tab-- this had to be right before the BSOD

Event Type: Information
Event Source: Ci
Event Category: CI Service
Event ID: 4138
Date: 7/16/2004
Time: 6:39:15 AM
User: N/A
Computer: JPSCOMPUTER
Description:
Content index corruption detected in component CI-RcovStorageObj1 in catalog c:\system volume information\catalog.wci. Stack trace is 0x5DCE96F3
0x5DCF30B3
0x5DCEA967
0x5DD302D7
0x5DD303E8
0x5DD27EEF
0x5DD28B00
0x5DD28EE8
0x77E7D33B
.