A lot of obsolete drivers should be updated
A Samsung Printer driver should be updated, the current installed version is dated 2005
Samsung
Update Logitech Mouse driver
Support + Downloads
Update ATI/AMD Display driver
AMD Graphics Drivers & Software
Update Realtek NIC driver
Realtek
Remove/Upgrade any CD/DVD/Multimedia Burning programs
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.
Code:
sptd.sys fffff880`010ca000 fffff880`011f0000 0x00126000 0x4ad24632 12/10/2009 00:55:14
Code:
PxHlpa64.sys fffff880`00e49000 fffff880`00e54e00 0x0000be00 0x4a416253 24/06/2009 03:16:35
Code:
Rt64win7.sys fffff880`048e4000 fffff880`04916000 0x00032000 0x49a65b0d 26/02/2009 13:04:13
Code:
atikmdag.sys fffff880`03e60000 fffff880`0450a000 0x006aa000 0x4bbbe425 07/04/2010 05:47:17
atikmpag.sys fffff880`037be000 fffff880`037f4000 0x00036000 0x4bbbde92 07/04/2010 05:23:30
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them. A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000007feffc7131a, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 0000000000000002, Thread->KernelApcDisable
Arg4: fffff880072d5ca0, Previous KernelApcDisable
Debugging Details:
------------------
FAULTING_IP:
+0
000007fe`ffc7131a ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ec1c69 to fffff80002ec2700
STACK_TEXT:
fffff880`072d5ad8 fffff800`02ec1c69 : 00000000`00000001 000007fe`ffc7131a 00000000`00000000 00000000`00000002 : nt!KeBugCheckEx
fffff880`072d5ae0 fffff800`02ec1ba0 : fffffa80`07233990 fffffa80`07723f60 ffffffff`fffd8f00 fffffa80`07723f60 : nt!KiBugCheckDispatch+0x69
fffff880`072d5c20 000007fe`ffc7131a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`02a6faf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ffc7131a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`02ec1ba0 4883ec50 sub rsp,50h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiSystemServiceExit+245
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fdd34
FAILURE_BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245
BUCKET_ID: X64_0x1_nt!KiSystemServiceExit+245
Followup: MachineOwner
---------