New
#1
WinDBG
I used WinDBG to try and figure out my solution, but I'm not sure where to go. I'm only getting this issue when I try and back up my computer using synctoy via firewire to my external hard drive. Previously with USB I had no problem. Here's the WinDBG report:
WARNING: Inaccessible path: 'C:\Symbols'
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\\Desktop\New folder\062210-22635-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'C:\Symbols'
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols;C:\Symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Tue Jun 22 15:45:47.488 2010 (UTC - 4:00)
System Uptime: 0 days 0:14:56.456
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FC, {fffff880015aec86, 8000000004039963, fffff8800e196790, 2}
Unable to load image \SystemRoot\System32\Drivers\ksecpkg.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ksecpkg.sys
*** ERROR: Module load completed but symbols could not be loaded for ksecpkg.sys
Probably caused by : hardware ( ksecpkg+14c86 )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff880015aec86, Virtual address for the attempted execute.
Arg2: 8000000004039963, PTE contents.
Arg3: fffff8800e196790, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: SyncToy.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800e196790 -- (.trap 0xfffff8800e196790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000801 rbx=0000000000000000 rcx=0000000000000000
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff880015aec86 rsp=fffff8800e196920 rbp=fffff8800c4f2980
r8=fffff80002e1c000 r9=0000000000000000 r10=ffffffffffffff7f
r11=fffff88003186100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
ksecpkg+0x14c86:
fffff880`015aec86 0000 add byte ptr [rax],al ds:52f8:00000000`00000801=??
Resetting default scope
MISALIGNED_IP:
ksecpkg+14c86
fffff880`015aec86 0000 add byte ptr [rax],al
LAST_CONTROL_TRANSFER: from fffff80002f0cb0f to fffff80002e8c600
STACK_TEXT:
fffff880`0e196628 fffff800`02f0cb0f : 00000000`000000fc fffff880`015aec86 80000000`04039963 fffff880`0e196790 : nt!KeBugCheckEx
fffff880`0e196630 fffff800`02e8a6ee : 00000000`00000008 fffff8a0`0de3cb40 00000000`00000000 00000000`00010224 : nt! ?? ::FNODOBFM::`string'+0x424d7
fffff880`0e196790 fffff880`015aec86 : 00000000`008f0000 fffff8a0`0de3cb40 fffff880`0c4f2980 00000000`00610004 : nt!KiPageFault+0x16e
fffff880`0e196920 00000000`008f0000 : fffff8a0`0de3cb40 fffff880`0c4f2980 00000000`00610004 00000000`00000000 : ksecpkg+0x14c86
fffff880`0e196928 fffff8a0`0de3cb40 : fffff880`0c4f2980 00000000`00610004 00000000`00000000 fffff880`0130752e : 0x8f0000
fffff880`0e196930 fffff880`0c4f2980 : 00000000`00610004 00000000`00000000 fffff880`0130752e 00000000`00000202 : 0xfffff8a0`0de3cb40
fffff880`0e196938 00000000`00610004 : 00000000`00000000 fffff880`0130752e 00000000`00000202 fffff800`02e910fa : 0xfffff880`0c4f2980
fffff880`0e196940 00000000`00000000 : fffff880`0130752e 00000000`00000202 fffff800`02e910fa fffff880`02fd5180 : 0x610004
STACK_COMMAND: kb
FOLLOWUP_IP:
ksecpkg+14c86
fffff880`015aec86 0000 add byte ptr [rax],al
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: ksecpkg+14c86
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_ksecpkg.sys
BUCKET_ID: X64_IP_MISALIGNED_ksecpkg.sys
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver
is on the stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff880015aec86, Virtual address for the attempted execute.
Arg2: 8000000004039963, PTE contents.
Arg3: fffff8800e196790, (reserved)
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFC
PROCESS_NAME: SyncToy.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800e196790 -- (.trap 0xfffff8800e196790)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000801 rbx=0000000000000000 rcx=0000000000000000
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff880015aec86 rsp=fffff8800e196920 rbp=fffff8800c4f2980
r8=fffff80002e1c000 r9=0000000000000000 r10=ffffffffffffff7f
r11=fffff88003186100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
ksecpkg+0x14c86:
fffff880`015aec86 0000 add byte ptr [rax],al ds:52f8:00000000`00000801=??
Resetting default scope
MISALIGNED_IP:
ksecpkg+14c86
fffff880`015aec86 0000 add byte ptr [rax],al
LAST_CONTROL_TRANSFER: from fffff80002f0cb0f to fffff80002e8c600
STACK_TEXT:
fffff880`0e196628 fffff800`02f0cb0f : 00000000`000000fc fffff880`015aec86 80000000`04039963 fffff880`0e196790 : nt!KeBugCheckEx
fffff880`0e196630 fffff800`02e8a6ee : 00000000`00000008 fffff8a0`0de3cb40 00000000`00000000 00000000`00010224 : nt! ?? ::FNODOBFM::`string'+0x424d7
fffff880`0e196790 fffff880`015aec86 : 00000000`008f0000 fffff8a0`0de3cb40 fffff880`0c4f2980 00000000`00610004 : nt!KiPageFault+0x16e
fffff880`0e196920 00000000`008f0000 : fffff8a0`0de3cb40 fffff880`0c4f2980 00000000`00610004 00000000`00000000 : ksecpkg+0x14c86
fffff880`0e196928 fffff8a0`0de3cb40 : fffff880`0c4f2980 00000000`00610004 00000000`00000000 fffff880`0130752e : 0x8f0000
fffff880`0e196930 fffff880`0c4f2980 : 00000000`00610004 00000000`00000000 fffff880`0130752e 00000000`00000202 : 0xfffff8a0`0de3cb40
fffff880`0e196938 00000000`00610004 : 00000000`00000000 fffff880`0130752e 00000000`00000202 fffff800`02e910fa : 0xfffff880`0c4f2980
fffff880`0e196940 00000000`00000000 : fffff880`0130752e 00000000`00000202 fffff800`02e910fa fffff880`02fd5180 : 0x610004
STACK_COMMAND: kb
FOLLOWUP_IP:
ksecpkg+14c86
fffff880`015aec86 0000 add byte ptr [rax],al
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: ksecpkg+14c86
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_ksecpkg.sys
BUCKET_ID: X64_IP_MISALIGNED_ksecpkg.sys
Followup: MachineOwner
---------
7: kd> lmvm hardware
start end module name
Any help would be awesome or direction pointing