Jump to content
Sign in to follow this  
fred93gt

Blue Screen of Death...."problem seems to be caused by....win32k.s

Recommended Posts

My wife's computer has been having a recurring problem with the blue screen of death and occasional reboots. I think I have fixed the reboot issue, vacuumed the inside out and used some compressed air to clean the heat sink on the CPU.

 

Anywho, the blue screen of death occurs randomly as far as I can tell. She has had the BSOD 3 times in one day. I had her write down what the screen displayed the last time she got the BSOD so I have that if needed. Did most of the recommended fixes in the test after I ran it. Here is the link to the results:

 

http://www.pcpitstop...?conid=25172957

 

Any help would be greatly appreciated.

 

Thanks in advance.

 

PS: It's a Windows XP machine, running 32bit with the latest service pack.

Edited by fred93gt

Share this post


Link to post
Share on other sites

A problem has been detected and windows has been shut down to prevent damage to your computer.

 

The problem seems ot be caused by the following file: Win32k.sys

 

Page_fault_in_nonpaged_area

 

If this is the first time you have seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

 

Check to make sure any new hardware or software is properly installed. If this is a new installation ask your hardware or software manufacturer for any windows updates you might need.

 

If the problem continues, disable or remove any newly installed hardware or software, disbale BIOS memory options such as caching or shadowing. If you need to use the safe mode to remove or disable components, restart your computer, press F8 to select advanced startup options, and then select safe mode.

 

Technical information:

 

***stop: 0x00000050 (0xE1E3B07C,0X00000000,0XBF82EBC7,0X00000007)

*** Win32k.sys -Address BF82EBC7 base at BF800000, Datestamp 50a7a76d

 

Beginning dump of physical memory.

 

Physical memory dump complete.

 

Contact your system adminstrator or tech support group for further assistance.

Share this post


Link to post
Share on other sites

Two possible causes are failing RAM and hard disks errors. To check the RAM, I recommend MemTest86 or Microsoft's WinDiag.

 

http://www.memtest86.com/download.html#R40a

 

http://web.archive.org/web/20110717101906/http://oca.microsoft.com/en/windiag.asp

 

For MemTest86, download the Windows ISO version. For WinDiag, run MTInst.exe and click the Save CD Image button to extract the ISO file. In either case, you'll burn a CD using the ISO as a disk image (putting it on a disc as a file won't work). Boot the problem computer from the CD.

 

To check for hard disk errors, log on to an account with administrator's rights. Click Start and Run, type Chkdsk /R and click OK. When prompted, type Y and press Enter, then restart the computer. The error check duration increases with the partition size, so a large drive will take some time.

Share this post


Link to post
Share on other sites

MemTest86 returned no errors as well as Checkdisk returning no errors on the harddrive. Don't know what else to do, haven't installed any hardware in a long time and the only software installed is updates through Windows Update.

Share this post


Link to post
Share on other sites

Does Windows eventually load and allow you to log in?

Share this post


Link to post
Share on other sites

Does the machine have a utility installed with which to report out Temperatures?

Examples:

SpeedFan

Everest

Specy

 

I prefer specy, a free version of which can be obtained here: http://www.piriform....speccy/download

Be sure to read the on-screen installation instructions carefully, and avoid installing the extra Google ToolBar, by de-selecting it (remove the checkmark/tick)

 

Report back to us the available Temperature reports

Most condensed method of finding all the temperatures in one reporting place is to look at the Summary.

 

Give some attention over time to Temperatures to see if there is any coincidence between Temperature and BSOD.

Share this post


Link to post
Share on other sites

That was another concern which is why I vacuumed out the case and used compressed air to clean the heat sink. I figured that the reboot issue was due to the dust build up, will run the suggested diagnostics tomorrow and hopefully get some answers.

Share this post


Link to post
Share on other sites

MemTest86 returned no errors as well as Checkdisk returning no errors on the harddrive.

Microsoft says that Stop: 0x50 is usually due to a hardware problem. You could begin by disabling unnecessary hardware in the Device Manager, i.e., modem, network adapter, sound card, etc.

Share this post


Link to post
Share on other sites

CPU temperature varies between 105-110 F, MB and HD both are consistant @103 F.

 

Those Temperatures are good.

 

back to the think-tank. post-28857-0-93733900-1356826967_thumb.gif

Share this post


Link to post
Share on other sites

I think I may have found the culprit - my wife's computer has been having issues with her sound lately now that I think about it. She has a Soundblaster Live 5.1 soundcard that is pretty old, it's a PCI cardif that says anything about how old it is. Anywho, lately the audio has been choppy when she watches internet videos on it. Since she got the BSOD 3 times again the other day I was thinking this is most likely the problem. She has on board audio that has never been used so I will try removing the SB card and use only the audio on the MB.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...