View Single Post
25 Aug 2010  
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by mpl34 View Post
Sorry had difficulty attaching it the first time
This one was caused by your US4Visa.sys part of us4vista.sys Universal Shield. It is 14 months old and should be removed



Old drivers that need updating
Code:
rixdptsk.sys        0x9161e000    0x9166f000    0x00051000    0x455a6ed7    11/14/2006 21:35:19                        
rimsptsk.sys        0x90fc0000    0x90fd4000    0x00014000    0x455a8cb5    11/14/2006 23:42:45                        
rimmptsk.sys        0x90fb2000    0x90fc0000    0x0000e000    0x455accd7    11/15/2006 04:16:23                        
bcm4sbxp.sys        0x90f5c000    0x90f6d000    0x00011000    0x4562f047    11/21/2006 08:25:43                        
pcouffin.sys        0x91799000    0x917a4900    0x0000b900    0x457584b9    12/5/2006 10:39:53                        
stwrt.sys        0x9248e000    0x924e3000    0x00055000    0x46e95767    9/13/2007 11:29:43                        
SynTP.sys        0x91687000    0x916b4980    0x0002d980    0x472254e1    10/26/2007 16:58:09                        
VSTCNXT3.SYS        0x9293e000    0x929f3000    0x000b5000    0x48f68ad9    10/15/2008 20:29:13                        
VSTAZL3.SYS        0x9252b000    0x92568000    0x0003d000    0x48f68b0b    10/15/2008 20:30:03                        
VSTDPV3.SYS        0x9283c000    0x9293e000    0x00102000    0x48f68b84    10/15/2008 20:32:04                        
nvlddmkm.sys        0x9181e000    0x91f504c0    0x007324c0    0x4982c9f0    1/30/2009 05:35:44                        
bcmwl6.sys        0x90e3a000    0x90f52000    0x00118000    0x49cc24c8    3/26/2009 20:58:48                        
spldr.sys        0x8b5ea000    0x8b5f2000    0x00008000    0x4a084ebb    5/11/2009 12:13:47                        
spsys.sys        0x9f0d1000    0x9f13b000    0x0006a000    0x4a085436    5/11/2009 12:37:10                        
GEARAspiWDM.sys        0x916d1000    0x916d6280    0x00005280    0x4a1151b5    5/18/2009 08:16:53                        
amdxata.sys        0x8afc2000    0x8afcb000    0x00009000    0x4a12f30f    5/19/2009 13:57:35                        
US4Vista.sys    US4Vista.sys+15ee    0x8b5d2000    0x8b5ea000    0x00018000    0x4a26569c    6/3/2009 06:55:24


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\082610-26176-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82a52000 PsLoadedModuleList = 0x82b9a810
Debug session time: Wed Aug 25 21:36:02.525 2010 (GMT-4)
System Uptime: 0 days 0:01:12.507
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\System32\Drivers\US4Vista.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for US4Vista.sys
*** ERROR: Module load completed but symbols could not be loaded for US4Vista.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8b5d35ee, 9fcfcb10, 0}

Probably caused by : US4Vista.sys ( US4Vista+15ee )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8b5d35ee, The address that the exception occurred at
Arg3: 9fcfcb10, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
US4Vista+15ee
8b5d35ee 8b490c          mov     ecx,dword ptr [ecx+0Ch]

TRAP_FRAME:  9fcfcb10 -- (.trap 0xffffffff9fcfcb10)
ErrCode = 00000000
eax=86b04464 ebx=86b04388 ecx=00000010 edx=86b04388 esi=8748f7d8 edi=00000000
eip=8b5d35ee esp=9fcfcb84 ebp=9fcfcba8 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
US4Vista+0x15ee:
8b5d35ee 8b490c          mov     ecx,dword ptr [ecx+0Ch] ds:0023:0000001c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  PDEngine.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 8b5d579a to 8b5d35ee

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
9fcfcba8 8b5d579a 8748f7d8 00000000 9fcfcbd0 US4Vista+0x15ee
9fcfcbb8 82a8e4bc 8748f720 86b04388 86b04388 US4Vista+0x379a
9fcfcbd0 8ae813e8 87473b38 00000000 86ba3b30 nt!IofCallDriver+0x63
9fcfcbfc 82a8e4bc 87473b38 86b04388 86b04388 fltmgr!FltpDispatch+0xe2
9fcfcc14 82c8ff2e 86ba3b30 86b04388 86b04464 nt!IofCallDriver+0x63
9fcfcc34 82cacd11 87473b38 86ba3b30 00000000 nt!IopSynchronousServiceTail+0x1f8
9fcfccd0 82caf4ec 87473b38 86b04388 00000000 nt!IopXxxControlFile+0x6aa
9fcfcd04 82a9544a 00000224 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
9fcfcd04 770b64f4 00000224 00000000 00000000 nt!KiFastCallEntry+0x12a
00cbeb00 00000000 00000000 00000000 00000000 0x770b64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
US4Vista+15ee
8b5d35ee 8b490c          mov     ecx,dword ptr [ecx+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  US4Vista+15ee

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: US4Vista

IMAGE_NAME:  US4Vista.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a26569c

FAILURE_BUCKET_ID:  0x8E_US4Vista+15ee

BUCKET_ID:  0x8E_US4Vista+15ee

Followup: MachineOwner
---------
My System SpecsSystem Spec