Most likely, the event was caused by an improper removal of the SD card. In any case, there is no threat to our important data which are hopefully not located on an SD card.
You may need a firmware upgrade, or you could have a slightly defective drive that is about to go out in flames. This site uses Akismet to reduce spam. That should tell you. Thanks for your reply. Attached is a screenshot for reference. Thanks again. That would have it's own logging and hopefully diagnostics too. For instance, in the following error, the matching disk to look for in Disk Management is "Disk 5".
NET ltd. I hadn't realized that your post was from May, but here is some info in case other run into this:. Fire that up and expand the "Device" tree node. Under there you will have several nodes for "Harddisk0" I was under the impression that "DR" stands for "disk removable", but I honestly wasn't able to find any references to that so I could be wrong.
But in my experience this error is almost always logged for USB drives and we see a lot of events since we do event log monitoring. One thing to note however, is that "DR" is being incremented as you insert new e. USB drives. So, if you insert a memory stick for the first time, it could be logged as. So you definitely can't go by the DR unless you use Winobj. The "Harddisk5" should refer to "Disk 5" in Disk Management however.
Every disk will have a device controlling the Raw Physical drive DR identifier and a device per each partition, controlling the partition DP instance. These are just unique random numbers. Ramhound I know windows starts counting at zero, but that Window's "zero" depends on the order that BIOS reports and often does not match physical device ports or location.
I thought you needed help identify it, knowing Windows starts counting at 0, helps you do exactly that. What BIOS does is outside of the scope of this question, Windows is generating the error, so what Windows does is really the only thing that is important. DR stands for Drive Removable, so it is a removable drive , not a fixed drive.
Show 4 more comments. Active Oldest Votes. The information still allows the disks to be identified. Improve this answer. Thank you. The second command lists them in reverse order from the first, but this tells me for sure which is which.
I wonder why yours are reversed compared to mine? The working command for PowerShell and Command with Administrator permission are different.
So, the above thread was not actually answered. The "unplug USB devices" was oddly, marked as an answer. Same question and lots of posts about how to fix the problem. But, the final post helpful at last but not from Microsoft unfortunately does say that "X" is simply the disk number in disk manager. Is this right?
Also, what is "Y"? This incorrectly states that Y is the disk number. How do I know this is incorrect? I for example, see "DR5" in the error but I only have 3 disks! The first post above also complains of the same problem, so we are no nearer knowing what Y actually is. The answer here is a very generic "look in disk manager". But, this does not actually answer the question.
The answer here is that Y should be a number, which indeed it is, but that doesn't really help answer the question. I'm hoping that someone from MS here will post a definite statement and not ask me for more details of "my" error, post links to 13 year old technet articles, or explain how to run chkdsk.
I am still awaiting the research results. Under Device it lists your storage devices. You will find that Y is a number that gets dynamically assigned to each drive.
When you go through the following sequence then you will see that the number keeps changing:. After opening the error event in the Event Viewer, click the Details tab to see the details below. Right at the end you will find the drive letter that the error message refers to. To get an authoritative and generalised answer you will have to wait until an expert on the subject contributes towards this thread or else do your own research which could be time consuming.
I unmarked the two comments marked as answers because the original question was "My question is: what exactly are X and Y?
I have attempted to reseacrh this myself and have come up with the links above, but no authoritative answer so far.
Clearly the numbers X and Y mean something deterministic, it's just a question of what? That seems like a rather eccentric way of finding out what X and Y are! I'm trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Expect for "DR", usually we also can see the "volume" "partition". I will update here for any results. This can be beneficial to other community members reading the thread.
Hi, thanks for the reply. WinObj has definitely shed some light on it. But, it's also showing me something odd. Disk0 has two partitions on it: the usual MB system reserved and the rest of the drive. The DR'Number' appears to be related to the entire disk, because each "Harddisk'number'" has only one DR'number', even if there is more than one partition.
0コメント