Blue screen problem

muneer afzal said:

Dear Sir,

I just 2 days ago installed windows 7 ultimate and having problem of blue screen dump memory could u please tell me remedies to get rid of this problem?
I am also uploading files of mini dump folder.

Welcome to the forum, muneer afzal. I am going to ask the moderators to move your post to a new thread. It is too confusing to address two different poster's problems in the same thread.

hayleywilliams said:

Hello!I have same problem with Windows 7 64bit Ultimate.Everyone help me plz.This is my dmp file.Thanks a lot!!

Welcome to the forum, Hayley. I am going to ask the moderators to move your post to a new thread. It is too confusing to address two different poster's problems in the same thread.

You have a an error code of 3B, SYSTEM_SERVICE_EXCEPTION, usually caused by system service, Device driver, graphics driver, ?memory. The dump file indicates memory corruption.

Code:

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


Loading Dump File [C:\Users\Owner\Downloads\082610-26847-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02817000 PsLoadedModuleList = 0xfffff800`02a54e50
Debug session time: Thu Aug 26 08:33:05.462 2010 (GMT-4)
System Uptime: 0 days 1:03:15.929
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff96000184377, fffff88003b29030, 0}

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

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

2: 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: fffff96000184377, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003b29030, 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`00184377 0fb7430c        movzx   eax,word ptr [rbx+0Ch]

CONTEXT:  fffff88003b29030 -- (.cxr 0xfffff88003b29030)
rax=fffff900c0200000 rbx=0000000000000000 rcx=fffffa8005b6a760
rdx=fffff900c0200000 rsi=0000000000000000 rdi=fffff900c0200000
rip=fffff96000184377 rsp=fffff88003b29a00 rbp=0000000000000000
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff88003b29a68 r12=0000000006882700 r13=0000000000000000
r14=0000000000000001 r15=0000000000000001
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`00184377 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 fffff9600033c8a0 to fffff96000184377

STACK_TEXT:  
fffff880`03b29a00 fffff960`0033c8a0 : fffff900`c20e88f0 00000000`00000001 ffffffff`8e120a5b fffff900`c2bd4cd0 : win32k!HmgLockEx+0xa3
fffff880`03b29a70 fffff960`0033bd9e : fffff900`c20e88f0 00000000`00000000 00000a5b`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x40
fffff880`03b29aa0 fffff960`0033cca3 : 00000000`00000000 ffffffff`8e120a5b fffff900`c20e88f0 00000000`068827fc : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`03b29ae0 fffff960`00299777 : 00000000`00000000 fffff900`c00bf010 fffff900`c20e88f0 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`03b29b20 fffff960`002baa50 : 00000000`00000001 00000000`00000001 fffff880`03b29c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`03b29b60 fffff800`02886993 : fffffa80`05b6a760 fffffa80`05b69060 fffffa80`00000000 fffffa80`05b69060 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`03b29be0 000007fe`fd8f4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0275f958 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd8f4efa


FOLLOWUP_IP: 
win32k!HmgLockEx+a3
fffff960`00184377 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:  4c1c483f

STACK_COMMAND:  .cxr 0xfffff88003b29030 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

BUCKET_ID:  X64_0x3B_win32k!HmgLockEx+a3

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

You have two out of date drivers on your system. Older drivers can an do cause memory corruption and crashes with Win 7. Update these drivers form the manufacturers websites.

ALSysIO64.sys Sun Apr 19 15:41:04 2009 - is a driver file from company Arthur Liberman belonging to product ALSysIO64. Core Temp - CPU temperature monitorCore Temp
Rt64win7.sys Thu Feb 26 04:04:13 2009 - Realtek Wired Network Driver Realtek

After you update these two drivers, reboot and run your system. If you get another BSOD, upload it to us and enable Driver Verifier.

Driver Verifier - Enable and Disable

Keep us updated.

It looks to be hardware related with memory being corrupted by a device driver. I added more information regarding updating two drivers.

On another note, I see that you are running Avast AV. Avast should not give problems with Win 7. But that is something we want to keep in mind. Keep Avast for now and lets see if the updated drivers solve your problem. If not, we will try Driver Verifier as I mentioned above. And we will go from there.

I have another question. What firewall, if any, are you running?

Very good. Windows Firewall will not cause problems with your system.