msvcrt.dll error

[Guest]

I'm running SP2 on a Intel Core2Duo machine and am pretty comfortable around
computer (having built my own in the recent past).

I've been having problems with IE 7.0.5. Can't read or open PDF files
(although I have Acrobat 8.0 installed), can't view page source, etc. I get
this message.

"Windows cannot access the specific device, path or file. You may not have
permission to access the item."

So yesterday, I ran the IE "diagnose connections problem" tool and low &
behold, it fixed the problem.

This morning I boot my machine and as it gets past post and starts to load
Windows, I get this message..."Procedure entry point_resetstkflw could not be
located in dynamic link library msvcrt.dll" Top of message was labeled
lsass.exe.

Then machine froze. I tried to boot to safe mode same thing.

Luckly, I was able to Restore my machine to yesterday morning (Norton GoBack).

I now see that the original problem with IE is back. (minor issue compared
to Windows not loading).

So, can anyone shed some light on the msvcrt.dll problem? Or a solution? Or
should I just be glad I got back to my Restore point and keep on truckin'...

Thanks,

John

 

[Guest]

I'm running SP2 on a Intel Core2Duo machine and am pretty comfortable around
computer (having built my own in the recent past).

I've been having problems with IE 7.0.5. Can't read or open PDF files
(although I have Acrobat 8.0 installed), can't view page source, etc. I get
this message.

"Windows cannot access the specific device, path or file. You may not have
permission to access the item."

So yesterday, I ran the IE "diagnose connections problem" tool and low &
behold, it fixed the problem.

This morning I boot my machine and as it gets past post and starts to load
Windows, I get this message..."Procedure entry point_resetstkflw could not be
located in dynamic link library msvcrt.dll" Top of message was labeled
lsass.exe.

Then machine froze. I tried to boot to safe mode same thing.

Luckly, I was able to Restore my machine to yesterday morning (Norton GoBack).

I now see that the original problem with IE is back. (minor issue compared
to Windows not loading).

So, can anyone shed some light on the msvcrt.dll problem? Or a solution? Or
should I just be glad I got back to my Restore point and keep on truckin'...

Thanks,

John

Hi John,
Does this happened after running the Norton WinWork?.
Before reading the info in the link below make sure you run a through scan
for malware and viruses on your system, with scanner online from another
vendor than the protection software you are using now.
http://www.microsoft.com/communitie...5dc71973d43c&lang=en&cr=US&sloc=en-us&m=1&p=1
HTH.
nass

 

[Guest]

hi nass,

Thanks for the quick reply.

It happens right after post, while windows is starting up. I get the windows
splash screen, then the screen goes black and I see the message window pop up
with the message about msvcrt.dll in it.

Then windows freezes. I can't get into windows or norton. (I was able to to
get to Norton GoBack, since it has a recovery screen just after post, but
prior to wondows loading)

I'll follow the links you provided to see where they lead.

thx

John

 

[RalfG]

Msvcrt.dll is a display related file that could be placed on your computer
multiple times by different software. For example thee are 17 instances of
this file on my computer, in 10 different versions.
The version installed by Microsoft in the system32 folder is the right one
and SFP should protect it from being changed. Problems happen when some
software or other invokes an obsolete version of the file (usually from
within program or game folders) instead of the current version. One of your
start-up apps maybe? If that situation comes up I usually change the file
extension of the version in the program folder to disable it and sometimes
put a copy of the current version in its place.

Msvcrt.dll also works in conjunction with the same version number of
Msvcirt.dll and a mismatch between versions of those two files can also
cause errors.

 

[Guest]

Interesting...

So what probably happened was when I installed the IE repair, it wrote-over
the system version of wcvcrt.dll and when I rebooted Windows was not happy,
so it refused to load.

Thanks

john

 

[RalfG]

I suppose it isn't impossible but you wouldn't expect an IE repair, or an MS
update to install an obsolete version of an MS file. A lot more people than
yourself would have experienced similar problems if that were the case. More
usually something else will have called up an older version of the file and
it was still in memory when Windows or another program needed to do
something that the old file couldn't cope with. The newer file versions
should be backwards compatible.