Unknown Driver causing me to BSOD

[mittens4kittens]

I have run a memory test to check my RAM sticks and everything checks out. I have updated most of my drivers to my knowledge but I still cant figure out whats causing me to bluescreen. I hope for a little insight/help from this community.

On Thu 6/6/2013 3:56:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060513-17082-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9ED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002EC9ED, 0xFFFFF8800AB8E100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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.

 

[KnowItAll]

I would do a fresh windows install. Can't hurt.

 

[neieus]

I have run a memory test to check my RAM sticks and everything checks out. I have updated most of my drivers to my knowledge but I still cant figure out whats causing me to bluescreen. I hope for a little insight/help from this community.

On Thu 6/6/2013 3:56:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060513-17082-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x22C9ED)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002EC9ED, 0xFFFFF8800AB8E100, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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.

You could always go to msconfig and disable items under start up to help narrow it down.