win32kfull.sys bluescreen

Page 1 of 4 123 ... LastLast

  1. Posts : 15
    Windows 10
       #1

    win32kfull.sys bluescreen


    Code:
    On Sat 4/16/2016 5:25:09 AM GMT your computer crashed
    crash dump file: C:\WINDOWS\Minidump\041616-8109-01.dmp
    This was probably caused by the following module: win32kfull.sys (win32kfull!SetRedirectedWindow+0x15F) 
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960EB8998BB, 0xFFFFD000235219D0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\WINDOWS\system32\win32kfull.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Full/Desktop Win32k Kernel Driver
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 


    This is one of the crash logs from Whocrashed.

    I have been having an issue that has been bugging intermittently and even followed me from Windows 8.1 to 10. Essentially what happens is at random points during use of my computer I will no longer be able to click anything on the taskbar, right click, open my start menu, open task manager, open any new programs, and sometimes it will all end with a bluescreen kicking me back the above error. Sometimes the blue screen does not happen, though.

    I posted on another forum about this and was directed to try here as well.

    Things I have tried: sfc/dism many times over, memtest86 overnight 9 passes, scanning for infections (just in case), making a new user account as well, and doing a fresh wipe down and re-install of my GPU drivers (as per recommendation of someone on another forum.)

    In the event viewer only one event sticks out:

    Code:
    The description for Event ID 243 from source Win32k cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    
    If the event originated on another computer, the display information had to be saved with the event.
    
    The following information was included with the event: 
    
    
    The specified resource type cannot be found in the image file
    
    
    This error seems to be a 'Desktop Heap Allocation Error' according to a quick google search.

    I'm nearly 100% sure that this error is related to the issue I'm having because every time I have this issue, this error is somewhere nearby in event viewer. I just have no idea how to fix it.

    Any help anybody can offer would be greatly appreciated. Thanks in advance.
      My Computer


  2. Posts : 654
    windows 10 Pro
       #2

    Please use the BSOD posting instruction to provide theDumpfile https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html
      My Computer


  3. Posts : 15
    Windows 10
    Thread Starter
       #3

    Here you are, sorry about that.

    Attachment 75159
      My Computer

  4. Arc's Avatar
    Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #4

    Your system specs says ....
    Memory 12GB Corsair Vengeance
    You have 8 GB Corsair (2x4GB) and the rest is something else (G.Skill) (2x2GB).

    Remove that 2x2GB G.Skill RAM. Report us for any further BSOD with only the 2x4GB Corsair RAM applied.

    Mixed RAM can always cause 0x3B BSOD. Use RAM that came in the same KIT only.
      My Computer


  5. Posts : 15
    Windows 10
    Thread Starter
       #5

    I'll give it a shot, but does that solution make sense considering the issue just seemed to randomly start a few weeks to a month ago? I've been using the same memory in this build for quite some time already. Just wondering.
      My Computer

  6. Arc's Avatar
    Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #6

    Iketsu31425 said:
    I'll give it a shot, but does that solution make sense considering the issue just seemed to randomly start a few weeks to a month ago? I've been using the same memory in this build for quite some time already. Just wondering.
    You haven't done the right thing.

    If you experience any further BSOD after removing the G.Skill RAM, post the dumps again. There might be other things, but you need to do this rectification at once for good.
      My Computer



  7. Posts : 15
    Windows 10
    Thread Starter
       #7

    Arc said:
    You haven't done the right thing.

    If you experience any further BSOD after removing the G.Skill RAM, post the dumps again. There might be other things, but you need to do this rectification at once for good.
    I will certainly give it a shot. I'll report back if I get the Error 243 from Win32k afterward.

    Just as an update: Memory has been removed, running on 8GB of Corsair now. I need to go to work now, but will check Event Viewer when I return and report back with any issues from here on out. Thanks again.
    Last edited by Iketsu31425; 16 Apr 2016 at 13:57. Reason: Update
      My Computer

  8. Arc's Avatar
    Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #8

    Iketsu31425 said:
    I will certainly give it a shot. I'll report back if I get the Error 243 from Win32k afterward.
    Well, my primary concern is the BSOD. If your primary object is to get rid of the Desktop Heap Allocation Failure, please add the following in your to-do list:

    Free up the startup. Windows does not need any other program to auto-start with it; but they can conflict which may cause various issues including randm crashes including BSODs.

    1. Right click on the taskbar and click on "Task Manager" in the context menu.
    2. It will open Task Manager with "Processes" tab selected. Click on the "Startup" tab.
    3. Select them all one by one and click "Disable" at the bottom right corner.
    4. Disable everything there other than the antivirus.

    See how it goes. Let us know.

    Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall the program at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.

    Open Killer Network Manager and disable the Network Bandwidth Control feature therein.

    Report us after doing all the three plus the previous one.
      My Computer


  9. Posts : 15
    Windows 10
    Thread Starter
       #9

    Step 1: I have disabled everything on startup to my knowledge.

    Step 2: I attempted to download the SPTD standalone and it says that my platform is not supported. Might not be a version for Windows 10?

    Step 3: I have disabled the Network Bandwith Control Feature.


    Previous Step: I have removed the G-Skill memory and am now running on 8GB of Corsair Vengeance.

    I will report back if the issue presents itself again. Thanks for all the help.
      My Computer

  10. Arc's Avatar
    Arc
    Posts : 1,626
    Microsoft Windows 10 Home
       #10

    Iketsu31425 said:
    I will report back if the issue presents itself again. Thanks for all the help.
    Yes, probably that tool does not support windows 10.
    Will wait to see how it goes.
      My Computer


 

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 11:16.
Find Us




Windows 10 Forums