![]() In due course I dare say one or other will get round to posting an updated driver or firmware to fix it. WD are asleep at the switch as usual, and M$ are no better. Samsung) of their drives, which stops the error on those drives. A number of manufacturers have provided updated drivers (e.g. The Windows 11 default NVMe driver throws this error for a lot of NVMe SSDs. However, I'm wondering if there is an updated driver newer than 2006? I wonder if WD even cares about this issue at all? I'm at the point where I feel like returning them for an alternative while I'm still within the return window. To have this issue only occurring with WD and not the Samsung 990 Pro is really frustrating. ![]() I spent over $2K on WD Black SN850X NVME Storage. The dump can't be created because the storage is experiencing issues and likely offline. Unfortunately, I can't even collect the debug logs because I get another event Error with the following:ĭump file creation failed due to error during dump creation. ![]() This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. The system has rebooted without cleanly shutting down first. Then comes the BSOD leaving a Critical event with the following message: The driver detected a controller error on \Device\RaidPort7. The driver detected a controller error on \Device\RaidPort6. The driver detected a controller error on \Device\RaidPort5. The driver detected a controller error on \Device\RaidPort4. The driver version and info for all the nvme drives, including the Samsung, is as follows: There is absolutely no difference at all. Interestingly, in device hardware I was able to compare the driver, driver version, and the options that are selected to the non-issue Samsung 990 Pro. 128GB of G.Skill Trident Z DDR5 6000 running at 5600Hz.I'm also getting randomized BSOD due to this exact issue! Post-post edit: The motherboard is Asus ROG STRIX Z790-E, i9-13900KF, Corsair 2x16GB DDR5 DRAMs pushed by XMP II to 5600, Windows installed and updated within the last week or so for the 1st time, two M.2 drives 1TB IN m.2_1, the other 2TB in M.2_2 - the latter WD 850x. If I don't see that error killing my PC in the future I'm gonna write this one up as a software glitch where some software entity isn't "being told" that a Sleep powerdown is about to happen so that software entity just spits out what it sees as an error rather than as a mundane to-be-expected event. Looking over the logs (Admin mostly) it appears this is consistent - the weird Raid error happens either on start of or end of Sleep state for the PC. It's possible the Error entry ALSO was a delayed entry from when the system went to sleep, not as it woke up. ![]() I came back from coffee break and hit a Shift key on the keyboard to wake the PC up and - tada! - the Event 11 showed up in the event log simultaneously to the Ethernet whatever reporting the network link was disconnected (that, of course, actually was a delayed log entry from when the PC went to sleep at 10:01): So, since I don't really have a LOT of those errors in my event logs, I decided to go have a mug of coffee and purposefully allowed my PC's "timeout" to occur, placing the PC in a sleep state: all things powerdown like fans, the monitor turns to blinking-power-light mode, the PC itself reverts to blinky-poweron-light mode. drives" to see if any errors showed up - they did not. Shortly after making that comment I decided to try the "Copy large files back and forth between M.2_. I noted before (January 3rd, too) that I was seeing the Event ID 11 show up in my event logs.
0 Comments
Leave a Reply. |