• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

win32k.sys bsod

D

DReborn

Limp Gawd
Joined
Aug 11, 2004
Messages
364
i keep getting hard crashes referring me to my win32k.sys file. i have done some research and people say that it is ram related but i ran memtest for hours and i didn't get a single error.

also they say that it could be video card related but i updated to the latest chipset/video drivers.

here is the error info:

Error code 1000008e, parameter1 c0000005, parameter2 bf80198d, parameter3 b90d7ba8, parameter4 00000000.

help! =\
 
Try testing your HDD, you may have recenlty got a bad sector and that file might be sitting on it. You can grab the tools you need from you hard drives manufacturer's website. Hope this helps
 
What are you doing when it crashes?

Can you recreate the crashes on purpose every time?

Have you done the usual software stuff?: Virus/Spyware check, defrag, etc..
 
haven't checked the hard drive but i will do that now, thanks.

ran the normal battery of virus/spyware removal.

i can't repeat it but it seems like it crashes when I am heavily using the internet; sending big files, VNC, etc.

sometimes it just happens when the computer is sitting idle.
 
so i checked the hardrive and all seems well. i also ran chkdsk which didn't seem to find any errors.

still getting this charming win32k.sys bsod...
 
Try putting your RAM in a different slot. If more than 1 stick, start re-arranging them.

If that doesn't work, 8e errors that indicate a Windows driver generally mean they need replacing. Do a Ssytem file check (Start -> Run -> type "sfc /scannow" without the quotes). If this doesn't fix it, a repair of Windows will almost always cure kernel problems like this. However if it does persist beyond this step, then you can assume it is a hardware issue. Memtest won't always pick up on the same problems that cause BSODs and errors in programs - OS's and progams stress RAM in different ways than memTest will.

Having said that, those errors are generally caused by Windows software problems. Do the SFC, and a repair only if necessary.
 
thanks...i actually tried switching the mem slots this morning and (cross my fingers) i have not had a stall since! I hope it was that simple but i feel it will happen again. if it does i will run sfc scannow

thanks for help. =)
 
You must log in or register to reply here.
Back
Top