What does the STATUS_DEVICE_DOES_NOT_EXIST error indicate?

[181951]

I have a dump file where I get this error. Does this error indicate a hardware problem with the disk or does it indicate a mismatch problem with the cables?

 

[ubuysa]

It means what it says on the tin. The 0xC0000C0 exception code indicates that the specified device does not exist in the system. What device is it? If you follow the BSOD posting instructions and upload the requested data we can probably help more.

 

[181951]

It means what it says on the tin. The 0xC0000C0 exception code indicates that the specified device does not exist in the system. What device is it? If you follow the BSOD posting instructions and upload the requested data we can probably help more.

Samsung 860EVO. I actually analyzed the dump file and the result was this error. I don't understand what exactly this error means.

 

[ubuysa]

Without seeing the dump, and the other related data requested in the BSOD posting instructions, I'd just be guessing. That exception is pretty straightforward though, it means that a device (the 850 EVO) was accessed but it wasn't present. That may be a drive failure, a SATA cable issue, a SATA port issue, or even a power issue. We ask for a range of data because they provide additional insight into what's going wrong.

 

[jcgriff2]

Hi. . .

It really may help us all out if you would please run the BSOD Dump + File Collection app -
Blue Screen of Death (BSOD) Posting Instructions - Windows 11, 10, 8.1 and 8

From Post #1 and Thread Title - STATUS_DEVICE_DOES_NOT_EXIST​

It really would very likely help us all if you would kindly run the Sysnative BSOD app so we all can see the output from \Documents\SysnativeFileCollectionApp

In early 2008, I wrote the first generation of the app that is executed today but did so rather slowly (requesting users to run CMD line commands at first) in bits and pieces and explained in great detail to users and staff exactly what I/the app was doing and why.

Finally, all of the CMD batch line commands were combined and areas in the main log that report the total execution run time for each app were analyzed to compare batch code run time vs. VBS run time. Overall, VBS is much faster than batch which led to many changes being implemented over the last 15 years. The first versions of the app took 15-20 minutes to run. These days depending on the hardware and Windows OS, the app can run in just a few minutes.

The app does not write to the Registry or any other "unknown" or "hiding" places. As the instructions say, a directory named \Documents\SysnativeFileCollectionApp is created and at the end of the run, that sub-directory is zipped up and will be waiting for you in \Documents to upload and attach it to your post. There is no personal or private data contained in any of the files. You can look through the files yourself if you wish to.

I just ran the app on my system and it completed in under 2 minutes. I have attached it to this post.

Device Manager does not display devices that are not connected -

Read this --> Device Manager does not display devices that are not connected - Microsoft Support (entire page)​

- Go into Device Manager (click on START or WIN key; then type or paste devmgmt.msc into a CMD screen
- click on view (at top; menu will drop down with ~7 items)
- click on Show Hidden Devices (should be the 6th item down on menu - W10 x64 Pro)
- check through the Device Manager for any red or yellow flags. We are likely looking for a USB related device, but no guarantees.

Do you know where the NT STATUS/exception error code 0xC0000C0 came from? If I enter that into Google, the first error code that Google Search Results bring back is for 0xc000009c.

Note that the Google returned code contains 8 digits after the 1st two 0x - which is exactly what I would expect to see. The 1st code only contains 7 digits -- one is missing and likely therefore giving us a false or misleading error.

The Google search mentioned above -

0xC0000C0 - Google Search

PLEASE run the app; upload and attach it to your next post.

Regards. . .

jcgriff2

p.s. THANK YOU!

 

[margarenao]

Without seeing the dump, and the other related data requested in the BSOD posting instructions, I'd just be guessing. That exception is pretty straightforward though, it means that a device (the 850 EVO) was accessed but it wasn't present. That may be a drive failure, a SATA cable issue, a SATA port issue, or even a power issue. We ask for a range of data because they provide additional insight into what's going wrong.

Based on the exception code, it sounds like the most likely cause is a problem with the 850 EVO drive. I mean I think that the drive itself may be failing.

In the meantime, is there anything else that can be done to fix the BSOD?

 

[ubuysa]

Without seeing the dump, and the other data we asked for, I can't help much more I'm afraid.