re: BSOD, win32k.sys
Friday, July 8, 2005 at 6:54 am Windows XP Annoyances Discussion Forum
Posted by annoyed at windows
(2 messages posted)
I was getting BSOD's identifying the driver win32k.sys in the message. I solved this
problem by uninstalling the codec pack - all in one I'd just installed from free-codecs.com.
On Tuesday, July 5, 2005 at 10:44 am, Geof Gibson wrote:
>I too, have developed this problem.
>I solved it by going into my BIOS and dropping my FSB from 200 (its max) to 166.
> I then ran the nTune app. which drives the nForce 2, and it bumped the FSB up to
>192 MHz with stability.
>
>I have noticed some trends whilst searching the net about this problem.
>1) The vast majority of sufferers are running AMD Althlons
>2) Most people who list their chipsets seem to list nForce 2
>3) Almost all solutions seem to require adding cooling or dropping bus speeds
>4) Many people have found memory errors while troubleshooting (is this the cuase
>or cuased by ??)
>
>In my case, Chaintech 7NJL6 board with nForce 2 chips. AMD Athlon 3200 CPU. 1GB
>of Viking RAM DDR 400. Diamond Viper 9600XT AGP card w/256 MB RAM.
>
>Hope this helps.
>
>
- Written in response to:
- re: BSOD, win32k.sys (Geof Gibson: Tuesday, July 5, 2005 at 10:44 am)
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 (annoyed at windows: Fri, Jul 8, 2005, 6:54 am) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|