Solved BSOD win32k / system service exception

RealPetChicken · Jan 18, 2014

I really can't figure out what is causing my BSOD, i am not doing anything extensive other than browsing the net, and it happens. Sometimes when about to search, but not all the time. Any help will be appreciated. I updated my NVidia drivers just in case. Hopefully no more BSOD. I used this application, if anyone is interested: http://www.nirsoft.net/utils/blue_screen_view.html

Here is some info:

Code:

==================================================
Dump File         : 011814-23088-01.dmp
Crash Time        : 1/18/2014 6:09:43 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff960`0015604b
Parameter 3       : fffff880`0cceb070
Parameter 4       : 00000000`00000000
Caused By Driver  : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+197cd8
File Description  : NVIDIA Windows Kernel Mode Driver, Version 332.21
Product Name      : NVIDIA Windows Kernel Mode Driver, Version 332.21
Company           : NVIDIA Corporation
File Version      : 9.18.13.3221
Processor         : x64
Crash Address     : ntoskrnl.exe+705c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\011814-23088-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 294,016
Dump File Time    : 1/18/2014 6:11:48 PM
==================================================

==================================================
Dump File         : 011714-34273-01.dmp
Crash Time        : 1/17/2014 6:51:59 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff960`001a604b
Parameter 3       : fffff880`09b8f070
Parameter 4       : 00000000`00000000
Caused By Driver  : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+1b906b
File Description  : NVIDIA Windows Kernel Mode Driver, Version 332.21
Product Name      : NVIDIA Windows Kernel Mode Driver, Version 332.21
Company           : NVIDIA Corporation
File Version      : 9.18.13.3221
Processor         : x64
Crash Address     : ntoskrnl.exe+705c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\011714-34273-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 294,072
Dump File Time    : 1/17/2014 7:03:10 PM
==================================================

==================================================
Dump File         : 011714-37923-01.dmp
Crash Time        : 1/17/2014 12:38:05 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff960`00251a2d
Parameter 3       : fffff880`043fd150
Parameter 4       : 00000000`00000000
Caused By Driver  : win32k.sys
Caused By Address : win32k.sys+231a2d
File Description  : Multi-User Win32 Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Crash Address     : ntoskrnl.exe+705c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\011714-37923-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 294,016
Dump File Time    : 1/17/2014 12:40:08 PM
==================================================

==================================================
Dump File         : 011114-26036-01.dmp
Crash Time        : 1/11/2014 10:13:14 PM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff960`002f1164
Parameter 3       : fffff880`0ec6ba50
Parameter 4       : 00000000`00000000
Caused By Driver  : win32k.sys
Caused By Address : win32k.sys+281164
File Description  : Multi-User Win32 Driver
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor         : x64
Crash Address     : ntoskrnl.exe+705c0
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\011114-26036-01.dmp
Processors Count  : 12
Major Version     : 15
Minor Version     : 7600
Dump File Size    : 294,016
Dump File Time    : 1/11/2014 10:15:06 PM
==================================================

koolkat77 · Jan 18, 2014

Please post your files following: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

RealPetChicken · Jan 23, 2014

where exactly should i upload it too and post it at? should i just post in this thread? will it be secure uploading information like that?

Arc · Jan 24, 2014

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Code:

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17118.amd64fre.win7_gdr.120830-0334

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
__________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000232d1c, fffff880041c8990, 0}

Probably caused by : win32k.sys ( win32k!EngDrawStream+f0 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff96000232d1c, Address of the instruction which caused the bugcheck
Arg3: fffff880041c8990, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


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

FAULTING_IP: 
win32k!EngDrawStream+f0
fffff960`00232d1c 4d399a080d0000  cmp     qword ptr [r10+0D08h],r11

CONTEXT:  fffff880041c8990 -- (.cxr 0xfffff880041c8990;r)
rax=fffff96000232b5c rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff880041c9e60 rdi=fffff900c3b4ccd0
rip=fffff96000232d1c rsp=fffff880041c9360 rbp=000000000000003c
 r8=000000000000003e  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=fffff900c3b4cce8 r13=fffff880041c9d70
r14=fffff900c19ffb70 r15=fffff900c0bcee90
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!EngDrawStream+0xf0:
fffff960`00232d1c 4d399a080d0000  cmp     qword ptr [r10+0D08h],r11 ds:002b:00000000`00000d08=????????????????
Last set context:
rax=fffff96000232b5c rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=fffff880041c9e60 rdi=fffff900c3b4ccd0
rip=fffff96000232d1c rsp=fffff880041c9360 rbp=000000000000003c
 r8=000000000000003e  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=fffff900c3b4cce8 r13=fffff880041c9d70
r14=fffff900c19ffb70 r15=fffff900c0bcee90
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!EngDrawStream+0xf0:
fffff960`00232d1c 4d399a080d0000  cmp     qword ptr [r10+0D08h],r11 ds:002b:00000000`00000d08=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff96000232d1c

STACK_TEXT:  
fffff880`041c9360 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!EngDrawStream+0xf0


FOLLOWUP_IP: 
win32k!EngDrawStream+f0
fffff960`00232d1c 4d399a080d0000  cmp     qword ptr [r10+0D08h],r11

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!EngDrawStream+f0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5006f2b7

IMAGE_VERSION:  6.1.7600.17073

STACK_COMMAND:  .cxr 0xfffff880041c8990 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!EngDrawStream+f0

BUCKET_ID:  X64_0x3B_win32k!EngDrawStream+f0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_win32k!engdrawstream+f0

FAILURE_ID_HASH:  {2ebd98d4-8b67-cf0c-b8cd-785f27518433}

Followup: MachineOwner
---------

RealPetChicken · Feb 1, 2014

So i updated my windows 7 to SP1, and so far no blue screens anymore, thanks for all the help. Hopefully it stays fixed.

Arc · Feb 1, 2014

Good news. Considering the issue as solved now. Let us know for any further issue.

Solved BSOD win32k / system service exception

RealPetChicken

New member

My Computer

koolkat77

New member

My Computer

RealPetChicken

New member

My Computer

Arc

New member

My Computer

RealPetChicken

New member

My Computer

Arc

New member

My Computer

Similar threads

Solved BSOD win32k / system service exception

RealPetChicken

New member

My Computer My Computer

koolkat77

New member

My Computer My Computer

RealPetChicken

New member

My Computer My Computer

Arc

New member

My Computer My Computer

RealPetChicken

New member

My Computer My Computer

Arc

New member

My Computer My Computer

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer