TV card virtual memory problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My Wintogo PCI Hauppauge TV card uses about 1 Gig of virtual memory so it can
be running on top when other software is also running.
The trouble is that all other TV viewiin/recording software just uses
conventional memory.
I think that is what causes the crashes in MM2, Power (producer,director,
VCRII, etc)
Trouble is, I can't work out the fix. Any ideas, see below for details of
crash.
Bob
This is a copy of the failure report I get.
Computer: BOBNEUMANN
Description:
Faulting application moviemk.exe, version 2.1.4026.0, faulting module
unknown, version 0.0.0.0, fault address 0x6689b9e0.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6d 6f 76 ure mov
0018: 69 65 6d 6b 2e 65 78 65 iemk.exe
0020: 20 32 2e 31 2e 34 30 32 2.1.402
0028: 36 2e 30 20 69 6e 20 75 6.0 in u
0030: 6e 6b 6e 6f 77 6e 20 30 nknown 0
0038: 2e 30 2e 30 2e 30 20 61 .0.0.0 a
0040: 74 20 6f 66 66 73 65 74 t offset
0048: 20 36 36 38 39 62 39 65 6689b9e
0050: 30 0d 0a 0..
 
Hi Bob!

Thanks for posting the fault address! I was able to find the Watson log you
sent into Microsoft.

It looks like the faulting module is "quicktime.qts" -- You might try doing
a quick search for the file, and re-naming it temporarily to see if it
resolves the issue. I'll bet all three of your capture applications are
DShow based, and are somehow picking up this 3rd party filter in their
capture graphs.

I *vaguely* remember a report about this file have some sort of heap
overflow/security fix release, so you may also want to check to see if you
have the latest version.

Let me know if this is useful...
Thanks!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thanks Kristen,

Renaming "quicktime.qts" to "quicktime.qts.old" seems to have done the
trick, don't quite know how ?
You are a mega star for sussing this out, it has troubled me for ages.
Thanks again
Bob

Kristen Miller said:
Hi Bob!

Thanks for posting the fault address! I was able to find the Watson log you
sent into Microsoft.

It looks like the faulting module is "quicktime.qts" -- You might try doing
a quick search for the file, and re-naming it temporarily to see if it
resolves the issue. I'll bet all three of your capture applications are
DShow based, and are somehow picking up this 3rd party filter in their
capture graphs.

I *vaguely* remember a report about this file have some sort of heap
overflow/security fix release, so you may also want to check to see if you
have the latest version.

Let me know if this is useful...
Thanks!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.


Bob Neumann said:
My Wintogo PCI Hauppauge TV card uses about 1 Gig of virtual memory so it
can
be running on top when other software is also running.
The trouble is that all other TV viewiin/recording software just uses
conventional memory.
I think that is what causes the crashes in MM2, Power (producer,director,
VCRII, etc)
Trouble is, I can't work out the fix. Any ideas, see below for details of
crash.
Bob
This is a copy of the failure report I get.
Computer: BOBNEUMANN
Description:
Faulting application moviemk.exe, version 2.1.4026.0, faulting module
unknown, version 0.0.0.0, fault address 0x6689b9e0.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6d 6f 76 ure mov
0018: 69 65 6d 6b 2e 65 78 65 iemk.exe
0020: 20 32 2e 31 2e 34 30 32 2.1.402
0028: 36 2e 30 20 69 6e 20 75 6.0 in u
0030: 6e 6b 6e 6f 77 6e 20 30 nknown 0
0038: 2e 30 2e 30 2e 30 20 61 .0.0.0 a
0040: 74 20 6f 66 66 73 65 74 t offset
0048: 20 36 36 38 39 62 39 65 6689b9e
0050: 30 0d 0a 0..
Click to expand...
Click to expand...
 
I solved the problem by first renaming the quicktime file quicktime.qts and
then by removing Quicktime altogether, it seem that it interferrs with the TV
card driver and other capture type of problems.
I have now purchased a licence for Power Director 3 it is just great for
Captuing/editing/authorising and burning DVD.
Thanks for your help
Bob

Kristen Miller said:
Hi Bob!

Thanks for posting the fault address! I was able to find the Watson log you
sent into Microsoft.

It looks like the faulting module is "quicktime.qts" -- You might try doing
a quick search for the file, and re-naming it temporarily to see if it
resolves the issue. I'll bet all three of your capture applications are
DShow based, and are somehow picking up this 3rd party filter in their
capture graphs.

I *vaguely* remember a report about this file have some sort of heap
overflow/security fix release, so you may also want to check to see if you
have the latest version.

Let me know if this is useful...
Thanks!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.


Bob Neumann said:
My Wintogo PCI Hauppauge TV card uses about 1 Gig of virtual memory so it
can
be running on top when other software is also running.
The trouble is that all other TV viewiin/recording software just uses
conventional memory.
I think that is what causes the crashes in MM2, Power (producer,director,
VCRII, etc)
Trouble is, I can't work out the fix. Any ideas, see below for details of
crash.
Bob
This is a copy of the failure report I get.
Computer: BOBNEUMANN
Description:
Faulting application moviemk.exe, version 2.1.4026.0, faulting module
unknown, version 0.0.0.0, fault address 0x6689b9e0.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6d 6f 76 ure mov
0018: 69 65 6d 6b 2e 65 78 65 iemk.exe
0020: 20 32 2e 31 2e 34 30 32 2.1.402
0028: 36 2e 30 20 69 6e 20 75 6.0 in u
0030: 6e 6b 6e 6f 77 6e 20 30 nknown 0
0038: 2e 30 2e 30 2e 30 20 61 .0.0.0 a
0040: 74 20 6f 66 66 73 65 74 t offset
0048: 20 36 36 38 39 62 39 65 6689b9e
0050: 30 0d 0a 0..
Click to expand...
Click to expand...
 
Terrific! I'm glad your capture is back up and running!

Best Wishes!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.



Bob Neumann said:
I solved the problem by first renaming the quicktime file quicktime.qts and
then by removing Quicktime altogether, it seem that it interferrs with the
TV
card driver and other capture type of problems.
I have now purchased a licence for Power Director 3 it is just great for
Captuing/editing/authorising and burning DVD.
Thanks for your help
Bob

Kristen Miller said:
Hi Bob!

Thanks for posting the fault address! I was able to find the Watson log
you
sent into Microsoft.

It looks like the faulting module is "quicktime.qts" -- You might try
doing
a quick search for the file, and re-naming it temporarily to see if it
resolves the issue. I'll bet all three of your capture applications are
DShow based, and are somehow picking up this 3rd party filter in their
capture graphs.

I *vaguely* remember a report about this file have some sort of heap
overflow/security fix release, so you may also want to check to see if
you
have the latest version.

Let me know if this is useful...
Thanks!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no
rights.


Bob Neumann said:
My Wintogo PCI Hauppauge TV card uses about 1 Gig of virtual memory so
it
can
be running on top when other software is also running.
The trouble is that all other TV viewiin/recording software just uses
conventional memory.
I think that is what causes the crashes in MM2, Power
(producer,director,
VCRII, etc)
Trouble is, I can't work out the fix. Any ideas, see below for details
of
crash.
Bob
This is a copy of the failure report I get.
Computer: BOBNEUMANN
Description:
Faulting application moviemk.exe, version 2.1.4026.0, faulting module
unknown, version 0.0.0.0, fault address 0x6689b9e0.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6d 6f 76 ure mov
0018: 69 65 6d 6b 2e 65 78 65 iemk.exe
0020: 20 32 2e 31 2e 34 30 32 2.1.402
0028: 36 2e 30 20 69 6e 20 75 6.0 in u
0030: 6e 6b 6e 6f 77 6e 20 30 nknown 0
0038: 2e 30 2e 30 2e 30 20 61 .0.0.0 a
0040: 74 20 6f 66 66 73 65 74 t offset
0048: 20 36 36 38 39 62 39 65 6689b9e
0050: 30 0d 0a 0..


:

When I use MM2, Powerproducer or Powerdirector and try to capture
video
from
my TV card the programs display an error box which basically says for
example
windows movie maker has encountered a problem and needs to close. We
are
sorry for the inconvenince." The program continues to function and
completes
the capture but when I close the error bow it freezes the screen and I
have
to end the program using task manager. Can someone help ?
Click to expand...
Click to expand...
Click to expand...
 
Hi Kristen,
The saga of this problem continues.
I got a reply form someone else suggesting that files (relating to
Quicktime) in NERO might cause the problem, see below.
"It may be of interest that a problem with the Pinnacle PCTV card that I
use was traced to an interaction with the latest version of Nero, and
specifically its filters for Quicktime. The problem is cured by
renaming those (NeQTADec.ax and NeQTVDec.ax in Program Files\Common
Files\Ahead\DSFilter), so this may arise with other video products and
other manifestations of Quicktime"

I renamed the two files, reloaded Quicktime and hey presto it's all fixed.
You were right it is a quicktime problem.
Thanks again, Bob

Kristen Miller said:
Terrific! I'm glad your capture is back up and running!

Best Wishes!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.



Bob Neumann said:
I solved the problem by first renaming the quicktime file quicktime.qts and
then by removing Quicktime altogether, it seem that it interferrs with the
TV
card driver and other capture type of problems.
I have now purchased a licence for Power Director 3 it is just great for
Captuing/editing/authorising and burning DVD.
Thanks for your help
Bob

Kristen Miller said:
Hi Bob!

Thanks for posting the fault address! I was able to find the Watson log
you
sent into Microsoft.

It looks like the faulting module is "quicktime.qts" -- You might try
doing
a quick search for the file, and re-naming it temporarily to see if it
resolves the issue. I'll bet all three of your capture applications are
DShow based, and are somehow picking up this 3rd party filter in their
capture graphs.

I *vaguely* remember a report about this file have some sort of heap
overflow/security fix release, so you may also want to check to see if
you
have the latest version.

Let me know if this is useful...
Thanks!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no
rights.


My Wintogo PCI Hauppauge TV card uses about 1 Gig of virtual memory so
it
can
be running on top when other software is also running.
The trouble is that all other TV viewiin/recording software just uses
conventional memory.
I think that is what causes the crashes in MM2, Power
(producer,director,
VCRII, etc)
Trouble is, I can't work out the fix. Any ideas, see below for details
of
crash.
Bob
This is a copy of the failure report I get.
Computer: BOBNEUMANN
Description:
Faulting application moviemk.exe, version 2.1.4026.0, faulting module
unknown, version 0.0.0.0, fault address 0x6689b9e0.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6d 6f 76 ure mov
0018: 69 65 6d 6b 2e 65 78 65 iemk.exe
0020: 20 32 2e 31 2e 34 30 32 2.1.402
0028: 36 2e 30 20 69 6e 20 75 6.0 in u
0030: 6e 6b 6e 6f 77 6e 20 30 nknown 0
0038: 2e 30 2e 30 2e 30 20 61 .0.0.0 a
0040: 74 20 6f 66 66 73 65 74 t offset
0048: 20 36 36 38 39 62 39 65 6689b9e
0050: 30 0d 0a 0..


:

When I use MM2, Powerproducer or Powerdirector and try to capture
video
from
my TV card the programs display an error box which basically says for
example
windows movie maker has encountered a problem and needs to close. We
are
sorry for the inconvenince." The program continues to function and
completes
the capture but when I close the error bow it freezes the screen and I
have
to end the program using task manager. Can someone help ?
Click to expand...
Click to expand...
Click to expand...
 
Thanks Bob!

I'll add the information you've provided to the history on this issue here
at MS. It's a much better solution, and allows people to keep quicktime
installed :)

Thanks for posting!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no rights.


Bob Neumann said:
Hi Kristen,
The saga of this problem continues.
I got a reply form someone else suggesting that files (relating to
Quicktime) in NERO might cause the problem, see below.
"It may be of interest that a problem with the Pinnacle PCTV card that I
use was traced to an interaction with the latest version of Nero, and
specifically its filters for Quicktime. The problem is cured by
renaming those (NeQTADec.ax and NeQTVDec.ax in Program Files\Common
Files\Ahead\DSFilter), so this may arise with other video products and
other manifestations of Quicktime"

I renamed the two files, reloaded Quicktime and hey presto it's all fixed.
You were right it is a quicktime problem.
Thanks again, Bob

Kristen Miller said:
Terrific! I'm glad your capture is back up and running!

Best Wishes!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no
rights.



Bob Neumann said:
I solved the problem by first renaming the quicktime file quicktime.qts
and
then by removing Quicktime altogether, it seem that it interferrs with
the
TV
card driver and other capture type of problems.
I have now purchased a licence for Power Director 3 it is just great
for
Captuing/editing/authorising and burning DVD.
Thanks for your help
Bob

:

Hi Bob!

Thanks for posting the fault address! I was able to find the Watson
log
you
sent into Microsoft.

It looks like the faulting module is "quicktime.qts" -- You might try
doing
a quick search for the file, and re-naming it temporarily to see if it
resolves the issue. I'll bet all three of your capture applications
are
DShow based, and are somehow picking up this 3rd party filter in their
capture graphs.

I *vaguely* remember a report about this file have some sort of heap
overflow/security fix release, so you may also want to check to see if
you
have the latest version.

Let me know if this is useful...
Thanks!
-Kristen Miller [MS]
This posting is provided "AS IS" with no warranties, and confers no
rights.


My Wintogo PCI Hauppauge TV card uses about 1 Gig of virtual memory
so
it
can
be running on top when other software is also running.
The trouble is that all other TV viewiin/recording software just
uses
conventional memory.
I think that is what causes the crashes in MM2, Power
(producer,director,
VCRII, etc)
Trouble is, I can't work out the fix. Any ideas, see below for
details
of
crash.
Bob
This is a copy of the failure report I get.
Computer: BOBNEUMANN
Description:
Faulting application moviemk.exe, version 2.1.4026.0, faulting
module
unknown, version 0.0.0.0, fault address 0x6689b9e0.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 6d 6f 76 ure mov
0018: 69 65 6d 6b 2e 65 78 65 iemk.exe
0020: 20 32 2e 31 2e 34 30 32 2.1.402
0028: 36 2e 30 20 69 6e 20 75 6.0 in u
0030: 6e 6b 6e 6f 77 6e 20 30 nknown 0
0038: 2e 30 2e 30 2e 30 20 61 .0.0.0 a
0040: 74 20 6f 66 66 73 65 74 t offset
0048: 20 36 36 38 39 62 39 65 6689b9e
0050: 30 0d 0a 0..


:

When I use MM2, Powerproducer or Powerdirector and try to capture
video
from
my TV card the programs display an error box which basically says
for
example
windows movie maker has encountered a problem and needs to close.
We
are
sorry for the inconvenince." The program continues to function and
completes
the capture but when I close the error bow it freezes the screen
and I
have
to end the program using task manager. Can someone help ?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top