jpara.sys

Does anyone have any idea what the driver “jpara.sys” is? I have a
client who has a customer that’s getting an occasional blue screen at
boot on a 64-bit Vista system when my web camera is plugged, and he
thinks this driver is involved.

If you do a web search for “jpara.sys”, one of the slimy “what does this
DLL do” sites says that it comes from Videology. That’s ironic, because
Videology is actually my client in this case, and I know this driver
didn’t come from them. Further, this is on a Vista 64 system, and
“jpara.sys” is apparently located in \windows\syswow64\drivers, which
makes it rather useless.

If anyone finds a copy of this driver on their hard disk and could send
me a copy, I’d appreciate it.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

If it is loading on a 64-bit system then it must be signed. Does the signature help identify who created it (it is meant to, after all!) ?

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Tim Roberts
Sent: Friday, June 12, 2009 9:32 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] jpara.sys

Does anyone have any idea what the driver “jpara.sys” is? I have a
client who has a customer that’s getting an occasional blue screen at
boot on a 64-bit Vista system when my web camera is plugged, and he
thinks this driver is involved.

If you do a web search for “jpara.sys”, one of the slimy “what does this
DLL do” sites says that it comes from Videology. That’s ironic, because
Videology is actually my client in this case, and I know this driver
didn’t come from them. Further, this is on a Vista 64 system, and
“jpara.sys” is apparently located in \windows\syswow64\drivers, which
makes it rather useless.

If anyone finds a copy of this driver on their hard disk and could send
me a copy, I’d appreciate it.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

xxxxx@McAfee.com wrote:

If it is loading on a 64-bit system then it must be signed. Does the signature help identify who created it (it is meant to, after all!) ?

I *think* the whole thing is a red herring, and I’m looking for evidence
to establish that The fact that it lives in syswow64\drivers tells me
that it was copied there by some 32-bit application, which implies to me
that it is a 32-bit driver, and hence is never actually being loaded at
all. He’s getting an event log message saying that the driver failed to
load because it was “incompatible with this system,” further adding
credence to my theory. He SAYS he only sees that message in the event
log when my camera is plugged in, but I suspect it’s been there all
along and he simply has not noticed it.

I’m trying to have him send me a copy so I can establish this for sure,
but it’s always awkward trying to do second level support for the
customers of my customers, because I end up going through two levels of
intermediaries.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.