Quantcast
Channel: Windows 7 Miscellaneous forum
Viewing all articles
Browse latest Browse all 11372

BSOD in DWM with Intel Haswell HD4600

$
0
0

Hello People and THANKS beforehand for the help,

I am at wits end with a BSOD problem.  I just bought and assembled a new computer Specs:


Specs (from Piriform Speccy):

OS: Windows 7 Ultimate 64-bit SP1
CPU: Intel Core i7 4770k @ 3.50 GHz
RAM: 8.00 GB Single-Channel DDR3 @ 799 MHz (11-11-11-28)
Motherboard: ASUSTeK Computer Inc. Z870A (Socket 1150)
Graphics:
 Sony TV (1280x720 running at 59 Hz) - Connecting HDMI to my TV
 Intel HD Graphics 4600
Storage: 931GB Western Digital WDC WD10EZEX-00BN5A0 ATA Device
Optical Drives: ASUS DRW-24F1ST a ATA Device
Audio: Intel Display Audio

I do not that the Intel Audio sometimes shows a disturbing sound effect when using Pandora, like ("brrr" or "bzzz") and you almost think it is going to BSOD but it doesn't.  I never have these BSOD's while using the computer, it is generally overnight while running CPU intensive Excel and VB macros.  During this time, I am not using any computer sound, i.e. not connected to Pandora, and the TV is turned off.  The system sits at high CPU running my macros against Excel data.

BSoD codes:
SYSTEM_SERVICE_EXCEPTION (3b)
DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)


I have updated to the latest motherboard BIOS, latest Intel HD4600 drivers, and latest sound card drivers (although I'm using Intel sound).  I do use my Sony TV connected via HDMI as the monitor.

Here are the two related Bug Checks.  I had driver verifier on everything in BUG CHECK #2 and only on non-Microsoft drivers in BUG CHECK #1.  For Bug Check #1 I had also disabled Hyper-threading of CPU's in the BIOS, so this didn't help.

************ BUG CHECK #1 *******************
----------------------------------------------

BugCheck 3B, {c0000005, fffff960002a3267, fffff8800928dea0, 0}
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960002a3267, Address of the instruction which caused the bugcheck
Arg3: fffff8800928dea0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

Page 1d02c6 not present in the dump file. Type ".hh dbgerr004" for details

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

FAULTING_IP:
win32k!SFMLOGICALSURFACE::SetShape+157
fffff960`002a3267 488b5508        mov     rdx,qword ptr [rbp+8]

CONTEXT:  fffff8800928dea0 -- (.cxr 0xfffff8800928dea0;r)
rax=fffff8800928e8c8 rbx=0000000000000000 rcx=fffff900c7b47450
rdx=fffff900c00ba010 rsi=0000000000000000 rdi=fffff900c7b47450
rip=fffff960002a3267 rsp=fffff8800928e880 rbp=0000000000000018
 r8=ffffffffc412080f  r9=00000000000007bb r10=0000000000001731
r11=fffff8800928e8b0 r12=0000000000000001 r13=fffff900c00ba010
r14=fffff900c00ba010 r15=8000000000001000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!SFMLOGICALSURFACE::SetShape+0x157:
fffff960`002a3267 488b5508        mov     rdx,qword ptr [rbp+8] ss:0018:00000000`00000020=????????????????
Last set context:
rax=fffff8800928e8c8 rbx=0000000000000000 rcx=fffff900c7b47450
rdx=fffff900c00ba010 rsi=0000000000000000 rdi=fffff900c7b47450
rip=fffff960002a3267 rsp=fffff8800928e880 rbp=0000000000000018
 r8=ffffffffc412080f  r9=00000000000007bb r10=0000000000001731
r11=fffff8800928e8b0 r12=0000000000000001 r13=fffff900c00ba010
r14=fffff900c00ba010 r15=8000000000001000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!SFMLOGICALSURFACE::SetShape+0x157:
fffff960`002a3267 488b5508        mov     rdx,qword ptr [rbp+8] ss:0018:00000000`00000020=????????????????
Resetting default scope

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER:  from fffff960001f9dbc to fffff960002a3267

STACK_TEXT: 
fffff880`0928e880 fffff960`001f9dbc : 00000000`00000000 00000000`00000001 fffff900`c2681080 fffff900`c28a9b10 : win32k!SFMLOGICALSURFACE::SetShape+0x157
fffff880`0928e8d0 fffff960`00174d0e : fffff880`00000001 fffff800`00000001 00000000`00000014 00000000`00000110 : win32k!GreTransferSpriteStateToDwmState+0x1d0
fffff880`0928e9e0 fffff960`00175743 : 00000000`00000000 fffff880`0928eb60 00000000`c0000001 fffff880`0928eb60 : win32k!zzzComposeDesktop+0x52
fffff880`0928ea80 fffff960`00109083 : 00000000`00000000 00000000`ffeda3b0 fffff880`09280000 00000000`00000018 : win32k!zzzDwmStartRedirection+0xbf
fffff880`0928eab0 fffff800`030c4e53 : fffffa80`0c1b0060 fffff880`0928eb60 fffffa80`0af25220 00000000`00000000 : win32k!NtUserDwmStartRedirection+0x6b
fffff880`0928eae0 00000000`76fa5f7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0227f6a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76fa5f7a


FOLLOWUP_IP:
win32k!SFMLOGICALSURFACE::SetShape+157
fffff960`002a3267 488b5508        mov     rdx,qword ptr [rbp+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!SFMLOGICALSURFACE::SetShape+157

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52f4357b

IMAGE_VERSION:  6.1.7601.18388

STACK_COMMAND:  .cxr 0xfffff8800928dea0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_VRF_win32k!SFMLOGICALSURFACE::SetShape+157

BUCKET_ID:  X64_0x3B_VRF_win32k!SFMLOGICALSURFACE::SetShape+157

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_vrf_win32k!sfmlogicalsurface::setshape+157

FAILURE_ID_HASH:  {463b6c85-5331-67ea-9b9d-05f489d363fd}

Followup: MachineOwner

************ BUG CHECK #2 *******************
----------------------------------------------

DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL (d5)
Memory was referenced after it was freed.
This cannot be protected by try-except.
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff900c92eecf8, memory referenced
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation
Arg3: fffff960002b9d84, if non-zero, the address which referenced memory.
Arg4: 0000000000000000, (reserved)

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

Page 1c25ef not present in the dump file. Type ".hh dbgerr004" for details

READ_ADDRESS:  fffff900c92eecf8 Special pool

FAULTING_IP:
win32k!GreTransferSpriteStateToDwmState+198
fffff960`002b9d84 8b4020          mov     eax,dword ptr [rax+20h]

MM_INTERNAL_CODE:  0

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52f4357b

MODULE_NAME: win32k

FAULTING_MODULE: fffff960000e0000 win32k

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD5

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

TRAP_FRAME:  fffff88008a25740 -- (.trap 0xfffff88008a25740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c92eecd8 rbx=0000000000000000 rcx=00000000000001fd
rdx=0000000000000007 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002b9d84 rsp=fffff88008a258d0 rbp=0000000000000001
 r8=000000000000006b  r9=fffff960003ce1fc r10=fffff88008a25ae0
r11=fffff88008a258b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
win32k!GreTransferSpriteStateToDwmState+0x198:
fffff960`002b9d84 8b4020          mov     eax,dword ptr [rax+20h] ds:fffff900`c92eecf8=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000310dbf0 to fffff8000308fbc0

STACK_TEXT: 
fffff880`08a255d8 fffff800`0310dbf0 : 00000000`00000050 fffff900`c92eecf8 00000000`00000000 fffff880`08a25740 : nt!KeBugCheckEx
fffff880`08a255e0 fffff800`0308dcee : 00000000`00000000 fffff900`c92eecf8 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`08a25740 fffff960`002b9d84 : 00000000`00000000 00000000`00000001 fffff900`cdb72fe0 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`08a258d0 fffff960`00234d0e : fffff880`00000001 fffff800`00000001 00000000`00000041 00000000`000000bf : win32k!GreTransferSpriteStateToDwmState+0x198
fffff880`08a259e0 fffff960`00235743 : 00000000`00000000 fffff880`08a25b60 00000000`c0000001 fffff880`08a25b60 : win32k!zzzComposeDesktop+0x52
fffff880`08a25a80 fffff960`001c9083 : 00000000`00000000 00000000`ff80a3b0 fffff880`08a20000 00000000`00000018 : win32k!zzzDwmStartRedirection+0xbf
fffff880`08a25ab0 fffff800`0308ee53 : fffffa80`0a3aa060 fffff880`08a25b60 fffffa80`0ae6de60 00000000`00000000 : win32k!NtUserDwmStartRedirection+0x6b
fffff880`08a25ae0 00000000`77395f7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0221f5b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77395f7a


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!GreTransferSpriteStateToDwmState+198
fffff960`002b9d84 8b4020          mov     eax,dword ptr [rax+20h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!GreTransferSpriteStateToDwmState+198

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.1.7601.18388

FAILURE_BUCKET_ID:  X64_0xD5_VRF_win32k!GreTransferSpriteStateToDwmState+198

BUCKET_ID:  X64_0xD5_VRF_win32k!GreTransferSpriteStateToDwmState+198

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd5_vrf_win32k!gretransferspritestatetodwmstate+198

FAILURE_ID_HASH:  {c3a8d87a-3ab8-71bb-6ec8-ff490f7fee0c}

Followup: MachineOwner


Viewing all articles
Browse latest Browse all 11372

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>