bsod on win32k.sys

working on a presario 6000 xp. getting bsod on win32k.sys. researching error ususally indicates some form of memory problem. problem here is i have run extensive diags on this machine for 24hour loop and all components pass with flying colors.

machine hasnt been on the web literally for 3 years. still on original xp no sp's. checking now using trendmicros online scan for any bugs and then will update to sp2.

any other possibles for the bsod ???

 

I suggest taking the RAM sticks out and cleaning them with either a soft pencil eraser or a Qtip and Isopropyl alcohol then reseat them. Also do the video card if it doesn't have onboard video. Make sure that the heatsink and fans are clean and the fans are running. Might as well pull all cable connections and reseat them too.

 

whiskeyman

did all of that before writing for suggestions. have updated to sp2, ran trendmicros online scan, ran chkdsk which did find at least one problem which it fixed and all pc certify pro diags. video is integrated. for a system this old is strangely clean inside case.

will now wait and see if machine poops out again. will do the loop diags again over night and see if any problems come morning.

thanks whiskeyman will post back if error comes back.

 

If the error come backs post the whole error report here. If it isn't hardware related then the rest of the error should point toward a software problem. Wish you luck.

 

thanks man is appreciated. greg

 

70% of the blue screen is related to hardware. You had better install the debugging tools and analyze the dump as 30% of the problem is related to device driver.

Debugging Tools from Microsoft
1) Create folder c:\symbols
2) Download and install the http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
3) Locate your latest memory.dmp file- C:\WINDOWS\ Minidump\Mini011005-01.dmp or whatever
4) open a CMD prompt and cd\program files\debugging tools for windows\
5) type the following stuff:

Code:
c:\program files\debugging tools>kd -z C:\WINDOWS\Minidump\Mini011005-01.dmp
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q

You now have a debuglog.txt in c:\, open it in notepad and post to this thread.

 

cpc2004

whoa now yours is a post to die for. have never done a debug as you are describing to do but will give that a try and definitely add this to my blue screen diagnostics.

thanks.

 

Some faulty ram can pass memtest.

Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard

If it still crashes, diagnostic which memory stick is faulty. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.

 

cpc2004

machine back at clients now. had running for straight 24 hours with no incidents after updating to sp2 and removing virus and spyware. ran pc certifies new diags in a 50 loop pattern and all past just fine. hopefully, i wont be hearing back from client.

only one thing still bothers me about her system and that being the psu. have a psu tester and 1 light out of the 6 was red but then did again and all was okay. forwarned client that if problem comes back will replace psu first.

thanks.