Blue Screen ?!?

agloth · 19th December 2002, 10:05

Hi,
when i double click a wsz skin file blue screen appears... (windowsXP)
here is the error message :

PAGE_FAULT_IN_NONPAGED_AREA
win32k.sys

Stop : 0x00000050
Adress BF842618 Base at BF800000
DateStamp 3b7dE698

Atmo · 19th December 2002, 10:16

Can be caused by faulty ram, L2 cache, or video ram, but it's probably a driver problem.

If you've changed any drivers or low level software (anti virus etc) try rolling back to previous versions and see if the problem persists.

You dont have any of your hardware overclocked do you?

agloth · 20th December 2002, 11:29

yes; i have a little change from 550 to 600 mhz and i ve changed the latency times from 3 to 2. but i thought these are very little changes...

Atmo · 20th December 2002, 16:04

Set it back to default and see if it still occurs.

Page faults are a side effect of having your ram running too fast.

Setting the cas latency to 2 instead of 3 is basically making it run 50% faster than it was intended to.

Im guessing you have a P3 right? Since they're multiplier locked, you're probably overclocking via the fsb, so the ram will be running faster than intended, that plus the lower latency is a recipe for crashes unless you have ram that can handle it.

Running your CPU 50mhz faster than stock shouldnt be a problem at all, so if the blue screens dissapear with stock settings, go out and buy some quality (kingmax or corsair) pc133 or pc150 sdram and it should run fine overclocked.

19th December 2002, 10:05	#1
agloth Junior Member Join Date: Dec 2002 Posts: 2	Blue Screen ?!? Hi, when i double click a wsz skin file blue screen appears... (windowsXP) here is the error message : PAGE_FAULT_IN_NONPAGED_AREA win32k.sys Stop : 0x00000050 Adress BF842618 Base at BF800000 DateStamp 3b7dE698

19th December 2002, 10:16	#2
Atmo The Freak (Forum King) Join Date: Feb 2002 Location: Australia Posts: 9,399	Can be caused by faulty ram, L2 cache, or video ram, but it's probably a driver problem. If you've changed any drivers or low level software (anti virus etc) try rolling back to previous versions and see if the problem persists. You dont have any of your hardware overclocked do you? :Psykotech:

20th December 2002, 16:04	#4
Atmo The Freak (Forum King) Join Date: Feb 2002 Location: Australia Posts: 9,399	Set it back to default and see if it still occurs. Page faults are a side effect of having your ram running too fast. Setting the cas latency to 2 instead of 3 is basically making it run 50% faster than it was intended to. Im guessing you have a P3 right? Since they're multiplier locked, you're probably overclocking via the fsb, so the ram will be running faster than intended, that plus the lower latency is a recipe for crashes unless you have ram that can handle it. Running your CPU 50mhz faster than stock shouldnt be a problem at all, so if the blue screens dissapear with stock settings, go out and buy some quality (kingmax or corsair) pc133 or pc150 sdram and it should run fine overclocked. :Psykotech:

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

20th December 2002, 11:29	#3
agloth Junior Member Join Date: Dec 2002 Posts: 2	yes; i have a little change from 550 to 600 mhz and i ve changed the latency times from 3 to 2. but i thought these are very little changes...