I have Win 2008 R2 std edition installed, since last 4 to 5 days it crashes and reboots once a day. I have attached the nfo file which has all the data. Can anyone please let me know what is causing the crash.

Win 2008 R2 Std crashes once in a day
Started by
webkida
, Jan 04 2013 12:36 AM
#1
Posted 04 January 2013 - 12:36 AM

I have Win 2008 R2 std edition installed, since last 4 to 5 days it crashes and reboots once a day. I have attached the nfo file which has all the data. Can anyone please let me know what is causing the crash.
#2
Posted 07 January 2013 - 01:59 AM

Can someone please help me out here, the machine rebooted again today.
#3
Posted 24 January 2013 - 09:29 AM

I apologize for the slow response. If your still having issues, we need to investigate the event log.
- Please download the Event Viewer Tool by Vino Rosso VEW and save it to your Desktop:
- Double-click VEW.exe
- Under 'Select log to query', select:
- Application
- System
- Under 'Select type to list', select:
- Error
- Click the radio button for 'Number of events'
- Type 10 in the 1 to 20 box
- Then click the Run button.
- Notepad will open with the output log.
#4
Posted 24 September 2013 - 12:24 PM

You will need to look at the event logs and see what time the crash occurs.
It could possibly be a software or program that kicks off and is corrupted that causes your computer to blue screen.
Try to note whats going on right before it blue screens.
It could possibly be a software or program that kicks off and is corrupted that causes your computer to blue screen.
Try to note whats going on right before it blue screens.
#5
Posted 04 January 2014 - 08:48 PM

Event logs will be extremely helpful. I
f this server is a known name brand server , the manufacturer will have diagnostic tools for it. I suggest running those.
The constant reboots will eventually corrupt the file system. I suggest before doing anything else, get a backup. Don't know how much drive space is used but if it's a small amount try to get a backup while the server is online , if it is a lot and there might be a crash/restart cycle during the backup then run an offline image level backup (there are popular tools for this - a boot up disk with backup/imaging software) to a network location before the system boots into the operating system.
f this server is a known name brand server , the manufacturer will have diagnostic tools for it. I suggest running those.
The constant reboots will eventually corrupt the file system. I suggest before doing anything else, get a backup. Don't know how much drive space is used but if it's a small amount try to get a backup while the server is online , if it is a lot and there might be a crash/restart cycle during the backup then run an offline image level backup (there are popular tools for this - a boot up disk with backup/imaging software) to a network location before the system boots into the operating system.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:






