Since moving my servers to the 8 core package, I have experienced several blue screen crashes and therefore shutdowns. The blue screen error code was 50, and a short google search relates that to faulty hardware and/or RAM. Previously I used the 4 core package and never had this issue. I pasted the full error message below, and provided a link to the dmp file. In the dmp file I noticed also mcupdate_GenuineIntel.dll mentioned which from my understanding relates to mcaffee products so I thought maybe if there is some kind of network scan being done maybe it has to do with that (I have not installed any mcaffee product on the machine) . Other files are mentioned as well so I'm not sure that it's that. I have not installed/uninstalled any drivers which came with the server.
Link to dmp file:
https://dl.dropboxusercontent.com/u/617 ... 280-01.dmp
Would appreciate any input someone might have.
Thanks
Below is the error message shown after logging into the server after the crash:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional information about the problem:
BCCode: 50
BCP1: FFFFF96000142A8D
BCP2: 0000000000000008
BCP3: FFFFF96000142A8D
BCP4: 0000000000000007
OS Version: 6_1_7601
Service Pack: 1_0
Product: 272_3
Files that help describe the problem:
C:\Windows\Minidump\051714-49280-01.dmp
C:\Users\Administrator\AppData\Local\Temp\2\WER-10699734-0.sysdata.xml
Blue screens since moving to VPS 8 core package. (Windows 2
-
- New to forums
- Posts: 8
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Sun May 18, 2014 2:58 am
Re: Blue screens since moving to VPS 8 core package. (Windo
Here is some additional data on the crash, viewed with BlueScreenView:
http://gflclan.com/uploads/imgs/pre_140 ... _bsod3.png
Everything I have found either refers to faulty memory(highly unlikely in a server environment) or a possible file corruption/partition issue for ntoskrnl.exe. Hope this information helps you find a solution.
http://gflclan.com/uploads/imgs/pre_140 ... _bsod3.png
Everything I have found either refers to faulty memory(highly unlikely in a server environment) or a possible file corruption/partition issue for ntoskrnl.exe. Hope this information helps you find a solution.
Not a NFO employee
Re: Blue screens since moving to VPS 8 core package. (Windo
That's a pretty generic error, unfortunately, though not common (so no easy fix).
If you open a support request, I can update the version of Xen on your hardware, in case it has an older version with some sort of bug.
If you open a support request, I can update the version of Xen on your hardware, in case it has an older version with some sort of bug.
-
- New to forums
- Posts: 8
- Joined: Sun May 18, 2014 2:58 am
Re: Blue screens since moving to VPS 8 core package. (Windo
Thank you both. Edge100x, how certain is it that Xen is the problem?
Re: Blue screens since moving to VPS 8 core package. (Windo
Since I haven't heard of this happening to another customer, I am not very certain of it.
-
- New to forums
- Posts: 8
- Joined: Sun May 18, 2014 2:58 am
Re: Blue screens since moving to VPS 8 core package. (Windo
Will updating Xen require a restart of the servers?
Re: Blue screens since moving to VPS 8 core package. (Windo
Yes, it would involve a reboot of the entire machine, but generally it's a pretty quick process.daniel_tin wrote:Will updating Xen require a restart of the servers?
@Kraze^NFo> Juski has a very valid point
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
@Juski> Got my new signature, thanks!
@Kraze^NFo> Out of context!
@Juski> Doesn't matter!
@Juski> You said I had a valid point! You can't take it back now! It's out there!
-
- New to forums
- Posts: 8
- Joined: Sun May 18, 2014 2:58 am
Re: Blue screens since moving to VPS 8 core package. (Windo
Alright thank you I'll go ahead and open a support request.
-
- New to forums
- Posts: 4
- Joined: Tue May 20, 2014 3:27 pm
Re: Blue screens since moving to VPS 8 core package. (Windo
The vast majority of blue screens that mark that executable as the failing factor are not actually caused by an issue with that executable, but by some other catastrophic failure that results in a failure with the ntoskrnl exe. This executable is one that is an integral part of the operating system, so it shows as the cause of a blue screen quite often.
Actually, come to think of it, I think every blue screen I've ever had and viewed info on via NirSoft BlueScreenView has shown ntoskrnl.exe as the point of failure.
I know I'm not presenting a solution, and I really can't due to the nature of the issue, but I thought I'd spread some info.
Actually, come to think of it, I think every blue screen I've ever had and viewed info on via NirSoft BlueScreenView has shown ntoskrnl.exe as the point of failure.
I know I'm not presenting a solution, and I really can't due to the nature of the issue, but I thought I'd spread some info.
