Would you try installing the program in safe mode? Maybe it can be installed in that mode without problems.
im pretty sure it gives a bsod when you log back into normal mode and the driver starts to load.
i have done a bit of work of my own in sorting this out, but i thought il discuss with you.
now, can you take a look at:
ntkrnlpa.exe i think this is microsoft related
Ironx86.sys i think this is symantec related
halmaci.dll microsoft related
symnets.sys symantec related
these could be conflicting, so please take a look at them, maybe theres an update available, or they can be disabled or something.
btw, is there an debug installer of nis 2011 i can have. basically one that gives you a log of the install, could be helpfull.
till you work on this i am trying to solve my windows 7 service pack 1 and the other update problem (they give me bsod) so maybe their problems are connected to the nis problem.
thanks
As mentioned in the previous thread, if Windows can't update itself, there is something wrong with the operating system and it's unlikely that there is anything that can be fixed on the NIS end.
One thing that occurred to me today would be to turn on verifier. At a cmd prompt enter...
verifier /flags 4059 /driver symefa.sys ironx86.sys symnets.sys
... and then restart your system. You can then try to reinstall NIS and capture any BSODs that occur. The BSOD is likely to be at a different spot so the dump will be valuable. Also take note of what the BSOD actually says on-screen.
hey
so there is a problem with windows, i did a sfc/scannow cmd command, it said it fixed some issues successfully. so maybe ill try installing the updates again. to solve this issue i have got this issue in another forum, which are for windows. (non symantec related)
what does this command do exactly, does it just check the drivers are working and are in place?
if its a windows problem perhaps you can help me in that? which may solve this problem too
thanks
SFC stands for System File Check. It validates that all of Microsoft's operating system files are in good shape. From the sound of it, SFC detected that some portion of your operating system installation had been damaged and repaired it. That potentially could explain all of the issues you've been having. The fact that some of the files have been damaged is concerning and, along with the dump you sent me, would indicate to me that either your hard drive is failing, your memory is faulty or your motherboard has issues.
thanks for the explanation, but i meant what does the verify command for drivers that you wrote do, not sfc.
i am considering partitioning my system and installing a second copy of windows 7
any guidance into doing this?
Verifier is a tool that is built into Windows that Microsoft provides to enable a number of built-in diagnostic features. The operating system is designed to be resilient and handle a lot of unexpected or invalid operations gracefully. When verifier is enabled it actually reports these unexpect and/or invalid operations. Very frequently verifier will detect one of the operations before a BSOD occurs. The earlier the error is detected, the more likely it is that the source of the problem can be determined.
Note that enabling verifier will slow your operating system down. At some point you'll want to simply run 'verifier' and from there choose to reset the verifier options.
thanks, for the clear info.
i think its time for the thread to be closed. the problem was not exactly fixed, but I made a partition on my hard drive, installed win 7 and then installed nis. it works fine, im now slowly merging things from my older partition to my newer partition. so thanks to everyone for their help and its time to close this thread.
thanks :)
Thanks for being patient and helping with this. Let us know if any new issues show up while or after migrating to the new partition.