Not A Valid Windows Image When Trying To Print 1

[Poppy64]

We currently run Windows NT4.0 (SP6a). Our company's printers all sit on a print server and we install from here any printers we require. Therefore all print drivers sit on the printer server and do not need to be installed on the users PC's.

One of our users cannot install a colour printer (Canon) on her pc from the server - when she tries she gets a message to say:

The application or DLL C:\System\System32\drivers\W32X386\2\CNP5CEUM.dll is not a valid image.

All other users are ok and we all have the same desktop image. (By the way: C:\System = C:\WINNT)

I had to reimage the pc concerned two days ago but the original image has not changed - and all other users are ok. Any ideas anyone?

Poppy64

 

[wolluf]

So you've reimaged the PC since this started happening and its still happening?

Does the PC exhibit any other oddities?

Assuming the file mentioned is not corrupt - this sort of behaviour can be caused by hardware problems (particularly RAM, overheating cpu...)

 

[Poppy64]

Wolluf

Sorry no (my bad explanation!)...I had to reimage the machine (due to something else - boot up file problems) on Monday. Everything seemed fine after the reimage, but then today she's tried to print to the colour printer...got the error message I described so deleted the printer and tried to reinstall it....and again got the same message upon this attempted printer reinstall.

All else fine she reports. The machine is a Fujitsu Scenic XS and is only around 18 months old.


Poppy64

 

[wolluf]

Did you delete that problem file specifically (ie, remove it from machine) before reinstalling printer? (sometimes need to actually remove all printer driver files before reinstalling printer - just deleting the printer leaves them all in place - just the settings get deleted).

boot up file problems - you know what caused them? (I'm still wondering if there isn't a hardware problem...)

 

[Poppy64]

No - I didn't remove anything as I've never had this problem before, so didn't think to. So I guess I should be deleting this named problem dll and then attempting to reinstall the printer in the first instance...

By the way, when her machine failed on Monday, it failed with a message that the dll file winsrv could not be found in the specified file or folder. There was also a code C0000135. Tried to fix using NT set up disks, ERD etc but things got worse after that (heaven knows what I did but I thought I was doing it all right!! Never mind) so I just reimaged it completely.

Thanks for your help so far...

Poppy64

 

[wolluf]

Definitely inclining to a hardware problem (not finding files on boot up is a common symptom) - but try the file delete & reinstall first.
Finding hardware problem (if it is that) can be difficult - especially as it sounds like this machine has been fine for a long time (I'd check the cpu fan is operating correctly, and replace RAM with known good as a start).

 

[Poppy64]

Wolluf - thank you. The deletion of the file (and another which made itself apparent) THEN the reinstall of the printer had cracked it.

Thanks so much - but I will also keep an eye on this PC/check out the cpu fan in case it is a hardware fault starting to wreak havoc.
Poppy

Poppy64