im trying to figure out how to get the driver bender64.sys v 2.0.19.0 11/27/2006 more stable on win7 64bit operating system. The driver is for a pinnacle pci capture device. i get consistent screen lockups, BSOD's, and sometimes just a crippled system until reset. i have nvidia geforce8400gs, and have updated the latest driver for that (258.96win64) and had the same problems before and after this driver update. the driver that is loaded for the pinnacle av/dv device has been automatically selected from windows, thank god, or i may have never found a driver for this device(i never did for xp64). so there is a driver for windows 7 64bit, but it crashes every time now for me, so something is wrong. i saw a couple guys talking about this topic so i thought i would ask here. thanks.
bender64.sys and irq_not_equal bsod during capture
- Thread starter wolfdogg
- Start date
Hello and welcome.
Please see the sticky thread on how to post crash dump and do so here.
Any driver from before July 2009 has high chances of crashing Windows 7.
For now also too, visit the manufacturer's site of the tv adapter and install the newest driver for it from there. You may not be able to use the card at all if it is too old.
Please see the sticky thread on how to post crash dump and do so here.
Any driver from before July 2009 has high chances of crashing Windows 7.
For now also too, visit the manufacturer's site of the tv adapter and install the newest driver for it from there. You may not be able to use the card at all if it is too old.
no problem, thanks. hmm, thats not good news. aernt alot of the older drivers being recoded for 64bit use though?
i think i will end up making a dual boot sys for 32bit win7 and see if that works in the end. but for now, forget i said that, hehe. i would like to solve this in 64bit first.
ooh, i DID find this. http://cdn.pinnaclesys.com/SupportFiles/Hardware_Installer/readmeHW10.htm thanks for the reminder of looking at the manu's site. thats one frequently overlooked.
i think i will end up making a dual boot sys for 32bit win7 and see if that works in the end. but for now, forget i said that, hehe. i would like to solve this in 64bit first.
ooh, i DID find this. http://cdn.pinnaclesys.com/SupportFiles/Hardware_Installer/readmeHW10.htm thanks for the reminder of looking at the manu's site. thats one frequently overlooked.
Last edited:
Ah VirtualDub user. Excellent software.
Anyhow:
1) Uninstall whatever Packet Sniffer software you have since its driver is too old:
pssdk42 pssdk42.sys Tue Jun 23 08:11:57 2009
Use Wireshark instead. It's the best.
2) Uninstall the wireless Novatel software related to these drivers:
NWADIenum NWADIenum.sys Mon Jun 02 19:25:53 2008
nwusbser2 nwusbser2.sys Fri May 09 14:06:57 2008
nwusbser2 nwusbser2.sys Fri May 09 14:06:57 2008
nwusbmdm nwusbmdm.sys Fri May 09 14:06:57 2008
If you lose wireless connectivity, simply update the driver itself for it from the manufacturer's site.
3) Definitely yes, this must be updated or removed from the system entirely to stop the bsods:
bender64 bender64.sys Mon Nov 27 05:13:48 2006
Do as I said above, for it.
Excellent software.Anyhow:
1) Uninstall whatever Packet Sniffer software you have since its driver is too old:
pssdk42 pssdk42.sys Tue Jun 23 08:11:57 2009
Use Wireshark instead. It's the best.
2) Uninstall the wireless Novatel software related to these drivers:
NWADIenum NWADIenum.sys Mon Jun 02 19:25:53 2008
nwusbser2 nwusbser2.sys Fri May 09 14:06:57 2008
nwusbser2 nwusbser2.sys Fri May 09 14:06:57 2008
nwusbmdm nwusbmdm.sys Fri May 09 14:06:57 2008
If you lose wireless connectivity, simply update the driver itself for it from the manufacturer's site.
3) Definitely yes, this must be updated or removed from the system entirely to stop the bsods:
bender64 bender64.sys Mon Nov 27 05:13:48 2006
Do as I said above, for it.
well, i was posting, when it crashed on me again. doh.
ok, i did the edits you asked me to do; i uninstalled the network device from device manager after removing it from the usb port, rebooted, then uninstalled the verizon vzaccess application, rebooted twice, then reconfigured the usb wireless device as a dialup adapter for connecting to the internet. and i uninstalled the port scanner/network monitor application that i thought might be the one responsible for the "packet sniffer" you mentioned, rebooted, then manually deleted the remenant pssdk42.sys. now it looks like my network recyclebin is complaining in th eevent log, so ill look into the fact that possible the pssdk42.sys was for that, instead of the port scanner.
the program did run better on the first run, which was just now that i tried it. the reason i say it ran better is because the first time i went into capture mode, the capture card starting displaying the video right away without tweaking with it, unlike any time before. so thats progress.
BUT, i had another bluescreen with the bender64 again during that first trial run. i was tweaking it pretty hard, so it never made it through the first run without the BSOD. Specifically, i was toggling between overlay, and preview mode, and preview acceleration odd field, to see if it could handle the load, it froze for a short time, then BlueScreened.
Ill post that dump file now.
ok, i went to c:\windows\minidump\ and found that only the same files i posted last time are in there, there is no new dump file, and last modified date is a month ago. but, and i assume this is related, when the BSOD happened, it dumps the memory somewhere according to the status message and percentage countdown, before the pc reboots automatically from the BSOD.
i dont know if this helps, but i got these two from the event log. it was the only logs i can find from the BSOD. i was hoping someone would recignize a correlation to the memory address below. otherwise please ignore the following and treat as non-related to this thread. .
1
--------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
+ System - Provider [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41 Version 2 Level 1 Task 63 Opcode 0 Keywords 0x8000000000000002 - TimeCreated [ SystemTime] 2010-11-05T08:20:20.366825900Z
EventRecordID 38786 Correlation - Execution [ ProcessID] 4 [ ThreadID] 8
Channel System Computer RedTail - Security [ UserID] S-1-5-18
- EventData
BugcheckCode 209
BugcheckParameter1 0xffffffffffffffd0
BugcheckParameter2 0x2
BugcheckParameter3 0x0
BugcheckParameter4 0xfffff88009648630
SleepInProgress false
PowerButtonTimestamp 0
2
----
The previous system shutdown at 1:18:40 AM on 11/5/2010 was unexpected.
+ System - Provider [ Name] EventLog
- EventID 6008 [ Qualifiers] 32768
Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2010-11-05T08:20:34.000000000Z
EventRecordID 38782 Channel System Computer RedTail Security
- EventData
1:18:40 AM
11/5/2010
690
DA070B0005000500010012002800EC01DA070B0005000500080012002800EC01600900003C000000010000006009000000000000B00400000100000000000000
Binary data:
In Words
0000: 000B07DA 00050005 00120001 01EC0028
0008: 000B07DA 00050005 00120008 01EC0028
0010: 00000960 0000003C 00000001 00000960
0018: 00000000 000004B0 00000001 00000000
In Bytes
0000: DA 07 0B 00 05 00 05 00 Ú.......
0008: 01 00 12 00 28 00 EC 01 ....(.ì.
0010: DA 07 0B 00 05 00 05 00 Ú.......
0018: 08 00 12 00 28 00 EC 01 ....(.ì.
0020: 60 09 00 00 3C 00 00 00 `...<...
0028: 01 00 00 00 60 09 00 00 ....`...
0030: 00 00 00 00 B0 04 00 00 ....°...
0038: 01 00 00 00 00 00 00 00 ........
ok, i did the edits you asked me to do; i uninstalled the network device from device manager after removing it from the usb port, rebooted, then uninstalled the verizon vzaccess application, rebooted twice, then reconfigured the usb wireless device as a dialup adapter for connecting to the internet. and i uninstalled the port scanner/network monitor application that i thought might be the one responsible for the "packet sniffer" you mentioned, rebooted, then manually deleted the remenant pssdk42.sys. now it looks like my network recyclebin is complaining in th eevent log, so ill look into the fact that possible the pssdk42.sys was for that, instead of the port scanner.
the program did run better on the first run, which was just now that i tried it. the reason i say it ran better is because the first time i went into capture mode, the capture card starting displaying the video right away without tweaking with it, unlike any time before. so thats progress.
BUT, i had another bluescreen with the bender64 again during that first trial run. i was tweaking it pretty hard, so it never made it through the first run without the BSOD. Specifically, i was toggling between overlay, and preview mode, and preview acceleration odd field, to see if it could handle the load, it froze for a short time, then BlueScreened.
Ill post that dump file now.
ok, i went to c:\windows\minidump\ and found that only the same files i posted last time are in there, there is no new dump file, and last modified date is a month ago. but, and i assume this is related, when the BSOD happened, it dumps the memory somewhere according to the status message and percentage countdown, before the pc reboots automatically from the BSOD.
i dont know if this helps, but i got these two from the event log. it was the only logs i can find from the BSOD. i was hoping someone would recignize a correlation to the memory address below. otherwise please ignore the following and treat as non-related to this thread.
. 1
--------------
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
+ System - Provider [ Name] Microsoft-Windows-Kernel-Power [ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID 41 Version 2 Level 1 Task 63 Opcode 0 Keywords 0x8000000000000002 - TimeCreated [ SystemTime] 2010-11-05T08:20:20.366825900Z
EventRecordID 38786 Correlation - Execution [ ProcessID] 4 [ ThreadID] 8
Channel System Computer RedTail - Security [ UserID] S-1-5-18
- EventData
BugcheckCode 209
BugcheckParameter1 0xffffffffffffffd0
BugcheckParameter2 0x2
BugcheckParameter3 0x0
BugcheckParameter4 0xfffff88009648630
SleepInProgress false
PowerButtonTimestamp 0
2
----
The previous system shutdown at 1:18:40 AM on 11/5/2010 was unexpected.
+ System - Provider [ Name] EventLog
- EventID 6008 [ Qualifiers] 32768
Level 2 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2010-11-05T08:20:34.000000000Z
EventRecordID 38782 Channel System Computer RedTail Security
- EventData
1:18:40 AM
11/5/2010
690
DA070B0005000500010012002800EC01DA070B0005000500080012002800EC01600900003C000000010000006009000000000000B00400000100000000000000
Binary data:
In Words
0000: 000B07DA 00050005 00120001 01EC0028
0008: 000B07DA 00050005 00120008 01EC0028
0010: 00000960 0000003C 00000001 00000960
0018: 00000000 000004B0 00000001 00000000
In Bytes
0000: DA 07 0B 00 05 00 05 00 Ú.......
0008: 01 00 12 00 28 00 EC 01 ....(.ì.
0010: DA 07 0B 00 05 00 05 00 Ú.......
0018: 08 00 12 00 28 00 EC 01 ....(.ì.
0020: 60 09 00 00 3C 00 00 00 `...<...
0028: 01 00 00 00 60 09 00 00 ....`...
0030: 00 00 00 00 B0 04 00 00 ....°...
0038: 01 00 00 00 00 00 00 00 ........
Last edited:
If there is no new bender.sys that is available from the manufacturer that fits the above criteria, purchase a new card that is compatible with Window 7
OR
dual boot with Windows XP to capture while disabling the card in 7 using the device manager.
i think i missed that the first time, (your #3)
were you saying that definitely the pssdk42 or the bender needs to removed?
note, the BSOD are only happening when using the card.
that sucks that i have to dual boot, i hoped to be leaving win xp behind me
its only been about 3 mos and already theres a definite need to digress from Win7. ouch. and the card is near $200, as much as a new mobo/processor/memory combo.
is there any developers out there that might want to work on the common bender driver?
and what is the best route to light a fire under pinnacle capture card company to get them to support their products for more than 2 years?
it is the dv500, i believe its called. its a pinnacle card, the one with the breakout box with composite and s-video in and out. in device manager its listed as a Pinnacle AV/DV2
Originally it came packaged with studio9, which i never got any use out of because of alot of quirks and system lockups a few years ago i might add. nowadays processors will probably handle the editing alot better. . i just use virtual dub.
are you familiar with this card?
can anyone recommend a new card, primarily for capturing vcr tapes that i will convert to dvd, and also for satellite tv capture for dvr purposes, most of which will eventually be converted to dvd. also i may have a use for a tuner, but since i usually subscribe to satellite i think the tuner will be of little use so isnt really an important feature.
Originally it came packaged with studio9, which i never got any use out of because of alot of quirks and system lockups a few years ago i might add. nowadays processors will probably handle the editing alot better. . i just use virtual dub.
are you familiar with this card?
can anyone recommend a new card, primarily for capturing vcr tapes that i will convert to dvd, and also for satellite tv capture for dvr purposes, most of which will eventually be converted to dvd. also i may have a use for a tuner, but since i usually subscribe to satellite i think the tuner will be of little use so isnt really an important feature.
Last edited:
Had the same problem with an elderly Pinnacle AV/DV2 card. BSOD every time, spent weeks researching problem, no luck. Simplest way without getting a new card is dual boot: using Win7-32bit or WinXp for capture. Try dual boot software "Easy BCD ", far superior to Windows version.
Unfortunately, no. Windows 7 32 bit is still going to crash in all likelihood in the same manner. Old drivers crash 32 or 64 bit all the same. And that's a really old 2006 driver from the company. The same defect in the 64 bit driver is going to be present in the 32 bit driver from the company, so the result will be the same.
So, Vista may work alright but doubtful.
XP will definitely be good.
-------------------
What you can try and may work, is to go through all of Pinnacle's software for other newer models to find like a 2008 or 2009 or ever 2010 driver for 64 bit. Simply copy bender.sys from the extracted download and overwrite the one at C:\Windows\System32\drivers then reboot.
It may actually work and be stable this way.
So, Vista may work alright but doubtful.
XP will definitely be good.
-------------------
What you can try and may work, is to go through all of Pinnacle's software for other newer models to find like a 2008 or 2009 or ever 2010 driver for 64 bit. Simply copy bender.sys from the extracted download and overwrite the one at C:\Windows\System32\drivers then reboot.
It may actually work and be stable this way.
Last edited:
ahh, ive done this sort of thing for many applications in a troubleshooting manner, and especially for drivers for various hardware. thanks for the idea. i will do that. if it works, it will show how much pinnacle neglects their freshly phased out products having a driver that works, and not even knowing it.