I downloaded the trail version to try out and while trying it out I get a BSOD.
it is a Windows 2003 SP2 server running in a Hyper-V virtual machine and it BSOD's the server when using the COM port with a IRQL_NOT_LESS_OR_EQUAL in the ftvspenum.sys
I'm trying to transmit a fax and it appears that it is doing this during transmission. I can connect to the com port on the Windows 2003 Hyper-V virtual machine and send modem commands which all seem fine.
1. What's the OS on your virtual machine; 2. What software do you use to send faxes; 3. Where does BSOD occur - virtual machine or Windows 2003 SP2; 4. On the whole could you please describe all your actions step by step that lead to BSOD? The more details the better.
The BSOD occurs on the Windows 2003 SP2 (guest OS).
It appears that it is BSODing while it transmitting the FAX, because I see the connection in the Fabula Tech software, it appears it’s doing something for several seconds and then it BSOD’s. On the Fax Sr. software it will say “sending” so I assuming that’s transmitting the fax when it BSODs.
I can also connect to the modem and run modem at commands without it BSODing, so I assume it’s at some point in the transmission.
Thanks for your reply. Could you please inform me about NSPK and fax software setting so we could reproduce the issue in our lab? The more details the better. Also I need to know if you experienced BSOD using a different faxing software and if BSOD occurs only in conjunction NSPK + your faxing software.
And could you please send me sysinfo from both machines to SUPPORT@FABULATECH.COM
Start -> Programs -> Accessories -> System Tools -> System Information -> File -> Save
And also I need kernel memory dump file: 1) Go to the System Properties ("Windows + Break" buttons on the keyboard) 2) Open "Advanced" tab 3) In the "Startup and Recovery" section press "Settings" button 4) Here you can see "Write debugging information" section. You must choose "Kernel memory dump" and remember the path to the file - MEMORY.DMP By default it's "%SystemRoot%\MEMORY.DMP" 5) Reproduce the BSOD once again 6) Go to the windows root folder and find that file: "Windows/MEMORY.DMP" 7) Zip this file and upload to our server (see private message).