I have recent problems with NIS 2009. It happened after the last Vista 64 bit update. All the securities were tuned off, firewall, malware and auto protection. I have Norton to fix it. After that, it went to liveupdate. Later, BSOD developed. This driver is the problem according to the Windows debugger, module name SRTSP64.SYS. Location is C:\Windows\system32\drivers\NISx64\1000000.07D\SRTSP64.SYS. Process name is ccSvcHst.exe. Below is the information that Windows gathered error code 0xC4.
Product Windows
Problem Shut down unexpectedly
Date11/11/2008 11:07 PM
Status More information available
Problem signature Problem Event Name: BlueScreenOS Version: 6.0.6001.2.1.0.256.1Locale ID: 1033
Files that help describe the problem (some files may no longer be available) Mini111108-04.dmpsysdata.xmlVersion.txt
Extra information about the problem
BCCode: c4BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000001
BCP4: 0000000000000000
OS Version: 6_0_6001Service Pack: 1_0Product: 256_1Server information: ddf5e68e-bf09-456d-a1c9-97ee51b1f7a8
I contacted support by phone. He claimed is known problem and he provided me with NIS 2008 saying the solution could take one to two months. He did not give me an incident number. Do you know about this problem? Can the most recent patch solve this? Your help would be appreciated.
I have recent problems with NIS 2009. It happened after the last Vista 64 bit update. All the securities were tuned off, firewall, malware and auto protection. I have Norton to fix it. After that, it went to liveupdate. Later, BSOD developed. This driver is the problem according to the Windows debugger, module name SRTSP64.SYS. Location is C:\Windows\system32\drivers\NISx64\1000000.07D\SRTSP64.SYS. Process name is ccSvcHst.exe. Below is the information that Windows gathered error code 0xC4.
Product Windows
Problem Shut down unexpectedly
Date11/11/2008 11:07 PM
Status More information available
Problem signature Problem Event Name: BlueScreenOS Version: 6.0.6001.2.1.0.256.1Locale ID: 1033
Files that help describe the problem (some files may no longer be available) Mini111108-04.dmpsysdata.xmlVersion.txt
Extra information about the problem
BCCode: c4BCP1: 0000000000000000
BCP2: 0000000000000000
BCP3: 0000000000000001
BCP4: 0000000000000000
OS Version: 6_0_6001Service Pack: 1_0Product: 256_1Server information: ddf5e68e-bf09-456d-a1c9-97ee51b1f7a8
I contacted support by phone. He claimed is known problem and he provided me with NIS 2008 saying the solution could take one to two months. He did not give me an incident number. Do you know about this problem? Can the most recent patch solve this? Your help would be appreciated.
1)The problem is reproducible. After installing NIS 2009 and ran liveupdate, just before the installations were completed I have the same BSOD 0xC4. There was about 15 MB. After it restarted, I restarted liveupdate. It downloaded about 42 MB. After completed the updates, I had a chance to check what the updates were about, it required restarting. After restarting, it did not let me go to Windows, the same BSOD 0xC4. I needed to uninstall the program in order to go to Windows. The most recent update did not resolve this problem. Have you seen this problem before?
2)Yes.
Do you suggest reinstalling the program and disabling the verifier? Is this driver a signed driver? I hope that a solution is possible so I can resume using NIS 2009. It is better program than 2008.
Medico, the problem is occurring because you are running verifier on the driver. If you stop running verifier on the driver the problem will go away. We also haven’t seen this problem with verifier in the past so getting the dump that Snehansh requested would help us understand the problem too.
Reese, thank you for your response, I will email the dump file to Snehansh and you, I do not see a way to attach the dump file. I have never had this problem before. NIS 2008 is working with no problem. I do not understand why this problem with 2009. I want to mention that autoprotect was disable. When I click to enable it, that triggered BSOD 0xC4 as before. After the update, it happened before reaching Windows. Again, I needed to uninstall to get to Windows. I would like to see solution before installing NIS 2009 again. I got tired of BSOD. I hope that a solution will be available soon.
I've sent you a Private Message (Look at the top right of this screen at the icon). Please check this message for instructions on how to get this file to us.
Message Edited by Tim_Lopez on 11-16-2008 01:31 PM
I checked the driver verifier, Deadlock Detection. This is not running. It is off. However, why is 2008 running fine and no 2009? After the installation, it was ok. The BSOD 0xC4 was triggered only when I clicked enable autoprotect and/or update software using Liveupdate.
0xc4 is a Verifier error so you must still have verifier checking the driver for something.
As far as the 2008 version working and the 2009 not, it's because they are not the same code. Once we look at the dump we should be able to better understand what verifier doesn't like about the 2009 version.
Message Edited by reese_anschultz on 11-17-2008 12:24 PM
Thank you for your response.I want to emphasize this so to pinpoint the cause of the problem. I was using NIS 2009 with no problems until last Vista 64-bit update and Norton liveupdate. The solution of the problem deals with Vista 64-bit last update and Liveupdate. Something changed that triggered the driver verifier to determine this driver SRTSP64.SYS. would corrupt the system.
Medico, the problem is that you are running Verifier against this driver. If you stop running verifier against this driver your problem will go away (and your system will probably speed up as well.)
In your particular case, Verifier is detecting a marginally incorrect, and harmless in this case, use of the operating system. We will be changing the code so that verifier will no longer detect this behavior.
As far as timing for this 'fix' is concerned, I can't commit to anything. This isn't really a 'bug' per se so it may not have a high priority for getting resolved.
Message Edited by reese_anschultz on 11-21-2008 11:13 AM
I researched how to disable verifier against one driver and I am unable to find anything for Vista 64 bit. I cannot do it on safe mode. The driver is loaded and it cannot be disable. Can you tell how to disable driver verifier against SRTSP64.SYS only until you can resolve this problem? I do not want to disable all drivers’ verifier, as you said just for that problematic diver. I hope that it would not take one year for the complete solution. Is that what you expect?
From what I gather from your description, you are trying to enable verifier against all the drivers on the system except srtsp64.sys. You can do that by typing verifier on the command line and then following the "Configuring Volatile Settings by Using Driver Verifier Manager (Windows XP and later)" section on the following page - http://msdn.microsoft.com/en-us/library/ms792869.aspx
Thank you for your reply. I tried to remove it following instructions but I got error that does not let me remove it because the driver is loaded. What is the process to unload the driver? I try to do it with NIS 2008. By unloading the file, I hope that I can install NIS 2009 and stop BSOD until you come with solution. You help will be appreciated it.
You should be able to go into "Safe Mode" and configure it.
Instead of what you are trying to do - couldn't you just enable the verifier settings for just the drivers that you need to debug instead of enabling it on all the drivers (including srtsp64) ?
I used the verifier as developer and I had to tell which drivers should be verified and how. It was rough but I was able to have NIS 2009 working until you fix the problem. I hope it would not take long time. I hope what I did will not affect for futures verified drivers.
icon). Please check this message for instructions on how to get this file to us.