Windows 10: The device, \Device\Harddisk1\DR1, has a bad block.

Hi everyone,

I have been having this specific error popping up in Event Viewer for the past couple of days. I have narrowed it down to my NVMe drive, which is a XPG GAMMIX S11 Pro 256.0 GB, although I am not sure what is really going on.

• OS Name Microsoft Windows 10 Pro
• Version 10.0.19042 Build 19042
• BaseBoard Product ROG STRIX B450-F GAMING
• Processor AMD Ryzen 5 3600 6-Core Processor, 3800 Mhz, 6 Core(s), 12 Logical Processor(s)
• Installed Physical Memory (RAM) 16.0 GB
• Name NVIDIA GeForce GTX 1660

This error usually occurs when I'm playing Apex Legends, it occurs randomly. I am able to listen to the in-game sound but I am not able to move my mouse, Alt-Tab, Alt-F4, etc.

I have tried the following:

1. Performed chkdsk C: /f /r - 0 KB in bad sectors.
2. Performed a quick and normal scan for bad sectors in HD Tune with all sectors being green - good.
3. Verified the game file's integrity.
4. sfc /scannow - Windows Resource Protection did not find any integrity violations.

As you can see, it appears that my drive does not have bad sectors and yet I am still getting this error and my computer keeps freezing. Do you know what might be the cause of this issue?

I tried reading the S.M.A.R.T. values but did not find anything out of the normal, if you need an specific value please ask.

I am getting a little bit worried about my information. Should I make a backup and change the drive?

Thanks in advanced!

submitted by /u/JesP96
[link] [comments]

:)

 

The device, \Device\Harddisk1\DR1, has a bad block

I can't run diskpart in Powershell - I'm not familiar with Powershell, but diskpart just opens up a command window when I type it in Powershell.

But I might have it matched up using Get-PhysicalDisk:

In Powershell, I have 3 drives listed under deviceid:

deviceid
------------
0
1
2

And in WinObj I have 3 physical drives listed - DR0, DR1 and DR2.

My main HDD is listed for deviceid 1 in Powershell, and my USB thumb drive is deviceid 2. So I'm guessing DR1 in WinOBj = deviceid 1 in Powershell? If so, then that's my main HDD. I was hoping the bad block was just my thumb drive.

 

The device, \Device\Harddisk1\DR1, has a bad block

Perhaps - that is a good thought. Easy (but a bit long winded) to check. Download WinObj

Go to GLOBAL?? and sort by SymLink





You can then find the PhysicalDrive for the DR number and match it against the deviceid in powershell

Get-PhysicalDisk | select deviceid,friendlyname,serialnumber,size | sort -Property deviceid
(or disk number in diskpart):





It isn't necessarily a 1:1 match - for me DR36 is physical drive 3 (a USB)

 

The device, \Device\Harddisk1\DR1, has a bad block

I was copying a large file from my main system disc (which I just successfully extracted from a .rar file moments earlier) to a USB thumb drive today using Fastcopy, and it popped up a CRC read error during the copy phase, before it was even half-way through. I tried twice more and both times the same thing happened at 11% complete. I checked the event viewer and it logged:

The device, \Device\Harddisk1\DR1, has a bad block.

I'm assuming it means my main HDD which I was copying from, and not the USB thumb drive I was copying to? Event viewer doesn't actually specify what drive DR1 is.

I ran the short test in WD data lifeguard diagnostics and it said "pass". I noticed in the S.M.A.R.T. it lists:

- reallocated sector count - 1
- reallocated sector event count - 0

Hard Disk Sentinel says the status is perfect, and after the short test, reports:

- reallocated sectors count - 0
- reallocation event count - 0

Not sure what to think about that. CrystalDiskInfo also reports 0 reallocated sectors.

As far as the file, I'm not worried because it was just a temp copy, but I thought the drive automatically re-allocates bad sectors during copying? If so, then why did the file extracted from the rar end up on a bad sector? Shouldn't the drive have spotted the bad sector during extraction and re-allocated it?

Should I run chkdsk /r to check for bad sectors? I hate to do that on my 1TB partition because it will take hours. Should I run the full test with WD data lifeguard diagnostics instead of chkdsk?

Now I'm wondering if I should continue to trust this drive? It's only 2 years old.