Share via

BSOD Win32full.sys

Anonymous
2018-02-27T03:02:06+00:00

Ever since I updated to the latest version of Windows 10, I have been getting random BSOD's.

It doesn't happen during gaming. And if it does happen on the Desktop it's normally happens randomly when clicking the mouse button.

I am beginning to think it's my mouse driver, but I have have included my crash dump.

Hopefully someone can shed some light on what's causing it.

Thank you for your time.

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)

An exception happened while executing a system service routine.

Arguments:

Arg1: 00000000c0000005, Exception code that caused the bugcheck

Arg2: ffff9f964baefc33, Address of the instruction which caused the bugcheck

Arg3: ffff8a855119b1c0, Address of the context record for the exception that caused the bugcheck

Arg4: 0000000000000000, zero.

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.248 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  To Be Filled By O.E.M.

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  3029   

BIOS_DATE:  10/09/2012

BASEBOARD_MANUFACTURER:  ASUSTeK Computer INC.

BASEBOARD_PRODUCT:  Crosshair IV Formula

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8

  Kernel Generated Triage Dump

BUGCHECK_P1: c0000005

BUGCHECK_P2: ffff9f964baefc33

BUGCHECK_P3: ffff8a855119b1c0

BUGCHECK_P4: 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 

win32kfull!xxxRealSleepThread+116ce3

ffff9f96`4baefc33 488b02          mov     rax,qword ptr [rdx]

CONTEXT:  ffff8a855119b1c0 -- (.cxr 0xffff8a855119b1c0)

rax=0000000000000010 rbx=ffff9fdb03805a50 rcx=fffffffffffd8f00

rdx=0000000000000000 rsi=0000000000000200 rdi=0000000000000000

rip=ffff9f964baefc33 rsp=ffff8a855119bbb0 rbp=ffff9fdb00a11b30

 r8=fffff78000000320  r9=fffff78000000004 r10=7ffffffffffffffc

r11=fffff80388017000 r12=0000000000000001 r13=0000000001de3f07

r14=0000000000000000 r15=0000000000000001

iopl=0         nv up ei ng nz na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286

win32kfull!xxxRealSleepThread+0x116ce3:

ffff9f964baefc33 488b02          mov     rax,qword ptr [rdx] ds:002b:0000000000000000=????????????????

Resetting default scope

CPU_COUNT: 8

CPU_MHZ: 1016

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 1

CPU_STEPPING: 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  BRIAN-PC

ANALYSIS_SESSION_TIME:  02-27-2018 02:44:33.0857

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

LAST_CONTROL_TRANSFER:  from ffff9f964b9d8408 to ffff9f964baefc33

STACK_TEXT:  

ffff8a855119bbb0 ffff9f964b9d8408 : ffff9fdb03800000 ffff9fdb00a10000 0000000000000000 ffff9fdb00000000 : win32kfull!xxxRealSleepThread+0x116ce3

ffff8a855119bc90 ffff9f964b9df329 : ffff9fdb038fa160 ffff9fdb03805a50 0000000000000202 ffff8a855119bf10 : win32kfull!xxxInterSendMsgEx+0xe38

ffff8a855119be40 ffff9f964ba9fe70 : 0000000000000000 0000000000000082 ffff8a855119c0d8 0000000000000000 : win32kfull!xxxCallHook2+0x859

ffff8a855119c0b0 ffff9f964c4981f6 : 0000000000000000 0000000000000000 ffffb00600000202 ffff9f964c4c8d6f : win32kfull!EditionLLMouseButtonHook+0x170

ffff8a855119c120 ffff9f964c494ccf : 000002210000023a ffff8a855119c280 0000000000000000 ffff9fdb00067010 : win32kbase!ApiSetEditionLLMouseButtonHook+0x82

ffff8a855119c180 ffff9f964c495264 : fffffd473d908835 ffff9f964c43fcf0 0000000000000002 ffff9fdb00067010 : win32kbase!CMouseProcessor::ProcessMouseButton+0x1cb

ffff8a855119c7f0 ffff9f964c493797 : ffff8a855119c8d0 ffff9f964c58e338 ffff9f964c58e348 0000000000000000 : win32kbase!CMouseProcessor::ComputeAndDeliverMouseButtons+0xf4

ffff8a855119c880 ffff9f964c4931d5 : ffff8a855119c9a0 ffff8a855119ca60 0000000000000001 0000000000000000 : win32kbase!CMouseProcessor::ProcessMouseEvent+0x1eb

ffff8a855119c990 ffff9f964ba8e4ce : ffff8a855119c9d8 ffffb006a1dc5a10 ffff8a855119cae0 ffff9f964c46d4bc : win32kbase!ProcessMouseEvent+0x25

ffff8a855119c9c0 ffff9f964c4bca7b : 0000000000000001 ffff9f964c4af502 0000000000000000 ffff9f9600000001 : win32kfull!EditionHandleMitSignal+0x5e

ffff8a855119c9f0 ffff9f964c46d258 : ffff9fdb03805a50 0000000000000000 0000000000000001 fffff80388062947 : win32kbase!ApiSetEditionHandleMitSignal+0x3f

ffff8a855119ca30 ffff9f964c495fe8 : 0000000000000001 0000000000000001 0000000000000000 ffff9f964c5c3ee8 : win32kbase!UserProcessMITInput+0x178

ffff8a855119cac0 fffff8038819f003 : ffffb006a24b0700 0000000000000001 0000000000000020 ffffb006a24b0700 : win32kbase!NtMITWaitForMultipleObjectsEx+0x48

ffff8a855119cb00 00007ffc3bd572c4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13

000000136fe7f368 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc`3bd572c4

THREAD_SHA1_HASH_MOD_FUNC:  088975a9141f7c3475a529ef5cc5000d00d50225

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  cffe1e516d0ca7577f09d10115a059bb213a479a

THREAD_SHA1_HASH_MOD:  78b3435bc6844a2cae7bbc63676a8f491a983cb5

FOLLOWUP_IP: 

win32kfull!xxxRealSleepThread+116ce3

ffff9f96`4baefc33 488b02          mov     rax,qword ptr [rdx]

FAULT_INSTR_CODE:  48028b48

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32kfull!xxxRealSleepThread+116ce3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32kfull

IMAGE_NAME:  win32kfull.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  519efeb4

IMAGE_VERSION:  10.0.16299.248

STACK_COMMAND:  .cxr 0xffff8a855119b1c0 ; kb

BUCKET_ID_FUNC_OFFSET:  116ce3

FAILURE_BUCKET_ID:  0x3B_win32kfull!xxxRealSleepThread

BUCKET_ID:  0x3B_win32kfull!xxxRealSleepThread

PRIMARY_PROBLEM_CLASS:  0x3B_win32kfull!xxxRealSleepThread

TARGET_TIME:  2018-02-27T02:39:00.000Z

OSBUILD:  16299

OSSERVICEPACK:  248

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-02-10 04:34:33

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.248

ANALYSIS_SESSION_ELAPSED_TIME:  8b7

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_win32kfull!xxxrealsleepthread

FAILURE_ID_HASH:  {5eeee367-4360-8935-5a48-3e6b37cd79f1}

Followup:     MachineOwner

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

11 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-02-28T22:42:05+00:00

    Hi.

    Sorry for the late reply. The wife hijacked my PC.

    I had forgotten I had Virtual Box installed.

    I have uninstalled it, and I will see how it goes over the next two or three days.

    Thanks for the help once again.

    Brian.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Sumit 43,806 Reputation points Volunteer Moderator
    2018-02-27T14:22:25+00:00

    No drivers were named in the crashes, so our next step would be to find the offending driver if any.

    Enable Driver Verifier:

    http://answers.microsoft.com/en-us/windows/wiki...

    Upload the newer dumps when you get Driver_Verifier_detected_voilation.

    Please note that the system might crash before you reach the desktop-if it does please let us know so that we can guide you to disable Verifier.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Sumit 43,806 Reputation points Volunteer Moderator
    2018-02-27T03:09:47+00:00

    Hello,

    We need log files(called dump files) that tell us what lead to crash.

    Please share them with us for a better analysis of the problem. Instructions can be found here:

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2018-02-27T22:25:36+00:00

    Thanks for your help.

    Driver Verifier did indeed crash the computer as expected.

    No worries, I simply restarted in safe mode and then disabled Verifier.

    Anyway, here is the new dump generated by Driver Verifier.

    Verifier Memory Dump

    Was this answer helpful?

    0 comments
  5. Anonymous
    2018-02-27T13:04:27+00:00

    Please find below the dump file along with the logs you requested.

    I have since changed to another mouse just in case.The mouse I was using was a PNY Riot Gaming Mouse.

    Logs

    Was this answer helpful?

    0 comments