Code:
chargeservice.exe c:\program files (x86)\msi\super-charger\chargeservice.exe 2316 8 200 1380 04/25/2012 12:36 1.2.6.0 135.52 KB (138,768 bytes) 02/27/2012 18:24
super-charger.exe c:\program files (x86)\msi\super-charger\super-charger.exe 6912 8 200 1380 04/25/2012 12:51 1.2.6.0 490.52 KB (502,288 bytes) 02/27/2012 18:24
Many of these faster charging applications cause crashes on systems because they stress the USB ports. I would recommend removing to test.
Code:
ccsvchst.exe c:\program files (x86)\norton 360 premier edition\engine\6.2.0.9\ccsvchst.exe 2440 8 1024 10240 04/25/2012 12:36 11.2.2.4 134.99 KB (138,232 bytes) 04/23/2012 15:54
ccsvchst.exe c:\program files (x86)\norton 360 premier edition\engine\6.2.0.9\ccsvchst.exe 6532 8 1024 10240 04/25/2012 12:51 11.2.2.4 134.99 KB (138,232 bytes) 04/23/2012 15:54
Norton 360 is fine to use; just avoid the registry cleaning feature.
Code:
signalislandui.exe c:\program files\intel\turboboost\signalislandui.exe 6988 8 200 1380 04/25/2012 12:51 2.1.23.0 199.50 KB (204,288 bytes) 11/29/2010 15:01
turboboost.exe c:\program files\intel\turboboost\turboboost.exe 3304 8 200 1380 04/25/2012 12:36 2.1.23.0 146.00 KB (149,504 bytes) 11/29/2010 15:00
If you are using the turboboost feature of your CPU, this is considered overclocking and should be disabled for the time being until we can determine the cause of your crashes.
Code:
pdagent.exe c:\program files\raxco\perfectdisk\pdagent.exe 2712 8 200 1380 04/25/2012 12:36 12.5.0.310 1.80 MB (1,890,568 bytes) 02/29/2012 03:19
pdagents1.exe c:\program files\raxco\perfectdisk\pdagents1.exe 4984 8 200 1380 04/25/2012 12:51 12.5.0.310 87.76 KB (89,864 bytes) 02/29/2012 03:19
perfectdisk.exe c:\program files\raxco\perfectdisk\perfectdisk.exe 5900 8 200 1380 04/25/2012 12:51 12.5.0.310 11.00 MB (11,539,208 bytes) 02/29/2012 03:19
PerfectDisk is known to cause problems with system restore points. Use at your own risk. Also, as an FYI: There are command line flags that will accomplish the same defragmenting with Windows defrag that PerfectDisk offers, and they don't require a 3rd party license/subscription cost.
Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\Derek02of13\Windows_NT6_BSOD_jcgriff2\042512-35178-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03c06000 PsLoadedModuleList = 0xfffff800`03e4a650
Debug session time: Wed Apr 25 11:59:02.604 2012 (UTC - 6:00)
System Uptime: 0 days 5:50:07.587
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80003c88f42}
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmiProcessTerminationCommand+5f )
Followup: MachineOwner
---------
4: 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: 0000000000000000, 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: fffff80003c88f42, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003eb4100
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiSignalSynchronizationObject+42
fffff800`03c88f42 488b3f mov rdi,qword ptr [rdi]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88007b96a00 -- (.trap 0xfffff88007b96a00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffff880009b2180
rdx=fffffa80145899e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003c88f42 rsp=fffff88007b96b90 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff88007b96c20 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz ac po cy
nt!KiSignalSynchronizationObject+0x42:
fffff800`03c88f42 488b3f mov rdi,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80003c82229 to fffff80003c82c80
STACK_TEXT:
fffff880`07b968b8 fffff800`03c82229 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`07b968c0 fffff800`03c80ea0 : 00000000`00000000 009e10f4`00000000 00000000`00000001 fffffa80`145899e8 : nt!KiBugCheckDispatch+0x69
fffff880`07b96a00 fffff800`03c88f42 : fffffa80`14589970 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`07b96b90 fffff800`03c87346 : 00000000`00000000 fffff880`04da81cc 00000000`00000000 fffffa80`11a4f010 : nt!KiSignalSynchronizationObject+0x42
fffff880`07b96be0 fffff880`04db836b : fffffa80`00000000 00000000`00000000 fffffa80`0d547a00 fffff880`07b96ca0 : nt!KeSetEvent+0x106
fffff880`07b96c50 fffff880`04dd616d : fffffa80`00000000 fffffa80`11a4f010 00000000`0000000f fffff880`04dd7f09 : dxgmms1!VidMmiProcessTerminationCommand+0x5f
fffff880`07b96ca0 fffff880`04dd53f8 : fffff800`055fc080 fffffa80`0d8f5d50 00000000`00000000 fffffa80`11a4f010 : dxgmms1!VidSchiSubmitDeviceCommand+0x39
fffff880`07b96cd0 fffff880`04dd4e96 : 00000000`00000000 fffffa80`147de010 00000000`00000080 fffffa80`11a4f010 : dxgmms1!VidSchiSubmitQueueCommand+0xb0
fffff880`07b96d00 fffff800`03f1cfda : 00000000`03f183a9 fffffa80`11a56620 fffffa80`0cd77990 fffffa80`11a56620 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`07b96d40 fffff800`03c739c6 : fffff800`03df7e80 fffffa80`11a56620 fffff800`03e05cc0 fffffa80`11fcd620 : nt!PspSystemThreadStartup+0x5a
fffff880`07b96d80 00000000`00000000 : fffff880`07b97000 fffff880`07b91000 fffff880`07b96470 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidMmiProcessTerminationCommand+5f
fffff880`04db836b 33d2 xor edx,edx
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: dxgmms1!VidMmiProcessTerminationCommand+5f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f
BUCKET_ID: X64_0xA_dxgmms1!VidMmiProcessTerminationCommand+5f
Followup: MachineOwner
---------
Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.
Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
- Download the drivers you want for your display card(s)
- Click Start Menu
- Click Control Panel
- Click Uninstall a program
- For AMD:
- Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
- If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
- 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
Alternatively:
- Login as an adminstrative user
- 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 driver you selected for the display cards once Windows starts