HGST 4u60 + LSI 9300 8i + Server 2019 = stuck at spinning logo

[denywinarto]

Specs :

MSI Z390 Pro
Intel i7 8700
32gb ram corsair
HGST 4u60
LSI 9300 8i
Intel i2Ti


Last night there was a power surge, not sure what caused it, and it fried my nvme i think, it became undetected
So i reinstalled a new nvme drive with server 2019.
During installation it went just fine.
But when i try to initialize drive, it freezes. And Got this BSOD screen saying

Unexpected kernel mode trap
What failed C1.dll

The thing that bothers me is that it has been working fine for almost a year with server 2016.

What i have tried

1. Full install all driver > resulting in spinning logo for 1 hour, so i just installed the audio and intel iris driver
2. Change the LSI 9300 8i, i happen to have a backup, but it's still the same thing, so its not sas card issue
3. Change the memory,
4. Remove the intel PCIE nic
5. Move the SAS card to another PCIE
6. Removing the SAS card cable > this solves the issue and windows loads correctly, but then i cannot access my jbod!

The only thing left is the motherboard and the rack...
And i happen to not have any backup for them..
Been struggling for hours now, any idea?

 

[ari2asem]

6. removing sas cable

it think easy...use another cable

 

[denywinarto]

it think easy...use another cable

The sas card has 2 cable connected,
And i notice when i plug the right port only it's still detecting all my drives.
So i tried both cables on right port, unfortunately its still the same..
Isnt it unlikely that 2 cables are troubled?
Forgot to add, during Bios boot, my sascard could detect all drives, the issue only occurs in windows

 

[ari2asem]

try once again to install server 2019 after fully format of your new nvme ssd.

if still the same issue, then try server 2016 after fully format of nvme.

if still same issue with cables, then you really need new cables

 

[denywinarto]

Well last night i tried it on another machine

B450 ASrock

Athlon 200GE

8 gb team ram

Server 2016



I forgot to mention, during my first reinstall, i screwed up drivepool disk detection and it created 2 pools.

I didn't like it so i reinstall again,

So Interestingly, during initializing the drives on this machine, i got 2 BSOD's

But then after i solve the duplicated pool issues, it's been stable until now almost 10 hours,



So it's either the motherboard, or the drivepool setup.

If it's the motherboard, could also be the drivers, cause i'm using unofficial server 2016 drivers for the coffee lake,
but then again, this driver has been working fine for almost a year