SYSTEM_SERVICE_EXCEPTION (win32kfull.sys)

Anonymous
2017-02-13T12:08:22+00:00

I am facing a blue screen with the error : SYSTEM_SERVICE_EXCEPTION (win32kfull.sys) 

and that's is right after using (installing and uninstalling) the following programs :

1- Aero glass W8+ v1.4.5 & then 1.5.2

2- UltraUXThemePatcher_3.1.0 for 14393 

3- Theme Signature Bypass

4- UxStyle_0242_x86_x64_preview

5- OldNewExplorer

6- AGTweaker-1.3.2

The dump file shows on WhoCrashed program 

On Mon 13-Feb-17 5:26:27 AM your computer crashed

crash dump file: C:\Windows\Minidump\021317-21750-01.dmp

This was probably caused by the following module: win32kfull.sys (win32kfull+0x1A95B6)

Bugcheck code: 0x3B (0xC0000005, 0xFFFFFE60C1D295B6, 0xFFFFB30114ED7400, 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. 

and here is the dump file

Any suggestion please?

I'm running now on Safe mode with network

[Moved from: Windows / Windows 10 / Devices & drivers / PC]

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

46 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-11-18T14:06:58+00:00

    Hi - 

    Can you clarify what actions you were taking that seemed to cause the BSOD to begin with?

    Marco was saying dragging around icons (of files/folders/shortcuts) on the desktop, but you've mentioned drag-n-drops in Chrome and media players - do you mean dragging files onto the Chrome window (as in for uploading, or just to view an image in Chrome, etc)? Where did you drag said files from - the desktop, an Explorer window?  

    Same for the media player - are you dragging files in from the desktop to a media player playlist? IF so, which one?

    I'm hoping to recreate this issue on my end, which I haven't seen since yesterday morning.

    Thanks!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-11-18T16:37:03+00:00

    Actually, I think it is Drag & Drop in general.

    I managed to trigger BSOD Drag & Dropping on the Desktop and also while moving files between Explorer windows.

    I suppose it might also happen while Drag & Dropping using other programs.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-11-18T19:20:39+00:00

    So an update on my end - got another BSOD just a few minutes ago.

    To recap, this was while running Volume² (v. 1.1.5.382), and with KB4048955 installed. I do not have the MSI Gaming App mentioned by others.

    The BSOD happened while I was dragging a URL inside a form element on a webpage. I saw the "ghosted" url start to move, then everything froze, went black, then blue, and audio was a consistent buzz (as you're all well aware).

    So, not in the clear yet.

    However, I have since attempted the same action, on the same webpage, and gotten nothing.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-11-19T15:27:09+00:00

    Hi,

    In Chrome I have the habit of selecting text within websites and dropping them to address bar ( new tab ) to search for that text in Google ( saves some time and clicks ). In the case of media players, the usual : dragging files from explorer onto the playlist of KMPlayer.  

    BTW, I think you guys should also try downgrading Volume² to stable version 1.1.4.347 to see if it solves something for you.. I haven't seen the BSOD for a while now..

    Was this answer helpful?

    0 comments