Hi
Does RMS3CC080 support CacheCade from LSI / Avago / Broadcom (what ever there calling themselves now).?
CacheCade into is here : MegaRAID CacheCade Pro 2.0 Software
Normally its a software key to activate the feature. The chip used in the Intel part (LSI3108) is not listed as compatible, but then LSI say i have to ask you guys.
Many Thanks
I have a S2400SC motherboard. Testing approved RAM, Samsung M393B2G70BH0-YH9 16GB ECC Registered Memory, using the Memtest86 v7.4 UEFI, I get a flood of bit fade errors (Test 10). The Memtest86 forum suggested that it might be a known bug in the Intel BIOS. In another forum posting, I saw a similar problem reported on various Intel MBs in the S2600 series. One individual reported that setting the BIOS to Optimize for UEFI fox it for him, but trying that, I still get a lot of errors.
The cpu is Intel E5-2450L (supports ECC RAM), and only 1 cpu is installed on the MB. I ran the tests using 1 core. I ran it again with 64GB installed (4 x 16GB), and again got a result showing 1024 errors in Test 10 only. The summary report shows
Lowest Error Address: 0x3FFFE018 (1023MB)
Highest Error Address: 0x3FFFF814 (1023 MB)
Bits in Error Mask: 00000000FFFFFFFF
Bits in Error - Total: 32 Min: 0 Max: 32
Max Contiguous Errors: 2
Thanks for any help in sorting this out.
Good day!I need help to activate Storage Management Pack (MFSLUNCOPY) and Advanced Management Pack (MFSADVMGMT)
Chassis Serial Number: BZMD13000739
Thank you for your participation and patience.
WBR, AK
Hello,
I have a Intel S3420GPC motherboard with a RAID1 configuration with 2 hdd.
I few days ago we had an issue with one of the hdd and the RAID1 was forced to go with status offline .
Operating system (centos 5.9-64 bits) works just fine with drive 0, it boots and all of that.
But i want to replace the bad drive.
I turned off the server to replace the bad drive (drive1) and I inserted a new hdd (same hdd as the first one ST1000DM010-2E102 - please see pic2)
Using the CTRL+E I entered the embedded raid config utility and tryed to restore the raid1.
port 0 ONLIN A00-00
port 1 READY
1. I tryed Check Consistency (please see pic 1)- I waited 1 hour with no progress 0% (please see pic 1)
2. I tryed to Rebuild with
port 0 ONLIN A00-00
port 1 READY
It says only hotspare and failed disk can be rebuild.
Then I went to Objects- Physical Drive - select drive 1 - mark as hotspare,
I go back to Rebuild , I see
port 0 ONLIN A00-00
port 1 HOTSP
I select HOTSP and hit F10 to rebuild - I receive message VD is not in degraded state, can not select drive for rebuilding. (please see pic 3)
What is the procedure to rebuild raid 1 ?
And I still want to have data from drive 0.(I don't want to use configure - new configuration)
Thank you
Adrian
Hi
Ive been looking for part numbers for a RAID cable that will come from the host (SFF8643) to standard straight SATA connectors (the drives).
Any ideas?
Many Thanks
Hi. I have an Intel Server System configured as follows:
(1) R2312WFTZS - Intel® Server System R2312WFTZS
(2) CD8067303561500 - Intel® Xeon® Silver 4108 Processor (11M Cache, 1.80 GHz)
(2) AXX1300TCRPS - AXX1300TCRPS - 1300W AC Power Supply
(8) KSM26RS8/8HAI - KINGSTON 8GB 2666MHZ DDR4 ECC REG CL19 DIMM 1RX8 HYNIX A IDT
(1) VROCSTANMOD - Raid On CPU standard Module
(1) AXXCBL600CVCR - 600 mm long, accessory cable kit (1 cable included), straight OCuLink SFF-8611 connector to right angle OCuLink SFF-8611 connector
(1) AXXCBL620CRCR - 620 mm long, spare cable kit (1 cable included), right angle OCuLink SFF-8611 connector to right angle OCuLink SFF-8611 connector
(2) SSDPE2MX450G701 - P3520 (450GB, 2.5IN PCIE 3.0 X4, 3D1)
(1) RMS3AC160- Intel Integrated RAID Module RMS3AC160
(1) AXXRMFBU6 - Intel MFBU6 RAID Super Capacitor Module BACKUP FOR RMS3AC160
(4) SSDSC2BB016T701 - DC S3520 Series 1.6TB 2.5inch SATA 6Gb/s 3D1 MLC Brown Box
When I attempt to configure the VROC RAID in the BIOS there are no options to configure. I am able to configure the RMS3AC160. Everything I have been reading says in order to enable the Raid in the CPU (VROC) I need the VROC Key which I have installed, but there seems to be no way to address the NVME u.2 drives to configure. Where am I suppose to go to configure the RAID so I can boot up on it? I have read the Configuration document(https://downloadmirror.intel.com/27135/eng/RSTe%20VROC%20Users%20Manual_1.0.pdf) referenced in another thread(Intel S2600WF (Wolf Pass) can't see NVMe Drives and VROC is not detected ). I configure the Intel VMD and then restart and try to find the "Intel VROC HII interface" in the Bios and cannot find it. I have installed the newest BIOS (S2600WF_EFI_BIOSR0009_ME04.00.04.288.0_BMC1.29.7d703f59_FRUSDR1.29). I have tried in uefi and in legacy boot. Help, all I want is a mirrored nvme boot drive to install Windows Server 2016 on. With a 4 drive RAID 6 SATA disk to hold our data and hyper-v vm's and vhdx's.
Also, I have not been able to get a windows installation to boot up on this system.
Thanks,
Rick Lund-Pedersen
Around The Clock I. T. Solutions Ltd.
Yesterday my machine rebooted without any warning. I have not been able to find the reason for this reboot. There was nothing changed at the system. I have neither touched the BIOS configuration nor the operating system. I have found the server running, but stuck at the very beginning of POST. The POST Error Code gave me the value "DB" and the system beeped six times short about every 10 minutes. Unfortunately this system state is not documented at all. The only way out of this situation has been a CMOS clear.
Now POST runs through without errors. After configuring BIOS (UEFI Boot, Intel VT-x, etc.) I tried to boot into the installed operating system (Windows Server 2016). The screen will show the windows logo for about 3 seconds, before a BSOD appears with the stop code "ACPI BIOS ERROR". I get the same result if I try a new installation of Windows Server 2016 or Windows Server 2012 R2. The system will load Windows PE from USB Drive fine. Afterwards the process of booting (Windows logo) will be interrupted after 3 seconds and results into a blue screen with ACPI BIOS ERROR.
So far I have tried:
System Details: Intel P4308CP4MHGC Case, Intel S2600CP Mainboard with latest BIOS (v02.06.0006), 2x Intel Xeon 2620v2, 64Gb RAM (registered ECC)
Hi,
Since 4 months we have a Windows 2016 Server with S1200SP Systemboard running smooth without any problems:
System Information
Remote Management Module key : Installed
Device (BMC) Available : Yes
BMC FW Build Time : 2017-09-11 15:42:03
BIOS ID : S1200SP.86B.03.01.0026.092720170729
BMC FW Rev : 1.10.10925
Boot FW Rev : 1.05
SDR Package Version : SDR Package 0.26
Mgmt Engine (ME) FW Rev : 04.01.04.054
but the last two day we had unexpected Shutdowns, but we have nothing changed (except: Windows Updates!)
Windows Eventlog:
BMC:
Memory.dmp:
icrosoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Temp\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 14393.2007.amd64fre.rs1_release.171231-1800
Machine Name:
Kernel base = 0xfffff802`18007000 PsLoadedModuleList = 0xfffff802`1830f1a0
Debug session time: Tue Feb 13 10:03:59.159 2018 (UTC + 1:00)
System Uptime: 0 days 18:18:50.499
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 80, {4f4454, 0, 0, 0}
Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 14393.2007.amd64fre.rs1_release.171231-1800
SYSTEM_MANUFACTURER: Intel Corporation
SYSTEM_PRODUCT_NAME: S1200SP
SYSTEM_SKU: SKU Number
SYSTEM_VERSION: ....................
BIOS_VENDOR: Intel Corporation
BIOS_VERSION: S1200SP.86B.03.01.0026.092720170729
BIOS_DATE: 09/27/2017
BASEBOARD_MANUFACTURER: Intel Corporation
BASEBOARD_PRODUCT: S1200SP
BASEBOARD_VERSION: H57534-250
DUMP_TYPE: 1
BUGCHECK_P1: 4f4454
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 8
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: BA'00000000 (cache) BA'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x80
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: xx
ANALYSIS_SESSION_TIME: 02-13-2018 16:25:58.0583
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff8021885f23e to fffff802181626e0
STACK_TEXT:
ffff8580`5dccee08 fffff802`1885f23e : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8580`5dccee10 fffff802`18236b7c : ffffab8d`fc48b968 fffff802`18876a70 fffff802`18876a70 00000000`00000001 : hal!HalBugCheckSystem+0x7e
ffff8580`5dccee50 fffff802`1886020e : fffff802`000006c0 fffff802`183c563c ffff8580`5dccef30 fffff802`180817f8 : nt!WheaReportHwError+0x258
ffff8580`5dcceeb0 fffff802`1808111a : ffff8580`5dcc1180 00000000`00000000 00000035`f7981a91 fffff802`180815c8 : hal!HalHandleNMI+0xfe
ffff8580`5dcceee0 fffff802`1816df02 : ffff8580`5dcc1180 ffff8580`5dccf0f0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x106
ffff8580`5dccef30 fffff802`1816dcc2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffff8580`5dccf070 fffff804`b3f51348 : fffff804`b3f51320 ffffab8d`fc8783d0 ffffab8d`fc4128d0 0000d7e0`07c7bf8c : nt!KiNmiInterrupt+0x482
ffff8580`5dcf27d8 fffff804`b3f51320 : ffffab8d`fc8783d0 ffffab8d`fc4128d0 0000d7e0`07c7bf8c 00000000`00000000 : intelppm!MWaitIdle+0x18
ffff8580`5dcf27e0 fffff802`1805d71c : 00000000`00000000 0000d7e0`0000001b 00000035`f7981a91 00000000`00000020 : intelppm!AcpiCStateIdleExecute+0x20
ffff8580`5dcf2810 fffff802`1805c8ca : fffff802`1805b150 00406299`00406299 fffff802`18007000 00406299`00406299 : nt!PpmIdleExecuteTransition+0xc9c
ffff8580`5dcf2a80 fffff802`18165ebc : 00000000`00000000 ffff8580`5dcc1180 ffff8580`5dccf200 ffffab8d`fed4c080 : nt!PoIdle+0x33a
ffff8580`5dcf2be0 00000000`00000000 : ffff8580`5dcf3000 ffff8580`5dcec000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: de588e0752e3f5f3e9b60d5dc1178386861b718c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 971c378bba6c1258bb583b5a27c253ba725bd373
THREAD_SHA1_HASH_MOD: 660bcac133d31e5273140ad75d80b5b0294f8e45
FOLLOWUP_IP:
intelppm!MWaitIdle+18
fffff804`b3f51348 c3 ret
FAULT_INSTR_CODE: ccccccc3
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: intelppm!MWaitIdle+18
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 578997a3
BUCKET_ID_FUNC_OFFSET: 18
FAILURE_BUCKET_ID: 0x80_intelppm!MWaitIdle
BUCKET_ID: 0x80_intelppm!MWaitIdle
PRIMARY_PROBLEM_CLASS: 0x80_intelppm!MWaitIdle
TARGET_TIME: 2018-02-13T09:03:59.000Z
OSBUILD: 14393
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 2
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 LanManNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-01-01 05:38:03
BUILDDATESTAMP_STR: 171231-1800
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.2007.amd64fre.rs1_release.171231-1800
ANALYSIS_SESSION_ELAPSED_TIME: b1e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x80_intelppm!mwaitidle
FAILURE_ID_HASH: {4d921e65-7fcd-f5e4-043a-b02bdcd10b07}
Followup: MachineOwner
---------
Any Ideas? Thanks in advance.
I've got a bunch of S2600WFs and I'd like/need to be able to disable the onboard NICs. There is an option grayed out in the BIOS under Advanced -> PCI Configuration -> NIC Configuration
I was wondering if some other setting will allow me to disable them, or perhaps a jumper setting... I didn't see anything in the manual (S2600WF_TPS.pdf).
I'm installed ubuntu16.04 desktop on this server. But network doesn't work, a "cable unplugged" always show in network setting.
I'm wondering is it a driver issue so I downloaded a driver from here: Download Intel® Ethernet Adapter Complete Driver Pack .
And then I installed "PROXGB\LINUX\ixgbe-5.3.5.tar\ixgbe-5.3.5" from it since I thought s2600wft uses x557-at2 Ethernet module
from this guide: https://www.intel.com/content/dam/support/us/en/documents/server-products/server-boards/S2600WF_TPS.pdf .
After that, the network status is shown as connected. But I still can't successfully ping addresses in the same subnet. And the very
strange thing is that I can see local ip in "ifconfig" when the cable is unplugged. Also, during every steps in my try, the rj45 light
doesn't blink. Had somebody encountered these problems for s2600wft?intel_adminCommunityAdminitpnadmin@
Hi, I'm trying to find out what the tested/approved memory is for the above board.
The links to the approved Memory is no longer on the web page?
Any help appreciated.
Thanks in advance.
Ralph Coulter
Hello,
i have a question...
Is it possible to enable SSD Cache Intel SRT on an Onboard Raid 10 (4x3TB WD Purple) on Supermicro X11SPL-F?
My Onboard Raid 10 is soo poor... ~40MBs r/w on an Server 2016 / Exchange 2016 with DHCP and DNS Server...
Specs are Xeon Silver 4108
6x4GB DDR4 2133 ECC Hex Channel
4x3TB Western Digital Purple
Onboard Raid 10 - tried Raid 5 but... hell no...
Performance was poor since fresh install, but now with everything installed... 30sec to open anything... Exchange laggs (e.g network scanner has sometimes problems to scan to mail)
So ive thought, hey...
i have an 120GB sata SSD here, part them into 2 parts
64GB for Cache, 32gb for pagefile - but...
i dont have any real options @Intel RSTe???? i mean ENTERPRISE? and missing features?
Should be Intel RSTe 5.3.0.1412
Does anyone has a hint maybe?
PS: i dont wanna rebuild the server
We have tested Software Mirrors on a number of Intel S1200SPLR motherboards under Windows Server 2016. In all instances we are unable to boot off the Secondary Mirror Disk. We installed a 3rd party Sata controller in the system and it works fine. The issue is definitely the Sata connectors on the Intel Motherboard. Has anyone else experienced this problem?
Hello
We currently have 2x "Intel Server System SR2600URBRPR" servers.
We are moving our offices to a new location but we cannot take our Rack chassis with us so we are looking to buy a new one.
In the current solution the servers do not fit the rack so they are resting at the bottom of the rack which is neither a pretty nor practical solution.
Right now we are looking to buy a "Toten 19" Floor Cabinet 15U 600X800" but as far as we can see the 2 servers wont fit just as the current solution.
1st reason is because we changed the disks to SSD's but SSD disks don't fit correctly in the drive bays so each bay extends a few cm from the server chassis.
2nd it seems the server chassis is a bit too long for the rack chassis - As far as we can tell.
It is not possible to replace the servers so the solutions we are looking at are the following:
1. Replace the server chassis with one that fits in the rack chassis.
2. Replace the rack chassis with one that fits the servers. The requirement are that we have both front and back access but with the possibility closing the rack both front and back.
3. If none of the above is possible then we have no choice but to place the servers outside the rack wither on the floor or on top of the rack. This solution is our fallback if neither solution 1 or 2 is possible.
We hope someone can point us in the right direction.
Thanks
Kenneth
Hi
I have installed two P4600 NVME devices in a server and installed Proxmox 5.1-3. The running kernel is 4.13.13-6-pve. There is no RAID controller involved.
# nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 BTLE736103CH4P0KGN INTEL SSDPEDKE040T7 1 4.00 TB / 4.00 TB 512 B + 0 B QDV10170
/dev/nvme1n1 BTLE736103AG4P0KGN INTEL SSDPEDKE040T7 1 4.00 TB / 4.00 TB 512 B + 0 B QDV10170
The output of "isdct show -a -intelssd" is attached in the file "intelssdp4600-2.txt".
Now by using LVM I can always reproduce a "hanging" behaviour of 1-2 minutes that does not lead to any fatal error:
vgcreate SSD /dev/nvme0n1 /dev/nvme1n1
lvcreate -l 100%FREE -n SSDVMSTORE01 --stripes 2 --stripesize 128 --type striped SSD
lvremove -d -v SSD/SSDVMSTORE01
Do you really want to remove and DISCARD active logical volume SSDTEST/SSDTEST01? [y/n]: y
here the command seems to be hanging for 1-2 minutes. in the Logs I see:
Feb 21 14:14:17 px kernel: [ 3654.745355] nvme nvme0: I/O 200 QID 14 timeout, aborting
Feb 21 14:14:17 px kernel: [ 3654.745772] nvme nvme0: I/O 201 QID 14 timeout, aborting
Feb 21 14:14:17 px kernel: [ 3654.746110] nvme nvme0: I/O 202 QID 14 timeout, aborting
Feb 21 14:14:17 px kernel: [ 3654.746436] nvme nvme0: I/O 203 QID 14 timeout, aborting
Feb 21 14:14:32 px kernel: [ 3669.013614] nvme nvme0: Abort status: 0x0
Feb 21 14:14:32 px kernel: [ 3669.014012] nvme nvme0: Abort status: 0x0
Feb 21 14:14:32 px kernel: [ 3669.014325] nvme nvme0: Abort status: 0x0
Feb 21 14:14:32 px kernel: [ 3669.014629] nvme nvme0: Abort status: 0x0
Feb 21 14:15:10 px kernel: [ 3707.737495] nvme nvme1: I/O 297 QID 14 timeout, aborting
Feb 21 14:15:10 px kernel: [ 3707.737902] nvme nvme1: I/O 298 QID 14 timeout, aborting
Feb 21 14:15:10 px kernel: [ 3707.738231] nvme nvme1: I/O 299 QID 14 timeout, aborting
Feb 21 14:15:10 px kernel: [ 3707.738547] nvme nvme1: I/O 300 QID 14 timeout, aborting
Feb 21 14:15:25 px kernel: [ 3722.005726] nvme nvme1: Abort status: 0x0
Feb 21 14:15:25 px kernel: [ 3722.006113] nvme nvme1: Abort status: 0x0
Feb 21 14:15:25 px kernel: [ 3722.006434] nvme nvme1: Abort status: 0x0
Feb 21 14:15:25 px kernel: [ 3722.006751] nvme nvme1: Abort status: 0x0
After this, the command completes without error.
This does not happen with Debian 9.3 (Kernel 4.9.x). If I partition the devices with one 2GB primary partition and do the same operation but with /dev/nvmeXn1p1 or p2 the timeout does happen on the second partition but not on the first:
parted -a optimal /dev/nvme0n1 mklabel gpt
parted -a optimal /dev/nvme0n1 mkpart primary 4 2047
parted -a optimal /dev/nvme0n1 mkpart primary 2048 100%
parted -a optimal /dev/nvme1n1 mklabel gpt
parted -a optimal /dev/nvme1n1 mkpart primary 4 2047
parted -a optimal /dev/nvme1n1 mkpart primary 2048 100%
Any clues?
Best,
Pierre
Hi,
Since 4 months we have a Windows 2016 Server with S1200SP Systemboard running smooth without any problems:
System Information
Remote Management Module key : Installed
Device (BMC) Available : Yes
BMC FW Build Time : 2017-09-11 15:42:03
BIOS ID : S1200SP.86B.03.01.0026.092720170729
BMC FW Rev : 1.10.10925
Boot FW Rev : 1.05
SDR Package Version : SDR Package 0.26
Mgmt Engine (ME) FW Rev : 04.01.04.054
but the last two day we had unexpected Shutdowns, but we have nothing changed (except: Windows Updates!)
Windows Eventlog:
BMC:
Memory.dmp:
icrosoft (R) Windows Debugger Version 10.0.10586.567 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Temp\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 14393.2007.amd64fre.rs1_release.171231-1800
Machine Name:
Kernel base = 0xfffff802`18007000 PsLoadedModuleList = 0xfffff802`1830f1a0
Debug session time: Tue Feb 13 10:03:59.159 2018 (UTC + 1:00)
System Uptime: 0 days 18:18:50.499
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 80, {4f4454, 0, 0, 0}
Probably caused by : intelppm.sys ( intelppm!MWaitIdle+18 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
NMI_HARDWARE_FAILURE (80)
This is typically due to a hardware malfunction. The hardware supplier should
be called.
Arguments:
Arg1: 00000000004f4454
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 14393.2007.amd64fre.rs1_release.171231-1800
SYSTEM_MANUFACTURER: Intel Corporation
SYSTEM_PRODUCT_NAME: S1200SP
SYSTEM_SKU: SKU Number
SYSTEM_VERSION: ....................
BIOS_VENDOR: Intel Corporation
BIOS_VERSION: S1200SP.86B.03.01.0026.092720170729
BIOS_DATE: 09/27/2017
BASEBOARD_MANUFACTURER: Intel Corporation
BASEBOARD_PRODUCT: S1200SP
BASEBOARD_VERSION: H57534-250
DUMP_TYPE: 1
BUGCHECK_P1: 4f4454
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CPU_COUNT: 8
CPU_MHZ: e10
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: BA'00000000 (cache) BA'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x80
PROCESS_NAME: System
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: xx
ANALYSIS_SESSION_TIME: 02-13-2018 16:25:58.0583
ANALYSIS_VERSION: 10.0.10586.567 amd64fre
LAST_CONTROL_TRANSFER: from fffff8021885f23e to fffff802181626e0
STACK_TEXT:
ffff8580`5dccee08 fffff802`1885f23e : 00000000`00000080 00000000`004f4454 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8580`5dccee10 fffff802`18236b7c : ffffab8d`fc48b968 fffff802`18876a70 fffff802`18876a70 00000000`00000001 : hal!HalBugCheckSystem+0x7e
ffff8580`5dccee50 fffff802`1886020e : fffff802`000006c0 fffff802`183c563c ffff8580`5dccef30 fffff802`180817f8 : nt!WheaReportHwError+0x258
ffff8580`5dcceeb0 fffff802`1808111a : ffff8580`5dcc1180 00000000`00000000 00000035`f7981a91 fffff802`180815c8 : hal!HalHandleNMI+0xfe
ffff8580`5dcceee0 fffff802`1816df02 : ffff8580`5dcc1180 ffff8580`5dccf0f0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x106
ffff8580`5dccef30 fffff802`1816dcc2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffff8580`5dccf070 fffff804`b3f51348 : fffff804`b3f51320 ffffab8d`fc8783d0 ffffab8d`fc4128d0 0000d7e0`07c7bf8c : nt!KiNmiInterrupt+0x482
ffff8580`5dcf27d8 fffff804`b3f51320 : ffffab8d`fc8783d0 ffffab8d`fc4128d0 0000d7e0`07c7bf8c 00000000`00000000 : intelppm!MWaitIdle+0x18
ffff8580`5dcf27e0 fffff802`1805d71c : 00000000`00000000 0000d7e0`0000001b 00000035`f7981a91 00000000`00000020 : intelppm!AcpiCStateIdleExecute+0x20
ffff8580`5dcf2810 fffff802`1805c8ca : fffff802`1805b150 00406299`00406299 fffff802`18007000 00406299`00406299 : nt!PpmIdleExecuteTransition+0xc9c
ffff8580`5dcf2a80 fffff802`18165ebc : 00000000`00000000 ffff8580`5dcc1180 ffff8580`5dccf200 ffffab8d`fed4c080 : nt!PoIdle+0x33a
ffff8580`5dcf2be0 00000000`00000000 : ffff8580`5dcf3000 ffff8580`5dcec000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: de588e0752e3f5f3e9b60d5dc1178386861b718c
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 971c378bba6c1258bb583b5a27c253ba725bd373
THREAD_SHA1_HASH_MOD: 660bcac133d31e5273140ad75d80b5b0294f8e45
FOLLOWUP_IP:
intelppm!MWaitIdle+18
fffff804`b3f51348 c3 ret
FAULT_INSTR_CODE: ccccccc3
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: intelppm!MWaitIdle+18
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: intelppm
IMAGE_NAME: intelppm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 578997a3
BUCKET_ID_FUNC_OFFSET: 18
FAILURE_BUCKET_ID: 0x80_intelppm!MWaitIdle
BUCKET_ID: 0x80_intelppm!MWaitIdle
PRIMARY_PROBLEM_CLASS: 0x80_intelppm!MWaitIdle
TARGET_TIME: 2018-02-13T09:03:59.000Z
OSBUILD: 14393
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 2
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 LanManNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2018-01-01 05:38:03
BUILDDATESTAMP_STR: 171231-1800
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.2007.amd64fre.rs1_release.171231-1800
ANALYSIS_SESSION_ELAPSED_TIME: b1e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x80_intelppm!mwaitidle
FAILURE_ID_HASH: {4d921e65-7fcd-f5e4-043a-b02bdcd10b07}
Followup: MachineOwner
---------
Any Ideas? Thanks in advance.
Hello, i own two of these systems with Intel Server Board S2600WTT and im having serious issues booting them up
For cpu i use one Xeon E5-2609V4 in each and two sticks of Samsung M393A1G40EB1-CPB0Q reg. ecc 2133 ddr4 ram
basically the system starts with three beeps, fans spin at full and leds show an error (one green, three ambers) , black screen.
Could it be a compatibility issue with V4 cpu or even memory ? dont have much experience with Intel systems
Hi,
Nowhere is mentioned is it possible to add m.2 pcie ssd from on board port in VMD domain pool? Or is ist possible to create raid with vroc on those m.2 pcie ssd. They are linked to PCH 62X but PCH is linked with pcie lanes to CPU so its no sense that this is not possible, but in documentation there is no any information regarding this. It will be very nice for 1U system for example 1304 or 1208 to create raid on those m.2 pcie ssd with vroc.
Please clarify is it possible or not, or is planed in future to be possible.
We have a Server with Integrated RAID Module RMS3CC040 (Firmware Package V: 24.21.0-0012, Firmware Version: 4.680.00-8249) with 3 Samsung 850 Pro Drives RAID 0 (HS)
Every Reboot the Controller shows 3 Warnings: Controller ID: 0 PD is not enterprise class self encrypting drive. Encryption capability of the drive will be disabled -:-:0
We Use AVAGo MSM 17.05.00.02
Any suggestions or ideas ? Thanks in advance.
Hi
Does RMS3CC080 support CacheCade from LSI / Avago / Broadcom (what ever there calling themselves now).?
CacheCade into is here : MegaRAID CacheCade Pro 2.0 Software
Normally its a software key to activate the feature. The chip used in the Intel part (LSI3108) is not listed as compatible, but then LSI say i have to ask you guys.
Many Thanks