page_fault_in_nonpaged_area

Yep...
Everything up-to-date...

"Gerry" wrote:

Albert

Have you been here for updated drivers?
http://www.asus.com/products4.aspx?l...&modelm enu=1

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Albert wrote:
Hi Gerry.
You are not gonna believe this!
I just got another BSOD, but this time its
DRIVER_IRQL_NOT_LESS_OR_EQUAL
The two "wierd" things I did this morning were
1. Update NVidia drivers
2. ChkDsk
Going nuts here!!!
To answer your previous post, My Windows XP is up-to-date 100%, and
I'm running an updated version of AVG anti virus.
I also have my Terminal Services set to Manual.

My win32k version is 5.1.2600.3099

I'm now gonna try Kelly's trick.

Thanks again,
Albert C.


"Gerry" wrote:

Albert

There is a noticeable similarity with this Windows 2000 error but I
cannot find a corresponding Windows XP Knowledge Base Article.
"Stop 0x50 in Win32k.sys" Error Message
http://support.microsoft.com/kb/281132

What is your your StartUp type for Terminal Services. Start, Control
Panel, Administrative Tools, Services. Mine is set to Manual. Have
you installed the Windows XP SP2 update and all subsequent updates?

What version of win32k.sys is located in your System 32 folder? Right
click on the file selecting Properties, Version?

I have found this post by Kelly dated 21 February 2004, which is
worth trying.
http://www.pcreview.co.uk/forums/thread-94921.php

Kelly is a very smart lady.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Albert wrote:
Hello Gerry.
I already disabled auto-restart. I have a Photo of the BSOD I got.
What should I do with it? What part specifically are you interested
in? Here are the parts I think are interesting...
PAGE_FAULT_IN_NONPAGED_AREA
caused by: win32k.sys
Technical Info:
Stop: 0x00000050 (0xFFE68108, 0x00000000, 0xBF8263F2,0x00000000)
WIN32K.SYS - Address BF8263F2 base at BF800000, DateStamp 45f013f6

Thanks again,
Albert C

"Gerry" wrote:

Albert

http://msdn2.microsoft.com/en-us/library/ms793437.aspx

Your reference to win32k.sys could be important.

Can you please post a copy of the Stop Error Report.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click on
the My Computer icon on the Desktop and select Properties,
Advanced, Start-Up and Recovery, System Failure and uncheck box
before Automatically Restart.

Do not re-enable automatic restart on system failure even after you
have solved the problem as it's better disabled. Check for variants
of the Stop Error message.

An alternative is to keep pressing the F8 key during Start-Up and
select option - Disable automatic restart on system failure.

If you are using a wireless keyboard and the F8 key does not work
substitute a wired keyboard and mouse for this exercise only.

You should test your RAM memory
http://www.memtest.org/

http://www.elephantboycomputers.com/...ardware_Tshoot


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Albert wrote:
Hello
Ok, I found 2 successive errors, 30 seconds appart from each
other. Here they go respectively. Sorry they are in Spanish, but
I think you'll understand the important stuff.

ERROR 1
-------
Aplicación con errores: iexplore.exe, versión: 7.0.6000.16512,
módulo con error: jscript.dll, versión 5.7.0.5730, dirección de
error 0x00022c32.

Para obtener más información, vea el Centro de ayuda y soporte
técnico en http://go.microsoft.com/fwlink/events.asp.
-------
ERROR 2 (This one actually produced the Crash & BSOD)
-------
Depósito 520983814 incorrecto.

Para obtener más información, vea el Centro de ayuda y soporte
técnico en http://go.microsoft.com/fwlink/events.asp.
-------
Since it says something aboutn Iexplore, this is the Internet
Explorer Version I am using:
7.0.5730.11

I thank you in advance,
Albert C.

"Gerry" wrote:

Albert

Please post a copy of the relevant Error Report in Event Viewer.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer. When researching the
meaning of the error, information regarding Event ID, Source and
Description are important.

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/kb/308427/en-us

Part of the Description of the error will include a link, which
you should double click for further information. You can copy
using copy and paste. Often the link will, however, say there is
no further information.
http://go.microsoft.com/fw.link/events.asp
(Please note the hyperlink above is for illustration purposes
only)

A tip for posting copies of Error Reports! Run Event Viewer and
double click on the error you want to copy. In the window, which
appears is a button resembling two pages. Click the button and
close Event Viewer.Now start your message (email) and do a paste
into the body of the message. Make sure this is the first paste
after exiting from Event Viewer.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


Albert wrote:
Hello!!!
I'm having the same problem.
It's been going on since I bought my machine.
I recently changed the power supply for a brand new Thermaltake
TR2-550W, and I changed my RAM for a brand new one too!
Did not solve the problem...
I use a little application called AIDA32 to monitor my system's
temperatures. All readings are around 48°C, which I suspect is
quite acceptable?
These are my system specs:

ASUS P5NSLI MoBo
1 X Intel Core 2 CPU 6300 @ 1.86GHz
1 X 1 GB SuperTalent RAM
2 X NVIDIA GeForce 7300 GT (I have 3 Monitors)
1 X Maxtor 80 GB SATA

I recently ran ChkDsk, and that didn't solve the issue either.
What step should I take next?
I thank you in advance,
Albert C...

Hi Albert,

Did you ever manage to fix your BSOD problems? It sounds like I'm having a
similar problem and wouuld be interested to know what you did.



"Albert" wrote:

Forgot to mention:
When I get the BSOD, it says something about win32k.sys
Thanks again.

Hi Sam.
Yes, as a matter of fact I solved it completely.
Turns out that the guy who sold me my SUPER EXPENSIVE computer decided to
save himself 5$ on a side fan, so the RAM was overheating. I installed an
extra fan and I haven't crashed once since then.
Hope this solves your problem as well.
Best regards,
Albert C.

"samthehands" wrote:

Hi Albert,

Did you ever manage to fix your BSOD problems? It sounds like I'm having a
similar problem and wouuld be interested to know what you did.



"Albert" wrote:

Forgot to mention:
When I get the BSOD, it says something about win32k.sys
Thanks again.

That's an interesting outcome Albert.


--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Albert wrote:
Hi Sam.
Yes, as a matter of fact I solved it completely.
Turns out that the guy who sold me my SUPER EXPENSIVE computer
decided to save himself 5$ on a side fan, so the RAM was overheating.
I installed an extra fan and I haven't crashed once since then.
Hope this solves your problem as well.
Best regards,
Albert C.

"samthehands" wrote:

Hi Albert,

Did you ever manage to fix your BSOD problems? It sounds like I'm
having a similar problem and wouuld be interested to know what you
did.



"Albert" wrote:

Forgot to mention:
When I get the BSOD, it says something about win32k.sys
Thanks again.

Yes, sorry I didn't mention it earlier, cause you were very nice to take the
time to try to help me.
I think the conclusion is that when the BSODs are frequent but different
each time, overheating is a good guess.
Belated thanks for your help,
Albert

"Gerry" wrote:

That's an interesting outcome Albert.


--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Albert wrote:
Hi Sam.
Yes, as a matter of fact I solved it completely.
Turns out that the guy who sold me my SUPER EXPENSIVE computer
decided to save himself 5$ on a side fan, so the RAM was overheating.
I installed an extra fan and I haven't crashed once since then.
Hope this solves your problem as well.
Best regards,
Albert C.

"samthehands" wrote:

Hi Albert,

Did you ever manage to fix your BSOD problems? It sounds like I'm
having a similar problem and wouuld be interested to know what you
did.



"Albert" wrote:

Forgot to mention:
When I get the BSOD, it says something about win32k.sys
Thanks again.