VS 9 vanishes
Moderator: Ken Berry
-
elchiki
VS 9 vanishes
Sometimes VS 9 vanishes with the usual error panel of windows mentioning: error ntdll.dll. Any idea ????
-
michaeltee
- Posts: 528
- Joined: Wed Aug 17, 2005 5:19 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: HP 82F1
- processor: Intel Core I5 7400 3 GHz
- ram: 16 GB DC
- Video Card: Intel HD Graphics 630
- sound_card: Realtek High Definition Audio
- Hard_Drive_Capacity: 2TB Hybrid
- Monitor/Display Make & Model: Samsung S24D300
- Corel programs: Installed: PS Pro 2021, VS Ultimate 2020
- Location: California, USA
Re: VS 9 vanishes
Which Windows operating system are you running... Windows 2000 or XP?elchiki wrote:Sometimes VS 9 vanishes with the usual error panel of windows mentioning: error ntdll.dll. Any idea ????
-
elchiki
-
elchiki
To tell the truth, as I have had this problem before, I reintalled all Windows !!!! and load VS 9 as first program = same result.
If none of the users of VS9 with XP have encountered the same problem as I....I'm just getting creasy because all my PC is new and I intalled the full version of VS 9.
In fact, sometimes, when reading the video, the disk (or program) starts working (noise) and a few seconds later the error message of windows (error ntdll.dll) appears.
If one solves this issue, I send him a medal !!!!
If none of the users of VS9 with XP have encountered the same problem as I....I'm just getting creasy because all my PC is new and I intalled the full version of VS 9.
In fact, sometimes, when reading the video, the disk (or program) starts working (noise) and a few seconds later the error message of windows (error ntdll.dll) appears.
If one solves this issue, I send him a medal !!!!
-
GeorgeBW
Hi,
This may not fully resolve your problem, but will nevertheless create a better set of fundamental conditions for UVS to work more successfully.
You are running XP.. If you have not converted to NTFS during the installation then you should do it... The NTFS conversion program should be in Accessories or System Tools in the main menu.. Should be OK but Back up any invaluable files just in case.. The reason.. If you are still using FAT format... WIndows will impose a 2GB limit on file size.. no matter how optimistic UVS may be about exceeding it.. This could account for the dropping-out phenomena..
Secondly.. 2GB of RAM is a goodly chunk, and it is a pity if your paging file isn't optimised to get the best out of both worlds. I would change the paging file to around 5GB minimum... if you have a good sized drive. Set both Max and Min to 5GB.. This is particularly helpful with video rendering, which is about the most arduous task that a PC can be asked to do..
Thirdly.. if you give a fuller description of your problem with info regarding the task and settings.. also plus details of your system... there is a good chance it will attract a complete solution..
Good luck
George
This may not fully resolve your problem, but will nevertheless create a better set of fundamental conditions for UVS to work more successfully.
You are running XP.. If you have not converted to NTFS during the installation then you should do it... The NTFS conversion program should be in Accessories or System Tools in the main menu.. Should be OK but Back up any invaluable files just in case.. The reason.. If you are still using FAT format... WIndows will impose a 2GB limit on file size.. no matter how optimistic UVS may be about exceeding it.. This could account for the dropping-out phenomena..
Secondly.. 2GB of RAM is a goodly chunk, and it is a pity if your paging file isn't optimised to get the best out of both worlds. I would change the paging file to around 5GB minimum... if you have a good sized drive. Set both Max and Min to 5GB.. This is particularly helpful with video rendering, which is about the most arduous task that a PC can be asked to do..
Thirdly.. if you give a fuller description of your problem with info regarding the task and settings.. also plus details of your system... there is a good chance it will attract a complete solution..
Good luck
George
-
Ken Berry
- Site Admin
- Posts: 22481
- Joined: Fri Dec 10, 2004 9:36 pm
- System_Drive: C
- 32bit or 64bit: 64 Bit
- motherboard: Gigabyte B550M DS3H AC
- processor: AMD Ryzen 9 5900X
- ram: 32 GB DDR4
- Video Card: AMD RX 6600 XT
- Hard_Drive_Capacity: 1 TB SSD + 2 TB HDD
- Monitor/Display Make & Model: Kogan 32" 4K 3840 x 2160
- Corel programs: VS2022; PSP2023; DRAW2021; Painter 2022
- Location: Levin, New Zealand
The file ntdll.dll is a Windows system file and not a Ulead one. Microsoft has a number of articles on it which you can find at http://search.microsoft.com/search/resu ... =ntdll.dll
The first three articles may have something of relevance to your problem: it seems fairly obvious (??) that something is causing a clash between VS9 and that system file and you may have to find another copy and reload the system file... If you are game, you can get another copy (free) at http://www.dll-files.com/dllindex/dll-files.shtml?ntdll
The first three articles may have something of relevance to your problem: it seems fairly obvious (??) that something is causing a clash between VS9 and that system file and you may have to find another copy and reload the system file... If you are game, you can get another copy (free) at http://www.dll-files.com/dllindex/dll-files.shtml?ntdll
Ken Berry
-
GeorgeBW
Hi Ken,
A good bit of research you have done there..
I have checked my PC's (3 x PC LAN) ...particularly the one dedicated to video work, which has UVS on board.. and found that this particular PC has two copies of ntdll.dll which appear to have been installed with the inititial Windows load.. However, the general purpose PC which I am now using has 4 copies... 2 of which appear to have been placed in the SP2 cache in the Windows folder during the SP2 upgrade. Yet all 3 of the PCs on the LAN have been upgraded to SP2... so this varying selectivity is a bit of a mystery..
Do you think System File Checker might help... if it is possibly a corrupt system file problem? Running the sfc /scannow command line from the Run box will envoke a Windows System File Check and repair or replace any corrupted files. But, as the WindowsXP installation CD needs to be in the drive for this scan ...any replacements will be in the mod-state form of the original file..
ntdll.dll is a system layering file that appears to control all NT functions within XP.. which includes the native (NTFS) disk filing system . (Why I thought that a FAT32 drive might cause a hiccup when ntdll.dll comes up against the 2GB file limitation). Perhaps elchiki will come back and clarify whether he is using FAT or NTFS. The ntdll.dll working file is stored in the system folder, and seems to have some particular virus vulnerability. So, might be wise to do a thorough up-to-date AV scan before running sfc or downloading a new copy of the file..
George
A good bit of research you have done there..
I have checked my PC's (3 x PC LAN) ...particularly the one dedicated to video work, which has UVS on board.. and found that this particular PC has two copies of ntdll.dll which appear to have been installed with the inititial Windows load.. However, the general purpose PC which I am now using has 4 copies... 2 of which appear to have been placed in the SP2 cache in the Windows folder during the SP2 upgrade. Yet all 3 of the PCs on the LAN have been upgraded to SP2... so this varying selectivity is a bit of a mystery..
Do you think System File Checker might help... if it is possibly a corrupt system file problem? Running the sfc /scannow command line from the Run box will envoke a Windows System File Check and repair or replace any corrupted files. But, as the WindowsXP installation CD needs to be in the drive for this scan ...any replacements will be in the mod-state form of the original file..
ntdll.dll is a system layering file that appears to control all NT functions within XP.. which includes the native (NTFS) disk filing system . (Why I thought that a FAT32 drive might cause a hiccup when ntdll.dll comes up against the 2GB file limitation). Perhaps elchiki will come back and clarify whether he is using FAT or NTFS. The ntdll.dll working file is stored in the system folder, and seems to have some particular virus vulnerability. So, might be wise to do a thorough up-to-date AV scan before running sfc or downloading a new copy of the file..
George
-
elchiki
Thanks a lot to both of you for these excellent information. All my disk are in NFTS. I have tried to set my paging file to 4 Go RAM....do you believe necessary to set the paging memory on the disk dedicated to the video (instead of on C) ?
I tried to launch sfc /scannow but I am asked to insert the XP CD professional version !!!! my orginal XP windows CD is the home version (normally OEM bought, paid and registered).
The version of my all recent XP windows ntdll.dll is 5.1.2600.2180.
As the program stops all the times when trying to read (on read, forward motion), I thought that the bug was linked to the connection of my video dedicated disk and therefore passed all the files to my system disk (second partition) but the problem remains the same.
I carry on triying VS 9 with these new setting and will keep you post.
Thank you again for your high level technical input and help
Eric
I tried to launch sfc /scannow but I am asked to insert the XP CD professional version !!!! my orginal XP windows CD is the home version (normally OEM bought, paid and registered).
The version of my all recent XP windows ntdll.dll is 5.1.2600.2180.
As the program stops all the times when trying to read (on read, forward motion), I thought that the bug was linked to the connection of my video dedicated disk and therefore passed all the files to my system disk (second partition) but the problem remains the same.
I carry on triying VS 9 with these new setting and will keep you post.
Thank you again for your high level technical input and help
Eric
-
elchiki
-
GeorgeBW
Elchiki,
I wouldn't put the paging file on the capture/video disk. If you have got a good size primary system drive, this is the best place for it.. 4GB of virtual memory should be OK.. although I would have been tempted to go for the 5GB. With video, you will be working with files far larger than any other media at any one time.
Ntdll.dll is a part of the NT shell and is a Windows protected file. The best thing to do is to make sure that you are logged on with full Administrator's rights and download the replacement file directly into the C:\Windows\System32 folder where it should overwrite the existing copy. You can run the System File Checker with Home Edition if you want to.. if you have the CD to hand just place it in the drive.. It will take about 15-20 minutes to complete the scan. It's useful to do this anyway from time to time.
Hope this helps
Good luck
George
I wouldn't put the paging file on the capture/video disk. If you have got a good size primary system drive, this is the best place for it.. 4GB of virtual memory should be OK.. although I would have been tempted to go for the 5GB. With video, you will be working with files far larger than any other media at any one time.
Ntdll.dll is a part of the NT shell and is a Windows protected file. The best thing to do is to make sure that you are logged on with full Administrator's rights and download the replacement file directly into the C:\Windows\System32 folder where it should overwrite the existing copy. You can run the System File Checker with Home Edition if you want to.. if you have the CD to hand just place it in the drive.. It will take about 15-20 minutes to complete the scan. It's useful to do this anyway from time to time.
Hope this helps
Good luck
George
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
It's not as easy to replace a windows system file that XP monitors and
considers critical.
The reason when you scan the harddisk and come up with 2 copies is
the 2nd copy is a backup.
Do an experiment, move or rename that file from the system32 directory.
Rescan the same directory and the file will be back again (F5)
Everytime you rename or move the file windows will replace it with
the backup copy, IF it is an important system protected file.
Hence 2 copies of the file under the windows directory.
(Part of Xp's protection system).
To replace the file with a file you know is absolutely good (keep a backup
copy of the original), replace the file that is pulled from the backup
location file with the new file you want to use.
Then erase the system file under system32 directory.
The backup copy which is the file you just replaced will replace the file
you erased from the system32 directory.
MD
considers critical.
The reason when you scan the harddisk and come up with 2 copies is
the 2nd copy is a backup.
Do an experiment, move or rename that file from the system32 directory.
Rescan the same directory and the file will be back again (F5)
Everytime you rename or move the file windows will replace it with
the backup copy, IF it is an important system protected file.
Hence 2 copies of the file under the windows directory.
(Part of Xp's protection system).
To replace the file with a file you know is absolutely good (keep a backup
copy of the original), replace the file that is pulled from the backup
location file with the new file you want to use.
Then erase the system file under system32 directory.
The backup copy which is the file you just replaced will replace the file
you erased from the system32 directory.
MD
-
GeorgeBW
Hi MD,
Yeah, see where you are coming from, but Windows will retain a copy of the protected file in the System32 folder, no matter what... If however another file named ntdll.dll can be copied to the system folder, then Windows will give the option of overwriting the existing version... Otherwise you get a chicken and egg argument going on.. I think you can only change these files' attributes at the command prompt, which can be a bit tricky unless you are really sure of your ground. Safest way is to introduce a new file either by allowing System File Checker to do it.. from the original cached files on the installation CD.. (At least this method allows the System File Checker to analyse the structure of the file and determine whether or not it is actually corrupted).. or replace the file anyway by introducing it from another trusted source..eg the backup file if it exists, will be located in C:\windows\system32\dllcache. If SP2 has been installed as an upgrade, there may be another copy in C:\windows\servicepackfiles\i386.
Copying either of these ...or the download, should enable you to overwrite the existing file.
Cheers
George
Yeah, see where you are coming from, but Windows will retain a copy of the protected file in the System32 folder, no matter what... If however another file named ntdll.dll can be copied to the system folder, then Windows will give the option of overwriting the existing version... Otherwise you get a chicken and egg argument going on.. I think you can only change these files' attributes at the command prompt, which can be a bit tricky unless you are really sure of your ground. Safest way is to introduce a new file either by allowing System File Checker to do it.. from the original cached files on the installation CD.. (At least this method allows the System File Checker to analyse the structure of the file and determine whether or not it is actually corrupted).. or replace the file anyway by introducing it from another trusted source..eg the backup file if it exists, will be located in C:\windows\system32\dllcache. If SP2 has been installed as an upgrade, there may be another copy in C:\windows\servicepackfiles\i386.
Copying either of these ...or the download, should enable you to overwrite the existing file.
Cheers
George
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
>>Otherwise you get a chicken and egg argument
I thought it would be easy to replace my cards scsi driver. Didn't turn out
to be as easy as I expected.
It's a nice feature in XP to protect the files. I would think that it's added
protection when an older program that overwrites those important system
files during installation. How many times people installed programs and the
system doesn't reboot properly because system files were replaced by
bad ones.
Back to VS9:
VS9 trial suddenly would exit without any errors on my system.
Just gone. I think it is happening on some systems.
Happens in MF4 also.
Usually when I would be using the mouse and clicking to fast.
If I went slower with the mouse then no problem.
Still a great program.
MD
I thought it would be easy to replace my cards scsi driver. Didn't turn out
to be as easy as I expected.
It's a nice feature in XP to protect the files. I would think that it's added
protection when an older program that overwrites those important system
files during installation. How many times people installed programs and the
system doesn't reboot properly because system files were replaced by
bad ones.
Back to VS9:
VS9 trial suddenly would exit without any errors on my system.
Just gone. I think it is happening on some systems.
Happens in MF4 also.
Usually when I would be using the mouse and clicking to fast.
If I went slower with the mouse then no problem.
Still a great program.
MD