![]() |
|
|
Welcome to the { mindfrost82.com } forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|||
|
BSOD when connecting to mapped network drive
Hello, I recently began getting a BSOD when I try to connect to a new mapped
network drive. I've been connecting to the same server for quite sometime. I recently added a new share on the server and since then I get a BSOD mots of the time I try to connect to that share. When I reboot I don't always get the same info from ms error reporting. But the last couple I noted were This problem was caused by Microsoft Multiple UNC Provider driver (mup.sys), which was created by Microsoft Corporation. or Problem caused by device driver I have not added any new hardware to the computer trying to access the shares. Also, since adding this new share I come close to crashing if I try to access the server by netbios name (not always but most of the time). \\myserver When I do this, a blank windows explorer will load with no share icons or anything, and pretty much my cmoputer locks up. I can't type or click anything. Several minutes of waiting and I can do other things but the windows explorer is still solid white and I can't see anything in the window. Is this the right newsgroup to post in? thanks |
![]() |
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|