Storage issue with Z230 SFF workstation

[RowPat]

Got a HP Z230 with 20GB RAM, and Windows 10 Pro. Recently added extra HDD at a total 5 HDD (3 of them being SSD).

I am doing a fresh install of Windows 10. The PC shows DPC_WATCHDOG_VIOLATION (at BSoD) screen. I can't figure out the source of the issue. Could it be that the 240W PSU cannot handle it? (internal DVD drive has been removed). Also there's no PCI card installed. All plain vanilla. 

Any suggestion would be appreciated.

[RowPat]

addendum:

All HDD and SSD firmware up to date.

After installing Windows 10 Pro, all drivers and updates installed.

[TheOldMan]

That error is a result of an error caused usually by a driver issue, but have a look

https://www.howtogeek.com/742322/how-to-fix-a-dpc-watchdog-violation-in-windows-10/

[tcsenter]

Always unplug/disconnect those secondary non-boot drives except the one you are installing Windows onto. MUCH more simple (and safer) that way. Plug them back in after Windows is up-and-running (but not while Windows is running, shut down first). The most simple check for a power issue would be to just unplugged (data and power) for two drives and try again.

[RowPat · Accepted solution]

After days of frustration and analysis of BSoD dumps, I figured out that Wi-Fi dongles are causing the crash. I have three TP-Link USB adapters, different models, and all of them creating same problem. Not sure if this is only specific to TP-Link or all wireless modules will behave the same way (i don't have other chip-set) BUT I do have USB storage sticks, wireless mouse dongles and USB keyboards connected without issue. I have removed the Wi-Fi dongle and connected with Ethernet cord. Problem solved now. As precaution I have also physically removed the front USB hub. The workstation is destined to become a home-lab server using Proxmox.

[TheOldMan]

Glad you found the problem.  That link said the WatchDog error was usually caused by a driver issue, so perhaps the driver for the TP-Link USB adapter was the issue.

[tcsenter]

I find it ridiculous that Microsoft still cannot give a bit more meaningful parsed debug info on a crash dump to the end user other than just the same derned blue screen basic bug check error codes from the XP days. And that new QR feature they have, wow what a big improvement. It just takes you to the link, as though people don't know how to get on the internet themselves.  Anyway, rant over. Glad you found the problem! I have also had a naughty WLAN adapter that took me like two days before I figured out it was the WLAN driver causing the BSOD!