[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now


The instruction at "0x77c71861" referenced memory at "0x0000004e".  The memory could not be read.

Posted on 2006-06-05
Medium Priority
Last Modified: 2012-06-27
Windows Server 2003 SP1 Terminal Services using remote desktop (no Citrix).  Remote desktop is configured to connect automatically to local printers when logged onto the remote computer.  When users report either a blank blue screen when they log into this server (not a blue screen of death) this error message is displayed on the server when I check the server.  The server itself has not crashed.  Other users report printers are not being connected when they log in.  I've run hardware diagnostics to check memory - no problems reported.  Dr. Watson logs don't have anything either.  After I respond the the dialog window for this error, the user can log in.  The only thing that changed on the server was adding a printer driver for an HP printer.  THis started about the middle of May.  Has anyone had similar problems or know of a fix?  
Question by:usemco1
1 Comment
LVL 33

Accepted Solution

NJComputerNetworks earned 2000 total points
ID: 16836198

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

by Batuhan Cetin In this article I will be guiding through the process of removing a failed DC metadata from Active Directory (hereafter, AD) using the ntdsutil tool in a Windows Server 2003 environment. These steps are not necessary in a Win…
Many of us need to configure DHCP server(s) in their environment. We can do that simply via DHCP console on server or using MMC snap-in on each computer with Administrative Tools installed in a network. But what if we have to configure many DHCP ser…
Integration Management Part 2
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

872 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question