re: BSOD, win32k.sys - Might be unfixable
Thursday, April 15, 2004 at 9:50 pm
Windows XP Annoyances Discussion Forum
Posted by Will
(1 messages posted)
I have read all the posts in this thread and I want to share what worked for me.
I have noticed we all seem to have AMD chips and some have Nvidia vid cards. I have
an ATI all in wonder in mine. I have been getting the win32k.sys BSOD at wierd times,
sometimes when just idling.
What worked for me was to unplug three of my hard drives to elemenate their power
draw. Once I did this I found that it runs and has not crashed for 2 weeks now. I
am currently ordering a 450 watt power supply so I can hook those other power robbing
drives back up.
When ever you start getting random reboots and you do tests and finds the memory
ok look at your TRUE power requirements and unplug some to see if that is helping
the problem.
On Thursday, March 11, 2004 at 8:32 am, dean wrote:
>I have gotten an answer that you many of you may not like. Most of the BSoD everyone
>here has been getting is a combination of Athlon XP processors, Nvidia chipset and/or
>a form of GeForce video card (most notably, GeForce 4 MX). There is an known issue
>at Microsoft between Windows XP and combinations of the hardware above.
>
>First thing to do is do a thorough check of the your RAM. Obviously bad RAM is
probably
>the problem. Also update your motherboard BIOS and any video card BIOS (if applicable).
>
>If you are getting BSoD noting "0x0000008e" and "win32k.sys", you need to get in
>touch with Microsoft and install hotfix KB827663 (you can also read about this at
>Microsoft Knowledge Base article 827663 - http://support.microsoft.com/default.aspx?scid=kb;[LN];827663
>). That link also tells you how to contact Microsoft to get the fix.
>
>If that fix does not work, you have to get the file 90422_ENU_i386_zip.exe. That
>file is a Micorosoft hotfix but there is no article number, and it's only referenced
>as a part of SP2. The MS technician sent it to me, you'll have to be persistent
>when trying to get this fix. Both these hotfixes are password protected and the
>passwords have expiration dates so I can't give them to you.
>
>I worked with Microsoft and installed both hotfixes. My blue screen error changed
>from citing "win32k.sys" to the "nv4" nvidia video driver. At that point, Microsoft
>said I have to either wait until new Nvidia drivers come out, wait for Microsoft's
>SP2 for WIN XP, or buy another video card. I bought a new video card and my system
>runs flawlessly.
>
>I bought the new video card because I had to get my system up and running as soon
>as possible. Some other things that I would have tried had I more time would be
>to deinstall my video drivers and roll back to earlier releases from NVidia.
>
>Hopefully the first hotfix will work for you, and if not hopefully the second one
>will work. I personally have an Athlon XP 2500+, ASUS A7N8X-VM/400 with onboard
>GeForce 4MX, but now i'm using a Matrox video card.
>
>
>
>
|
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 - Might be unfixable (Will: Thu, Apr 15, 2004, 9:50 pm) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
