BSOD win32k.sys

Hello guys. Since i upgraded to windows 7 ultimate x64 (clean install) i keep taking a frustrating BSOD about win32k.sys. Besides i can't find tuner driver (winfast tv 2000 xp deluxe) this bsod makes me think seriously of returning to Xp Sp3. Usually i noticed that this error occurs when i have a game minimized and i chat on yahoo messenger. (especially when i have CS in taskbar or lineage 2). My system specs are:
Gigabyte GA-P35-DS3L
Intel E8200 2.66 Ghz
4 GB RAM (4x 1GB Kingmax KLED48F-A8KI5 at 1066 Mhz - these are OC to 1066 as they run at 800 standard, and timings are modified 5-5-5-15 with +0.2 V from 1.8 to 2.0).
Seagate 320 GB Sata II
Winfast Nvidia 8600 GT which also causes some problems as once in a while BSOD is about cdd.dll when i exit games and temperatures of GPU reach easily 70 degrees dunno why. Sometimes windows 7 says that nvidia driver has stopped responding and recovered.

So what could be the problem guys? It's rly frustrating. I attach to this message 2 minidumps if they can help. Thx in advance.

Later edit: I mention that i had run memtest86+ for 2 hours without any problems and i posted this after a lot of searching documentation on Google. Some people say it might be a hardware problem. Well why windows xp hadn't crashed and windows 7 does if it's hardware? If it was hardware problem all systems would have been unstable. Anyway it could be because of OC.

Dyablor said:

Hello guys. Since i upgraded to windows 7 ultimate x64 (clean install) i keep taking a frustrating BSOD about win32k.sys. Besides i can't find tuner driver (winfast tv 2000 xp deluxe) this bsod makes me think seriously of returning to Xp Sp3. Usually i noticed that this error occurs when i have a game minimized and i chat on yahoo messenger. (especially when i have CS in taskbar or lineage 2). My system specs are:
Gigabyte GA-P35-DS3L
Intel E8200 2.66 Ghz
4 GB RAM (4x 1GB Kingmax KLED48F-A8KI5 at 1066 Mhz - these are OC to 1066 as they run at 800 standard, and timings are modified 5-5-5-15 with +0.2 V from 1.8 to 2.0).
Seagate 320 GB Sata II
Winfast Nvidia 8600 GT which also causes some problems as once in a while BSOD is about cdd.dll when i exit games and temperatures of GPU reach easily 70 degrees dunno why. Sometimes windows 7 says that nvidia driver has stopped responding and recovered.

So what could be the problem guys? It's rly frustrating. I attach to this message 2 minidumps if they can help. Thx in advance.

Later edit: I mention that i had run memtest86+ for 2 hours without any problems and i posted this after a lot of searching documentation on Google. Some people say it might be a hardware problem. Well why windows xp hadn't crashed and windows 7 does if it's hardware? If it was hardware problem all systems would have been unstable. Anyway it could be because of OC.

Click to expand...

Dyablor

\Hi and welcome.

Both of these BSOD's were probably caused by a combination of things
win 32.sys
memory
heat
overclocking
raid if you have one.

While there are benifts to overclocking the resultant instability causes crashes (like yours) heat (like yours) and random errors

I would
run system file chekc to verify and repair your system files
to run type cmd insearch>right click ande run as admin>SFC /SCANNOW
let us know the results

RUN MEMTESTX86 FOR SEVERAL HOURS (OVERNIGHT PREFERED)

STOP overclocking and get an app to measure temps. your temps might go down if you are not overclocking

Hope this helps

Ken J++


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\111809-19437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c53000 PsLoadedModuleList = 0xfffff800`02e90e50
Debug session time: Wed Nov 18 16:19:21.962 2009 (GMT-5)
System Uptime: 0 days 13:00:41.679
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000114283, fffff880072db060, 0}

Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )

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: fffff96000114283, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880072db060, 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!HmgLockEx+a3
fffff960`00114283 0fb7430c movzx eax,word ptr [rbx+0Ch]

CONTEXT: fffff880072db060 -- (.cxr 0xfffff880072db060)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa8005e0ab60
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff96000114283 rsp=fffff880072dba40 rbp=0000000000000000
r8=0000000000000001 r9=0000000000000000 r10=0000000000000000
r11=fffff880072dbaa8 r12=0000000005073b00 r13=0000000000000000
r14=0000000000000001 r15=0000000000000000
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!HmgLockEx+0xa3:
fffff960`00114283 0fb7430c movzx eax,word ptr [rbx+0Ch] ds:002b:00000000`0000000c=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff960002cc6b0 to fffff96000114283

STACK_TEXT:
fffff880`072dba40 fffff960`002cc6b0 : fffff900`c1f0bac0 00000000`00000001 ffffffff`f7121aab fffff900`c25937a0 : win32k!HmgLockEx+0xa3
fffff880`072dbab0 fffff960`002cbbae : fffff900`c1f0bac0 00000000`00000000 00001aab`624d4653 00000000`00000000 : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`072dbae0 fffff960`002ccab3 : 00000000`00000000 ffffffff`f7121aab fffff900`c1f0bac0 00000000`05073b60 : win32k!SFMLOGICALSURFACE:eInitialize+0x4e
fffff880`072dbb20 fffff960`002295ff : 00000000`00000000 fffff900`c00d2280 fffff900`c1f0bac0 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`072dbb60 fffff960`0024a908 : 00000800`00000001 00000000`00000001 fffff880`072dbca0 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`072dbba0 fffff800`02cc4153 : fffffa80`05e0ab60 00000000`03d3f970 000007fe`f8d3d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`072dbc20 000007fe`fea44efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03d3f3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fea44efa


FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00114283 0fb7430c movzx eax,word ptr [rbx+0Ch]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!HmgLockEx+a3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

STACK_COMMAND: .cxr 0xfffff880072db060 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3

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

Re:

Hello and thx for the answer. DWM.exe is desktop windows manager which caused my probmes in vista too (i only used vista one month) and it could be because of aero i will see. My temps are ok. Last days i cleaned my processor and i applied thermal grease on it. It's temp was a little high (65 degrees, now is around 40 idle). I don't know about RAM temps, but the rest are ok, except GPU which i read it's normal to be 75 to 85 degrees (WTF?). I dont use raid but my hdd is set to work on AHCI. Well i'll try to let the ram standard and see what happens.

Ok i return with the results. Overclocked ram to 1066, 4 hours and a half in memtest with no errors. For some time the problem disappeared and yesterday i got another bsod when i quit a game with cdd.dll error. Frustrating :/.

The info from the minidump is:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\112809-25116-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Inaccessible path: 'E:\Symbols'
Symbol search path is: E:\Symbols;C:\websymbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e42e50
Debug session time: Sat Nov 28 19:12:55.041 2009 (GMT+2)
System Uptime: 0 days 22:41:49.711
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c36547a0, 0, fffff960006adc51, 0}


Could not read faulting driver name
Probably caused by : cdd.dll ( cdd!CddBitmapHw::Release+31 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c36547a0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960006adc51, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ead0e0
fffff900c36547a0

FAULTING_IP:
cdd!CddBitmapHw::Release+31
fffff960`006adc51 483b9080070000 cmp rdx,qword ptr [rax+780h]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: hl.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88007d486a0 -- (.trap 0xfffff88007d486a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c3654020 rbx=0000000000000000 rcx=fffff900c2435030
rdx=fffffa8004ad6290 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960006adc51 rsp=fffff88007d48830 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=0000000000007dc1
r11=fffff88007d48850 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cdd!CddBitmapHw::Release+0x31:
fffff960`006adc51 483b9080070000 cmp rdx,qword ptr [rax+780h] ds:0005:fffff900`c36547a0=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cf61e4 to fffff80002c76f00

STACK_TEXT:
fffff880`07d48538 fffff800`02cf61e4 : 00000000`00000050 fffff900`c36547a0 00000000`00000000 fffff880`07d486a0 : nt!KeBugCheckEx
fffff880`07d48540 fffff800`02c74fee : 00000000`00000000 fffff900`c00bf010 00000000`00000000 fffff900`c242fcd0 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`07d486a0 fffff960`006adc51 : 00000000`00000000 00001248`00000000 000029eb`07d488d8 fffff900`c242fcd0 : nt!KiPageFault+0x16e
fffff880`07d48830 fffff960`00105080 : 00000000`00000001 fffff900`c00bf010 00000000`00000001 fffff900`c07b5920 : cdd!CddBitmapHw::Release+0x31
fffff880`07d48870 fffff960`0010d4a9 : 00000000`00000000 00000000`00000001 fffff900`c07b5920 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x358
fffff880`07d489c0 fffff960`00104920 : 00000000`00001248 00000000`00000000 fffff900`c066e6a0 fffff960`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`07d48a20 fffff960`00104063 : fffffa80`05986600 00000000`00000001 fffffa80`04ad6290 fffff800`02f702bd : win32k!GdiProcessCallout+0x200
fffff880`07d48aa0 fffff800`02f595e1 : fffffa80`05986660 00000000`00000000 00000000`00000000 fffffa80`04ad6290 : win32k!W32pProcessCallout+0x6b
fffff880`07d48ad0 fffff800`02f32cb8 : 00000000`c000004b 00000000`00000001 fffffa80`043de500 00000000`00000000 : nt!PspExitThread+0x2b1
fffff880`07d48ba0 fffff800`02c76153 : fffffa80`043de530 fffff880`c000004b fffffa80`04ad6290 fffffa80`068b2e90 : nt!NtTerminateProcess+0x138
fffff880`07d48c20 00000000`778b017a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778b017a


STACK_COMMAND: kb

FOLLOWUP_IP:
cdd!CddBitmapHw::Release+31
fffff960`006adc51 483b9080070000 cmp rdx,qword ptr [rax+780h]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: cdd!CddBitmapHw::Release+31

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: cdd

IMAGE_NAME: cdd.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bde94

FAILURE_BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31

BUCKET_ID: X64_0x50_cdd!CddBitmapHw::Release+31

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

Try running Driver Verifier and then try the procedure with the same game that caused the BSOD.
It could be an issue with a driver, or it could be an issue with the CD/DVD that the game uses.

Here's instructions on how to use Driver Verifier:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.


Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
​

Click to expand...

It was something with the drivers as when i installed some vista chipset drivers win32k.sys bsod disappeared. I see now gigabyte released windows 7 official chipset drivers but anyway yesterday i switched to win 7 ultimate x86 and this OS is running without any problems. Thx for the answer anyway. x86 is far more stable than x64 but much slower in multitasking and system speed. I could even find tuner drivers (vista ones worked) for winfast tv 2000 xp deluxe .

I have a win32k.sys BSOD too. this is an upload that BSOD thread requests. Please help

I am sorry, but I cannot provide a dump file as Windows will not start in any mode. During start up in safe mode windows gets as far as loading the AVG drivers and then crashes - so I am taking a wild guess that it is something to do with AVG. My system is , regrettably (a mistake I shall not make again), entirely Truecrypt, which means that I cannot run a recovery disk.

My question is, before I go for a complete reinstall, can I disable AVG from outside of windows, perhaps by installing ubuntu or some such on the encrypted partition?