re: BSOD, win32k.sys
Friday, June 25, 2004 at 7:20 am
Windows XP Annoyances Discussion Forum
Posted by Sabyre
(1 messages posted)
Win32k.sys, Nv4_disp.dll
Page_Fault_In_Nonpaged_Area
Stop 0x00000050
Wow I see a lot of input on this issue. The thing is you are all right in your own
respects.
Most often it is Windows XP that makes this problem come to light. If you cant contribute
this problem to an overheating video card, which is usually not the problem, a cooler
video card runs more stable.
This BSOD is caused by a data moving issue between apreture, RAM, and VidRAM. Asynch,
Synch. It is a problem of tolerance. This data is driven by the way your OS utilizes
your video driver within the constraints of your mainboard. Phew, thats a big pill
to swallow.
With so many variables and important ones at that it could be most anything that
is causing the crash. Anything from drivers to hardware. Here is how I would go about
resolving this issue for a client.
1. Check the drivers. Make sure they are up to date. Video, Mainboard (Chipset),
NIC, Sound.
2. Check the BIOS. If you are overclocking DONT. "Turn down" your settings. Turn
off caching, shadowing, fast writes, latency, apreture, agpx, and anything that you
consider as a performance enhancement.
3. Check IRQ's. If you are still getting the error, make sure the IRQ's for your
video card is dedicated.
4. Consider your RAM. I hate to get to the point when you have to consider the hardware
that is used because you can usually correct hardware with software, but. If you
have only one stick consider lowering the operating speed or changing it with a premium
brand. When ever possible dont use ECC RAM. Count the chips, if there are an odd
number that is ECC. If you have multiple sticks make sure that they are of the same
brand specs and contact material. If not remove all but one and test it.
5. Mainboard. Check the manual to make sure that the devices you have installed are
compatible. Check jumpers. Reseat the CPU (properly). Reseat the RAM, and Video.
6. Keep it simple. Try the program thats causing the problems with the simplest of
setups ... Only what you need for hardware, disable all else. That way you can tell
if its another piece hardware causing the issue.
7. If all else fails consider a diiferent OS. This problem is more common with XP
than any other version of Windows. Consider Windows 2000 Pro.
8. If you have come to this point the only thing left to do is change your hardware.
You can try a different video card or a different card maker. Personaly I recommend
MSI for all your devices. Rock solid products. More than likely (especially you Dell
folks) its your Mainboard causing the issues.
Remember take your time do things right and never loose your patience. It is very
frustrating for things not to work right.
If you have any questions you can email me:
acsmaine@hotmail.com or visit our website:
www.acsmaine.com
Thanks,
Sabyre
On Wednesday, June 16, 2004 at 5:26 pm, Axl Myk wrote:
>I seem to be having some luck with this problem..
>It started when I upgraded to 1gig DDR400 (2x512)..
>Usually it was the win32k.sys error that everyone is getting, but a few times, nview
>was doing it.. I was running ver 56.72 but I back-leveled to 56.64 AFTER un-installing
>56.72, deleting the nvidia directory, re-booting, running "Registry Mechanic" to
>clean the registry out, re-booting, then installing 56.64 ..
>So far, the machine has been running all day without BSOD, when normally I would
>get hit with it 4-10 times a day.. I suspect it was cleaning the registry that
did
>it..
>
>
>ASUS a7n8x dlx
>AMD 3200+
>Crucial DDR400 2x512 (Infineon)
>Geforce 5700u
>
>
>
- Written in response to:
- re: BSOD, win32k.sys (Axl Myk: Wednesday, June 16, 2004 at 5:26 pm)
There are presently no replies to this message.
|
|
All messages in this thread [show all]
 |  | | | | |  | Confused (Adri1456: Fri, May 14, 2004, 3:29 pm) |
| | | | | |  | Crash (greine12: Tue, Apr 6, 2004, 4:57 pm) |
| | | | | | | | | re: Crash (MadMan: Sat, Apr 10, 2004, 1:19 pm) |
| | |  | re: BSOD, win32k.sys (Sabyre: Fri, Jun 25, 2004, 7:20 am) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
