Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

BSOD ONLY after logging in.

$
0
0

I have a Hyper-V Windows Web Server 2008 R2 (Core) that's only role is an FTP server. I know that the GUI is a blank desktop and task manager on a core server, but I cannot even access that.  Every time I connect to the server (either via RDP or Virtual Machine Connection) I get a BSOD after I enter my credentials and the server reboots.  The BSOD is not the same every time either, most of the time it's 0x00000050 though.

I can access remote powershell, psexec to the command line, issue remote commands, use RSATs, etc... but I cannot access the "desktop" i normal mode (I can in safe mode).

I didn't mind too much because I could do everything I needed to do remotely.  But just recently we've developed a problem where OSX devices download files from the FTP EXTREMELY slow and the server needs to be rebooted.  I'm not a fan of the "reboot fix" and need a more permanent solution.

Here's some more technical specs:

Host server: Server 2008 R2 Enterprise SP1, Dual Xeon E5645, 48GB RAM

Host server uses iSCSI connection to a Windows Storage Server Standard w/ a Xeon E5620, 12GB RAM so each VHD is using it's own iSCSI LUN and therefore independent (and redundant) spindles to increase I/O throughput.  The Storage server uses a 10Gbps connection directly to the host server (iSCSI data is not sent over our main network).

Client Server: Windows Web Server 2008 R2 SP1 (core), 1 CPU, 1 GB RAM.

Here's what I've tried so far:

1. Create a new virtual server and attach a copy of the FTP servers drive

2. Apply all windows updates from the internet and not our WSUS server

3. Remove our anti-virus from the client

4. Remove SCSI virtual devices from the virtual server

5. Remove all integration services

6. Using safe-mode, used autoruns to disable all services

Normally I'd just rebuild the server and copy all the necessary info over, but the FTP server has dozens of local users (and their passwords) that need to be migrated to the new server.  I guess this can be done with the migration kit, just not on windows web server (booo).  A 3rd party tool is an option as well if that's all there is available.

Any help will be greatly appreciated.


Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>