Recently Microsoft Support had me "upgrade" or rather replace the installation of Windows because I had an SFC error that could not be resolved any other way, apparently.
SFC now runs without reporting any errors.
All "new" external drives to my system cause a BSOD when adding of changing a drive letter.
I have 3 external drives.
disk 1: 1TB is an hard drive previously used on the system with Windows prior to the recent upgrade and is still recognised and is in use without issue.
disk 2: 1GB is a flash disk previously used on the system with Windows prior to the recent upgrade, but now requires drivers to be installed. After drivers are installed automatically, the system BSODs.
disk 3: 2TB is a new drive which also behaves in the same way as disk 2 causing a BSOD.
All of the drives can be seen and used connected to the same system when running Linux.
This means there is an issue with the new installation of Windows.
Things I have tried:
With disk 3, Disk Management enumerates the drive and allows me to use the New Simple Volume Wizard. I use the following settings:
- Volume Size: Defaults to "1907727MB"
- Assign Following Drive Letter: set to "do not assign drive letter path"
- Format this volume: defaults to NTFS
- Allocation Size: "Default"
- Volume Label: defaults to "New Volume"
- Perform Quick Format: default Checked.
- Enable File and Folder compression: default Unchecked.
The Wizard starts the job, an egg timer sits there for a while, no other information is displayed, I would have hoped for "formatting" to pop up with the drive listing.
When complete the wizard comes up with the following error:
"The operation failed to complete because the Disk Management view is
Restarting the system does not change the situation and I am unable to add or change the drive letter.
Disk Management (specify drive letter)
If in Windows Disk Management I follow the same proceedure above but during the wizard I assign a drive letter ("X:"), the wizard does not show an egg timer, but instead says "formatting", which looks more usual.
But then, when the wizard completes, I momentarily see "Healthy, Primary Disk" and then I get a BSOD and memory dump.
On reboot of Windows the same BSOD occurs after loading the desktop.
automount disableto allow the drive to be visible but not mounted
select disk 3
cleanthe partition table
create partition primary
format fs=ntfs quick
- (Device Manager) uninstall the drivers for the disk.
- Back in diskpart
I see the drivers being automatically installed and momentarily see the autorun box pop up with the drive letter and then BSOD again.
I have seen reports of people finding Unknown Device in the Device Manager. I too have found this and uninstalled the Unknown Device, and also uninstalled the known device, disconnected and reconnected the device to see the drivers automatically install and a BSOD result.
Disk 3 behaves in this way whether connected by eSATA or USB interface.
Windows Updates are up to date, and the system BIOS is up to date.
Windows 7 Pro 64-bit SP1 – Dell M4400 – Nvidia FX770
Found the BSOD
A problem has been detected and Windows has been shut down to prevent
damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
If this is the first time you've seen this stop error screen, restart
your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software
manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup Options, and then
select Safe Mode.
*** STOP: 0x0000003b (0x00000000c0000005, 0xfffff80002aa8157,
*** ntoskrnl.exe – Address 0xfffff80002ad7c40 base at
0xfffff80002a5b000 DateStamp 0x4e02aaa3