Hi, minidump file check - in part.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff96000106923, fffff880071df070, 0}
Probably caused by : win32k.sys ( win32k!HmgLockEx+a3 )
Followup: MachineOwner
---------
0: kd> !analyze -v
SYSTEM_SERVICE_EXCEPTION (3b)
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff960002cc1e0 to fffff96000106923
STACK_TEXT:
fffff880`071dfa40 fffff960`002cc1e0 : fffff900`c098cca0 00000000`00000001 ffffffff`8d120baf fffff900`c332bcd0 : win32k!HmgLockEx+0xa3
fffff880`071dfab0 fffff960`002cb6de : fffff900`c098cca0 00000000`00000000 00000baf`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE:OwnsSurfaceCleanup+0x40
fffff880`071dfae0 fffff960`002cc5e3 : 00000000`00000000 ffffffff`8d120baf fffff900`c098cca0 00000000`03b9b920 : win32k!SFMLOGICALSURFACE:eInitialize+0x4e
fffff880`071dfb20 fffff960`00227c9f : 00000000`00000000 fffff900`c00ca280 fffff900`c098cca0 00000000`00000000 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`071dfb60 fffff960`00249278 : 00000000`00000001 00000000`00000001 fffff880`071dfca0 fffff960`002490d0 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`071dfba0 fffff800`02ec5953 : 00000000`00000000 00000000`05c8afd0 000007fe`fa5bd601 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`071dfc20 000007fe`ff854efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03b1f148 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff854efa
FOLLOWUP_IP:
win32k!HmgLockEx+a3
fffff960`00106923 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: 54163648
STACK_COMMAND: .cxr 0xfffff880071df070 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3
BUCKET_ID: X64_0x3B_win32k!HmgLockEx+a3
Followup: MachineOwner
---------
0: kd> kc
Call Site
nt!KeBugCheckEx
nt!KiBugCheckDispatch
nt!KiSystemServiceHandler
nt!RtlpExecuteHandlerForException
nt!RtlDispatchException
nt!KiDispatchException
nt!KiExceptionDispatch
nt!KiPageFault
win32k!HmgLockEx
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup
win32k!SFMLOGICALSURFACE::eInitialize
win32k!bhLSurfDestroyLogicalSurfaceObject
win32k!GreSfmCloseCompositorRef
win32k!NtGdiHLSurfSetInformation
nt!KiSystemServiceCopyEnd
0x0
0: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`071de7a8 fffff800`02ec5c69 : 00000000`0000003b 00000000`c0000005 fffff960`00106923 fffff880`071df070 : nt!KeBugCheckEx
fffff880`071de7b0 fffff800`02ec55bc : fffff880`071df808 fffff880`071df070 00000000`00000000 fffff960`002ed374 : nt!KiBugCheckDispatch+0x69
fffff880`071de8f0 fffff800`02eec49d : fffff960`0033f4a4 00000000`00000000 fffff960`00040000 fffff880`071df808 : nt!KiSystemServiceHandler+0x7c
fffff880`071de930 fffff800`02ef3b10 : fffff800`03016198 fffff880`071de9a8 fffff880`071df808 fffff800`02e56000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`071de960 fffff800`02f00a6f : fffff880`071df808 fffff880`071df070 fffff880`00000000 fffff900`c0210000 : nt!RtlDispatchException+0x410
0: kd> kn
# Child-SP RetAddr Call Site
00 fffff880`071de7a8 fffff800`02ec5c69 nt!KeBugCheckEx
01 fffff880`071de7b0 fffff800`02ec55bc nt!KiBugCheckDispatch+0x69
02 fffff880`071de8f0 fffff800`02eec49d nt!KiSystemServiceHandler+0x7c
03 fffff880`071de930 fffff800`02ef3b10 nt!RtlpExecuteHandlerForException+0xd
04 fffff880`071de960 fffff800`02f00a6f nt!RtlDispatchException+0x410
05 fffff880`071df040 fffff800`02ec5d42 nt!KiDispatchException+0x16f
06 fffff880`071df6d0 fffff800`02ec48ba nt!KiExceptionDispatch+0xc2
07 fffff880`071df8b0 fffff960`00106923 nt!KiPageFault+0x23a
Where the blue screen error is reported, is not necessarily where it first started and may not be the cause.
And the above is not telling us much.
Some reasons for
Blue Screens
New hardware - software installed.
Device driver - Video driver - corrupted - faulty.
Faulty Ram - Overheating - Dying hard drive etc.
======
When does the blue screen happen - at start up, playing videos, games, etc?
======
Check the pc manufacturers website for any needed driver updates.
======
Run a Mem Test.
http://www.memtest.org/
Scroll down to 'Download (Pre-built & ISOs)'
'Download - Pre-Compiled Bootable ISO (.zip)'
Download the ISO file - then burn the ISO to a Cd.
Start the Pc using the Cd and run the memory test overnight or for at least 8 passes.
It is best to run a full scan on individual Ram sticks if you can.
Or run the test but if any errors are shown - then remove all sticks of Ram and test each Ram stick one at a time.
Guide to using Memtest86+
http://www.bleepingcomputer.com/forums/topic207910.html
======
Let us have some Pc specifications.
Check and post
TSG System Information Utility - found here.
http://static.techguy.org/download/SysInfo.exe
======
Download Security Check by screen317 from.
http://screen317.spywareinfoforum.org/
Or
http://www.bleepingcomputer.com/download/securitycheck/dl/123/
Save it to your Desktop.
Double click the install icon.
If using Vista - Win 7 - right click the install icon and select "Run as Administrator"
A command Prompt window will open.
Let it scan the Pc - press any key when asked.
It should now open in Notepad.
Copy and Paste the result of the scan in the reply box below.