Windows Forum

Ask something
Discussion Locked

problems in win2k

0 helpful
5 replies

by hcbraj

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

The following are the errors in win2k. somebody help me.
Firstly, even thought the modem is installed it is shown as " not present" after startup.I have to get the modem recongised & then use it.
Secondly,soon after the startup if I clik on anyof the desktop application icons, the apps doesn't start, the system is somewhat in a suspended action and start after waiting for sometime.
Thidly, when browsing the interenet the internet explorer, the msn messenger & netsonic (internet accelerator )hangs quite a lot of times. I am attaching the error msgs from the event viewer. Hope somebody can help me solve my woes.

Application popup: IEXPLORE.EXE - Application Error : The instruction at "0x01a12ca8" referenced memory at "0x00000000". Thememory could not be "read".
Application popup: Windows Security: winlogon.exe - Application Error : The instruction at "0x77f46b90" referenced memory at "0x57ea840f". The memory could not be "written".
Application popup: Explorer.exe - ApplicationError : The instruction at "0x77f46b90" referenced memory at "0x57ea840f". The memory could not be "written".
Application popup: taskmgr.exe - Application Error : The instruction at "0x77f46b90" referenced memory at "0x57ea840f". The memory could not be "written".
Application popup: CSC Notifications Window: Explorer.exe - Application Error : The instruction at "0x77f46b90" referenced memory at "0x57ea840f". The memory could not be "written".
Application popup: msdev.exe - Application Error : The instruction at "0x77f46b90" referenced memory at "0x57ea840f". The memory could not be "written".
Application popup: O: msimn.exe - Application Error : The instruction at "0x77f46b90" referenced memory at "0x57ea8410". The memory could not be "written".
Application popup: WebMain.exe - Application Error : The instruction at "0x77f46b90" referenced memory at "0x57ea840f". The memory could not be "written".

5 replies

by dc1

Could be bad hardware (modem or memory) or a resource issue (Jumpers. switches, etc)

by law

Win2K doesn't allow direct access to physical memory. Sounds like the apps you want to run are trying to do that. Are these apps (other than IE) rated to run on Win2K? Or NT4.0? If these are Win98/95/3.1 apps, they are trying to direct access memory and won't work.

also sounds like maybe your hardware isn't up to the requirements for Win2k. You really need more than what the stats say.

This discussion is closed to new replies.