jjstewart

Me too! Win 7 64. v. 1.42 Full story: I had v. 1.42 running and the driver was installed; i.e., it appeared in the Sound setup box. Then I installed v. 2.10. But I would reliably get blue screen crashes in an hour or two after starting SountTap which always said, "Process Has Locked Pages." Event Viewer only knew that the system crashed; there was no indication of why. There was nothing showing that led up to the crash. Was it SoundTap 2.10 causing it? The only thing to doubt it was that it happened 1-2 hours after starting SoundTap (after starting, not after ending). The only other thing running was Word. Sometimes I will follow with WavePad, but not always. But the most consistent indicator was that the system crashed EVERY TIME I had run SoundTap earlier. Since I only run SoundTap every week or two, and not always on the same day of the week, that nailed it down for me. Now: my problem with the driver: Because of the BSD problem with 2.10, I uninstalled 2.10 and went back to my 1.42 download. I rebooted after each step. During installation it would come up with a box saying it was going to install the SoundTap Audio Driver and gave some kind of a heads-up that indicated I would need to allow Windows to install the driver. After I OK'd that box, there was no Windows confirmation--it just went right on with the install, and other than the driver install fluke, everything else seemed to act normally. When I ran 1.42 and then my sound source, the "screen" in SoundTap did not indicate that it detected any audio, and so it didn't create a file. I checked ControlPanel/Sound and the driver did not appear in the Playback tab where I had seen it when I last ran SoundTap (before I installed 2.10). I installed Win 7 64 bit when it first came out, having run Vista before. I think I upgraded to SoundTap 2.10 while I was on Win 7. If so, then it worked right and the driver did install before I went to 2.10, but it won't install now after several tries. This may be a hopeless cause--I notice that there have been no solutions posted here.