By Chewbocko
Dec 30, 2009
  1. So I just got this, I herd it could be a driver problem or a ram issue.

    Its been happening for a few months now, I can't remember if it happened before or after I added some new ram or if it happened before or after I added a new hard drive.

    Tech info:

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

    *** Stop: 0x00000050(0xAC03B1C8, 0x00000000, 0xBF820956, 0x00000000)

    Win32k.sys - BF820956 base at BF800000, Datestamp 40856407

    Any ideas?

    Thanks in advance!
  2. Tedster

    Tedster Techspot old timer..... Posts: 6,000   +15

    generally caused by bad or failing ram (or incompatible ram)
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...