*****not sure if this thread should be in Computer********
I recently upgraded my PC to Win 10 Pro 64, re-installed AVISynth (32bit) and VirtualDub (1.10.4 build 35491). Iíve had a few issues with my Osprey 827e video card. First, I couldn't capture digital audio, only analog. Iíve been in contact with Ospreyís friendly tech support and they gave me a link to an older driver which worked for digital audio, but now about 50% of the time when I attempt to capture .AVI via VirtualDub my PC crashes with the Windows blue screen Stopcode message (fault ďOsprey HDCap_64.sysĒ).
The trick that seemed to work 50% of the time was setting VirtualDub to Compatibility mode of Windows 8. The 827e card is Win 10 compatible. Iíve done all the recommendations from Osprey (disable C-States and Boot Secure in BIOS, setting performance to max, power save modes to Never etc).
Iím not sure if this version of VirtualDub is 64 bit? Would that matter since my version of Win is 64? Tech support has been very patient, but Iím wondering if they soon will say itís my PC and nothing else they can do. At this point I canít remember if my PC crashed with the latest driver version.
Please help. Thank you in advance.
+ Reply to Thread
Results 1 to 10 of 10
Do a memory test to make sure your ram is stable,i always do that when win 10 starts acting funny.I think,therefore i am a hamster.
I ran Windows Memory Diagnostic and says "detected no errors".
I forgot to mention I sometimes get the Windows Stopcode blue screen when I shut the PC down as well.
Sounds like you have some driver issues.I think,therefore i am a hamster.
Yes it's the driver that's causing the PC to crash. If I disable it, I don't get the Stopcode but obviously I can't use the video card. Osprey has given me both 32 & 64 bit drivers for the current one on the web site, and an older driver. They say no one else has had any driver issues with Win 10. Is there anything else I can check besides RAM?
Do a windows sfc /scannow,copy that into a Command Prompt with admin rights.I think,therefore i am a hamster.
Ok did the scannow; "Window did not find any violations".
I just remembered that when I did Windows Memory Diagnostic test, I had the driver disabled, does that matter?
no. a memory test only accesses the ram.
maybe try VirtualDub2
"a lot of people are better dead" - prisoner KSC2-303
try reading the PDF troubleshooting guide - https://www.ospreyvideo.com/images/osprey/PCIe_Capture/Osprey_800_series_PCIe_188.8.131.52_Readme.pdf
Last edited by october262; 12th Feb 2020 at 17:59.
Could be your system just doesn't like osprey,not much you can do about it unless you get drivers that work.I think,therefore i am a hamster.