Mysterious Bluescreen

[sonofvirginia]

This system is a dual CPU Opteron server. Server Mobo, ECC ram, Raid controller. It is running as a DVR/NVR for 12 HD IP cameras.

Every now and then (sometimes once a month, sometimes a few months in between) it will blue screen and restart. At one point i thought i had it narrowed down to a dip in the line voltage causing issues, and added an Eaton UPS to the mix. This appeared to improve it, but last night it happened again.

I have included the zip as requested, any guidance on this would be great. I know servers in general can be wacky, and Opterons even more so.

Thank You

 

[marytran]

The first place to look is Event Viewer, and then use BlueScreenViewer to diagnose minidump file.

 

[sonofvirginia]

The first place to look is Event Viewer, and then use BlueScreenViewer to diagnose minidump file.

==================================================
Dump File : 020417-33296-01.dmp
Crash Time : 2/3/2017 11:08:58 PM
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000018
Parameter 2 : 00000000`00000000
Parameter 3 : fffff880`030f2180
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+72a40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.18798 (win7sp1_gdr.150316-1654)
Processor : x64
Crash Address : ntoskrnl.exe+72a40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\020417-33296-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 272,672
Dump File Time : 2/4/2017 9:58:08 AM
================================================



unfortunately doesn't really narrow it down since the fault is in ntoskrnl

 

[Layback Bear]

I suggest going here.

https://www.sevenforums.com/bsod-help-support/

Then complete this.

Blue Screen of Death (BSOD) Posting Instructions

Please keep in mind that are BSOD Team are very busy.

Jack

 

[axe0]

A kernel dump will be required for this particual BSOD to analyze properly.
The basic reason is that a minidump is not capable of telling is what caused the BSOD because it cannot hold that much information.

 

[torchwood]

Hi SonofVirginia,

from the event viewer, the first lot not neccessarily related to BSOD, but as your running a surveillance system these will be of interest to you.

The last however is different and may be the cause


EventID 36888 Description: Schannel, 10 1203
If a user tries to access a web site using HTTP but specifies an SSL port in the URL then this event is logged. This event is expected as the client is trying to use the wrong port or the wrong protocol to access the site.

EventID 36874 Description: Schannel, TLS 1.0
An TLS 1.0 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The SSL connection request has failed.

EventID 36888 Description: Schannel, 40 1205
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection.


Event[35280]:
Log Name: System
Source: b57nd60a
Date: 2017-02-04T09:58:01.078
Event ID: 4
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: CamServ
Description:
Broadcom NetXtreme Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.


Event[30143]:
Log Name: System
Source: Disk
Date: 2016-10-09T01:47:03.275
Event ID: 7
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: CamServ
Description:
The device, \Device\Harddisk1\DR1, has a bad block.


Roy

 

[sonofvirginia]

A kernel dump will be required for this particual BSOD to analyze properly.
The basic reason is that a minidump is not capable of telling is what caused the BSOD because it cannot hold that much information.

What would be the best way to generate this?

 

[sonofvirginia]

thank you Torchwood.

I will look into those errors.

The bad block is interesting.

ill be interested to find out if the kernel dump points to such an issue as well.

 

[axe0]

A kernel dump is automatically generated and located in c: windows

 

[sonofvirginia]

A kernel dump is automatically generated and located in c: windows

It looks like this setting will need to be enabled and then wait for the next crash. It could be a while.

 

[sonofvirginia]

It looks like this setting will need to be enabled and then wait for the next crash. It could be a while.

Disregard it looks like it was enabled.

file is quite large so i have it linked
https://itelite.org/MEMORY.rar

 

[axe0]

I took a quick look at what happened on each core.
It looks like they were all working on I/O related things, some are blaming the SATA controller driver, but with the bad block(s) it is more likely bad communication with a HDD.