Jump to content

Recommended Posts

Posted

hi we have a Server 2008R2 which isn't running AD.

its the schools SIMS server. The server is fully upto date, drivers and windows updates.

 

When using the server, if I go to the mapped network drive F:\ (SIMS folder) it blue screens the server.

If I go direct to the data which is sat on this server d:\SIMS\ server works fine.

 

If any workstations use F:\ Mapped to this server - Server still works fine.

 

Its only when any user that's logged into the server and uses mapped F:\ it blue screens. Even create new administrator and it still does it.

 

Hardware is fine, hard disk test ok.

 

HELP :-)

  • 1 month later...
Posted (edited)

set verbose logging in via:

 

Right-click computer - 'properties', then select 'advanced system settings', then select 'settings...' in the 'Startup and Recovery'.

Make sure the options are set here for 'small memory dump' (use the second option kernel memory dump if this options does not get results).

NB: Check the area the dump file will save as (usually %systemroot%\MEMORY.DMP)

 

This should mean that when the server blue screens it will report to the MEMORY.DMP file the reasons for the bluescreen.

 

Use the following link from Microsoft:

How to read the small memory dump file that is created by Windows if a crash occurs

 

To interpret the 'MEMORY.DMP' file.

 

(This would of course mean purposely crashing the server!)

Edited by Roopert
long legged squirrel intervention team
Posted (edited)

Something created a ridiculously long file name for some reason in there? Or created a really deep file structure?

 

Boot the server into a linux distro that can read NTFS something like UBCD and browse the folder structure in that area, look for anything obvious that windows would have a fit over and copy them off, see if that shows anything obvious

Edited by Bananas
Posted (edited)

Also, are you mapping via the advertised share e.g. f:\ = \\server\someshare

 

Try mapping directly to your hidden disk share

 

net use f: \\127.0.0.1\d$

Edited by jinnantonnixx

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...