BSOD running MSE scan, WoW error 1000007e

AlidaV · Jan 18, 2012

Hello, here is my basic information:

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64bit
- the original installed OS on the system? Yes
- an OEM or full retail version? Full Retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? Purchased + built the computer on December 26th.
- What is the age of OS installation (have you re-installed the OS?) No.

writhziden · Jan 18, 2012

Code:

[list=1]
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\AlidaV\Windows_NT6_BSOD_jcgriff2\011712-12324-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e91670
Debug session time: Tue Jan 17 19:20:26.560 2012 (UTC - 7:00)
System Uptime: 1 days 15:04:25.793
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa801906b048, 0, fffff88001409a5f, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys

Could not read faulting driver name
Probably caused by : atikmpag.sys ( atikmpag+9a5f )

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

3: 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: fffffa801906b048, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88001409a5f, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efb100
 fffffa801906b048 

FAULTING_IP: 
atikmpag+9a5f
fffff880`01409a5f 488b4008        mov     rax,qword ptr [rax+8]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800b156ff0 -- (.trap 0xfffff8800b156ff0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa801906b040 rbx=0000000000000000 rcx=fffffa800d13b000
rdx=ffffffffffe30000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001409a5f rsp=fffff8800b157180 rbp=fffffa800d13b000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffffa800d13b000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
atikmpag+0x9a5f:
fffff880`01409a5f 488b4008        mov     rax,qword ptr [rax+8] ds:bb00:fffffa80`1906b048=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c733f0 to fffff80002cc8c40

STACK_TEXT:  
fffff880`0b156e88 fffff800`02c733f0 : 00000000`00000050 fffffa80`1906b048 00000000`00000000 fffff880`0b156ff0 : nt!KeBugCheckEx
fffff880`0b156e90 fffff800`02cc6d6e : 00000000`00000000 fffffa80`1906b048 fffffa80`0d13b000 fffff880`0b157240 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`0b156ff0 fffff880`01409a5f : fffff8a0`1891f8f0 fffff880`0b157240 00000000`00010d42 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0b157180 fffff8a0`1891f8f0 : fffff880`0b157240 00000000`00010d42 00000000`00000000 ffffffff`c000000d : atikmpag+0x9a5f
fffff880`0b157188 fffff880`0b157240 : 00000000`00010d42 00000000`00000000 ffffffff`c000000d 00000000`00000001 : 0xfffff8a0`1891f8f0
fffff880`0b157190 00000000`00010d42 : 00000000`00000000 ffffffff`c000000d 00000000`00000001 fffffa80`0cf6b000 : 0xfffff880`0b157240
fffff880`0b157198 00000000`00000000 : ffffffff`c000000d 00000000`00000001 fffffa80`0cf6b000 fffffa80`0a626040 : 0x10d42


STACK_COMMAND:  kb

FOLLOWUP_IP: 
atikmpag+9a5f
fffff880`01409a5f 488b4008        mov     rax,qword ptr [rax+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  atikmpag+9a5f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME:  atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ca29309

FAILURE_BUCKET_ID:  X64_0x50_atikmpag+9a5f

BUCKET_ID:  X64_0x50_atikmpag+9a5f

Followup: MachineOwner
---------
[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\AlidaV\Windows_NT6_BSOD_jcgriff2\011712-17768-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02ea0670
Debug session time: Tue Jan 17 19:36:12.666 2012 (UTC - 7:00)
System Uptime: 0 days 0:15:09.899
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a08b2031e8, 0, fffff8800541d135, 5}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5 )

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

3: 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: fffff8a08b2031e8, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800541d135, 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 fffff80002f0a100
 fffff8a08b2031e8 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5
fffff880`0541d135 48395f18        cmp     qword ptr [rdi+18h],rbx

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  Wow.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800a468f60 -- (.trap 0xfffff8800a468f60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=0000000000000154
rdx=fffff8a011bd6000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800541d135 rsp=fffff8800a4690f0 rbp=fffff8800a469900
 r8=fffffa80074c64e8  r9=0000000000000002 r10=00000000f4dbd025
r11=0000000080005500 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x1e5:
fffff880`0541d135 48395f18        cmp     qword ptr [rdi+18h],rbx ds:8400:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c823bf to fffff80002cd7c40

STACK_TEXT:  
fffff880`0a468df8 fffff800`02c823bf : 00000000`00000050 fffff8a0`8b2031e8 00000000`00000000 fffff880`0a468f60 : nt!KeBugCheckEx
fffff880`0a468e00 fffff800`02cd5d6e : 00000000`00000000 fffff8a0`8b2031e8 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44791
fffff880`0a468f60 fffff880`0541d135 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0a4690f0 fffff880`054033e7 : fffffa80`06dda301 fffffa80`072b2f10 00000000`03ae04e8 fffff880`000000fd : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x1e5
fffff880`0a4691e0 fffff880`05552fae : fffff880`0a469260 00000000`00000200 fffff880`0a469900 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`0a469230 fffff880`05552773 : fffff8a0`00000001 fffff8a0`0e6a5f10 fffff880`0a4698b0 00000000`00000003 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`0a469840 fffff960`001bf80e : 00000000`0656e4e0 fffff880`00000200 00000000`fff29000 00000000`00000000 : dxgkrnl!DxgkRender+0x3e7
fffff880`0a469ab0 fffff800`02cd6ed3 : fffffa80`0b773b60 fffff880`0a469b60 00000000`00000000 fffffa80`0b429800 : win32k!NtGdiDdDDIRender+0x12
fffff880`0a469ae0 00000000`7311164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0656e4b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7311164a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5
fffff880`0541d135 48395f18        cmp     qword ptr [rdi+18h],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+1e5

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\AlidaV\Windows_NT6_BSOD_jcgriff2\011712-15334-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4d670
Debug session time: Tue Jan 17 20:22:39.842 2012 (UTC - 7:00)
System Uptime: 0 days 0:02:01.685
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80000c7c93c, 8, fffff80000c7c93c, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+447c6 )

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

1: 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: fffff80000c7c93c, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80000c7c93c, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb7100
 fffff80000c7c93c 

FAULTING_IP: 
+6438396639323130
fffff800`00c7c93c ??              ???

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800331bab0 -- (.trap 0xfffff8800331bab0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880009ea180
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000c7c93c rsp=fffff8800331bc40 rbp=0000000012000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=000000000002599b r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na po nc
fffff800`00c7c93c ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c2f3f0 to fffff80002c84c40

STACK_TEXT:  
fffff880`0331b948 fffff800`02c2f3f0 : 00000000`00000050 fffff800`00c7c93c 00000000`00000008 fffff880`0331bab0 : nt!KeBugCheckEx
fffff880`0331b950 fffff800`02c82d6e : 00000000`00000008 fffff800`00c7c93c fffffa80`0b00cb00 fffff880`009ea180 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`0331bab0 fffff800`00c7c93c : fffff880`009ea180 fffff880`00000002 00000000`00000002 fffff800`00000000 : nt!KiPageFault+0x16e
fffff880`0331bc40 fffff880`009ea180 : fffff880`00000002 00000000`00000002 fffff800`00000000 fffff880`0331bc70 : 0xfffff800`00c7c93c
fffff880`0331bc48 fffff880`00000002 : 00000000`00000002 fffff800`00000000 fffff880`0331bc70 00000000`00000000 : 0xfffff880`009ea180
fffff880`0331bc50 00000000`00000002 : fffff800`00000000 fffff880`0331bc70 00000000`00000000 00000000`00000000 : 0xfffff880`00000002
fffff880`0331bc58 fffff800`00000000 : fffff880`0331bc70 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2
fffff880`0331bc60 fffff880`0331bc70 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00000000
fffff880`0331bc68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`0331bc70


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+447c6
fffff800`02c2f3f0 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+447c6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+447c6

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+447c6

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\AlidaV\Windows_NT6_BSOD_jcgriff2\011712-11029-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e5f670
Debug session time: Tue Jan 17 21:17:42.850 2012 (UTC - 7:00)
System Uptime: 0 days 0:48:44.083
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {18, 2, 0, fffff80002d42077}

Probably caused by : memory_corruption ( nt!MiIdentifyPfn+317 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000018, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002d42077, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec9100
 0000000000000018 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiIdentifyPfn+317
fffff800`02d42077 488b4118        mov     rax,qword ptr [rcx+18h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff880066ec3a0 -- (.trap 0xfffff880066ec3a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000007c555 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002d42077 rsp=fffff880066ec530 rbp=fffffa800c30e100
 r8=000000000013df57  r9=0000000000000001 r10=0000000000000042
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiIdentifyPfn+0x317:
fffff800`02d42077 488b4118        mov     rax,qword ptr [rcx+18h] ds:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c961e9 to fffff80002c96c40

STACK_TEXT:  
fffff880`066ec258 fffff800`02c961e9 : 00000000`0000000a 00000000`00000018 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`066ec260 fffff800`02c94e60 : 00000000`42506650 00000000`00000000 00000000`00000000 02000000`9220c4cb : nt!KiBugCheckDispatch+0x69
fffff880`066ec3a0 fffff800`02d42077 : 00000000`00000000 02000000`0005c96f 00000000`42506600 fffff800`02f8273f : nt!KiPageFault+0x260
fffff880`066ec530 fffff800`02d42c7b : 00000000`00000000 00000000`00000004 fffffa80`11f6a750 fffffa80`11f69000 : nt!MiIdentifyPfn+0x317
fffff880`066ec5d0 fffff800`030a77e5 : fffffa80`11f69000 fffff880`066ecb60 fffff880`066ec6a8 00000000`00000000 : nt!MmQueryPfnList+0xbb
fffff880`066ec610 fffff800`02fea4c8 : 00000000`00000006 00000000`00000000 fffffa80`11f69000 00000000`00000001 : nt!PfpPfnPrioRequest+0x115
fffff880`066ec660 fffff800`02fa0bd3 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`066ec701 : nt! ?? ::NNGAKEGL::`string'+0x4810d
fffff880`066ec6f0 fffff800`02fa1449 : 00000000`0132b6e8 fffff800`02ca2f58 00000000`0132b740 00000000`ffffffff : nt!ExpQuerySystemInformation+0x1193
fffff880`066ecaa0 fffff800`02c95ed3 : 00000000`01f1f938 fffff880`066ecb60 00000000`01f56290 00000000`02aaf800 : nt!NtQuerySystemInformation+0x4d
fffff880`066ecae0 00000000`772c167a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0132b608 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772c167a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiIdentifyPfn+317
fffff800`02d42077 488b4118        mov     rax,qword ptr [rcx+18h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiIdentifyPfn+317

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+317

BUCKET_ID:  X64_0xA_nt!MiIdentifyPfn+317

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

[*]
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\AlidaV\Windows_NT6_BSOD_jcgriff2\011712-16598-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02ea3670
Debug session time: Tue Jan 17 22:41:30.221 2012 (UTC - 7:00)
System Uptime: 0 days 0:56:20.454
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc000001d, fffff880030b7dc8, fffff880065bb308, fffff880065bab60}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkCddGdiCommand+0 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff880030b7dc8, The address that the exception occurred at
Arg3: fffff880065bb308, Exception Record Address
Arg4: fffff880065bab60, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
dxgkrnl!DxgkCddGdiCommand+0
fffff880`030b7dc8 48895c2408      mov     qword ptr [rsp+8],rbx

EXCEPTION_RECORD:  fffff880065bb308 -- (.exr 0xfffff880065bb308)
ExceptionAddress: fffff880030b7dc8 (dxgkrnl!DxgkCddGdiCommand)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880065bab60 -- (.cxr 0xfffff880065bab60)
rax=0000000000000003 rbx=0000000000000000 rcx=fffff880065bb6b0
rdx=0000000000000000 rsi=0000000000000240 rdi=fffff900c00c04e8
rip=fffff880030b7dc8 rsp=fffff880065bb548 rbp=fffff900c00bf020
 r8=0000000000000000  r9=0000000000000000 r10=fffffffffffffff7
r11=fffff880065bb838 r12=0000000000000001 r13=0000000000000000
r14=0000000000000001 r15=0000000000000004
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
dxgkrnl!DxgkCddGdiCommand:
fffff880`030b7dc8 48895c2408      mov     qword ptr [rsp+8],rbx ss:0018:fffff880`065bb550=0000000000000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER:  from fffff9600072b264 to fffff880030b7dc8

FAILED_INSTRUCTION_ADDRESS: 
dxgkrnl!DxgkCddGdiCommand+0
fffff880`030b7dc8 48895c2408      mov     qword ptr [rsp+8],rbx

STACK_TEXT:  
fffff880`065bb548 fffff960`0072b264 : 00000000`00000000 00000000`00000000 fffff900`c00bf020 00000000`00000000 : dxgkrnl!DxgkCddGdiCommand
fffff880`065bb550 fffff960`007295d5 : fffffa80`0b083190 fffffa80`0b083190 00000000`00000000 fffff900`c00bf020 : cdd!CHwCommandBuffer::FlushGdiCommands+0xb4
fffff880`065bb840 fffff960`00725c6e : ffffffff`fffd74f6 00000000`00000010 00000000`00000001 fffff900`00000000 : cdd!CDDPDEV::FlushGdiOutput+0x81
fffff880`065bb870 fffff800`02f75fee : 00000000`01bed4b1 fffffa80`0b0d3b60 00000000`00000080 fffffa80`0b082b30 : cdd!PresentWorkerThread+0x902
fffff880`065bbc00 fffff800`02ccc5e6 : fffff880`033d7180 fffffa80`0b0d3b60 fffff880`033e1fc0 0000004b`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`065bbc40 00000000`00000000 : fffff880`065bc000 fffff880`065b6000 fffff880`065bb3a0 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP: 
dxgkrnl!DxgkCddGdiCommand+0
fffff880`030b7dc8 48895c2408      mov     qword ptr [rsp+8],rbx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgkrnl!DxgkCddGdiCommand+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799fa

STACK_COMMAND:  .cxr 0xfffff880065bab60 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_dxgkrnl!DxgkCddGdiCommand+0

BUCKET_ID:  X64_0x7E_BAD_IP_dxgkrnl!DxgkCddGdiCommand+0

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


[/list]

If you are overclocking anything, please stop.

Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers...
- The driver blamed is your display card driver.
  - Make sure Catalyst Control Center/AMD Vision Engine Control Center is not overclocking your display card.
  - Install the latest driver for the display card, or re-install it if it is already the latest. Use the following steps.
    
    Download the latest drivers for your display card(s)
    
    Click Start Menu
    
    Right Click My Computer/Computer
    
    Click Manage
    
    Click Device Manager from the list on the left
    
    Expand Display adapters
    
    Do the following for each adapter (in case you have multiple display cards)
    
    Right click the adapter
    
    Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    
    Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    
    Restart your computer after uninstalling drivers for all display cards
    
    Install the latest driver for the display cards once Windows starts
    
    Alternatively:
    
    Login as an adminstrative user
    
    Download the latest drivers for your display card(s)
    
    Click Start Menu
    
    Click Control Panel
    
    Click Hardware and Sound
    
    Click Device Manager (the last link under Devices and Printers)
    
    Expand Display adapters
    
    Do the following for each adapter (in case you have multiple display cards)
    
    Right click the adapter
    
    Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
    
    Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    
    Restart your computer after uninstalling drivers for all display cards
    
    Install the latest driver for the display cards once Windows starts
- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
- Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.
- Install all updates through Windows Updates.
- An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
Same as 1. except DirectX is blamed. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers...

Follow the steps for Diagnosing basic problems with DirectX. Use the same steps as in 1. for re-installing the display card if you feel the need to do so again.
Same as 1. and 2. except system process was blamed. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers...
Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates...
Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
Update the following driver.
Code:
```
GEARAspiWDM	fffff880`03062000	fffff880`0306f000	Mon May 18 06:17:04 2009 (4a1151c0)	000159b4		GEARAspiWDM.sys
```
You may use the following sites as references for finding drivers. We recommend finding the manufacturer of the driver and downloading drivers directly from the manufacturer or software developer. If you have trouble finding a driver or driver manufacturer, let us know and we will do our best to assist you. If you need help, please provide the device name, manufacturer, and the driver .sys file that you are looking for.
1. Driver Reference is a good site to find the driver .sys files, their descriptions, and the site most likely to contain an update.
2. Driver Search Methods provides driver manufacturers and links to their homepages.
There are a few methods for updating drivers.
To fully re-install a driver, use the following steps.
1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Restart your computer
10. Install the latest driver for the device once Windows starts.
Alternatively:
1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer
11. Install the latest driver for the device once Windows starts.

Thanks to Dave76 for help understanding possible causes.

AlidaV · Jan 18, 2012

Thank you for the quick response.
I tried reinstalling my display driver last night and got a BSOD.

I have tried again using your method (uninstalling, deleting software, restarting the computer and reinstalling). I had a BSOD on the reboot after uninstalling and deleting software. After BSOD/reboot, windows performed a disk check automatically and deleted/repaired some system files. After this happened, it could not boot into windows and suggested I launch startup repair (which I did). I attempted a system restore. This worked, and I booted successfully into windows only to be met with a BSOD.

At this point, I was unable to boot into windows normally. I booted into safe mode and did a system restore to the earliest point I could.

Although this partially worked, it still froze when I ran MSE. MSE and all antivirus software turned itself off automatically at random intervals. I am guessing this is a virus and I am reformatting the hard drive/reinstalling everything at the moment. Wish me luck.

writhziden · Jan 18, 2012

AlidaV said:
Thank you for the quick response.
I tried reinstalling my display driver last night and got a BSOD.

I have tried again using your method (uninstalling, deleting software, restarting the computer and reinstalling). I had a BSOD on the reboot after uninstalling and deleting software. After BSOD/reboot, windows performed a disk check automatically and deleted/repaired some system files. After this happened, it could not boot into windows and suggested I launch startup repair (which I did). I attempted a system restore. This worked, and I booted successfully into windows only to be met with a BSOD.

At this point, I was unable to boot into windows normally. I booted into safe mode and did a system restore to the earliest point I could.

Although this partially worked, it still froze when I ran MSE. MSE and all antivirus software turned itself off automatically at random intervals. I am guessing this is a virus and I am reformatting the hard drive/reinstalling everything at the moment. Wish me luck.

Good luck! If that does not work, you will want to do a clean all through Diskpart before installing to clean out any possible rootkit virus infections. The instructions for a clean all can be found in the http://www.sevenforums.com/tutorials/52129-disk-clean-clean-all-diskpart-command.html instructions.

AlidaV · Jan 18, 2012

Thank you again for the advice!

I ran clean all through diskpart and it completely successfully. However, when I set it to install windows... I got a BSOD.

What could possibly be causing problems? Is it a hardware problem of some kind?

I am very frustrated because the system is very new, so hardware problems seem very unlikely.

Thank you for your time.

EDIT: It may have been because I didn't reformat the disk to NTFS. I'm really, really hoping this is the problem.

writhziden · Jan 19, 2012

AlidaV said:
Thank you again for the advice!

I ran clean all through diskpart and it completely successfully. However, when I set it to install windows... I got a BSOD.

What could possibly be causing problems? Is it a hardware problem of some kind?

I am very frustrated because the system is very new, so hardware problems seem very unlikely.

Thank you for your time.

EDIT: It may have been because I didn't reformat the disk to NTFS. I'm really, really hoping this is the problem.

New hardware can be faulty when bought. It can also be damaged during assembly if electrostatic discharge safety techniques are not used. Additionally, I have seen a number of cases where users bought memory that was not compatible with the motherboard or added memory that was not compatible with the memory already in the machine. It is rare for the motherboard, CPU, or graphics card to be faulty when bought, but it does happen. You will have to go through the hardware diagnostics tools and see if you can determine any problems.

You may also want to check that all your connectors are connected properly for fans, power, etc. I had a system behave very strangely once throwing up lots of temperature related alarms just because I swapped two fan connectors.

AlidaV · Jan 19, 2012

Hello again,

After properly partitioning everything, windows 7 installed without a hitch.

However, as soon as I installed all the drivers I got a BSOD with the following reason: MEMORY_MANAGEMENT. It doesn't seem to have left a log for me anywhere, so I don't have any more data.

I'm running the memory diagnostic tool right now and hoping that I find something.

writhziden · Jan 19, 2012

AlidaV said:
Hello again,

After properly partitioning everything, windows 7 installed without a hitch.

However, as soon as I installed all the drivers I got a BSOD with the following reason: MEMORY_MANAGEMENT. It doesn't seem to have left a log for me anywhere, so I don't have any more data.

I'm running the memory diagnostic tool right now and hoping that I find something.

Memory management points to a memory problem or drivers. Checking your memory is a good first step.

AlidaV · Jan 19, 2012

I ran windows memory diagnostic for two passes on standard and found no problems. I am now running it on extended while I'm at school in the hopes that it finds something. I have also emailed NCIX (which is where I bought the parts) to see what they think. Hopefully if they take it in for repairs it does not cost me too much money.

writhziden · Jan 19, 2012

AlidaV said:
I ran windows memory diagnostic for two passes on standard and found no problems. I am now running it on extended while I'm at school in the hopes that it finds something. I have also emailed NCIX (which is where I bought the parts) to see what they think. Hopefully if they take it in for repairs it does not cost me too much money.

Don't forget to run Memtest86+ as well. Sometimes Windows diagnostic does not pick up errors that Memtest86+ does, and vice versa. Occasionally, neither picks up errors and we have to troubleshoot memory just by removing modules and running Windows normally to see if the crashes still occur.

writhziden · Feb 9, 2012

Did you find any memory errors?

BSOD running MSE scan, WoW error 1000007e

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

New member

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

Closed by request.

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer

My Computer