Solved

Windows Server 2008 R2 keeps rebooting -BSOD

Posted on 2010-08-17
11
4,982 Views
Last Modified: 2012-05-10
Fully patched

getting this in Event log

Log Name:      System
Source:        Microsoft-Windows-WER-SystemErrorReporting
Date:          8/17/2010 1:30:00 PM
Event ID:      1001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SVR-ENT08R2-VM
Description:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000041201, 0xfffff68000014180, 0x0000000000000003, 0xfffffa801c603010). A dump was saved in: C:\Windows\MEMORY.DMP.

this is copy from NirSoft AppCRash app


==================================================
Dump File         : 081610-68047-01.dmp
Crash Time        : 8/16/2010 10:39:18 PM
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : fffffd7f`fffffff4
Parameter 2       : 00000000`00000001
Parameter 3       : fffff800`0165d3b0
Parameter 4       : 00000000`00000007
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor         : x64
Computer Name     :
Full Path         : C:\Windows\Minidump\081610-68047-01.dmp
Processors Count  : 16
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 081710-69202-01.dmp
Crash Time        : 8/17/2010 1:29:58 PM
Bug Check String  : MEMORY_MANAGEMENT
Bug Check Code    : 0x0000001a
Parameter 1       : 00000000`00041201
Parameter 2       : fffff680`00014180
Parameter 3       : 00000000`00000003
Parameter 4       : fffffa80`1c603010
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor         : x64
Computer Name     :
Full Path         : C:\Windows\Minidump\081710-69202-01.dmp
Processors Count  : 16
Major Version     : 15
Minor Version     : 7600
==================================================

==================================================
Dump File         : 081610-67657-01.dmp
Crash Time        : 8/16/2010 10:24:31 AM
Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code    : 0x00000050
Parameter 1       : ffffffff`f8008000
Parameter 2       : 00000000`00000000
Parameter 3       : fffff800`0170cc30
Parameter 4       : 00000000`00000002
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+11aa9
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Computer Name     :
Full Path         : C:\Windows\Minidump\081610-67657-01.dmp
Processors Count  : 16
Major Version     : 15
Minor Version     : 7600
==================================================




0
Comment
Question by:piotrmikula108
  • 4
  • 3
  • 3
  • +1
11 Comments
 
LVL 4

Expert Comment

by:cdowdy
ID: 33460453
My vote would be bad ram. I'd run your favorite memtest variant overnight and see what you get.
0
 
LVL 6

Expert Comment

by:ChiefoftheChiss
ID: 33460495
Windows 2008 server comes with its own RAM diag tool
Click Start
in the search box start to type
windows memory diagnostic

you'll see it pop up on the top of the list.
0
 
LVL 1

Author Comment

by:piotrmikula108
ID: 33460533
my gut feeling is the same - RAM, will run the test and let you, I manage the server remotely so will it record the results in event log once the server is back up?
0
NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

 
LVL 2

Expert Comment

by:paulstorm
ID: 33460708
You may also want to run a chkdsk on the drive where you have you paging file, as the disk could be faulty, generating the BSOD when the memory writes (or tries to write) to the pagefile.
0
 
LVL 6

Expert Comment

by:ChiefoftheChiss
ID: 33460983
Yes, which is a great part of using the built in Windows one,


To find the results of your Windows Memory Diagnostic Tool after the computer restarts, do this:
1) Right-click on COMPUTER in your Vista start menu and choose MANAGE.
2) In the Computer Management screen that pops up, expand the EVENT VIEWER in the left-hand panel by clicking on the little arrow to the left of the words EVENT VIEWER.
3) From this expanded menu, expand WINDOWS LOGS.
4) On this expanded menu, left-click on SYSTEM.
5) Now, the middle panel will be populated with a huge number of events. To find the one you're looking for, click on FIND in the right panel.
6) In the Find window, type "MemoryDiagnostics" (all one word, but without the quotes) and click the FIND NEXT button. (Note: you could just type "memory" and still find what you're looking for.)
7) Now, in the panel below, you'll see two tabs: GENERAL and DETAILS. Click on DETAILS.
8) Now, you'll see data about your test. If the test passed, you'll see the word PASS on about the fifth line down next to COMPLETION TYPE.
0
 
LVL 6

Expert Comment

by:ChiefoftheChiss
ID: 33460988
it would be nice to have someone who can walk up to it and tell it to run an extended test though, which can be changed by hitting F10 while the test is running.
0
 
LVL 1

Author Comment

by:piotrmikula108
ID: 33465895
mem test and chkdsk had no errors, all drivers and firmware is up to date - I will keep investigating
0
 
LVL 2

Expert Comment

by:paulstorm
ID: 33472273
I don't suppose there is a usb or network backup drive that it could be writing to?
0
 
LVL 1

Author Comment

by:piotrmikula108
ID: 33476561
No,but it has a SAN thou where all the vms are stored
0
 
LVL 1

Accepted Solution

by:
piotrmikula108 earned 0 total points
ID: 33537810
well, after updating BIOS the server has been stable for the past week
0
 
LVL 2

Expert Comment

by:paulstorm
ID: 33538005
I'd say you have solved it as updating the BIOS will bring the rest of the hardware into line.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
extra RAM sticks on server board 9 35
Cisco AP to get ip from DHCP 10 73
NTFS Permissions 6 43
Active Directory Failed Logon Attempts. 18 51
New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
OfficeMate Freezes on login or does not load after login credentials are input.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

785 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question