BSOD - Vista clashes with Kaspersky

D

dragonorient

New Member
Vista Home Premium 32-bit
Originally upgraded using an upgrade CD from Windows XP Home Premium OEM on HP Desktop,

- The computer is 4 years and 2 months
- The current OS is restored from a ghost copy of the upgraded Vista OS with a few applicatioins.
- The same system had no issues with North, Bitdefender and F-Secure installations.
- It has the same issues after installation of previous 2009 and 2010 Kaspersky versions.

I can restart the system by choosing last good configuration, but Kaspersky's virus definitions are obsolete and some applications are not enabled. If I update the definitions and these applications, then the system crashes upon restart.

It must be a conflict with Kaspersky, but I cannot figure out what is wrong here.

Thank you for your help!
 

Attachments

  • BSOD with Kaspersky.zip
    818.3 KB · Views: 11

My Computer

System One

  • Manufacturer/Model
    HP Media Centre PC M7640N
    CPU
    AMD Dual Core 5000+ 2.61 GHZ
    Motherboard
    Asus A8M2N-LA
    Memory
    3518MB
    Graphics Card(s)
    NVIPIA GeForce 6150 LE
    Sound Card
    Realtek High Definition Audio/Aauppauge WTV PVR PCIII 26xx
    Monitor(s) Displays
    LG Flatron L204WT
Code: 
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_BSOD%20with%20Kaspersky[1].zip\Windows_NT6_BSOD_jcgriff2\Mini021711-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16973.x86fre.vista_gdr.091208-0542
Machine Name:
Kernel base = 0x82400000 PsLoadedModuleList = 0x82511e10
Debug session time: Thu Feb 17 17:19:28.453 2011 (GMT-5)
System Uptime: 0 days 0:00:15.031
Loading Kernel Symbols
...............................................................
...................
Loading User Symbols
Loading unloaded module list
..
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {18, 2, 0, 908c1651}
Unable to load image \SystemRoot\system32\DRIVERS\sis163u.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sis163u.sys
*** ERROR: Module load completed but symbols could not be loaded for sis163u.sys
Probably caused by : sis163u.sys ( sis163u+1651 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 908c1651, address which referenced memory
Debugging Details:
------------------
 
READ_ADDRESS: GetPointerFromAddress: unable to read from 825315ac
Unable to read MiSystemVaType memory at 825117e0
 00000018 
CURRENT_IRQL:  2
FAULTING_IP: 
sis163u+1651
908c1651 ??              ???
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  8c0a147c -- (.trap 0xffffffff8c0a147c)
ErrCode = 00000000
eax=88816878 ebx=87eae110 ecx=00000010 edx=8899700c esi=887e5a20 edi=874b3780
eip=908c1651 esp=8c0a14f0 ebp=8c0a1504 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
sis163u+0x1651:
908c1651 ??              ???
Resetting default scope
LOCK_ADDRESS:  8252e080 -- (!locks 8252e080)
Resource @ nt!PiEngineLock (0x8252e080)    Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
 
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE: 
 Lock address  : 0x8252e080
 Thread Count  : 0
 Thread address: 0x00000000
 Thread wait   : 0x0
LAST_CONTROL_TRANSFER:  from 908c1651 to 8248fe14
STACK_TEXT:  
8c0a147c 908c1651 badb0d00 8899700c 0008800a nt!KiTrap0E+0x2ac
WARNING: Stack unwind information not available. Following frames may be wrong.
8c0a14ec 887e5a20 887d6000 887e8650 00000010 sis163u+0x1651
8c0a1504 908c1c1a 007d6000 8899700c 007e5a20 0x887e5a20
8c0a154c 908c2485 887d6000 88a6e8f0 885c4000 sis163u+0x1c1a
8c0a1564 908e323e 887d6000 88822804 885c4000 sis163u+0x2485
8c0a157c 908e3aa9 885c4000 88822804 8c0a15a8 sis163u+0x2323e
8c0a158c 908d360a 885c4000 88822804 88a6e8f0 sis163u+0x23aa9
8c0a15a8 908e2621 885c4000 88822804 8c0a1600 sis163u+0x1360a
8c0a15d8 908e2774 88700408 88822804 000000ff sis163u+0x22621
8c0a1608 908dec0d 88700408 00000004 88700408 sis163u+0x22774
8c0a161c 908dd54b 88700408 000000ff 88700408 sis163u+0x1ec0d
8c0a1634 908dc207 88700408 00000011 00000000 sis163u+0x1d54b
8c0a1648 908dc146 88700408 00000011 00000000 sis163u+0x1c207
8c0a1660 908cdaee 88700408 00000000 877fd0e8 sis163u+0x1c146
8c0a1678 908c43bb 887d6000 8c0a1704 877f5010 sis163u+0xdaee
8c0a168c 908c0643 887d6000 877fdee0 8c0a1948 sis163u+0x43bb
8c0a169c 82dccb50 8c0a16d8 8c0a1738 82d318c0 sis163u+0x643
8c0a1948 82dd46aa 877f5010 877fd0e8 877fdee0 ndis!ndisMInitializeAdapter+0x5aa
8c0a1980 82dd4525 877f5010 877fd030 877f52d0 ndis!ndisInitializeAdapter+0x109
8c0a19a8 82dcfedc 877fd030 00000000 87401ee0 ndis!ndisPnPStartDevice+0xf3
8c0a19f8 82427f9f 877fd030 87401e28 8c0a1a74 ndis!ndisPnPDispatch+0x697
8c0a1a10 825b0809 00000000 8525ec90 87ea0110 nt!IofCallDriver+0x63
8c0a1a2c 8240797b 8c0a1a50 824077b5 87ea0110 nt!PnpAsynchronousCall+0x96
8c0a1a78 825b9731 824077b5 87ea0110 8525eb08 nt!PnpStartDevice+0xb7
8c0a1ad4 825b9094 87ea0110 0000000d 00000000 nt!PnpStartDeviceNode+0x13a
8c0a1af0 825b68a8 00000000 00000001 8252d2f0 nt!PipProcessStartPhase1+0x65
8c0a1cec 824072f5 852d6768 874bff18 8c0a1d38 nt!PipProcessDevNodeTree+0x18d
8c0a1d44 82478fc0 00000000 00000000 852cd580 nt!PnpDeviceActionWorker+0x21b
8c0a1d7c 82625544 00000000 8c0aa680 00000000 nt!ExpWorkerThread+0xfd
8c0a1dc0 8249162e 82478ec3 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
sis163u+1651
908c1651 ??              ???
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  sis163u+1651
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: sis163u
IMAGE_NAME:  sis163u.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  43682a32
FAILURE_BUCKET_ID:  0xD1_sis163u+1651
BUCKET_ID:  0xD1_sis163u+1651

Give priority to update this driver
Sis163u.sys file description
Productname: NDIS 5.1 NIC Driver
Description: SiS163 USB Wireless LAN Adapter Driver
Company: Silicon Integrated Systems Corp.

Adjust Windows Automatic Update to download drivers. All that are not updated after about a week or so. Update manually.
Other outdated drivers.
Code: 
 sis163u  sis163u.sys  Tue Nov 01 22:53:38 2005 
PxHelp20 PxHelp20.sys Mon Jul 24 20:18:21 2006 
nvstor   nvstor.sys   Tue Oct 03 20:25:15 2006 
spldr    spldr.sys    Wed Oct 25 18:40:44 2006 
amdk8    amdk8.sys    Thu Nov 02 04:30:18 2006 
fltmgr   fltmgr.sys   Thu Nov 02 04:30:58 2006 
mup      mup.sys      Thu Nov 02 04:31:04 2006 
msisadrv msisadrv.sys Thu Nov 02 04:35:08 2006 
mssmbios mssmbios.sys Thu Nov 02 04:35:13 2006 
pci      pci.sys      Thu Nov 02 04:35:13 2006 
fileinfo fileinfo.sys Thu Nov 02 04:36:47 2006 
watchdog watchdog.sys Thu Nov 02 04:37:44 2006 
msrpc    msrpc.sys    Thu Nov 02 04:50:16 2006 
mountmgr mountmgr.sys Thu Nov 02 04:51:06 2006 
swenum   swenum.sys   Thu Nov 02 04:51:15 2006 
ks       ks.sys       Thu Nov 02 04:51:18 2006 
CLASSPNP CLASSPNP.SYS Thu Nov 02 04:51:34 2006 
crashdmp crashdmp.sys Thu Nov 02 04:51:36 2006 
SCSIPORT SCSIPORT.SYS Thu Nov 02 04:51:38 2006 
disk     disk.sys     Thu Nov 02 04:51:40 2006 
cdrom    cdrom.sys    Thu Nov 02 04:51:44 2006 
volmgr   volmgr.sys   Thu Nov 02 04:51:44 2006 
storport storport.sys Thu Nov 02 04:51:45 2006 
partmgr  partmgr.sys  Thu Nov 02 04:51:47 2006 
volmgrx  volmgrx.sys  Thu Nov 02 04:51:54 2006 
crcdisk  crcdisk.sys  Thu Nov 02 04:52:27 2006 
msiscsi  msiscsi.sys  Thu Nov 02 04:52:40 2006 
ecache   ecache.sys   Thu Nov 02 04:52:42 2006 
WMILIB   WMILIB.SYS   Thu Nov 02 04:54:53 2006 
USBD     USBD.SYS     Thu Nov 02 04:55:00 2006 
usbehci  usbehci.sys  Thu Nov 02 04:55:04 2006 
usbohci  usbohci.sys  Thu Nov 02 04:55:05 2006 
USBPORT  USBPORT.SYS  Thu Nov 02 04:55:09 2006 
1394BUS  1394BUS.SYS  Thu Nov 02 04:55:12 2006 
ohci1394 ohci1394.sys Thu Nov 02 04:55:16 2006 
usbhub   usbhub.sys   Thu Nov 02 04:55:20 2006 
umbus    umbus.sys    Thu Nov 02 04:55:24 2006 
ndis     ndis.sys     Thu Nov 02 04:57:33 2006 
raspppoe raspppoe.sys Thu Nov 02 04:58:12 2006 
rasl2tp  rasl2tp.sys  Thu Nov 02 04:58:13 2006 
ndiswan  ndiswan.sys  Thu Nov 02 04:58:13 2006 
raspptp  raspptp.sys  Thu Nov 02 04:58:14 2006 
TDI      TDI.SYS      Thu Nov 02 04:58:46 2006 
modem    modem.sys    Thu Nov 02 04:58:52 2006 
termdd   termdd.sys   Thu Nov 02 05:02:00 2006 
BOOTVID  BOOTVID.dll  Thu Nov 02 05:39:29 2006 
kdcom    kdcom.dll    Thu Nov 02 05:42:20 2006 
PSHED    PSHED.dll    Thu Nov 02 05:42:51 2006 
aijbwfy6 aijbwfy6.SYS Sun Nov 12 05:40:09 2006 
sptd     sptd.sys     Thu Dec 21 09:01:52 2006 
hal      halmacpi.dll Sat Dec 23 23:05:34 2006 
hcwPP2   hcwPP2.sys   Tue Feb 06 13:27:02 2007 
HDAudBus HDAudBus.sys Sat Mar 24 14:54:34 2007 
tunmp    tunmp.sys    Wed Jun 06 22:56:53 2007 
tunnel   tunnel.sys   Wed Jun 06 22:57:03 2007 
dxgkrnl  dxgkrnl.sys  Mon Jul 02 21:01:10 2007 
ndistapi ndistapi.sys Tue Jul 03 21:28:09 2007 
NDProxy  NDProxy.SYS  Tue Jul 03 21:28:13 2007 
acpi     acpi.sys     Thu Aug 30 20:57:46 2007 
volsnap  volsnap.sys  Thu Oct 25 22:04:17 2007 
nvstor32 nvstor32.sys Fri Oct 26 14:50:16 2007 
CLFS     CLFS.SYS     Wed Dec 05 20:55:42 2007 
mouclass mouclass.sys Wed Dec 05 21:18:22 2007 
kbdclass kbdclass.sys Wed Dec 05 21:18:23 2007 
WDFLDR   WDFLDR.SYS   Wed Dec 05 21:21:19 2007 
Wdf01000 Wdf01000.sys Wed Dec 05 21:21:28 2007 
Ntfs     Ntfs.sys     Sun Dec 16 04:31:37 2007

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. Each remedy suggested must be performed regardless of placement in this report or other variables. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command


Scan with your Anti Virus

Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored.

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
and here
http://www.edbott.com/weblog/the-vista-master-driver-list/
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/
You can also locate information about your driver using this information
http://www.sevenforums.com/tutorials/96442-device-manager-finding-unknown-devices.html

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
http://www.duplexsecure.com/en/downloads
Use this SPTD uninstaller when you're done:



Uninstall your current Anti Virus and replace with Microsoft Security Essentials.
www.microsoft.com/Security_Essentials/


After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
It is very important to remember that the dump reports only give clues as to the problem and although it is very easy to analyze only one or two, usually more are needed. If you experience additional BSOD after installing a current version of the driver in question, be sure to post so that we can use the additional information to assist you in preventing the BSOD's
 

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
Richard, thank you very much for your most generous help. I finally solved this BSOD issue by deleting the driver of and unstalling Daemon Tools and the driver of Trendnet Wireless Adapter at your suggestion.

I did not post a reply earlier because I worked hard to try to delete a folder in Vista which did not give me the administrative privileges. I finally worked around by refering to some old posts on this website.
 

My Computer

System One

  • Manufacturer/Model
    HP Media Centre PC M7640N
    CPU
    AMD Dual Core 5000+ 2.61 GHZ
    Motherboard
    Asus A8M2N-LA
    Memory
    3518MB
    Graphics Card(s)
    NVIPIA GeForce 6150 LE
    Sound Card
    Realtek High Definition Audio/Aauppauge WTV PVR PCIII 26xx
    Monitor(s) Displays
    LG Flatron L204WT
No need to aplogize about the delay in your response. I am just glad that the problem was resolved. Good luck
 

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
You must log in or register to reply here.
Back
Top