Hi!
This is my first post, so please let me know if you need more information, or I'm missing something.
We've had about 8 HP workstations all have Blue Screens only when users log do a log off or shutdown.
This occurrence is profile specific, meaning if this happens for 1 user on a particular workstation, it will not happen if I log in to the same workstation and do a log off/shutdown. These are all HP desktops, different models, different RAM, CPU, etc. All 8 are running Windows 7 Enterprise 64-bit. We run SCCM 2013 to push out our updates and run Symantec Antivirus.
We've gotten around the issue by just recreating the affect user's profile. However, this is only a workaround and if there is better solution, we are open to suggestion.
These blue screens have all occurred after the latest Windows 7 Updates were applied (June 2015). NOTE - in our organization, we only install security patches or mandatory updates.
I've checked the dumps and the analysis is the same...
*******************************************************************************
* *
* 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: fffff900c0119050, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600022283c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
READ_ADDRESS: fffff900c0119050 Paged session pool
FAULTING_IP:
win32k!SpNotifyLSurfaceRedirSurfAssoc+14
fffff960`0022283c 488b4940 mov rcx,qword ptr [rcx+40h]
MM_INTERNAL_CODE: 0
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 556356ff
MODULE_NAME: win32k
FAULTING_MODULE: fffff96000040000 win32k
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
TRAP_FRAME: fffff88002d52630 -- (.trap 0xfffff88002d52630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff900c0119010
rdx=000000000512086e rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600022283c rsp=fffff88002d527c0 rbp=0000000000000000
r8=fffff900c215f5a8 r9=0000000000000000 r10=00000000000017c7
r11=fffff88002d52810 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
win32k!SpNotifyLSurfaceRedirSurfAssoc+0x14:
fffff960`0022283c 488b4940 mov rcx,qword ptr [rcx+40h] ds:fffff900`c0119050=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002f43c07 to fffff80002ec7a40
STACK_TEXT:
fffff880`02d524c8 fffff800`02f43c07 : 00000000`00000050 fffff900`c0119050 00000000`00000000 fffff880`02d52630 : nt!KeBugCheckEx
fffff880`02d524d0 fffff800`02ec5b6e : 00000000`00000000 fffff900`c0119050 fffff900`c1c05c00 fffff900`c215f7a8 : nt! ?? ::FNODOBFM::`string'+0x41c2f
fffff880`02d52630 fffff960`0022283c : 000007ed`c021be38 fffff960`0010900b fffff900`c0772010 fffff960`001de820 : nt!KiPageFault+0x16e
fffff880`02d527c0 fffff960`002ce041 : fffff900`c0119010 fffff900`c215f7a8 fffff900`c215f5a8 fffff960`002ce670 : win32k!SpNotifyLSurfaceRedirSurfAssoc+0x14
fffff880`02d52810 fffff960`002cda41 : fffff900`c0772010 00000000`00000001 fffff900`c215f590 00000000`0512086e : win32k!SFMLOGICALSURFACE::SetShape+0xd1
fffff880`02d52860 fffff960`002cea77 : 00000000`00000000 00000000`0512086e fffff900`c0772010 00000000`00000002 : win32k!SFMLOGICALSURFACE:
eInitialize+0x71
fffff880`02d528a0 fffff960`001101b5 : 00000000`0512086e 00000000`00000001 00000000`00000268 00000000`00000000 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`02d528e0 fffff960`00277f6d : 00000000`00000268 00000000`00000001 00000000`00000000 00000000`4d504f47 : win32k!NtGdiCloseProcess+0x6d
fffff880`02d52940 fffff960`00131fe5 : 00000000`00000000 fffff880`07419000 fffff8a0`06ac82a0 fffff880`0000028d : win32k!MultiUserNtGreCleanup+0x8d
fffff880`02d52980 fffff800`0311192c : 00000000`00000001 00000000`00000000 fffff880`07419000 fffffa80`0735cb50 : win32k!Win32KDriverUnload+0xa5
fffff880`02d529d0 fffff800`03211435 : fffff880`02d52a68 00000000`0000002a 00000000`00000000 fffff880`07419000 : nt!MiDereferenceSessionFinal+0xfc
fffff880`02d52a70 fffff800`02e99954 : fffff800`0305a940 fffff8a0`12d3c5e0 00000000`00000000 fffffa80`07108b30 : nt! ?? ::NNGAKEGL::`string'+0x2a3b5
fffff880`02d52aa0 fffff800`0319c156 : fffff8a0`12d3c5e0 00000000`00000000 fffffa80`0735cb50 fffffa80`0735cb50 : nt!MmCleanProcessAddressSpace+0x628
fffff880`02d52af0 fffff800`0319c52d : fffff8a0`00000000 fffff800`03161a01 00000000`00000000 fffffa80`08d3c3e0 : nt!PspExitThread+0x56a
fffff880`02d52bf0 fffff800`02eb9426 : fffff880`03172180 00000000`00000080 fffffa80`0735cb50 fffff880`02d52d40 : nt!PspTerminateThreadByPointer+0x4d
fffff880`02d52c40 00000000`00000000 : fffff880`02d53000 fffff880`02d4d000 fffff880`0c610740 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!SpNotifyLSurfaceRedirSurfAssoc+14
fffff960`0022283c 488b4940 mov rcx,qword ptr [rcx+40h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!SpNotifyLSurfaceRedirSurfAssoc+14
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7601.18869
FAILURE_BUCKET_ID: X64_0x50_win32k!SpNotifyLSurfaceRedirSurfAssoc+14
BUCKET_ID: X64_0x50_win32k!SpNotifyLSurfaceRedirSurfAssoc+14
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x50_win32k!spnotifylsurfaceredirsurfassoc+14
FAILURE_ID_HASH: {f5333549-c6e4-fdbc-f193-fb7666686780}
Followup: MachineOwner
---------
Has anyone else experienced this? I can't seem to find any posts with this specific issue.
I'm thinking something somehow in the particular Windows profile has been corrupted but can't figure out what or how to resolve.
This is my first post, so please let me know if you need more information, or I'm missing something.
We've had about 8 HP workstations all have Blue Screens only when users log do a log off or shutdown.
This occurrence is profile specific, meaning if this happens for 1 user on a particular workstation, it will not happen if I log in to the same workstation and do a log off/shutdown. These are all HP desktops, different models, different RAM, CPU, etc. All 8 are running Windows 7 Enterprise 64-bit. We run SCCM 2013 to push out our updates and run Symantec Antivirus.
We've gotten around the issue by just recreating the affect user's profile. However, this is only a workaround and if there is better solution, we are open to suggestion.
These blue screens have all occurred after the latest Windows 7 Updates were applied (June 2015). NOTE - in our organization, we only install security patches or mandatory updates.
I've checked the dumps and the analysis is the same...
*******************************************************************************
* *
* 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: fffff900c0119050, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600022283c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
READ_ADDRESS: fffff900c0119050 Paged session pool
FAULTING_IP:
win32k!SpNotifyLSurfaceRedirSurfAssoc+14
fffff960`0022283c 488b4940 mov rcx,qword ptr [rcx+40h]
MM_INTERNAL_CODE: 0
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 556356ff
MODULE_NAME: win32k
FAULTING_MODULE: fffff96000040000 win32k
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre
TRAP_FRAME: fffff88002d52630 -- (.trap 0xfffff88002d52630)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff900c0119010
rdx=000000000512086e rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600022283c rsp=fffff88002d527c0 rbp=0000000000000000
r8=fffff900c215f5a8 r9=0000000000000000 r10=00000000000017c7
r11=fffff88002d52810 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
win32k!SpNotifyLSurfaceRedirSurfAssoc+0x14:
fffff960`0022283c 488b4940 mov rcx,qword ptr [rcx+40h] ds:fffff900`c0119050=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002f43c07 to fffff80002ec7a40
STACK_TEXT:
fffff880`02d524c8 fffff800`02f43c07 : 00000000`00000050 fffff900`c0119050 00000000`00000000 fffff880`02d52630 : nt!KeBugCheckEx
fffff880`02d524d0 fffff800`02ec5b6e : 00000000`00000000 fffff900`c0119050 fffff900`c1c05c00 fffff900`c215f7a8 : nt! ?? ::FNODOBFM::`string'+0x41c2f
fffff880`02d52630 fffff960`0022283c : 000007ed`c021be38 fffff960`0010900b fffff900`c0772010 fffff960`001de820 : nt!KiPageFault+0x16e
fffff880`02d527c0 fffff960`002ce041 : fffff900`c0119010 fffff900`c215f7a8 fffff900`c215f5a8 fffff960`002ce670 : win32k!SpNotifyLSurfaceRedirSurfAssoc+0x14
fffff880`02d52810 fffff960`002cda41 : fffff900`c0772010 00000000`00000001 fffff900`c215f590 00000000`0512086e : win32k!SFMLOGICALSURFACE::SetShape+0xd1
fffff880`02d52860 fffff960`002cea77 : 00000000`00000000 00000000`0512086e fffff900`c0772010 00000000`00000002 : win32k!SFMLOGICALSURFACE:
fffff880`02d528a0 fffff960`001101b5 : 00000000`0512086e 00000000`00000001 00000000`00000268 00000000`00000000 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`02d528e0 fffff960`00277f6d : 00000000`00000268 00000000`00000001 00000000`00000000 00000000`4d504f47 : win32k!NtGdiCloseProcess+0x6d
fffff880`02d52940 fffff960`00131fe5 : 00000000`00000000 fffff880`07419000 fffff8a0`06ac82a0 fffff880`0000028d : win32k!MultiUserNtGreCleanup+0x8d
fffff880`02d52980 fffff800`0311192c : 00000000`00000001 00000000`00000000 fffff880`07419000 fffffa80`0735cb50 : win32k!Win32KDriverUnload+0xa5
fffff880`02d529d0 fffff800`03211435 : fffff880`02d52a68 00000000`0000002a 00000000`00000000 fffff880`07419000 : nt!MiDereferenceSessionFinal+0xfc
fffff880`02d52a70 fffff800`02e99954 : fffff800`0305a940 fffff8a0`12d3c5e0 00000000`00000000 fffffa80`07108b30 : nt! ?? ::NNGAKEGL::`string'+0x2a3b5
fffff880`02d52aa0 fffff800`0319c156 : fffff8a0`12d3c5e0 00000000`00000000 fffffa80`0735cb50 fffffa80`0735cb50 : nt!MmCleanProcessAddressSpace+0x628
fffff880`02d52af0 fffff800`0319c52d : fffff8a0`00000000 fffff800`03161a01 00000000`00000000 fffffa80`08d3c3e0 : nt!PspExitThread+0x56a
fffff880`02d52bf0 fffff800`02eb9426 : fffff880`03172180 00000000`00000080 fffffa80`0735cb50 fffff880`02d52d40 : nt!PspTerminateThreadByPointer+0x4d
fffff880`02d52c40 00000000`00000000 : fffff880`02d53000 fffff880`02d4d000 fffff880`0c610740 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!SpNotifyLSurfaceRedirSurfAssoc+14
fffff960`0022283c 488b4940 mov rcx,qword ptr [rcx+40h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!SpNotifyLSurfaceRedirSurfAssoc+14
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.1.7601.18869
FAILURE_BUCKET_ID: X64_0x50_win32k!SpNotifyLSurfaceRedirSurfAssoc+14
BUCKET_ID: X64_0x50_win32k!SpNotifyLSurfaceRedirSurfAssoc+14
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x50_win32k!spnotifylsurfaceredirsurfassoc+14
FAILURE_ID_HASH: {f5333549-c6e4-fdbc-f193-fb7666686780}
Followup: MachineOwner
---------
Has anyone else experienced this? I can't seem to find any posts with this specific issue.
I'm thinking something somehow in the particular Windows profile has been corrupted but can't figure out what or how to resolve.
My Computer
At a glance
Windows 7 Enterprise 64-bit
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- HP
- OS
- Windows 7 Enterprise 64-bit

