cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

vsp.sys creates the problem and my server restarted automatically... Needs tye location from where I can download the latest driver fopr vsp.sys

Mandeep_Singh_M
Level 4
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [F:\Logs\Gursrv023_Memory_Dump\MEMORY_DUMP_31_JULY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*F:\Symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (8 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Built by: 3790.srv03_sp2_gdr.090319-1204
Machine Name:
Kernel base = 0xe1000000 PsLoadedModuleList = 0xe10af9c8
Debug session time: Fri Jul 31 03:58:03.281 2009 (GMT+5)
System Uptime: 5 days 20:23:01.859
Loading Kernel Symbols
...............................................................
..........................................................
Loading User Symbols

Loading unloaded module list
............................
*** ERROR: Module load completed but symbols could not be loaded for vsp.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3F, {0, 0, 0, 0}

Probably caused by : vsp.sys ( vsp+89f )

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

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

NO_MORE_SYSTEM_PTES (3f)
No System PTEs left. Usually caused by a driver not cleaning up
properly. If kernel debugger available get stack trace and
"!sysptes 3".
Set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes
to a DWORD 1 value and reboot. Then the system will save stack traces
so the guilty driver can be identified. There is no other way to find out
which driver is neglecting to clean up the I/Os.
A bugcheck DRIVER_USED_EXCESSIVE_PTES will then occur if the system runs out of
PTEs again and the offending driver's name will be printed.
Arguments:
Arg1: 00000000, PTE Type (0 - system expansion, 1 nonpaged pool expansion)
Arg2: 00000000, Requested size
Arg3: 00000000, Total free system PTEs
Arg4: 00000000, Total system PTEs

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


DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x3F

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from f5d0789f to e107c476

STACK_TEXT:
f5893c30 f5d0789f 0000003f 97cd7000 fb946750 nt!KeBugCheck+0x14
WARNING: Stack unwind information not available. Following frames may be wrong.
f5893c44 f5d09ca6 fcb0f008 00000000 97cd7000 vsp+0x89f
f5893cb8 f5d0c081 fc6474f0 fb946750 fc6474f0 vsp+0x2ca6
f5893d24 f5d0ce32 fc6474f0 fb946750 fca98c80 vsp+0x5081
f5893d5c f5d0a1b7 fc6475e8 fb946750 f5d10820 vsp+0x5e32
f5893d94 f5d07862 fca98c80 00000000 fe6ccdb0 vsp+0x31b7
f5893dac e1120833 f5d10814 00000000 00000000 vsp+0x862
f5893ddc e103fe9f f5d077d8 f5d10814 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
vsp+89f
f5d0789f 6685ff test di,di

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: vsp+89f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: vsp

IMAGE_NAME: vsp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 445a6f10

FAILURE_BUCKET_ID: 0x3F_vsp+89f

BUCKET_ID: 0x3F_vsp+89f

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

4: kd> lmvm vsp
start end module name
f5d07000 f5d12480 vsp (no symbols)
Loaded symbol image file: vsp.sys
Image path: vsp.sys
Image name: vsp.sys
Timestamp: Fri May 05 02:46:00 2006 (445A6F10)
CheckSum: 0000EC63
ImageSize: 0000B480
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4








vsp.sys creates the problem and my server restarted automatically... Needs tye location from where I can download the latest driver fopr vsp.sys
1 REPLY 1

Anonymous
Not applicable
vsp.sys is not a standalone driver. It is included in the NetBackup Client for Windows software.

So to get the latest version as you requested, then suggest to install NetBackup 6.5 and 6.5 Update 4 to be up to date.

Of course best practices follow that you upgrade NetBackup in the following steps

Master Server first
Media Servers/Clients next