Windows XPPost your Windows XP related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
Remote Desktop won't connect, causes computer to crash
Hi guys and gals,
I have been reading this fourm for over 2 years now, and it is one of the best I have read by far!!
I have a little problem and can't seem to figure it out...even with all of the research I have done at this site and others, even over at M$ site...I can't seem to be able to connect to my computer's remote desktop no matter what I try!
I am running XP Pro on a 2.4Gig P4, 768RAM Dell 8200 on a Broadband connection with a Netgear MR814 Router.
I have enabled all of the settings on my computer, such as in system properties on the Remote tab -checked the Remote Desktop and checked the Remote Assistance, then I went to the Remote Users and allowed myself to be able to connect to the Remote Desktop.....I have configured the Sygate Firewall to allow Remote Desktop.....I have configured the Netgear Router to open port 3389...
When I type in the IP address of my computer (host) from another computer (server) to try to get a connection to my computer remotely, I get as far as the page starting to load up, and the taskbar starting to appear somewhat, but then everything freezes on the screen.
When I go to my computer(host) it has a "blue screen of death" on it everytime, and it says the following:
"A problem has been dected and windows has shut down to prevent damage to your computer.
If this is the first time you have seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure you have adequate disk space. If a driver is identified in the Stop message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters.
Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable componets, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.
*** win32k.sys Address BF93DA45 base at BF800000, Date Stamp 43446a58
So, that is what I see when I go to my host computer every time after I try to connect remotely from some other computer! I have checked the driver of the nVidia graphics card and made sure the driver is updated ( it is a
nVidia GE Force4 MX 420, and the driver is version 6.1.7.7 ) I used to be able to connect to this computer a year or so ago, and I have not changed anything except upgraded my monitor from a Dell 15inch flat panel monitor to a Samsung 17inch Syncmaster 911T.
Does anyone have any ideas as to what might be wrong here?
Thanks in advance for your help!
Didn't find the information you thought to find? Check out these Similar Threads
I remember seeing this address error today in a search with Microsoft that you have listed: Address BF93DA45 base at BF800000. If this is the only computer causing the problem, I agree with the response you already received from "A". If not, then check out the M$ site with a search for BF80000 to look at those errors.
*** ERROR: Module load completed but symbols could not be loaded for sam_nv4_disp.dll
Probably caused by : sam_nv4_disp.dll ( sam_nv4_disp+6f9c )
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf93da45, The address that the exception occurred at
Arg3: ec817834, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
Hope you can get some info from this dump. All is well with my computer otherwise as far as I can tell, it just won't connect to another computer remotely, and I am at a loss as what to do. Thanks again!!
my .02 = vanilla the box ... i'm a big believer in the KISS principle
it's one of the things i almost always fall back to but ... pre-built systems tend to overload w/ software 'goodies' that u just don't need. so ... kill them
by vanilla i mean create a simple startup environ and test. if that works, start throwing the kitchen sink software glut that dell provides (not just them really but ... they do) back into the mix ... if u see fit
i'd kill off sygate entirely to test too. eg - turn it off and test. if it works, turn it back on and fix it.
check all HW updates as well. BSDs are often relative to a HW issue or a firmware update that's not applied.
i'd also consider removing hw - even it's working - like modems/serial ports if they're not used. i just plain pull the modems after purging any software that's associated w/ them. and i'd use bios options to shut off any serial ports to return the io/irqs to available. u can always reinstall or flip the bios switch to turn em back on.
Last edited by skeet6961; 25th January 2006 at 12:13.
Thanks Arie! I will try that update. . . I thought I had the latest one, but guess not. I am on my way to work, so I will try this evening and will post back with the results. Thank you for your help!
Success!! Thanks Arie!! It was the Nivida driver that was the problem, I updated it to the newest version and now I am able to connect remotely to my computer once again! Lesson learned: always keep up on the latest updates for your computer hardware drivers!
Thanks once again, I knew that I would find an answer here on Windows BBS because this is one of the best places to go for help and knowledge on the entire internet!! You all rock!!
I am on my way to work, so I will try this evening and will post back with the results. Thank you for your help!
