Problem Devices:
Code:
Not Available ROOT\SCSIADAPTER\0000 The drivers for this device are not installed.
ASUSTeK Computer Inc. -Support- Drivers and Download K42Jr -> OS: Windows 7 64bit -> Others -> Intel Rapid Storage Technology
Security Software (This is just to check that it is installed and working properly; nothing needs to be done with this information at this time):
Code:
tmbmsrv.exe c:\program files\trend micro\bm\tmbmsrv.exe 4596 8 200 1380 7/4/2012 9:14 PM 2.80.0.1063 557.26 KB (570,632 bytes) 11/11/2010 3:12 AM
sfctlcom.exe c:\program files\trend micro\internet security\sfctlcom.exe 1932 8 200 1380 7/4/2012 9:12 PM 17.50.0.1659 839.49 KB (859,640 bytes) 23/2/2010 7:21 PM
tmproxy.exe c:\program files\trend micro\internet security\tmproxy.exe 4716 8 200 1380 7/4/2012 9:13 PM 5.8.0.1092 896.26 KB (917,768 bytes) 11/11/2010 3:12 AM
ufseagnt.exe c:\program files\trend micro\internet security\ufseagnt.exe 3092 8 200 1380 7/4/2012 9:12 PM 17.50.0.1659 998.93 KB (1,022,904 bytes) 23/2/2010 7:22 PM
Problematic software:
Code:
tuneuputilitiesapp64.exe c:\program files (x86)\tuneup utilities 2010\tuneuputilitiesapp64.exe 2848 8 200 1380 7/4/2012 9:12 PM 9.0.3000.135 784.32 KB (803,144 bytes) 17/12/2009 11:50 PM
tuneuputilitiesservice64.exe c:\program files (x86)\tuneup utilities 2010\tuneuputilitiesservice64.exe 1984 8 200 1380 7/4/2012 9:12 PM 9.0.3000.135 1.33 MB (1,394,504 bytes) 17/12/2009 11:50 PM
Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.
Possible out of date drivers:
Code:
sncduvc fffff880`02bd8000 fffff880`02be0a80 Mon Dec 29 02:14:26 2008 (495894f2) 00012294 sncduvc.SYS
btwl2cap fffff880`02ccb000 fffff880`02cd7000 Fri Apr 03 18:28:45 2009 (49d6a9bd) 00009866 btwl2cap.sys
ATK64AMD fffff880`02ff0000 fffff880`02ff8000 Tue May 12 19:04:54 2009 (4a0a1cb6) 000096a6 ATK64AMD.sys
amdxata fffff880`01282000 fffff880`0128d000 Tue May 19 11:56:59 2009 (4a12f2eb) 00011b8c amdxata.sys
snp2uvc fffff880`02a0f000 fffff880`02bc6600 Wed May 20 02:11:05 2009 (4a13bb19) 001c0e6e snp2uvc.sys
btusbflt fffff880`02bef000 fffff880`02bff000 Tue Jun 09 15:46:26 2009 (4a2ed832) 000122fa btusbflt.sys
btwavdt fffff880`05828000 fffff880`058a3000 Wed Jun 24 23:50:13 2009 (4a431015) 0002ce2d btwavdt.sys
btwrchid fffff880`02cd7000 fffff880`02cda880 Wed Jun 24 23:51:37 2009 (4a431069) 0000f764 btwrchid.sys
btwaudio fffff880`02c45000 fffff880`02ccb000 Wed Jul 01 07:54:56 2009 (4a4b6ab0) 0001c389 btwaudio.sys
ASMMAP64 fffff880`048dd000 fffff880`048e5000 Thu Jul 02 03:13:26 2009 (4a4c7a36) 0000ceab ASMMAP64.sys
sncduvc.SYS
btwl2cap.sys
ATK64AMD.sys
amdxata.sys
snp2uvc.sys
btusbflt.sys
btwavdt.sys
btwrchid.sys
btwaudio.sys
ASMMAP64.sys
Out of date Bluetooth drivers can cause instability; see if there are updates at the ASUS support site: ASUSTeK Computer Inc. -Support- Drivers and Download K42Jr. The rest of the above drivers are not really a concern.
Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\MrJohnMark21\Windows_NT6_BSOD_jcgriff2\040712-24429-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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`03057e50
Debug session time: Sat Apr 7 07:11:19.915 2012 (UTC - 6:00)
System Uptime: 0 days 0:01:56.976
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa800719c110, 2, 1, fffff80002e93365}
Unable to load image \SystemRoot\system32\DRIVERS\ewusbnet.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ewusbnet.sys
*** ERROR: Module load completed but symbols could not be loaded for ewusbnet.sys
Probably caused by : ewusbnet.sys ( ewusbnet+2e36 )
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: fffffa800719c110, 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: fffff80002e93365, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c20e0
fffffa800719c110
CURRENT_IRQL: 2
FAULTING_IP:
nt!KeAcquireSpinLockRaiseToDpc+55
fffff800`02e93365 f0480fba2900 lock bts qword ptr [rcx],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff8800350fa40 -- (.trap 0xfffff8800350fa40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800719c110
rdx=fffffa8006b8b740 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002e93365 rsp=fffff8800350fbd0 rbp=fffffa800719c110
r8=0000000000000000 r9=0000000000000000 r10=000000000000000d
r11=fffffa80049fd170 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeAcquireSpinLockRaiseToDpc+0x55:
fffff800`02e93365 f0480fba2900 lock bts qword ptr [rcx],0 ds:7180:fffffa80`0719c110=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e89ca9 to fffff80002e8a740
STACK_TEXT:
fffff880`0350f8f8 fffff800`02e89ca9 : 00000000`0000000a fffffa80`0719c110 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0350f900 fffff800`02e88920 : fffffa80`0175cd20 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0350fa40 fffff800`02e93365 : 00000000`00000000 fffffa80`01835b60 fffff800`0302f5a0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0350fbd0 fffff880`02d09e36 : 00000000`00000000 fffff880`0176410c fffffa80`0719c000 fffffa80`06bd8050 : nt!KeAcquireSpinLockRaiseToDpc+0x55
fffff880`0350fc20 00000000`00000000 : fffff880`0176410c fffffa80`0719c000 fffffa80`06bd8050 00000000`00000001 : ewusbnet+0x2e36
STACK_COMMAND: kb
FOLLOWUP_IP:
ewusbnet+2e36
fffff880`02d09e36 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: ewusbnet+2e36
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ewusbnet
IMAGE_NAME: ewusbnet.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b1ce881
FAILURE_BUCKET_ID: X64_0xA_ewusbnet+2e36
BUCKET_ID: X64_0xA_ewusbnet+2e36
Followup: MachineOwner
---------
Your crash was caused by ewusbnet.sys:USB NDIS Miniport Driver - likely for Huawei Mobil Connect package. Seen with T-Mobile webConnect. If the device is needed, re-install its driver or install an updated driver. The driver is either corrupted or out of date.
To fully re-install a driver, use the following steps.
- First, download the latest driver. Then do the next steps.
- Click Start Menu
- Right Click My Computer/Computer
- Click Manage
- Click Device Manager from the list on the left
- Find the device you are trying to uninstall by expanding the appropriate set of devices
- Right click the device
- 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 only if Windows asks you to.
- Install the latest driver for the device.
Alternatively:
- Login as an adminstrative user.
- First, download the latest driver. Then do the next steps.
- Click Start Menu
- Click Control Panel
- Click Hardware and Sound
- Click Device Manager (the last link under Devices and Printers)
- Find the device you are trying to uninstall by expanding the appropriate set of devices
- Right click the device
- 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 only if Windows asks you to.
- Install the latest driver for the device.
Quote