BSOD Probably caused by : win32k.sys, help!

Discussion in 'Windows 8 Blue Screen of Death (BSOD)' started by oldschoola, Oct 24, 2014.

  1. oldschoola

    oldschoola New Member

    Oct 22, 2014
    Likes Received:
    I've been getting random BSOD's for a long time now ever since i purchased the machine.
    Tried analyzing the file using windbg and pasted the bugcheck analysis at the end of this post. but i always see Probably caused by : win32k.sys ( win32k!xxxSendMessageToClient+0 )

    I have the latest windows 8 updates and I've updated my Bios with the latest ver (i think)
    I ran memtestx86 on each dimm for 7+ passes on each dimm with no issues.

    I've upload everything asked in How To Ask For Help With BSOD forum.
    The files uploaded are as followed:
    A. - this is a zip of the w7f collection but while w7f tool was running
    the pc blue screened.
    B. - this is a zip of the w7f collection after the blue screen
    mentioned above. this one finished correctly with no bsod during the log collection.
    C. cpu_& - this is a zip of the cpuz screenshots and html report, and the RAMMON tool html report.
    D. windb_analysis.txt - the analysis file from windbg after i ran the -analyze command on the memory.dmp file

    I am creating the large memory dumps so i have dmp files that are 7gb in size.

    any assistance would be greatly appreciated

    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Aug 28, 2007
    Likes Received:
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 1A, {41287, 2e03c0, 0, 0}
    Probably caused by : win32k.sys ( win32k!vSolidFillRect1+110 )
    Followup: MachineOwner
    Hi oldschoola,
    I went through all your dump files as I wasn't sure if any had been replicated and they are as follows:
    Bugcheck 101: 3
    Bugcheck 1A: 2
    Bugcheck 3B: 19
    Bugcheck 27: 2
    Bugcheck A: 4
    Bugcheck C4: 2
    Bugcheck BE: 2
    Bugcheck 24: 6

    It does look like from all these different Bughchecks that it's a hardware issue. If the machine has been doing this since purchase then it needs returning if the warranty allows.
    Looking at the above I'd would hazard this it's possibly (Possibly underlined) a memory issue as most of the Bugchecks are memory related in some way. As your using an onboard GPU device which shares the onboard RAM the large amount of Bugcheck 3Bs would suggest that the issue lay in this direction. Try changing the amount of RAM the GPU accesses via the bios.
    Another thing to try would be turning off any video caching, check for this option in the Bios.

    Check that the GPU is stable by running this stress test:

    When do the BSODs occur? Do they happen randomly or when your doing something like gaming?
    Also which revision or version is your motherboard as this depends on which Bios you need. The Bios dated on the dump files:
    BiosVersion = 4.6.5
    BiosReleaseDate = 08/10/2012
    Looking at the support page I see an update has been released in 2013 but you need to know which version your motherboard is (it should be written on the actual motherboard itself) so you can get the correct Bios for your version of that motherboard. I do have this link but again make sure it's your motherboard before applying any updates:

    NTFS appeared in the Bugchecks 6 times so please run a chkdsk. Follow the method in this guide as it's basically the same for windows 8:

    atikmdag.sys Sat Jul 28 02:48:09 2012: AMD GPU driver please update: (I had a bit of trouble finding the correct driver download for you.. Try the auto update utility found on the AMD page)

    DrvAgent64.SYS Mon Dec 14 10:23:26 2009: FLEXnet Licensing Service 64 - Acresso Software Inc. Is this still needed? If so please update if possible. If not then please remove:

    Also please do a search for command prompt, right click on it and run as admin. Type:
    sfc /scannow
    Press enter and wait for results.
    Post any new dump files
    (hopefully not so many next time...:) )

    I forgot to add... I checked the compatibility of your RAM against the list which is on the support page. Although the list isn't conclusive I couldn't see your RAM. Food for thought perhaps?

Share This Page