Windows has recovered from an unexpected shutdown

[Brazen87]

Hey guys, my laptop keeps crashing to bluescreen. Its only about 2 weeks old and I don't really know much about how to resolve issues, can someone please help??

Here is the message I receive upon reboot of OS:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 3081
Additional information about the problem:
BCCode: c5
BCP1: 0000000000000008
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF80002FAB0BF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1
Files that help describe the problem:
C:\Windows\Minidump\060710-22074-01.dmp
C:\Users\Bo\AppData\Local\Temp\WER-53118-0.sysdata.xml

The only new programs I installed are itunes, VLC and some automatic updates for Microsoft Office. I repaired both itunes & VLC, uninstalled the Office updates as an attempt to repair wasn't possible due to the fact that Windows couldn't find where the program files were. I also cleaned the disk and will defrag If the problem continues. Any Ideas??

 

[richc46]

Welcome,

We would like to help but we need your cooperation, first. Follow these directives.

http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

 

[Brazen87]

Sure thing mate, attached is the zip folder of DMP files.

Sorry it took so long, got BSOD while attempting upload.

 

[richc46]

Here is the result of the mini dump. The cause of your problem can have several potential causes. Here are two threads that relate to your problem. Give it a try, aske questions, and lets hope for the best.

Its just a guess, but I would update all graphic cards, and all drivers.
Download and run memtest86
.http://www.geekstogo.com/forum/Guide-to-using-Memtest86-t246994.html

Here are the opinions of others.

dxgmms1.sys crash – Blue Screen Of Death
dxgmms1.sys - nV News Forums
and from our own Forum
http://www.sevenforums.com/crashes-debugging/38569-bsod-running-crysis-dxgmms1-sys.html

   ..........................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa805ddbe44c, 0, fffff8800534ee99, 5}
 
Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+5 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa805ddbe44c, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800534ee99, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000005, (reserved)
Debugging Details:
------------------
 
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030af0e0
 fffffa805ddbe44c 
FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+5
fffff880`0534ee99 48894c2408      mov     qword ptr [rsp+8],rcx
MM_INTERNAL_CODE:  5
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  dwm.exe
CURRENT_IRQL:  0
TRAP_FRAME:  fffff880057808d0 -- (.trap 0xfffff880057808d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8008d3c000
rdx=fffff8a008bfa6c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800534ee99 rsp=fffff88005780a68 rbp=fffff8a001d1b000
 r8=0000000000000000  r9=0000000000000002 r10=fffff880053448d0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x5:
fffff880`0534ee99 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff880`05780a70=0000000000000000
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff80002ef6801 to fffff80002e77600
STACK_TEXT:  
fffff880`05780768 fffff800`02ef6801 : 00000000`00000050 fffffa80`5ddbe44c 00000000`00000000 fffff880`057808d0 : nt!KeBugCheckEx
fffff880`05780770 fffff800`02e756ee : 00000000`00000000 00000000`00000000 fffff880`05780c00 fffff880`0526c906 : nt! ?? ::FNODOBFM::`string'+0x40ecb
fffff880`057808d0 fffff880`0534ee99 : fffff880`05335260 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`05780a68 fffff880`05335260 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+0x5
fffff880`05780a70 fffff880`0529ee9f : 00000000`01d0eed0 fffffa80`08d34000 00000000`01ae8018 fffff880`0524107b : dxgmms1!VidMmBeginCPUAccess+0x28
fffff880`05780ac0 fffff880`0529f566 : fffff8a0`01bd7740 fffff8a0`01bd7740 fffff880`05780ca0 00000000`00000000 : dxgkrnl!DXGDEVICE::Lock+0x287
fffff880`05780b20 fffff960`0022b416 : 00000000`01d0eed0 00000000`00000400 00000000`000007db fffff8a0`01d1b000 : dxgkrnl!DxgkLock+0x22a
fffff880`05780bf0 fffff800`02e76853 : fffffa80`09436060 fffff880`05780c01 fffffa80`048c0e40 fffffa80`00000000 : win32k!NtGdiDdDDILock+0x12
fffff880`05780c20 000007fe`ff90148a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01d0eea8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff90148a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+5
fffff880`0534ee99 48894c2408      mov     qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+5
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME:  dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+5
BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::BeginCPUAccess+5
Followup: MachineOwner
---------