the win32k.sys blue screen problem

[Guest]

hello. noticed other people have had this problem before as well. My pc isnt
overheating and the graphics card is ok (i think) with latest drivers.

I randomly have an issue where the pc restarts, stating win32k.sys as the
problem, also referencing 0x0000008E and 0x00000000. It is also happening on
another PC in my house, but i havent seen the blue screen information yet, so
it may not be win32k.sys.

I have win32k.sys version 5.1.2600.2770 in system32.

I also have version 5.1.2600.2622 in C:\WINDOWS\$hf_mig$\KB890859\SP2QFE.
There are also versions 1106, 1134, 1275, 1581, 2180 in NTuninstall folders.

Can i replace the system32 file with another version and which one will
hopefully sort this problem?

hope someone can advise me

 

[Unk]

hello. noticed other people have had this problem before as well. My pc isnt
overheating and the graphics card is ok (i think) with latest drivers.

I randomly have an issue where the pc restarts, stating win32k.sys as the
problem, also referencing 0x0000008E and 0x00000000. It is also happening on
another PC in my house, but i havent seen the blue screen information yet, so
it may not be win32k.sys.

I have win32k.sys version 5.1.2600.2770 in system32.

I also have version 5.1.2600.2622 in C:\WINDOWS\$hf_mig$\KB890859\SP2QFE.
There are also versions 1106, 1134, 1275, 1581, 2180 in NTuninstall folders.

Can i replace the system32 file with another version and which one will
hopefully sort this problem?

hope someone can advise me

Windows XP has a default setting to "Restart on failure"

Right click on "My Computer" and select Manage.
Expand the Event Viewer category and look through each of the three sub-categories for the red
flagged error records. The date and time of these should correspond to your restarts. Double
click on an error record to see the details of the error.

You can change this restart behavior:

Click Start, Settings, Control Panel, System, Advanced. In the Startup and Recovery section,
click on the "Settings" button to open the Startup and Recovery window. In the System Failure
section, uncheck "Automatically restart", Click "Apply", "OK"

After that change the computer will no longer restart when a system failure occurs. Instead it
will probably throw up a "Blue Screen Of Death" with a STOP error message and then halt
completely, requiring a manual power off and restart (or reset if it has a hardware reset
switch). But the contents of the STOP error message will give a specific clue as to the
underlying cause of the problem.

Don't be suprised, if after changing the setting, things appear to run just fine.
Some errors are so minor that they will only show up in the Event logs and not produce a BSD.
However, they would still evoke the restart if the setting were changed back to the default.

 

[Guest]

hello.

nothing appears in the event viewer corresponding to the restarts and I
turned off automatic restarting so I could see the bsod. It throws up
0x0---8E and 0x0--00 errors. but i cant seem to solve the problem. So i was
hoping that i might be able to replace win32k.sys with another version...

 

[Malke]

hello.

nothing appears in the event viewer corresponding to the restarts and
I turned off automatic restarting so I could see the bsod. It throws
up 0x0---8E and 0x0--00 errors. but i cant seem to solve the problem.
So i was hoping that i might be able to replace win32k.sys with
another version...

Since your problems are random, do some hardware troubleshooting. Start
with testing the RAM. Here are some general hardware troubleshooting
steps:

http://www.elephantboycomputers.com/page2.html#Hardware_Troubleshooting

Testing hardware failures often involves swapping out suspected parts
with known-good parts. If you can't do the testing yourself and/or are
uncomfortable opening your computer, take the machine to a professional
computer repair shop (not your local equivalent of BigStoreUSA).

Malke

 

[Guest]

thanks for replies.

I have run windows ram testing and tufftest as well. I keep my pc clean so i
dont think its dust. Im going to give seatools and memtest a go and see if
they report anything.