Windows Server 2008 R2 Standard keeps bluescreening
Hi All,
Im new to this forum, so forgive me if this is posted in the wrong section. I seem to be having an issue with my Windows Server 2008 R2 Machine. It keeps bluescreening randomly.
Here is the event details:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 6/13/2010 3:24:48 AM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: WIN-DEKJ8IMQMAI
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8000166b554, 0xfffff88009942e30, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 061310-36441-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-06-13T10:24:48.000000000Z" />
<EventRecordID>3076</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>WIN-DEKJ8IMQMAI</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x0000003b (0x00000000c0000005, 0xfffff8000166b554, 0xfffff88009942e30, 0x0000000000000000)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">061310-36441-01</Data>
</EventData>
</Event>
I'm not too good at deciphering this, but i've googled the error codes, and haven't been able to pinpoint the problem. Any response would be appreciated :)
Cheers,
Michael
June 13th, 2010 4:20am
Hello,
what i realized is that this often belong to the hardware, so make sure to use the latest drivers and updates from the hardware vendor. What kind of server/model is it?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
June 13th, 2010 2:16pm
------------------
System Information
------------------
Time of this report: 6/13/2010, 22:33:18
Machine name: WIN-DEKJ8IMQMAI
Operating System: Windows Server 2008 R2 Standard 64-bit (6.1, Build 7600) (7600.win7_gdr.100226-1909)
Language: English (Regional Setting: English)
System Manufacturer: MICRO-STAR INTERNATIONAL CO.,LTD
System Model: MS-7596
BIOS: Default System BIOS
Processor: AMD Athlon(tm) II X4 630 Processor (4 CPUs), ~2.8GHz
Memory: 8192MB RAM
Available OS Memory: 7936MB RAM
Page File: 1121MB used, 14747MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7600.16385 64bit Unicode
It's a custom build. It's in a datacentre located in Scranton, PA.
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2010 3:36pm
Hi MNewton91,
This problem can be caused by faulty hardware, device drivers or corrupt system files.
Here’re my suggestions:
a.
Try to run Startup Repair with Installation CD/DVD
1)
Insert the installation disc.
2)
Restart the computer from CD/DVD.
3)
Set your language preference, and then click
Next.
4)
Click
Repair your computer.
5)
In the
System Recovery Options dialog box, click the operating system that you want to repair, and then click
Next.
6)
In the
System Recovery Options menu, click Startup Repair to start the repair process.
7)
When the repair process is complete, click
Finish.
b.
Run a memory diagnostic test. It will help you to determine whether the problems are caused by failing hardware, such as RAM or the memory system
of your motherboard. You can download the Windows Memory Diagnostic tool from the link below.
http://oca.microsoft.com/en/windiag.asp
Additionally, please check whether the KB article below applies.
"STOP 0x0000003B" Stop error on a computer that is running Windows 7 or Windows Server 2008 R2 when you use some IEEE 1394 devices
http://support.microsoft.com/kb/980932
If the methods above donot work, I would suggest contacting Microsoft Customer Service and Support (CSS) via telephone so that a dedicated
Support Professional can assist with your request. Because this issue seems to be system crash issue and we need to analyze the crash dump file to narrow down the root cause of the issue. Unfortunately, it is not effective for us to debug the crash dump file
here due to the nature of the forum. Please be advised that contacting phone support will be a charged call.
To obtain the phone numbers for specific technology request please take a look at the web site listed below:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
Hope the issue will be resolved soon.
Regards,
Karen Ji
On July 1st we will be making this forum read only. After receiving a lot of feedback from the community, it was decided that this forum is a duplication
and therefore redundant of the General Forum. So, until July 1st, we will start asking customers to redirect their questions to the
General Forum. On June 11th, CSS engineers will move any new threads to the
General Forum.
Please post a reply to
the announcement thread if you have any feedback on this decision or the process. You can
also email WSSDComm@microsoft.com.
This posting is provided "AS IS" with no warranties, and confers no rights.
June 14th, 2010 10:26am