BSOD dwm.exe - Windows 7 x64

kinster45 · Feb 21, 2014

OK so I'm having a BSOD more an more often. It has to do with something interacting with dwm.exe and happens when I'm minimizing chrome.

I'm running Windows 7 it's OEM and I installed it.
The parts in the computer are of differing ages. Nothing is older than 3 years though.
The operating system was installed Around December 2011

CPU:i7-2600k
Video card: ATI 7870
Powersupply: Corsair gold 1200 Watts

It's a frankenstein.

View attachment 7131

jcgriff2 · Feb 23, 2014

Hi -

The zip file contained 15 dump files dating back to September 2012.

ASMedia USB 3.0 driver named in 2012 BSOD - needs to be updated -

Code:

[FONT=lucida console]asmthub3.sys               Wed Nov 02 23:00:32 2011 (4EB203D0)[/FONT]

http://sysnative.com/drivers/driver.php?id=asmthub3.sys

Creative audio also named in prior BSODs - update drivers -

Code:

[FONT=lucida console]ha20x22k.sys               Tue Dec 18 07:00:49 2012 (50D05AF1)
ctsfm2k.sys                Tue Dec 18 06:56:34 2012 (50D059F2)
ctoss2k.sys                Tue Dec 18 06:56:56 2012 (50D05A08)
ctaud2k.sys                Tue Dec 18 07:02:52 2012 (50D05B6C)
CTHWIUT.SYS                Tue Dec 18 07:05:02 2012 (50D05BEE)
CTEXFIFX.SYS               Tue Dec 18 07:04:49 2012 (50D05BE1)
CT20XUT.SYS                Tue Dec 18 07:04:57 2012 (50D05BE9) [/FONT]

http://sysnative.com/drivers/driver.php?id=ha20x22k.sys
http://sysnative.com/drivers/driver.php?id=ctsfm2k.sys
http://sysnative.com/drivers/driver.php?id=CT20XUT.SYS
http://sysnative.com/drivers/driver.php?id=ctaud2k.sys
http://sysnative.com/drivers/driver.php?id=CTHWIUT.SYS
http://sysnative.com/drivers/driver.php?id=ctoss2k.sys

Please uninstall Elby and any other virtual devices for now -

Code:

[FONT=lucida console]ElbyCDIO.sys               Mon Mar 04 04:21:51 2013 (513467AF)[/FONT]

http://sysnative.com/drivers/driver.php?id=ElbyCDIO.sys

Norton is very likely involved based on the varios bugchecks that had a common exception error code - 0xc0000005 = memory access violation which can also be interpreted as "access denied" -

Code:

[FONT=lucida console]
SYMDS64.SYS                Tue Jul 30 19:29:08 2013 (51F84C44)
ccSetx64.sys               Mon Sep 23 23:58:04 2013 (52410DCC)
SYMEFA64.SYS               Sat Aug 31 00:02:36 2013 (52216ADC)
SRTSP64.SYS                Wed Sep 25 20:23:42 2013 (52437E8E)
SRTSPX64.SYS               Fri Jul 26 22:45:06 2013 (51F33432)
Ironx64.SYS                Mon Jul 29 20:59:35 2013 (51F70FF7)
SYMEVENT64x86.SYS          Fri Jul 26 22:26:58 2013 (51F32FF2)
IDSvia64.sys               Fri Jan 10 22:57:07 2014 (52D0C113)
SYMNETS.SYS                Mon Sep 23 22:41:10 2013 (5240FBC6)
EX64.SYS                   Thu Aug 22 16:36:51 2013 (52167663)
eeCtrl64.sys               Wed Oct 09 16:50:19 2013 (5255C18B)
EraserUtilRebootDrv.sys    Wed Oct 09 16:50:19 2013 (5255C18B)
ENG64.SYS                  Thu Aug 22 16:38:20 2013 (521676BC)
IDSvia64.sys               Thu Dec 05 20:53:44 2013 (52A12E28)
BHDrvx64.sys               Thu Dec 05 17:05:28 2013 (52A0F8A8)[/FONT]

Code:

[FONT=lucida console]
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\021814-10374-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Feb 18 09:39:50.098 2014 (UTC - 5:00)
System Uptime: 0 days 19:14:14.972
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::SetShape+157 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`003632f7 fffff880`15190ea0 00000000`00000000
BiosVersion = 4001
BiosReleaseDate = 06/12/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\021614-11325-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Sun Feb 16 12:00:39.112 2014 (UTC - 5:00)
System Uptime: 3 days 23:41:02.050
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::SetShape+157 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`003232f7 fffff880`15d3aea0 00000000`00000000
BiosVersion = 4001
BiosReleaseDate = 06/12/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\020614-10483-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Thu Feb  6 12:59:59.055 2014 (UTC - 5:00)
System Uptime: 1 days 22:52:26.688
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::SetShape+157 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`002c32f7 fffff880`0867dea0 00000000`00000000
BiosVersion = 4001
BiosReleaseDate = 06/12/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\020414-13462-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Tue Feb  4 14:06:47.914 2014 (UTC - 5:00)
System Uptime: 2 days 17:52:01.084
Probably caused by : win32k.sys ( win32k!W32PIDLOCK::vLockSingleThread+22 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!W32PIDLOCK::vLockSingleThread+22
Bugcheck code 0000000A
Arguments 00000000`001e0874 00000000`00000002 00000000`00000001 fffff800`038c893c
BiosVersion = 4001
BiosReleaseDate = 06/12/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\SysnativeBSODApps\012014-10826-01.dmp]
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Debug session time: Mon Jan 20 14:38:47.346 2014 (UTC - 5:00)
System Uptime: 3 days 17:02:33.244
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::SetShape+157 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  dwm.exe
FAILURE_BUCKET_ID:  X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`003132f7 fffff880`02b6bea0 00000000`00000000
BiosVersion = 4001
BiosReleaseDate = 06/12/2012
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

        
             
       [COLOR=#555555]J. C. Griffith, Microsoft MVP (jcgriff2)[/COLOR]   
             
           [URL="http://mvp.microsoft.com/en-us/mvp/John%20C.%20Griffith-4025562"][COLOR=#555555][U]http://mvp.microsoft.com/en-us/mvp/John%20C.%20Griffith-4025562[/U][/COLOR][/URL]   

           [URL="https://www.sysnative.com"][COLOR=#555555][/COLOR][/URL][COLOR=#555555][U][URL="https://www.sysnative.com"]www.sysnative.com[/URL][/U][/COLOR]
             
           [URL="http://jcgriff2.com"][COLOR=#555555][/COLOR][/URL][COLOR=#555555][U][URL="http://www.jcgriff2.com"]www.jcgriff2.com[/URL][/U][/COLOR] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  [/FONT]

kinster45 · Feb 23, 2014

Ok Norton removed and Creative Drivers updated. For my chipset my Asmedia drivers are the newest. I ran Driver Verifier and it crashed my computer but not by ending in a BSOD like it should have. Instead it basically turned my screen into a thousand blurred lines.

jcgriff2 · Feb 23, 2014

Did it clear up?

Are your video drivers updated?

Can you swap out the video card?

kinster45 · Feb 23, 2014

jcgriff2 said:
Did it clear up?

Are your video drivers updated?

Can you swap out the video card?

I haven't had a BSOD yet so I'm guessing it's gone but I'll find out in a few days. I'll swap out the video card for good measure. Thank you so much for your help so far. I also want to state this tool you've created is absolutely awesome!

jcgriff2 · Feb 26, 2014

kinster45 said:
I also want to state this tool you've created is absolutely awesome!

Thank you!

If it is Sysnative BSOD Processing Apps 2.15.3, the author is Admin writhziden

If it is BSOD Posting Instructions - the author is me!

Kind Regards. . .

jcgriff2

nabilishes · Jun 1, 2014

What is the tool you used to check whether the drivers are updated on not updated?

BSOD dwm.exe - Windows 7 x64

kinster45

New member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

kinster45

New member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

kinster45

New member

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

nabilishes

New member

BSOD dwm.exe - Windows 7 x64

New member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

New member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

New member

Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.)

New member

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)