BSOD stop code 3b, unclear cause

[kennethe]

I have been getting a BSOD every couple days. The error is a system_service_exception with stop code 3b. (STOP: 0x0000003b (0x00000000C0000005, 0xFFFFF9600010D010, 0XFFFFF88E011B40, 0x000000000000)

To explain further, I have had this exact same error on TWO different computers, one of them completely new, while running the same combination of programs/drivers. They are both Stop code 3b with Parameter 1 the same, 0x00000000C0000005 (though Parameter 2 and 3 are different for each time the BSOD comes up). The two computers have different graphics drivers, so I believe graphics drivers can be ruled out as the problem (one is a AMD Radeon 6750M, the other is an Intel HD Graphics 4000). The graphics drivers are also updated. They are both running Windows 7, one is a Lenovo ThinkPad x1 Carbon, the other is a Macbook Pro running Bootcamp (I blamed bootcamp for the problem, which is why I got the new computer, but it seems that it is not the problem).

In both cases, I am running a 30" external monitor via a DVI-D to Displayport adapter, made by Accell (with additional USB powering). I believe this may be the problem, because after several days not using the monitor I did not have the crash. This is not conclusive though, because it normally only crashes every 2-5 days, but I think it may be a good place for a knowledgeable person to start. However, I used the computer for many months without any crashes with this external monitor, and it has only been crashing in the last month.

I am also running a Logitech external trackball mouse and have a somewhat new Brother printer and it's associated drivers. I have Nod32 ESET antivirus, updated to the most recent version. I'm also using a program that uses a PostGreSQL database, and am running several applications at a time (not graphics intensive but I believe it does use up a fair amount of resources). For the most part, the crash has only happened after a couple hours of use. I have had all of these things installed and running on both computers when they crashed.

According to BlueScreenView, on both computers the error is caused by driver win32k.sys, caused by address win32k.sys+7d010. The crash address is ntoskrnl.exe+7efc0.

My plan is to keep using the computer(s) without the external monitor, and see if they ever crash. If the monitor is the cause, I would hope for some solution that would allow me to use the monitor (I'd be willing to buy a new adapter if it might make a difference).

I have uploaded the .dmp file zipped. Thanks for the help!

 

[Arc]

Welcome aboard.

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red][B]BugCheck 3B[/B][/COLOR], {c0000005, fffff960000dd010, fffff880072a8b40, 0}

Probably caused by : win32k.sys ( win32k!xxxProcessEventMessage+1c0 )

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

According to Carrona.org, STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTIONhttp://www.carrona.org/bsodindx.html#top
Usual causes: System service, Device driver, graphics driver, memory

Bet there is neither any driver nor the memory is listed as the probable cause. So, let us check for any faulty driver first. In such a situation, it is better to 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.

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

The next time, post it following the Blue Screen of Death (BSOD) Posting Instructions. A single crash dump is not enough info.

 

[kennethe]

Thank you for the response. I am running Driver Verifier now, and have also uploaded the SF diagnostic tool results if they help. Will post back after 24 hours or next crash.

 

[kennethe]

Actually, I spoke too soon, after I had enabled Driver Verifier but before restarting.

Driver Verifier does not seem to work at all. After turning it on, following the instructions in that post, my computer fails to start windows again, and has to go through Startup Repair and then it Restores to an earlier point in order to turn back on. So as far as I can tell, Driver Verifier is not turned on.

Please advise an alternative or how I can make Driver Verifier work correctly.

 

[Arc]

To make driver verifier work correctly, you need to follow the instructions, step by step.
:ar: Driver Verifier - Enable and Disable.

Make it sure that you are not checking any microsoft's drivers.

 

[kennethe]

I did follow the directions exactly, without scanning any Microsoft drivers. However, in the picture in the directions, many non Microsoft drivers are also unchecked (such as the unknown ones), are there others I should leave unchecked, or perhaps just a handful that I should check? Thanks for the help!

 

[Arc]

You check all non-microsoft drivers and proceed. It should work.