re: BSOD, win32k.sys
Sunday, June 6, 2004 at 5:23 pm
Windows XP Annoyances Discussion Forum
Posted by Luke
(1 messages posted)
Okay, here is a thread update for those of you who really cannot read the many many
threads above.
Overview: General Windows XP BSOD (STOP screens). Highly variant, sometimes mentioning
win32k.sys and other times referencing NVIDIA files.
This problem seems to be specific; so far the following consistencies have been identified:
* Under AMD processors
* Under NVIDIA or ATI graphics
* Possibly under VIA chipsets
* Possibly only on systems with higher levels of RAM
* People using Windows XP, all versions
You cant do much with the above information, other than decide if this thread applies
to you.
A couple of people have posted back with solutions, listed below. These solutions
are usually echoed by a couple of other people so take note:
Overheating:
Some people have narrowed this problem down to system overheating. You can check
to see if your system is overheating by removing the case and directing a box fan
straight into your system. If the problems stop then you can be pretty sure its heat
related. Invest in some extra fans, internal cooling, or just leave the box fan in
place!
Memory:
Some people have just had incompatible memory; now don’t get me wrong, not faulty
memory but incompatible. This means your memory wont work with your system configuration.
You can see if this is your problem by replacing the memory with a different brand.
Memory configuration:
Also, some people have determined that removing a stick of memory out of a two stick
configuration can solve these problems. You can try this by removing one stick and
running on half memory for a while.
Graphics software:
This problem seems to be graphics orientated, and some people have found that the
errors are removed simply by installing the latest drivers. This particularly applies
to NVIDIA.
Graphics hardware:
Another common solution is simply replacing the graphics card with another make,
or if you have integrated graphics, to install a card and disable the chip in the
BIOS.
System voltage:
Reducing the system voltage might help. In one example, setting 3.45V (Default)
to 3.3V was enough to stop the problem. You can change the voltage setting through
the BIOS, but be careful, and use only small increments, bad voltage settings can
kill your computer.
Troubleshooting help: Some of the worse problems to troubleshoot with are infrequent
problems. This seems to particularly apply to this case, some people are receiving
the messages very frequently and the less fortunate are getting them on a weekly
basis. The problem with infrequent errors is that they can be almost impossible to
diagnose, without a heck of a lot of time on your hands.
Try to search for something to reproduce the problem, or run a system stress test
so you can at least tell when you’ve fixed the problem. Failing that, try a number
of solutions (listed above) at once. Although messy there will be a good chance you’ll
hit it first time.
Most importantly, don’t forget to try reinstalling Windows, 90% of the time this
will remove long term errors, also check that the software you are using is bug free.
Good luck and happy hunting.
If you need any more advice, you can contact me through this forum!
Luke
- Written in response to:
- re: BSOD, win32k.sys (larry: Wednesday, June 2, 2004 at 4:45 pm)
Responses 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 (Luke: Sun, Jun 6, 2004, 5:23 pm) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
