winxp Capture card driver issues

[mikefletcher85]

I'm hoping someone here could help me out. I'm trying to build a DVR computer for my home security setup. Currently I have a STB like unit that is a pain to configure and monitor. I recently acquired an older DVR PC that has 3 Capture cards in it (VG4C-RT4). The OS on the box is not working right, so I took one of the cards out (I currently only have 4 cameras so one card is all I need right now) and put it in another system that I intend on using as my DVR box for now. It had Windows Server 2012 64bit on it, I got the drivers from the manufactures site, but its looks pretty outdated http://vguard.tw/support.html. As soon as I tried to load the drivers for the device the computer crashed/rebooted. Seeing that my OS wasn't supported I tried Windows 7 Pro 32bit and Windows XP Pro 32bit all with the same issue. The machine has Windows XP on it now so I grabbed the MiniDump file from it and looked it over. Below is what it says, I emailed the manufacture, but I have a feeling I will never hear back from them.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [G:\Mini060713-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\Windows\symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Jun  7 20:32:58.968 2013 (UTC - 4:00)
System Uptime: 0 days 0:02:27.636
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.......................................................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck CA, {2, 8a69e250, 0, 0}
Unable to load image Chtdm642.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Chtdm642.sys
*** ERROR: Module load completed but symbols could not be loaded for Chtdm642.sys
Probably caused by : Chtdm642.sys ( Chtdm642+f37 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*																			 *
*						Bugcheck Analysis									*
*																			 *
*******************************************************************************
PNP_DETECTED_FATAL_ERROR (ca)
PnP encountered a severe error, either as a result of a problem in a driver or
a problem in PnP itself.  The first argument describes the nature of the
problem, the second argument is the address of the PDO.  The other arguments
vary depending on argument 1.
Arguments:
Arg1: 00000002, Invalid PDO
An API which requires a PDO has been called with either an FDO,
a PDO which hasn't been initialized yet (returned to PnP in a
QueryDeviceRelation/BusRelations), or some random piece of
memory.
Arg2: 8a69e250, Purported PDO.
Arg3: 00000000, Driver object.
Arg4: 00000000
Debugging Details:
------------------

BUGCHECK_STR:  0xCA_2
DEVICE_OBJECT: 8a69e250
DRIVER_OBJECT: 8a6b5768
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  DRIVER_FAULT
PROCESS_NAME:  System
LAST_CONTROL_TRANSFER:  from 80586dfc to 804f9f33
STACK_TEXT:
ba4fb8fc 80586dfc 000000ca 00000002 8a69e250 nt!_woutput+0x404
ba4fb98c ba468f37 8a69e250 89d18f40 89d18f3c nt!CcPfOpenVolumesForPrefetch+0x133
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4fb9e0 ba46ab2e 8a4f4818 0000001b 89d18ca8 Chtdm642+0xf37
ba4fba08 ba46a9a1 8a4f4818 8a4f48f4 8a3b7be0 Chtdm642+0x2b2e
ba4fba28 ba468973 1b4f4818 804ef18f 89d18bf0 Chtdm642+0x29a1
ba4fba6c 80592be1 89d18bf0 ba4fba88 00000000 Chtdm642+0x973
ba4fbab0 804f61ea 8a69e658 89f8bb30 00000001 nt!MmExtendSection+0x4db
ba4fbacc 8059229b 8a69e658 8a69e601 89f8bb30 nt!MmPurgeSection+0x35e
ba4fbd24 805927fa 8a652ee8 00000001 00000000 nt!FsRtlAddToTunnelCache+0x140
ba4fbd54 804f698e 00000003 8055b5c0 8056485c nt!RtlGenerate8dot3Name+0x1ef
ba4fbd7c 8053876d 00000000 00000000 8a6968b8 nt!RtlDeleteElementGenericTableAvl+0x42
ba4fbdac 805cff64 00000000 00000000 00000000 nt!MiTrimPte+0x1ee
ba4fbddc 805460de 8053867e 00000001 00000000 nt!IopQueryReconfiguration+0x17
ba4fbdf8 00000000 00000000 00000000 00001f80 nt!ExpRemovePoolTracker+0x6b

STACK_COMMAND:  kb
FOLLOWUP_IP:
Chtdm642+f37
ba468f37 ??			  ???
SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  Chtdm642+f37
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: Chtdm642
IMAGE_NAME:  Chtdm642.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  419c5a66
FAILURE_BUCKET_ID:  0xCA_2_Chtdm642+f37
BUCKET_ID:  0xCA_2_Chtdm642+f37
Followup: MachineOwner
---------
[/CODE]