Unending EventViewer Error 507: failed non-ReadWrite SCSI SRB request

I have an ASUS Z390M-pro Wireless motherboard, a Samsung EVO 970 Pro SSD (boot), two separate HDD's with my Desktop junction-pointed to one, and Windows10x64 version 1903. No other storage.

• I keep getting EventViewer Error 507 "Completing a failed non-ReadWrite SCSI SRB request," about 30+ per second when idle. The system is about 1 month new and I do not know how long this has been going on, perhaps since the beginning--the log truncates at about 12,000 entries. The log is [Applications and Services Logs -> Microsoft -> Windows -> StorDiag -> Microsoft-Windows-Storage-ClassPnP/Operational]..
• I can find nothing useful on the internet except that StorDiag is a new Windows feature. Following an example, I ran
  > stordiag.exe -collectEtw -checkFSConsistency -out c:\users\john\desktop
  There were no printed errors and casually browsing the output folder Desktop/StorDiag showed nothing bad. chkdsk and sfc /scannow also come up errorless.

I know nothing here. Does anyone know what could be going on? Any help woud be appreciated.
Regards,
-Cab-

- - - Updated - - -

Thanks to Mark Berry in his post: StorDiag Errors after Windows 10 Upgrade | MCB Systems I have discovered that if I disable certain USB devices, the errors stop. Specifically, Device Manager shows the following devices:

• Disk Drives
  - Generic- Compact Flash USB Device
  - Generic- MS/MS-Pro USB Device
  - Generic- SD/MMC USB Device
  - Generic- SMxD-Picture USB Device
  [...]

If I disable all of them the 507 Errors stop--in fact no more entries are logged. And windows states that the best driver is already installed, for each--but "there may be better drivers on the Mfr website."

on researching multiple posts about same topic it seams this error usually generate if you have a built in card reader that didn't receive a windows 10 driver update . or on upgrading from windows 7 to windows 10 while the system have a built in card reader (by built in meaning they are not plugged in through usb , but maybe soldered or hardwired to the board) so yea the forum suggests that all it takes to fix it is disable the faulty driver in device manager . however i recommend you try to find them a dedicated windows 10 driver on manufacturer's website and installing it after completely removing and deleting older ones on prompt .

Microsoft iSCSI initiator Service. Try and disable that. See what happens

Silly Me--I was waiting for an email to let me know someone had replied. Now I see have three very prompt ones. Many Thanks:
.
@nIGHTmAYOR: I get about equal frequency of errors for each of the four USB ports I listed. They are all on a new ASUS z390M-Pro motherboard (specifying Windows 10x64) and the system was built about a month ago--installing 10-pro and updating (as far as I know). For each device DeviceManager's [Update Driver] reports that the "best" driver is installed. The Manufacturer is listed as "(Standard disk drives)." I cannot find anything specific for these ports on the ASUS site.
. @swarfega: I have nothing plugged into any of the USB ports.
.
@Pluginz: MSiSCSI service was Manual-start and was not running. I started it, but that did not help. I changed the startup-type to Automatic and rebooted. There was no change.
.
I appreciate all these suggestions.
-Cab-

Right, right, swarfega. I think opening the tower and handling the motherboard is beyond my paltry skillset. But I could disable that port in Device Manager if I knew which one. But each error specifically references one of the four USB ports I mentioned. Those errors do stop as each is disabled. I hope disabling would accomplish the kind of test you suggested.

Just to bump this thread with some info, this also manifests on USB connected Alcor Micro card readers that are built into PC cases, which do actually have vendor drivers available for windows 10, the same issue also occurs on the microsoft generic storage driver,

Its due to these older USB 2 readers not detecting card insertion and attempting to mount the device whilst no card is inserted,

The multiple Stordiag errors coincide with a single entry under the StorageSpaces-Driver reporter

Code:

Physical disk {00000000-0000-0000-0000-000000000000} failed while arriving. Return Code: {No Disk}
There is no disk in the drive.
Please insert a disk into drive %hs..                  
Pool Id: {00000000-0000-0000-0000-000000000000}                  
Drive Number: -1                  
Drive Manufacturer: NULL                  
Drive Model Number: NULL                  
Drive Serial Number: NULL

Up front: I am sorry, I do not have a solution for this.

Having more or less the same problem, I posted on various forums. Regretfully, it seems no-one has a solution or a clue what it might be.

My event log is flooded with thousands and thousands of such errors.
EventID 500 : Completing a failed upper level read request.
EventID 502: Completing a failed upper level paging read request.
EventID 505: Completing a failed Read SCSI SRB request
EventID 507: Completing a failed non-ReadWrite SCSI SRB request
All from: Microsoft-Windows-StorDiag

Sometimes many times per second.
Yesterday I had an error that was repeated 488x ...
(copied/pasted the error into Excel and did a count)
488x within 1/one second (14:29:15)!

With me, these errors are mostly (if not all) related to external USB HDD's.
Drives usually work fine though. Chkdsk, disktools, they do not show errors.

Yesterday, when copying from a drive, after some 30 seconds of copying, WIndows stopped copying: it could not find the drive.

However, itt was listed in device manager and Explorer and I could access the drive, like it was normal.
Except for copying: it halted then, after creating a few empty folders.

Today the drive seems to work fine.

With all this I justy want to say: if things work fine, well, maybe you should 'softpedal' on this.
I spent hours and hours, all the chkdsk, sfc, clean boot, dism restorehealth, whatever other commands, they did not help.
Maybe it has something to do with TRIM(??)
Some time ago I believe I'v read about disable stordiag (??) I don't know....

As said, it doesn't solve your problem.