[RESOLVED] USB hard drive crashes the computer

Hi,

A couple of questions if i may?

1. Are the USB connections and functions, affected by the 64 bit part of my system?

2. And are there any 64 bit drivers for the USB devices?

Because i have just tried the hard drive on my wife's Vista 32 bit laptop, and the Safely Remove Device works correctly.
And i have just found this Hitachi Compatability Document, and i suspect that the drive is not compatable with either my system, or Vista 64 bit.

http://www.hitachigst.com/tech/techlib.nsf/techdocs/CEA0F8491B9295F1862570E400716E05/$file/7K500_com.pdf

Thanks.

Gary

Hi,

I have also found this problem after i have tried to remove the drive safely, and i get the grey screen about it cannot be stopped.

https://discussions.virtualdr.com/im...2010/04/12.jpg

I have also tried the suggestions from the Acronis forum here.

http://forum.acronis.com/forum/9881

Gary

Quote:

---

Originally Posted by Johkaz

1. Are the USB connections and functions, affected by the 64 bit part of my system?

2. And are there any 64 bit drivers for the USB devices?

---

1) There is no "64 bit part of the system", in the sense of there being separate x64 and x86 parts. It is all 64-bit, but with a 32-bit subsystem to allow 32-bit apps to run.

2) The 64-bit USB drivers will be installed as part of Windows, they cannot be upgraded independently.

Try running the System File Checker. Go to Start and type "cmd" without the quotes, then right-click cmd.exe and choose "Run as Administrator". Once at the Command Prompt, type "sfc /scannow" without the quotes. You may need your Vista disc, though most of the time you don't.

As a research tool, you might run USBDeview to see what the PC says may be going on. It gives lots of info and also has disconnect capability (I believe it may be the same one on Windows though.) If you use it to disconnect, try refreshing the screen after your attempted disconnection to see what USBDeview says about the drive then.

USBDeview can also delete a drive's entry from Windows. This means that if the USB driver for your external drive is corrupted, and you delete the entry using USBDeview, it would be rebuilt the next time the drive is connected.

http://www.nirsoft.net/utils/usb_devices_view.html

Hi,

Many thanks to all for bearing with me on this problem.

And i have as you suggested downloaded and run the USBDview program, but the results that i have saved as a text file, are too big to be able to be posted here. So i have posted the results of the two tests on the webpage below.

One test is after i have rebooted the computer and then ran the USBDview program, before i have attempted a Safely Remove Device command.

The second set of results are after i have run the Safely Remove Device command, which also gave me a grey screen about how the 'Generic Device cannot be stopped'.

http://johkaz.byethost16.com/USBDview.html

I hope this can help?

And for information purposes, the external drive is configured in Windows as L:\, S:\ and T:\ drives.

Also from the results would anyone be able to tell me, which is the entry for the external drive? So that i can try to delete the entry to see if it can be rebuilt.

Thanks.

Gary

Hi,

Edit:

If it will be easier for us all, if you require any information about my computer settings, if you can tell me what screen to show i will try to take a screenshot of it and post it here.

SuperSparks:

I have run the SFC /scannow command as you have asked and i have got the results back from it, but again the size of the text makes it impossible for me to post it here.

https://discussions.virtualdr.com/im...2010/04/11.jpg

But i did find the following at the bottom of the results, about some files that it could not repair.

POQ 119 ends.
2010-04-11 22:47:15, Info CSI 000002db [SR] Verify complete
2010-04-11 22:47:15, Info CSI 000002dc [SR] Repairing 1 components
2010-04-11 22:47:15, Info CSI 000002dd [SR] Beginning Verify and Repair transaction
2010-04-11 22:47:15, Info CSI 000002de Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..lprinting.resources_31bf3856ad364e35_6.0.6000.16386_en-us_c9d4245a2a075d13\usbmon.dll.mui do not match actual file [l:28{14}]"usbmon.dll.mui" :
Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:7CpWIOLBpJOR0fQrwvWkduOi31kX1E9D2t3wS+GA0Wo=}
2010-04-11 22:47:15, Info CSI 000002df [SR] Cannot repair member file [l:28{14}]"usbmon.dll.mui" of Microsoft-Windows-Printing-LocalPrinting.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-04-11 22:47:15, Info CSI 000002e0 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..lprinting.resources_31bf3856ad364e35_6.0.6000.16386_en-us_c9d4245a2a075d13\usbmon.dll.mui do not match actual file [l:28{14}]"usbmon.dll.mui" :
Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:7CpWIOLBpJOR0fQrwvWkduOi31kX1E9D2t3wS+GA0Wo=}
2010-04-11 22:47:15, Info CSI 000002e1 [SR] Cannot repair member file [l:28{14}]"usbmon.dll.mui" of Microsoft-Windows-Printing-LocalPrinting.Resources, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2010-04-11 22:47:15, Info CSI 000002e2 [SR] This component was referenced by [l:266{133}]"Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.0.6000.16386.Windows Foundation Language Pack"
2010-04-11 22:47:15, Info CSI 000002e3 Hashes for file member \??\C:\Windows\System32\en-US\usbmon.dll.mui do not match actual file [l:28{14}]"usbmon.dll.mui" :
Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:7CpWIOLBpJOR0fQrwvWkduOi31kX1E9D2t3wS+GA0Wo=}
2010-04-11 22:47:15, Info CSI 000002e4 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-p..lprinting.resources_31bf3856ad364e35_6.0.6000.16386_en-us_c9d4245a2a075d13\usbmon.dll.mui do not match actual file [l:28{14}]"usbmon.dll.mui" :
Found: {l:32 b:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=} Expected: {l:32 b:7CpWIOLBpJOR0fQrwvWkduOi31kX1E9D2t3wS+GA0Wo=}
2010-04-11 22:47:15, Info CSI 000002e5 [SR] Could not reproject corrupted file [ml:520{260},l:58{29}]"\??\C:\Windows\System32\en-US"\[l:28{14}]"usbmon.dll.mui"; source file in store is also corrupted
2010-04-11 22:47:15, Info CSI 000002e6 Repair results created:
POQ 120 starts:

POQ 120 ends.
2010-04-11 22:47:15, Info CSI 000002e7 [SR] Repair complete
2010-04-11 22:47:15, Info CSI 000002e8 [SR] Committing transaction
2010-04-11 22:47:15, Info CSI 000002e9 Creating NT transaction (seq 1), objectname [6]"(null)"
2010-04-11 22:47:15, Info CSI 000002ea Created NT transaction (seq 1) result 0x00000000, handle @0xa18
2010-04-11 22:47:15, Info CSI 000002eb@2010/4/11:21:47:15.525 CSI perf trace:
CSIPERF:TXCOMMIT;3
2010-04-11 22:47:15, Info CSI 000002ec [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
2010-04-11 22:54:13, Info CBS Scavenge: Package store indicates there is no component to scavenge, skipping.

You've obviously got some corrupted Windows files :( If this were my system, I would bite the bullet and do a reinstall of Windows at this stage, simply because it's quicker an easier than trying to track down and repair all the problems. If you feel that you really don't want to do that, Windows can probably be repaired, though it may take some time. Do you have a proper Windows 7 DVD?

Hi,

I have been thinking about doing a clean install of my system to be honest, as i am sure that it cure a lot of the problems. The only trouble is, this computer was made and assembled by someone for me. And when i got it here it was ready for use, so i am unsure about how i can clear the C:\ drive and re-install the Windows Vista Home Premium 64 bit system again.

I do have a Vista Windows disk, but i have been told that it is a lot harder to do than with XP.

Gary

Then you have been misinformed, it is in fact vastly easier to install Win 7 than it was with XP :)

It's best to download the drivers first, though Win7 will probably install the vast majority of what you need. Indeed with some installs, I haven't had to install any at all :) I generally write them to a USB stick so that I have everything to hand in one place.

Then just boot up with the DVD in the drive, and once Setup has loaded and you've chosen the language, chose "Custom install". Once it comes to the list of hard drives, select the existing Windows volume, and click "Format". Then just click through the rest of the Wizard, sit back and watch it do it's thing. It generally takes around 20 minutes :) Here are a couple of good articles:

How to install Windows 7

Install Windows 7 the right way

If a fresh installation is on the table, then that's the way to go! And Nick, he is mentioning Vista, not Win 7... :) (Don't know if that would make much of a difference?)

Hi,

Many thanks for the reply.
But i am afraid that i am a bit confused, as you talk about Windows 7.
But i only have Vista Home Premium 64 as an operating system.

Thanks.

Gary

Oops, I got mixed up with another thread, sorry about that :o

But it doesn't make the slightest difference, Setup is identical in Vista and Win 7 :) Here are some Vista specific articles:

Windows Vista Install

How to install Windows Vista

Hi,

Many thanks for the pointers to the helpsites, and i have found one that looks like it is idiot proof...

(Even i should be able to use it)

http://vistahomepremium.windowsreins...ista/index.htm

Which i have copied to Word and printed out as well.

I am just downloading the driver updates for the computer, and i am hoping to give this a try later on.

Best regards.

Gary

One very small point that may be worth mentioning - I generally don't enter a Product Key when asked. If you don't Windows will install quite normally and you get a 30-day trial period. That way you can get everything working properly before you need to activate, and you can hose everything and start over if necessary. Then just enter the key when you are happy and it is time to activate.

Hi,

Many thanks for mentioning about the Product Key, as that could come in handy in case i foobar the install.

Thanks.

Gary