Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\Windows7_BSOD_jcgriff2\080310-28220-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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c5c000 PsLoadedModuleList = 0xfffff800`02e99e50
Debug session time: Wed Aug 4 00:18:33.460 2010 (GMT-4)
System Uptime: 0 days 13:24:51.879
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {248, 2, 1, fffff80002d2ad9e}
Probably caused by : afd.sys ( afd!AfdAllocateMdlChain32+fa )
Followup: MachineOwner
---------
0: 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: 0000000000000248, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002d2ad9e, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f040e0
0000000000000248
CURRENT_IRQL: 2
FAULTING_IP:
nt! ?? ::FNODOBFM::`string'+1192e
fffff800`02d2ad9e f0480fc18148020000 lock xadd qword ptr [rcx+248h],rax
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: chrome.exe
TRAP_FRAME: fffff880089f15d0 -- (.trap 0xfffff880089f15d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000040 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cec560 rsp=fffff880089f1760 rbp=fffff880089f1ca0
r8=fffffa800947b668 r9=000000000331d000 r10=0000000000000040
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
nt!MmProbeAndLockPages+0x130:
fffff800`02cec560 410fb601 movzx eax,byte ptr [r9] ds:7030:00000000`0331d000=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002ccbb69 to fffff80002ccc600
STACK_TEXT:
fffff880`089f0e18 fffff800`02ccbb69 : 00000000`0000000a 00000000`00000248 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`089f0e20 fffff800`02cca7e0 : 00000000`00000080 fffffa80`00000000 00000000`00000002 00000000`00000008 : nt!KiBugCheckDispatch+0x69
fffff880`089f0f60 fffff800`02d2ad9e : fffffa80`0012a560 00000000`00000001 fffffa80`0012a560 00000000`00000080 : nt!KiPageFault+0x260
fffff880`089f10f0 fffff800`02d8d1dd : fffffa80`00000000 fffff880`089f1240 00000000`00000080 00000000`0006d115 : nt! ?? ::FNODOBFM::`string'+0x1192e
fffff880`089f1150 fffff800`02d3bb53 : 00000000`0000003c fffff880`089f1240 fffffa80`0a501a18 00000000`00000003 : nt!MiRemoveLowestPriorityStandbyPage+0x2ad
fffff880`089f11d0 fffff800`02cf2d88 : 00000000`00000000 00000000`0331d000 fffff880`089f15d0 fffff8a0`011f5bb0 : nt! ?? ::FNODOBFM::`string'+0x29d34
fffff880`089f12c0 fffff800`02ce849e : 00000000`00000000 00000000`0331d000 fffff680`000198e8 fffffa80`0a501a18 : nt!MiResolveProtoPteFault+0x508
fffff880`089f1360 fffff800`02ce6623 : ffffffff`ffffff00 00000000`0331d000 fffff800`02e46e80 fffff880`00000000 : nt!MiDispatchFault+0x1de
fffff880`089f1470 fffff800`02cca6ee : 00000000`00000000 ffffffff`ffffffff 00000000`63416d00 fffffa80`00d47b70 : nt!MmAccessFault+0x343
fffff880`089f15d0 fffff800`02cec560 : 00000000`00000000 fffff800`02e5b888 fffffa80`0a501600 00000000`00000801 : nt!KiPageFault+0x16e
fffff880`089f1760 fffff880`042ef4ba : fffffa80`0947b550 fffff800`02fddd01 00000000`00000001 00000000`03300000 : nt!MmProbeAndLockPages+0x130
fffff880`089f1870 fffff880`042ecdf4 : ffffffff`00040000 00000000`0b816aac fffffa80`00000001 fffffa80`00000001 : afd!AfdAllocateMdlChain32+0xfa
fffff880`089f1900 fffff800`02fe86b7 : fffffa80`096f3b70 fffffa80`09b0e010 fffffa80`00000000 fffffa80`00000020 : afd! ?? ::GFJBLGFE::`string'+0xeecc
fffff880`089f1a10 fffff800`02fe8f16 : fffff880`089f1bf8 00000000`00000b84 00000000`00000001 00000000`0b816a84 : nt!IopXxxControlFile+0x607
fffff880`089f1b40 fffff800`02ccb853 : fffff880`089f1ca0 fffffa80`0976c1c0 fffff880`089f1bf8 00000000`00000000 : nt!NtDeviceIoControlFile+0x56
fffff880`089f1bb0 00000000`75082dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0035eb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75082dd9
STACK_COMMAND: kb
FOLLOWUP_IP:
afd!AfdAllocateMdlChain32+fa
fffff880`042ef4ba 4d892f mov qword ptr [r15],r13
SYMBOL_STACK_INDEX: b
SYMBOL_NAME: afd!AfdAllocateMdlChain32+fa
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc184
FAILURE_BUCKET_ID: X64_0xA_afd!AfdAllocateMdlChain32+fa
BUCKET_ID: X64_0xA_afd!AfdAllocateMdlChain32+fa
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\Windows7_BSOD_jcgriff2\080610-25818-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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e58e50
Debug session time: Fri Aug 6 09:49:12.765 2010 (GMT-4)
System Uptime: 0 days 0:10:37.591
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff800024ca788, 8, fffff800024ca788, 0}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+42877 )
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: fffff800024ca788, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff800024ca788, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec30e0
fffff800024ca788
FAULTING_IP:
+5b8c952f00b3d810
fffff800`024ca788 ?? ???
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: havasvc.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff88005ff5350 -- (.trap 0xfffff88005ff5350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88005ff5e70 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff88005ff5b18 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800024ca788 rsp=fffff88005ff54e0 rbp=fffff80002f593c0
r8=00000000000002d4 r9=0000000000000003 r10=fffff88005ff5570
r11=fffff80002c1b000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff800`024ca788 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002d0be54 to fffff80002c8b600
STACK_TEXT:
fffff880`05ff51e8 fffff800`02d0be54 : 00000000`00000050 fffff800`024ca788 00000000`00000008 fffff880`05ff5350 : nt!KeBugCheckEx
fffff880`05ff51f0 fffff800`02c896ee : 00000000`00000008 fffff880`05ff5600 00000000`00000000 fffffa80`055e51a0 : nt! ?? ::FNODOBFM::`string'+0x42877
fffff880`05ff5350 fffff800`024ca788 : fffff880`05ff6600 00000000`00000000 fffff880`05ff55e8 fffff800`02c63d92 : nt!KiPageFault+0x16e
fffff880`05ff54e0 fffff880`05ff6600 : 00000000`00000000 fffff880`05ff55e8 fffff800`02c63d92 fffff800`000002d4 : 0xfffff800`024ca788
fffff880`05ff54e8 00000000`00000000 : fffff880`05ff55e8 fffff800`02c63d92 fffff800`000002d4 fffff800`02eacda0 : 0xfffff880`05ff6600
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+42877
fffff800`02d0be54 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+42877
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+42877
BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+42877
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\Windows7_BSOD_jcgriff2\080810-24273-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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c60000 PsLoadedModuleList = 0xfffff800`02e9de50
Debug session time: Sun Aug 8 15:20:30.442 2010 (GMT-4)
System Uptime: 1 days 3:42:53.268
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff960007a09da, fffff88003a37af0, 0}
Probably caused by : cdd.dll ( cdd!DrvMovePointer+a )
Followup: MachineOwner
---------
3: 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: fffff960007a09da, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88003a37af0, 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:
cdd!DrvMovePointer+a
fffff960`007a09da 488b5910 mov rbx,qword ptr [rcx+10h]
CONTEXT: fffff88003a37af0 -- (.cxr 0xfffff88003a37af0)
rax=00000000450b75c0 rbx=fffff900c00f8010 rcx=0000000000000000
rdx=0000000000000487 rsi=fffff900c011dce8 rdi=0000000000000081
rip=fffff960007a09da rsp=fffff88003a384c0 rbp=0000000000000487
r8=0000000000000081 r9=0000000000000000 r10=fffffa80091260d0
r11=fffffa800920c720 r12=0000000000000000 r13=0000000000000081
r14=0000000000000001 r15=0000000000000c07
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
cdd!DrvMovePointer+0xa:
fffff960`007a09da 488b5910 mov rbx,qword ptr [rcx+10h] ds:002b:00000000`00000010=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960007a09da
STACK_TEXT:
fffff880`03a384c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!DrvMovePointer+0xa
FOLLOWUP_IP:
cdd!DrvMovePointer+a
fffff960`007a09da 488b5910 mov rbx,qword ptr [rcx+10h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: cdd!DrvMovePointer+a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4bf4408a
STACK_COMMAND: .cxr 0xfffff88003a37af0 ; kb
FAILURE_BUCKET_ID: X64_0x3B_cdd!DrvMovePointer+a
BUCKET_ID: X64_0x3B_cdd!DrvMovePointer+a
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_BSODs.zip\Windows7_BSOD_jcgriff2\072910-21340-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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e42e50
Debug session time: Wed Jul 28 22:46:24.608 2010 (GMT-4)
System Uptime: 0 days 2:42:14.636
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff68000605658, d620000025ed4867, fffff68000603358}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+31f32 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000605658
Arg3: d620000025ed4867
Arg4: fffff68000603358
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_403
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: AfterFX.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ce7608 to fffff80002c75600
STACK_TEXT:
fffff880`095227b8 fffff800`02ce7608 : 00000000`0000001a 00000000`00000403 fffff680`00605658 d6200000`25ed4867 : nt!KeBugCheckEx
fffff880`095227c0 fffff800`02ca6251 : 00000000`00000000 fffff680`00605920 fffffa80`03fd8060 fffff900`c0237ab8 : nt! ?? ::FNODOBFM::`string'+0x31f32
fffff880`09522970 fffff800`02cb6fca : 00000000`00000000 00000000`c0b24fff fffffa80`00000000 fffffa80`03fd8060 : nt!MiDeleteVirtualAddresses+0x408
fffff880`09522b30 fffff800`02c74853 : ffffffff`ffffffff 00000000`0008e310 00000000`0008e308 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`09522c20 00000000`77baff3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e2d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77baff3a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+31f32
fffff800`02ce7608 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+31f32
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb
FAILURE_BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f32
BUCKET_ID: X64_0x1a_403_nt!_??_::FNODOBFM::_string_+31f32
Followup: MachineOwner
---------
One dump specifically points out I looked at the four most recent dumps. The error codes are all hardware/hardware related. A couple specifically mentions memory corruption. Click on the links to see the usual causes.