Hello,

I need to work and Windows Vista always crashes randomly when I use my
external USB Hard Drive. I have tried the drive in the same computer with
Windows XP and it does not happen. I have also tried it in other computers
and there were no problems. Is there any fix for this USB bug?

I also contacted PHILIPS regarding this and they told me that it's an
operating system fault.

Any help or reference will be greatly appreciated.

Details follow:

Blue Screen Of Death with BUGCODE_USB_DRIVER when using external USB PHILIPS
Hard Drive.

This problem is always reproducible.



Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1032

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 81C6A672
BCP3: 98FCFB2C
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1



Files that help describe the problem:
C:\Windows\Minidump\Mini061007-01.dmp



C:\Users\Deathwing00\AppData\Local\Temp\WERB73D.tmp.version.txt

Windows NT Version 6.0 Build: 6000
Product (0x6): Windows Vista (TM) Business
Edition: Business
BuildString: 6000.16386.x86fre.vista_rtm.061101-2205
Flavor: Multiprocessor Free
Architecture: X86
LCID: 1033


Read our privacy statement:
http://go.microsoft.com/fwlink/?link...3&clcid=0x0409



------------------
System Information
------------------
Time of this report: 6/10/2007, 22:51:14
Machine name: RO
Operating System: Windows Vistaâ„¢ Business (6.0, Build 6000)
(6000.vista_rtm.061101-2205)
Language: Greek (Regional Setting: Greek)
System Manufacturer: Micro-Star International
System Model: MS-1633X
BIOS: Ver 1.000
Processor: AMD Turion(tm) 64 X2 Mobile Technology TL-52 (2 CPUs),
~1.6GHz
Memory: 1022MB RAM
Page File: 871MB used, 1424MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 10
DX Setup Parameters: Not found
DxDiag Version: 6.00.6000.16386 32bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: NVIDIA GeForce Go 7600
Manufacturer: NVIDIA
Chip type: GeForce Go 7600
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0398&SUBSYS_3FCC1462&REV_A1
Display Memory: 376 MB
Dedicated Memory: 120 MB
Shared Memory: 255 MB
Current Mode: 1280 x 800 (32 bit) (60Hz)
Monitor: Generic PnP Monitor
Driver Name: nvd3dum.dll,nvwgf2um.dll
Driver Version: 7.15.0011.5824 (English)
DDI Version: 9Ex
Driver Attributes: Final Retail
Driver Date/Size: 4/26/2007 16:17:00, 4669440 bytes
WHQL Logo'd: Yes
WHQL Date Stamp:
Device Identifier: {D7B71E3E-40D8-11CF-1261-C71F01C2CA35}
Vendor ID: 0x10DE
Device ID: 0x0398
SubSys ID: 0x3FCC1462
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_B ModeWMV9_B ModeVC1_A
ModeWMV9_A
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)

Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)

Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)

Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)

Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0)

Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0)

Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0)

Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0)

Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}:
Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
{B338D50D-A64A-4790-AC01-475B64252A78}:
Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=

(0,0,0) Caps=
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled

-------------
Sound Devices
-------------
Description: Speakers (Realtek High Definition Audio)
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID:
HDAUDIO\FUNC_01&VEN_10EC&DEV_0883&SUBSYS_14623FCC&REV_1000
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: RTKVHDA.sys
Driver Version: 6.00.0001.5413 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 5/10/2007 18:25:12, 1775712 bytes
Other Files:
Driver Provider: Realtek Semiconductor Corp.
HW Accel Level: Basic
Cap Flags: 0xF1F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 1, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No

---------------------
Sound Capture Devices
---------------------
Description: Microphone (Realtek High Definition Audio)
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: RTKVHDA.sys
Driver Version: 6.00.0001.5413 (English)
Driver Attributes: Final Retail
Date and Size: 5/10/2007 18:25:12, 1775712 bytes
Cap Flags: 0x1
Format Flags: 0xFFFFF

-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a

Poll w/ Interrupt: No

-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x10DE, 0x026D
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 11/2/2006 10:55:21, 191488 bytes
| Driver: usbd.sys, 11/2/2006 10:55:00, 5888 bytes
|
+-+ USB Human Interface Device
| | Vendor/Product ID: 0x046D, 0xC019
| | Location: Port_#0003.Hub_#0001
| | Matching Device ID: usb\class_03&subclass_01
| | Service: HidUsb
| | Driver: hidusb.sys, 11/2/2006 10:55:01, 12288 bytes
| | Driver: hidclass.sys, 11/2/2006 10:55:01, 38912 bytes
| | Driver: hidparse.sys, 11/2/2006 10:55:00, 25472 bytes
| |
| +-+ HID-compliant mouse
| | | Vendor/Product ID: 0x046D, 0xC019
| | | Matching Device ID: hid_device_system_mouse
| | | Service: mouhid
| | | Driver: mouhid.sys, 11/2/2006 10:51:12, 15872 bytes
| | | Driver: mouclass.sys, 11/2/2006 11:49:54, 31848 bytes

----------------
Gameport Devices
----------------

------------
PS/2 Devices
------------
+ Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 11/2/2006 10:51:13, 54784 bytes
| Driver: kbdclass.sys, 11/2/2006 11:49:57, 32872 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: i8042prt.sys, 11/2/2006 10:51:13, 54784 bytes
| Driver: kbdclass.sys, 11/2/2006 11:49:57, 32872 bytes
|
+ Microsoft PS/2 Mouse
| Matching Device ID: *pnp0f03
| Service: i8042prt
| Driver: i8042prt.sys, 11/2/2006 10:51:13, 54784 bytes
| Driver: mouclass.sys, 11/2/2006 11:49:54, 31848 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 11/2/2006 11:50:28, 50792 bytes
| Driver: sermouse.sys, 11/2/2006 10:51:11, 19968 bytes
| Driver: mouclass.sys, 11/2/2006 11:49:54, 31848 bytes

------------------------
Disk & DVD/CD-ROM Drives
------------------------
Drive: C:
Free Space: 15.7 GB
Total Space: 42.8 GB
File System: NTFS
Model: n/a

Drive: D:
Free Space: 15.9 GB
Total Space: 43.0 GB
File System: NTFS
Model: n/a

Drive: G:
Free Space: 73.5 GB
Total Space: 100.0 GB
File System: NTFS
Model: SAMSUNG HM120JI SCSI Disk Device

Drive: I:
Free Space: 9.5 GB
Total Space: 9.5 GB
File System: FAT32
Model: SAMSUNG HM120JI SCSI Disk Device

Drive: E:
Model: HL-DT-ST DVDRAM GMA-4082N ATA Device
Driver: c:\windows\system32\drivers\cdrom.sys, 6.00.6000.16386 (Greek),
11/2/2006 10:51:44, 67072 bytes

--------------
System Devices
--------------
Name: 802.11g MiniPCI Wireless Network Adapter
Device ID: PCI\VEN_1814&DEV_0201&SUBSYS_68331462&REV_01\4&5505873&0&4880
Driver: C:\Windows\system32\DRIVERS\RT2500.sys, 3.02.0000.0000 (English),
6/2/2006 05:37:58, 236800 bytes

Name: O2Micro OZ711MP1/MS1 MemoryCardBus Controller
Device ID: PCI\VEN_1217&DEV_7134&SUBSYS_3FCC1462&REV_21\4&5505873&0&2080
Driver: C:\Windows\system32\DRIVERS\pcmcia.sys, 6.00.6000.16386
(English), 11/2/2006 11:51:12, 167528 bytes

Name: O2Micro Integrated MS/MSPRO Controller
Device ID: PCI\VEN_1217&DEV_7130&SUBSYS_3FCC1462&REV_01\4&5505873&0&2380
Driver: C:\Windows\system32\DRIVERS\o2media.sys, 1.01.0001.0001
(English), 4/3/2007 10:04:28, 39680 bytes

Name: O2Micro Integrated MMC/SD controller
Device ID: PCI\VEN_1217&DEV_7120&SUBSYS_3FCC1462&REV_01\4&5505873&0&2280
Driver: C:\Windows\system32\DRIVERS\o2sd.sys, 1.00.0002.0008 (English),
4/2/2007 16:11:08, 35712 bytes

Name: OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_1217&DEV_00F7&SUBSYS_00F71217&REV_02\4&5505873&0&2480
Driver: C:\Windows\system32\DRIVERS\ohci1394.sys, 6.00.6000.16386
(English), 11/2/2006 10:55:16, 62080 bytes
Driver: C:\Windows\system32\DRIVERS\1394bus.sys, 6.00.6000.16386
(English), 11/2/2006 10:55:12, 53376 bytes

Name: Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)
Device ID: PCI\VEN_10EC&DEV_8168&SUBSYS_3FCC1462&REV_01\4&3462B538&0&0010
Driver: C:\Windows\system32\DRIVERS\Rtlh86.sys, 6.190.0115.2007
(English), 1/15/2007 14:28:20, 70144 bytes

Name: NVIDIA GeForce Go 7600
Device ID: PCI\VEN_10DE&DEV_0398&SUBSYS_3FCC1462&REV_A1\4&1BC86A40&0&0020
Driver: C:\Windows\system32\DRIVERS\nvlddmkm.sys, 7.15.0011.5824
(English), 4/26/2007 16:17:00, 7475072 bytes
Driver: C:\Windows\system32\nvd3dum.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 4669440 bytes
Driver: C:\Windows\system32\nvwgf2um.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 1424384 bytes
Driver: C:\Windows\system32\nvapi.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 352256 bytes
Driver: C:\Windows\system32\nvoglv32.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 6852608 bytes
Driver: C:\Windows\system32\nvcpl.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 8429568 bytes
Driver: C:\Windows\system32\nvsvc.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 86016 bytes
Driver: C:\Windows\system32\nvmctray.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 81920 bytes
Driver: C:\Windows\system32\nvdisps.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 6221824 bytes
Driver: C:\Windows\system32\nvgames.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 3289088 bytes
Driver: C:\Windows\system32\nvmccss.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 188416 bytes
Driver: C:\Windows\system32\nvmobls.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 1101824 bytes
Driver: C:\Windows\system32\nvvitvs.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 3538944 bytes
Driver: C:\Windows\system32\nvmccs.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 229376 bytes
Driver: C:\Windows\system32\nvmccsrs.dll, 7.15.0011.5824 (Greek),
4/26/2007 16:17:00, 45056 bytes
Driver: C:\Windows\system32\nvwss.dll, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 2273280 bytes
Driver: C:\Windows\system32\nvcolor.exe, 7.15.0011.5824 (English),
4/26/2007 16:17:00, 143360 bytes
Driver: C:\Windows\system32\nvudisp.exe, 1.00.0001.0056 (English),
4/26/2007 16:17:00, 356352 bytes
Driver: C:\Windows\system32\nvapps.xml, 4/26/2007 16:17:00, 114915 bytes
Driver: C:\Windows\system32\nvwsapps.xml, 4/26/2007 16:17:00, 81125 bytes
Driver: C:\Windows\system32\nvuninst.exe, 1.00.0001.0056 (English),
4/26/2007 16:17:00, 356352 bytes
Driver: C:\Windows\system32\nvdisp.nvu, 4/26/2007 16:17:00, 5674 bytes
Driver: C:\Windows\system32\dpinst.exe, 2.00.0001.0000 (English),
4/12/2007 17:07:00, 521128 bytes
Driver: C:\Windows\help\nvcpl\nvdsp.chm, 4/26/2007 16:17:00, 170201 bytes
Driver: C:\Windows\help\nvcpl\nv3d.chm, 4/26/2007 16:17:00, 91094 bytes
Driver: C:\Windows\help\nvcpl\nvmob.chm, 4/26/2007 16:17:00, 54988 bytes
Driver: C:\Windows\help\nvcpl\nvwks.chm, 4/26/2007 16:17:00, 174650 bytes
Driver: C:\Windows\nvtmpinst\nvcpl.cpl, , 0 bytes
Driver: C:\Windows\nvtmpinst\nvcplui.exe, , 0 bytes
Driver: C:\Windows\nvtmpinst\nvexpbar.dll, , 0 bytes
Driver: C:\Windows\nvtmpinst\nvcpl.chm, , 0 bytes
Driver: C:\Windows\system32\nvcod.dll, 1.00.0000.0035 (English),
4/26/2007 16:17:00, 37888 bytes
Driver: C:\Windows\system32\nvcodins.dll, 1.00.0000.0035 (English),
4/26/2007 16:17:00, 37888 bytes

Name: nForce Memory Controller
Device ID: PCI\VEN_10DE&DEV_02FF&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&05
Driver: n/a

Name: nForce Memory Controller
Device ID: PCI\VEN_10DE&DEV_02FE&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&02
Driver: n/a

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_10DE&DEV_02FD&SUBSYS_000010DE&REV_A1\3&267A616A&0&18
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6000.16386 (English),
11/2/2006 11:50:57, 140392 bytes

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_10DE&DEV_02FC&SUBSYS_000010DE&REV_A1\3&267A616A&0&10
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6000.16386 (English),
11/2/2006 11:50:57, 140392 bytes

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_10DE&DEV_02FB&SUBSYS_000010DE&REV_A1\3&267A616A&0&20
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6000.16386 (English),
11/2/2006 11:50:57, 140392 bytes

Name: nForce Memory Controller
Device ID: PCI\VEN_10DE&DEV_02F9&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&04
Driver: n/a

Name: nForce Memory Controller
Device ID: PCI\VEN_10DE&DEV_02F8&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&03
Driver: n/a

Name: PCI standard RAM Controller
Device ID: PCI\VEN_10DE&DEV_02F7&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&00
Driver: n/a

Name: nForce Memory Controller
Device ID: PCI\VEN_10DE&DEV_027F&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&06
Driver: n/a

Name: nForce Memory Controller
Device ID: PCI\VEN_10DE&DEV_027E&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&07
Driver: n/a

Name: NVIDIA nForce System Management Controller
Device ID: PCI\VEN_10DE&DEV_0271&SUBSYS_3FCC1462&REV_A3\3&267A616A&0&53
Driver: C:\Windows\system32\DRIVERS\nvsmu.sys, 5.00.0000.0000 (English),
11/14/2006 10:04:48, 11648 bytes

Name: nForce Memory Controller
Device ID: PCI\VEN_10DE&DEV_0270&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&48
Driver: n/a

Name: PCI standard PCI-to-PCI bridge
Device ID: PCI\VEN_10DE&DEV_026F&SUBSYS_CB8410DE&REV_A2\3&267A616A&0&80
Driver: C:\Windows\system32\DRIVERS\pci.sys, 6.00.6000.16386 (English),
11/2/2006 11:50:57, 140392 bytes

Name: Standard Enhanced PCI to USB Host Controller
Device ID: PCI\VEN_10DE&DEV_026E&SUBSYS_3FCC1462&REV_A3\3&267A616A&0&59
Driver: C:\Windows\system32\drivers\usbehci.sys, 6.00.6000.16386
(English), 11/2/2006 10:55:04, 38400 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6000.16386
(English), 11/2/2006 10:55:11, 223744 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6000.16386
(English), 11/2/2006 10:55:21, 191488 bytes
Driver: C:\Windows\system32\hccoin.dll, 6.00.6000.16386 (English),
11/2/2006 11:46:05, 8704 bytes

Name: Standard OpenHCD USB Host Controller
Device ID: PCI\VEN_10DE&DEV_026D&SUBSYS_3FCC1462&REV_A3\3&267A616A&0&58
Driver: C:\Windows\system32\drivers\usbohci.sys, 6.00.6000.16386
(English), 11/2/2006 10:55:05, 19456 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.00.6000.16386
(English), 11/2/2006 10:55:11, 223744 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.00.6000.16386
(English), 11/2/2006 10:55:21, 191488 bytes

Name: High Definition Audio Controller
Device ID: PCI\VEN_10DE&DEV_026C&SUBSYS_3FCC1462&REV_A2\3&267A616A&0&81
Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 6.00.6000.16385
(English), 5/1/2007 14:56:32, 53760 bytes

Name: NVIDIA nForce Serial ATA Controller
Device ID: PCI\VEN_10DE&DEV_0266&SUBSYS_3FCC1462&REV_A1\3&267A616A&0&70
Driver: C:\Windows\system32\DRIVERS\nvstor32.sys, 5.10.2600.0931
(English), 12/22/2006 20:07:10, 93696 bytes
Driver: C:\Windows\system32\nvraidco.dll, 5.10.2600.0931 (English),
12/22/2006 20:12:34, 358912 bytes
Driver: C:\Windows\system32\nvraiins.dll, 5.10.2600.0931 (English),
12/22/2006 20:12:34, 358912 bytes

Name: Standard Dual Channel PCI IDE Controller
Device ID: PCI\VEN_10DE&DEV_0265&SUBSYS_3FCC1462&REV_A1\3&267A616A&0&68
Driver: C:\Windows\system32\DRIVERS\pciide.sys, 6.00.6000.16386
(English), 11/2/2006 11:49:20, 13416 bytes
Driver: C:\Windows\system32\DRIVERS\pciidex.sys, 6.00.6000.16386 (Greek),
11/2/2006 11:50:18, 42600 bytes
Driver: C:\Windows\system32\DRIVERS\atapi.sys, 6.00.6000.16386 (English),
11/2/2006 11:49:36, 19048 bytes
Driver: C:\Windows\system32\DRIVERS\ataport.sys, 6.00.6000.16386 (Greek),
11/2/2006 11:50:41, 107112 bytes

Name: NVIDIA nForce PCI System Management
Device ID: PCI\VEN_10DE&DEV_0264&SUBSYS_3FCC1462&REV_A3\3&267A616A&0&51
Driver: n/a

Name: PCI standard ISA bridge
Device ID: PCI\VEN_10DE&DEV_0260&SUBSYS_3FCC1462&REV_A3\3&267A616A&0&50
Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 6.00.6000.16386
(English), 11/2/2006 11:49:20, 13928 bytes

Name: AMD Miscellaneous Configuration
Device ID: PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&267A616A&0&C3
Driver: n/a

Name: AMD DRAM and HyperTransport(tm) Trace Mode Configuration
Device ID: PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&267A616A&0&C2
Driver: n/a

Name: AMD Address Map Configuration
Device ID: PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&267A616A&0&C1
Driver: n/a

Name: AMD HyperTransport(tm) Configuration
Device ID: PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&267A616A&0&C0
Driver: n/a

Deathwing00,

Anyone troubleshooting this problem should be able to read and interpret
Windows error reports. I don't know whether anyone here can do that, but
time will tell. I searched the Internet on BCCode 1000008e and found the
following explanation (at the link, read down for full explanation):

http://www.pcreview.co.uk/forums/thread-439539.php

Of course, reading all that information does not provide the solution to
your specific issue. It does, however, suggest that the problem is
associated with a driver issue. Which driver is hard to tell without further
troubleshooting, but one has to know how to go about doing troubleshooting.

One can start troubleshooting by trying certain steps to see what happens.
For example, download and install all updates available at the Microsoft
update site, if you haven't already done that. You might get a fix by luck
that way.

In addition, check Device Manager to see whether some indication of a
problem is disclosed there. If there is, you can use the procedures in
Device Manager to updating drivers. That is, Device Manager can search for
updated drivers.

Another approach is to determine whether the external hard drive requires a
driver to function properly. Some external devices need special drivers,
apart from the normal USB port drivers, and some don't. For example, your
hard drive may have an integrated controller requiring a driver, but I have
no knowledge whether it does or not.

These comments are just some things to consider. Others may have additional
information for you.



--
freddy


"Deathwing00" wrote:

> Hello,
>
> I need to work and Windows Vista always crashes randomly when I use my
> external USB Hard Drive. I have tried the drive in the same computer with
> Windows XP and it does not happen. I have also tried it in other computers
> and there were no problems. Is there any fix for this USB bug?
>
> I also contacted PHILIPS regarding this and they told me that it's an
> operating system fault.
>
> Any help or reference will be greatly appreciated.
>
> Details follow:
>
> Blue Screen Of Death with BUGCODE_USB_DRIVER when using external USB PHILIPS
> Hard Drive.
>
> This problem is always reproducible.
>
>
>
> Problem signature:
> Problem Event Name: BlueScreen
> OS Version: 6.0.6000.2.0.0.256.6
> Locale ID: 1032
>
> Additional information about the problem:
> BCCode: 1000008e
> BCP1: C0000005
> BCP2: 81C6A672
> BCP3: 98FCFB2C
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 256_1
>
> Files that help describe the problem:
> C:\Windows\Minidump\Mini061007-01.dmp
>
>
>
> C:\Users\Deathwing00\AppData\Local\Temp\WERB73D.tmp.version.txt
>
> Windows NT Version 6.0 Build: 6000
> Product (0x6): Windows Vista (TM) Business
> Edition: Business
> BuildString: 6000.16386.x86fre.vista_rtm.061101-2205
> Flavor: Multiprocessor Free
> Architecture: X86
> LCID: 1033
>
>
> Read our privacy statement:
> http://go.microsoft.com/fwlink/?link...3&clcid=0x0409
>
>
>
> ------------------
> System Information
> ------------------
> Time of this report: 6/10/2007, 22:51:14
> Machine name: RO
> Operating System: Windows Vistaâ„¢ Business (6.0, Build 6000)
> (6000.vista_rtm.061101-2205)
> Language: Greek (Regional Setting: Greek)
> System Manufacturer: Micro-Star International
> System Model: MS-1633X
> BIOS: Ver 1.000
> Processor: AMD Turion(tm) 64 X2 Mobile Technology TL-52 (2 CPUs),
> ~1.6GHz
> Memory: 1022MB RAM
> Page File: 871MB used, 1424MB available
> Windows Dir: C:\Windows
> DirectX Version: DirectX 10
> DX Setup Parameters: Not found
> DxDiag Version: 6.00.6000.16386 32bit Unicode
>
> ------------
> DxDiag Notes
> ------------
> Display Tab 1: No problems found.
> Sound Tab 1: No problems found.
> Input Tab: No problems found.
>
> --------------------
> DirectX Debug Levels
> --------------------
> Direct3D: 0/4 (retail)
> DirectDraw: 0/4 (retail)
> DirectInput: 0/5 (retail)
> DirectMusic: 0/5 (retail)
> DirectPlay: 0/9 (retail)
> DirectSound: 0/5 (retail)
> DirectShow: 0/6 (retail)
>
> ---------------
> Display Devices
> ---------------
> Card name: NVIDIA GeForce Go 7600
> Manufacturer: NVIDIA
> Chip type: GeForce Go 7600
> DAC type: Integrated RAMDAC
> Device Key: Enum\PCI\VEN_10DE&DEV_0398&SUBSYS_3FCC1462&REV_A1
> Display Memory: 376 MB
> Dedicated Memory: 120 MB
> Shared Memory: 255 MB
> Current Mode: 1280 x 800 (32 bit) (60Hz)
> Monitor: Generic PnP Monitor
> Driver Name: nvd3dum.dll,nvwgf2um.dll
> Driver Version: 7.15.0011.5824 (English)
> DDI Version: 9Ex
> Driver Attributes: Final Retail
> Driver Date/Size: 4/26/2007 16:17:00, 4669440 bytes
> WHQL Logo'd: Yes
> WHQL Date Stamp:
> Device Identifier: {D7B71E3E-40D8-11CF-1261-C71F01C2CA35}
> Vendor ID: 0x10DE
> Device ID: 0x0398
> SubSys ID: 0x3FCC1462
> Revision ID: 0x00A1
> Revision ID: 0x00A1
> Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_B ModeWMV9_B ModeVC1_A
> ModeWMV9_A
> Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)
>
> Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> DeinterlaceTech_PixelAdaptive
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)
>
> Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> DeinterlaceTech_BOBVerticalStretch
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)
>
> Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0)
>
> Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> DeinterlaceTech_BOBVerticalStretch
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0)
>
> Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> DeinterlaceTech_PixelAdaptive
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0)
>
> Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> DeinterlaceTech_BOBVerticalStretch
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0)
>
> Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0)
>
> Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> DeinterlaceTech_BOBVerticalStretch
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
> VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
> VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
> VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
> VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
> VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX
> VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {6CB69578-7617-4637-91E5-1C02DB810285}:
> Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {335AA36E-7884-43A4-9C91-7F87FAF3E37E}:
> Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}:
> Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> {B338D50D-A64A-4790-AC01-475B64252A78}:
> Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=
>
> (0,0,0) Caps=
> DDraw Status: Enabled
> D3D Status: Enabled
> AGP Status: Enabled
>
> -------------

Thanks a lot for your quick reply.

"freddy" wrote:

> Deathwing00,
>
> Anyone troubleshooting this problem should be able to read and interpret
> Windows error reports. I don't know whether anyone here can do that, but
> time will tell. I searched the Internet on BCCode 1000008e and found the
> following explanation (at the link, read down for full explanation):
>
> http://www.pcreview.co.uk/forums/thread-439539.php
>
> Of course, reading all that information does not provide the solution to
> your specific issue. It does, however, suggest that the problem is
> associated with a driver issue. Which driver is hard to tell without further
> troubleshooting, but one has to know how to go about doing troubleshooting.
>
> One can start troubleshooting by trying certain steps to see what happens.
> For example, download and install all updates available at the Microsoft
> update site, if you haven't already done that. You might get a fix by luck
> that way.

Fully up to date.

>
> In addition, check Device Manager to see whether some indication of a
> problem is disclosed there. If there is, you can use the procedures in
> Device Manager to updating drivers. That is, Device Manager can search for
> updated drivers.
>

It says all drivers are up and running fine.

> Another approach is to determine whether the external hard drive requires a
> driver to function properly. Some external devices need special drivers,
> apart from the normal USB port drivers, and some don't. For example, your
> hard drive may have an integrated controller requiring a driver, but I have
> no knowledge whether it does or not.
>

The vendor says there is no need for any driver. In fact, the driver works,
but it always ends up sooner or later with that blue screen. I also checked
nVidia's website for drivers, but there are none.

> These comments are just some things to consider. Others may have additional
> information for you.
>

Thank you. I'll try to post the details of the blue screen later on.

>
>
> --
> freddy
>
>

Deathwing00,

I just recalled a procedure you can use to help troubleshoot your issue.
Proceeding on the premise that a driver is behind your problem, Vista
includes a utility that can identify unsigned drivers. Microsoft asks
vendors to submit their drivers to Microsoft for testing to ensure they work
properly. When the drivers pass this quality check they are called signed
drivers (like signed of on by Microsoft).

Here is how you can identify the unsigned drivers running on your system:
Click on Start and select Run. In the window that opens, type sigverif.exe
and click on OK. The utility will run and list all unsigned drivers it finds.

Not all unsigned drivers will cause problems, but some might. The problem
is in determining whether one of them is the bad one.

Also, your hard drive crashing doesn't necessarily mean that there is
something wrong with the hard drive or with the USB associated drivers. A
problem elsewhere can cause your hard drive to crash, making isolating the
problem a confusing exercise. A problem with NIC drivers, video card
drivers, and any other drivers, can precipitate the issue you are having.

These comments are only intended to help in understanding the issue.
--
freddy


"Deathwing00" wrote:

> Thanks a lot for your quick reply.
>
> "freddy" wrote:
>
> > Deathwing00,
> >
> > Anyone troubleshooting this problem should be able to read and interpret
> > Windows error reports. I don't know whether anyone here can do that, but
> > time will tell. I searched the Internet on BCCode 1000008e and found the
> > following explanation (at the link, read down for full explanation):
> >
> > http://www.pcreview.co.uk/forums/thread-439539.php
> >
> > Of course, reading all that information does not provide the solution to
> > your specific issue. It does, however, suggest that the problem is
> > associated with a driver issue. Which driver is hard to tell without further
> > troubleshooting, but one has to know how to go about doing troubleshooting.
> >
> > One can start troubleshooting by trying certain steps to see what happens.
> > For example, download and install all updates available at the Microsoft
> > update site, if you haven't already done that. You might get a fix by luck
> > that way.
>
> Fully up to date.
>
> >
> > In addition, check Device Manager to see whether some indication of a
> > problem is disclosed there. If there is, you can use the procedures in
> > Device Manager to updating drivers. That is, Device Manager can search for
> > updated drivers.
> >
>
> It says all drivers are up and running fine.
>
> > Another approach is to determine whether the external hard drive requires a
> > driver to function properly. Some external devices need special drivers,
> > apart from the normal USB port drivers, and some don't. For example, your
> > hard drive may have an integrated controller requiring a driver, but I have
> > no knowledge whether it does or not.
> >
>
> The vendor says there is no need for any driver. In fact, the driver works,
> but it always ends up sooner or later with that blue screen. I also checked
> nVidia's website for drivers, but there are none.
>
> > These comments are just some things to consider. Others may have additional
> > information for you.
> >
>
> Thank you. I'll try to post the details of the blue screen later on.
>
> >
> >
> > --
> > freddy
> >
> >
>

Hi again and thanks for your reply.

Well, it's not that the Hard Drive crashes, it works, it's Vista that
BlueScreens. I can confirm you that it is the hard drive the one causing the
blue screen because I isolated the problem. If the hard drive is not
connected, there are no problems at all.

I presume it is either a Windows Vista internal bug (wouldn't be the first
one, there are quite a lot to be fixed already), an nVidia driver problem
(not so strange, nVidia is slacking a lot with Windows Vista) or a BIOS
problem (strange, because on Windows XP SP2 it works fine).

I'll check the signatures and will report back, but I recall that when I
installed the nVidia drivers, Windows did not complain about an unsigned
driver.

Thank you once again.

"freddy" wrote:

> Deathwing00,
>
> I just recalled a procedure you can use to help troubleshoot your issue.
> Proceeding on the premise that a driver is behind your problem, Vista
> includes a utility that can identify unsigned drivers. Microsoft asks
> vendors to submit their drivers to Microsoft for testing to ensure they work
> properly. When the drivers pass this quality check they are called signed
> drivers (like signed of on by Microsoft).
>
> Here is how you can identify the unsigned drivers running on your system:
> Click on Start and select Run. In the window that opens, type sigverif.exe
> and click on OK. The utility will run and list all unsigned drivers it finds.
>
> Not all unsigned drivers will cause problems, but some might. The problem
> is in determining whether one of them is the bad one.
>
> Also, your hard drive crashing doesn't necessarily mean that there is
> something wrong with the hard drive or with the USB associated drivers. A
> problem elsewhere can cause your hard drive to crash, making isolating the
> problem a confusing exercise. A problem with NIC drivers, video card
> drivers, and any other drivers, can precipitate the issue you are having.
>
> These comments are only intended to help in understanding the issue.
> --
> freddy
>
>
> "Deathwing00" wrote:
>
> > Thanks a lot for your quick reply.
> >
> > "freddy" wrote:
> >
> > > Deathwing00,
> > >
> > > Anyone troubleshooting this problem should be able to read and interpret
> > > Windows error reports. I don't know whether anyone here can do that, but
> > > time will tell. I searched the Internet on BCCode 1000008e and found the
> > > following explanation (at the link, read down for full explanation):
> > >
> > > http://www.pcreview.co.uk/forums/thread-439539.php
> > >
> > > Of course, reading all that information does not provide the solution to
> > > your specific issue. It does, however, suggest that the problem is
> > > associated with a driver issue. Which driver is hard to tell without further
> > > troubleshooting, but one has to know how to go about doing troubleshooting.
> > >
> > > One can start troubleshooting by trying certain steps to see what happens.
> > > For example, download and install all updates available at the Microsoft
> > > update site, if you haven't already done that. You might get a fix by luck
> > > that way.
> >
> > Fully up to date.
> >
> > >
> > > In addition, check Device Manager to see whether some indication of a
> > > problem is disclosed there. If there is, you can use the procedures in
> > > Device Manager to updating drivers. That is, Device Manager can search for
> > > updated drivers.
> > >
> >
> > It says all drivers are up and running fine.
> >
> > > Another approach is to determine whether the external hard drive requires a
> > > driver to function properly. Some external devices need special drivers,
> > > apart from the normal USB port drivers, and some don't. For example, your
> > > hard drive may have an integrated controller requiring a driver, but I have
> > > no knowledge whether it does or not.
> > >
> >
> > The vendor says there is no need for any driver. In fact, the driver works,
> > but it always ends up sooner or later with that blue screen. I also checked
> > nVidia's website for drivers, but there are none.
> >
> > > These comments are just some things to consider. Others may have additional
> > > information for you.
> > >
> >
> > Thank you. I'll try to post the details of the blue screen later on.
> >
> > >
> > >
> > > --
> > > freddy
> > >
> > >
> >

Deathwing00,

I have some unsigned drivers on my system, and Windows hasn't complained
about it. So, I don't know under what circumstances you'd get a Windows
complaint. I had an unusual crash not long ago while performing some routine
that had nothing to do with what caused the crash. It turned out the driver
for the Asus motherboard monitor was the bad guy, and I got a crash while not
using the motherboard monitor. You never know.

When I say that the external USB hard drive crashes, I'm not saying that
there is anything wrong with the hard drive. Read my comments carefully and
you'll see that I'm not saying that. I'm just saying you get a crash when
you try using the HD, and that the cause could be elsewhere, so that one
can't conclude that the HD or the drivers associated with the HD are at
fault. This can be complicated stuff.

It's also very speculative in using logic in trying to understand the
problem, because a lot of this stuff isn't subject to layman's logic.
Anyway, post back on what unsigned drivers you find. You may get to the
bottom of this yet.
--
freddy


"Deathwing00" wrote:

> Hi again and thanks for your reply.
>
> Well, it's not that the Hard Drive crashes, it works, it's Vista that
> BlueScreens. I can confirm you that it is the hard drive the one causing the
> blue screen because I isolated the problem. If the hard drive is not
> connected, there are no problems at all.
>
> I presume it is either a Windows Vista internal bug (wouldn't be the first
> one, there are quite a lot to be fixed already), an nVidia driver problem
> (not so strange, nVidia is slacking a lot with Windows Vista) or a BIOS
> problem (strange, because on Windows XP SP2 it works fine).
>
> I'll check the signatures and will report back, but I recall that when I
> installed the nVidia drivers, Windows did not complain about an unsigned
> driver.
>
> Thank you once again.
>
> "freddy" wrote:
>
> > Deathwing00,
> >
> > I just recalled a procedure you can use to help troubleshoot your issue.
> > Proceeding on the premise that a driver is behind your problem, Vista
> > includes a utility that can identify unsigned drivers. Microsoft asks
> > vendors to submit their drivers to Microsoft for testing to ensure they work
> > properly. When the drivers pass this quality check they are called signed
> > drivers (like signed of on by Microsoft).
> >
> > Here is how you can identify the unsigned drivers running on your system:
> > Click on Start and select Run. In the window that opens, type sigverif.exe
> > and click on OK. The utility will run and list all unsigned drivers it finds.
> >
> > Not all unsigned drivers will cause problems, but some might. The problem
> > is in determining whether one of them is the bad one.
> >
> > Also, your hard drive crashing doesn't necessarily mean that there is
> > something wrong with the hard drive or with the USB associated drivers. A
> > problem elsewhere can cause your hard drive to crash, making isolating the
> > problem a confusing exercise. A problem with NIC drivers, video card
> > drivers, and any other drivers, can precipitate the issue you are having.
> >
> > These comments are only intended to help in understanding the issue.
> > --
> > freddy
> >
> >
> > "Deathwing00" wrote:
> >
> > > Thanks a lot for your quick reply.
> > >
> > > "freddy" wrote:
> > >
> > > > Deathwing00,
> > > >
> > > > Anyone troubleshooting this problem should be able to read and interpret
> > > > Windows error reports. I don't know whether anyone here can do that, but
> > > > time will tell. I searched the Internet on BCCode 1000008e and found the
> > > > following explanation (at the link, read down for full explanation):
> > > >
> > > > http://www.pcreview.co.uk/forums/thread-439539.php
> > > >
> > > > Of course, reading all that information does not provide the solution to
> > > > your specific issue. It does, however, suggest that the problem is
> > > > associated with a driver issue. Which driver is hard to tell without further
> > > > troubleshooting, but one has to know how to go about doing troubleshooting.
> > > >
> > > > One can start troubleshooting by trying certain steps to see what happens.
> > > > For example, download and install all updates available at the Microsoft
> > > > update site, if you haven't already done that. You might get a fix by luck
> > > > that way.
> > >
> > > Fully up to date.
> > >
> > > >
> > > > In addition, check Device Manager to see whether some indication of a
> > > > problem is disclosed there. If there is, you can use the procedures in
> > > > Device Manager to updating drivers. That is, Device Manager can search for
> > > > updated drivers.
> > > >
> > >
> > > It says all drivers are up and running fine.
> > >
> > > > Another approach is to determine whether the external hard drive requires a
> > > > driver to function properly. Some external devices need special drivers,
> > > > apart from the normal USB port drivers, and some don't. For example, your
> > > > hard drive may have an integrated controller requiring a driver, but I have
> > > > no knowledge whether it does or not.
> > > >
> > >
> > > The vendor says there is no need for any driver. In fact, the driver works,
> > > but it always ends up sooner or later with that blue screen. I also checked
> > > nVidia's website for drivers, but there are none.
> > >
> > > > These comments are just some things to consider. Others may have additional
> > > > information for you.
> > > >
> > >
> > > Thank you. I'll try to post the details of the blue screen later on.
> > >
> > > >
> > > >
> > > > --
> > > > freddy
> > > >
> > > >
> > >

Hey there!!!!

I finally solved the problem. I bought a simple USB hub and used it to
connect the hard drive to it, instead of directly to the laptop. No more
crashes since then.

Cheers!

"freddy" wrote:

> Deathwing00,
>
> I have some unsigned drivers on my system, and Windows hasn't complained
> about it. So, I don't know under what circumstances you'd get a Windows
> complaint. I had an unusual crash not long ago while performing some routine
> that had nothing to do with what caused the crash. It turned out the driver
> for the Asus motherboard monitor was the bad guy, and I got a crash while not
> using the motherboard monitor. You never know.
>
> When I say that the external USB hard drive crashes, I'm not saying that
> there is anything wrong with the hard drive. Read my comments carefully and
> you'll see that I'm not saying that. I'm just saying you get a crash when
> you try using the HD, and that the cause could be elsewhere, so that one
> can't conclude that the HD or the drivers associated with the HD are at
> fault. This can be complicated stuff.
>
> It's also very speculative in using logic in trying to understand the
> problem, because a lot of this stuff isn't subject to layman's logic.
> Anyway, post back on what unsigned drivers you find. You may get to the
> bottom of this yet.
> --
> freddy
>
>
> "Deathwing00" wrote:
>
> > Hi again and thanks for your reply.
> >
> > Well, it's not that the Hard Drive crashes, it works, it's Vista that
> > BlueScreens. I can confirm you that it is the hard drive the one causing the
> > blue screen because I isolated the problem. If the hard drive is not
> > connected, there are no problems at all.
> >
> > I presume it is either a Windows Vista internal bug (wouldn't be the first
> > one, there are quite a lot to be fixed already), an nVidia driver problem
> > (not so strange, nVidia is slacking a lot with Windows Vista) or a BIOS
> > problem (strange, because on Windows XP SP2 it works fine).
> >
> > I'll check the signatures and will report back, but I recall that when I
> > installed the nVidia drivers, Windows did not complain about an unsigned
> > driver.
> >
> > Thank you once again.
> >
> > "freddy" wrote:
> >
> > > Deathwing00,
> > >
> > > I just recalled a procedure you can use to help troubleshoot your issue.
> > > Proceeding on the premise that a driver is behind your problem, Vista
> > > includes a utility that can identify unsigned drivers. Microsoft asks
> > > vendors to submit their drivers to Microsoft for testing to ensure they work
> > > properly. When the drivers pass this quality check they are called signed
> > > drivers (like signed of on by Microsoft).
> > >
> > > Here is how you can identify the unsigned drivers running on your system:
> > > Click on Start and select Run. In the window that opens, type sigverif.exe
> > > and click on OK. The utility will run and list all unsigned drivers it finds.
> > >
> > > Not all unsigned drivers will cause problems, but some might. The problem
> > > is in determining whether one of them is the bad one.
> > >
> > > Also, your hard drive crashing doesn't necessarily mean that there is
> > > something wrong with the hard drive or with the USB associated drivers. A
> > > problem elsewhere can cause your hard drive to crash, making isolating the
> > > problem a confusing exercise. A problem with NIC drivers, video card
> > > drivers, and any other drivers, can precipitate the issue you are having.
> > >
> > > These comments are only intended to help in understanding the issue.
> > > --
> > > freddy
> > >
> > >
> > > "Deathwing00" wrote:
> > >
> > > > Thanks a lot for your quick reply.
> > > >
> > > > "freddy" wrote:
> > > >
> > > > > Deathwing00,
> > > > >
> > > > > Anyone troubleshooting this problem should be able to read and interpret
> > > > > Windows error reports. I don't know whether anyone here can do that, but
> > > > > time will tell. I searched the Internet on BCCode 1000008e and found the
> > > > > following explanation (at the link, read down for full explanation):
> > > > >
> > > > > http://www.pcreview.co.uk/forums/thread-439539.php
> > > > >
> > > > > Of course, reading all that information does not provide the solution to
> > > > > your specific issue. It does, however, suggest that the problem is
> > > > > associated with a driver issue. Which driver is hard to tell without further
> > > > > troubleshooting, but one has to know how to go about doing troubleshooting.
> > > > >
> > > > > One can start troubleshooting by trying certain steps to see what happens.
> > > > > For example, download and install all updates available at the Microsoft
> > > > > update site, if you haven't already done that. You might get a fix by luck
> > > > > that way.
> > > >
> > > > Fully up to date.
> > > >
> > > > >
> > > > > In addition, check Device Manager to see whether some indication of a
> > > > > problem is disclosed there. If there is, you can use the procedures in
> > > > > Device Manager to updating drivers. That is, Device Manager can search for
> > > > > updated drivers.
> > > > >
> > > >
> > > > It says all drivers are up and running fine.
> > > >
> > > > > Another approach is to determine whether the external hard drive requires a
> > > > > driver to function properly. Some external devices need special drivers,
> > > > > apart from the normal USB port drivers, and some don't. For example, your
> > > > > hard drive may have an integrated controller requiring a driver, but I have
> > > > > no knowledge whether it does or not.
> > > > >
> > > >
> > > > The vendor says there is no need for any driver. In fact, the driver works,
> > > > but it always ends up sooner or later with that blue screen. I also checked
> > > > nVidia's website for drivers, but there are none.
> > > >
> > > > > These comments are just some things to consider. Others may have additional
> > > > > information for you.
> > > > >
> > > >
> > > > Thank you. I'll try to post the details of the blue screen later on.
> > > >
> > > > >
> > > > >
> > > > > --
> > > > > freddy
> > > > >
> > > > >
> > > >

Deathwing00,

Like we were saying, you never know. How did you manage to decide to try
that solution? I also wonder why that approach solved the crash problem. Any
ideas?
--
freddy


"Deathwing00" wrote:

> Hey there!!!!
>
> I finally solved the problem. I bought a simple USB hub and used it to
> connect the hard drive to it, instead of directly to the laptop. No more
> crashes since then.
>
> Cheers!
>
> "freddy" wrote:
>
> > Deathwing00,
> >
> > I have some unsigned drivers on my system, and Windows hasn't complained
> > about it. So, I don't know under what circumstances you'd get a Windows
> > complaint. I had an unusual crash not long ago while performing some routine
> > that had nothing to do with what caused the crash. It turned out the driver
> > for the Asus motherboard monitor was the bad guy, and I got a crash while not
> > using the motherboard monitor. You never know.
> >
> > When I say that the external USB hard drive crashes, I'm not saying that
> > there is anything wrong with the hard drive. Read my comments carefully and
> > you'll see that I'm not saying that. I'm just saying you get a crash when
> > you try using the HD, and that the cause could be elsewhere, so that one
> > can't conclude that the HD or the drivers associated with the HD are at
> > fault. This can be complicated stuff.
> >
> > It's also very speculative in using logic in trying to understand the
> > problem, because a lot of this stuff isn't subject to layman's logic.
> > Anyway, post back on what unsigned drivers you find. You may get to the
> > bottom of this yet.
> > --
> > freddy
> >
> >
> > "Deathwing00" wrote:
> >
> > > Hi again and thanks for your reply.
> > >
> > > Well, it's not that the Hard Drive crashes, it works, it's Vista that
> > > BlueScreens. I can confirm you that it is the hard drive the one causing the
> > > blue screen because I isolated the problem. If the hard drive is not
> > > connected, there are no problems at all.
> > >
> > > I presume it is either a Windows Vista internal bug (wouldn't be the first
> > > one, there are quite a lot to be fixed already), an nVidia driver problem
> > > (not so strange, nVidia is slacking a lot with Windows Vista) or a BIOS
> > > problem (strange, because on Windows XP SP2 it works fine).
> > >
> > > I'll check the signatures and will report back, but I recall that when I
> > > installed the nVidia drivers, Windows did not complain about an unsigned
> > > driver.
> > >
> > > Thank you once again.
> > >
> > > "freddy" wrote:
> > >
> > > > Deathwing00,
> > > >
> > > > I just recalled a procedure you can use to help troubleshoot your issue.
> > > > Proceeding on the premise that a driver is behind your problem, Vista
> > > > includes a utility that can identify unsigned drivers. Microsoft asks
> > > > vendors to submit their drivers to Microsoft for testing to ensure they work
> > > > properly. When the drivers pass this quality check they are called signed
> > > > drivers (like signed of on by Microsoft).
> > > >
> > > > Here is how you can identify the unsigned drivers running on your system:
> > > > Click on Start and select Run. In the window that opens, type sigverif.exe
> > > > and click on OK. The utility will run and list all unsigned drivers it finds.
> > > >
> > > > Not all unsigned drivers will cause problems, but some might. The problem
> > > > is in determining whether one of them is the bad one.
> > > >
> > > > Also, your hard drive crashing doesn't necessarily mean that there is
> > > > something wrong with the hard drive or with the USB associated drivers. A
> > > > problem elsewhere can cause your hard drive to crash, making isolating the
> > > > problem a confusing exercise. A problem with NIC drivers, video card
> > > > drivers, and any other drivers, can precipitate the issue you are having.
> > > >
> > > > These comments are only intended to help in understanding the issue.
> > > > --
> > > > freddy
> > > >
> > > >
> > > > "Deathwing00" wrote:
> > > >
> > > > > Thanks a lot for your quick reply.
> > > > >
> > > > > "freddy" wrote:
> > > > >
> > > > > > Deathwing00,
> > > > > >
> > > > > > Anyone troubleshooting this problem should be able to read and interpret
> > > > > > Windows error reports. I don't know whether anyone here can do that, but
> > > > > > time will tell. I searched the Internet on BCCode 1000008e and found the
> > > > > > following explanation (at the link, read down for full explanation):
> > > > > >
> > > > > > http://www.pcreview.co.uk/forums/thread-439539.php
> > > > > >
> > > > > > Of course, reading all that information does not provide the solution to
> > > > > > your specific issue. It does, however, suggest that the problem is
> > > > > > associated with a driver issue. Which driver is hard to tell without further
> > > > > > troubleshooting, but one has to know how to go about doing troubleshooting.
> > > > > >
> > > > > > One can start troubleshooting by trying certain steps to see what happens.
> > > > > > For example, download and install all updates available at the Microsoft
> > > > > > update site, if you haven't already done that. You might get a fix by luck
> > > > > > that way.
> > > > >
> > > > > Fully up to date.
> > > > >
> > > > > >
> > > > > > In addition, check Device Manager to see whether some indication of a
> > > > > > problem is disclosed there. If there is, you can use the procedures in
> > > > > > Device Manager to updating drivers. That is, Device Manager can search for
> > > > > > updated drivers.
> > > > > >
> > > > >
> > > > > It says all drivers are up and running fine.
> > > > >
> > > > > > Another approach is to determine whether the external hard drive requires a
> > > > > > driver to function properly. Some external devices need special drivers,
> > > > > > apart from the normal USB port drivers, and some don't. For example, your
> > > > > > hard drive may have an integrated controller requiring a driver, but I have
> > > > > > no knowledge whether it does or not.
> > > > > >
> > > > >
> > > > > The vendor says there is no need for any driver. In fact, the driver works,
> > > > > but it always ends up sooner or later with that blue screen. I also checked
> > > > > nVidia's website for drivers, but there are none.
> > > > >
> > > > > > These comments are just some things to consider. Others may have additional
> > > > > > information for you.
> > > > > >
> > > > >
> > > > > Thank you. I'll try to post the details of the blue screen later on.
> > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > freddy
> > > > > >
> > > > > >
> > > > >

It's a windows vista driver problem with HDD USB disks with the current
nForce drivers. nVidia on drivers sucks definitely. Next time I go ATI, at
least ATI gives you new drivers every month and does not suddently drop
support.

Now that I am using the hub, the calls go through it, not directly to the
device, and the driver used is for the hub, not for the disk.


"freddy" wrote:

> Deathwing00,
>
> Like we were saying, you never know. How did you manage to decide to try
> that solution? I also wonder why that approach solved the crash problem. Any
> ideas?
> --
> freddy
>
>
> "Deathwing00" wrote:
>
> > Hey there!!!!
> >
> > I finally solved the problem. I bought a simple USB hub and used it to
> > connect the hard drive to it, instead of directly to the laptop. No more
> > crashes since then.
> >
> > Cheers!
> >
> > "freddy" wrote:
> >
> > > Deathwing00,
> > >
> > > I have some unsigned drivers on my system, and Windows hasn't complained
> > > about it. So, I don't know under what circumstances you'd get a Windows
> > > complaint. I had an unusual crash not long ago while performing some routine
> > > that had nothing to do with what caused the crash. It turned out the driver
> > > for the Asus motherboard monitor was the bad guy, and I got a crash while not
> > > using the motherboard monitor. You never know.
> > >
> > > When I say that the external USB hard drive crashes, I'm not saying that
> > > there is anything wrong with the hard drive. Read my comments carefully and
> > > you'll see that I'm not saying that. I'm just saying you get a crash when
> > > you try using the HD, and that the cause could be elsewhere, so that one
> > > can't conclude that the HD or the drivers associated with the HD are at
> > > fault. This can be complicated stuff.
> > >
> > > It's also very speculative in using logic in trying to understand the
> > > problem, because a lot of this stuff isn't subject to layman's logic.
> > > Anyway, post back on what unsigned drivers you find. You may get to the
> > > bottom of this yet.
> > > --
> > > freddy
> > >
> > >
> > > "Deathwing00" wrote:
> > >
> > > > Hi again and thanks for your reply.
> > > >
> > > > Well, it's not that the Hard Drive crashes, it works, it's Vista that
> > > > BlueScreens. I can confirm you that it is the hard drive the one causing the
> > > > blue screen because I isolated the problem. If the hard drive is not
> > > > connected, there are no problems at all.
> > > >
> > > > I presume it is either a Windows Vista internal bug (wouldn't be the first
> > > > one, there are quite a lot to be fixed already), an nVidia driver problem
> > > > (not so strange, nVidia is slacking a lot with Windows Vista) or a BIOS
> > > > problem (strange, because on Windows XP SP2 it works fine).
> > > >
> > > > I'll check the signatures and will report back, but I recall that when I
> > > > installed the nVidia drivers, Windows did not complain about an unsigned
> > > > driver.
> > > >
> > > > Thank you once again.
> > > >
> > > > "freddy" wrote:
> > > >
> > > > > Deathwing00,
> > > > >
> > > > > I just recalled a procedure you can use to help troubleshoot your issue.
> > > > > Proceeding on the premise that a driver is behind your problem, Vista
> > > > > includes a utility that can identify unsigned drivers. Microsoft asks
> > > > > vendors to submit their drivers to Microsoft for testing to ensure they work
> > > > > properly. When the drivers pass this quality check they are called signed
> > > > > drivers (like signed of on by Microsoft).
> > > > >
> > > > > Here is how you can identify the unsigned drivers running on your system:
> > > > > Click on Start and select Run. In the window that opens, type sigverif.exe
> > > > > and click on OK. The utility will run and list all unsigned drivers it finds.
> > > > >
> > > > > Not all unsigned drivers will cause problems, but some might. The problem
> > > > > is in determining whether one of them is the bad one.
> > > > >
> > > > > Also, your hard drive crashing doesn't necessarily mean that there is
> > > > > something wrong with the hard drive or with the USB associated drivers. A
> > > > > problem elsewhere can cause your hard drive to crash, making isolating the
> > > > > problem a confusing exercise. A problem with NIC drivers, video card
> > > > > drivers, and any other drivers, can precipitate the issue you are having.
> > > > >
> > > > > These comments are only intended to help in understanding the issue.
> > > > > --
> > > > > freddy
> > > > >
> > > > >
> > > > > "Deathwing00" wrote:
> > > > >
> > > > > > Thanks a lot for your quick reply.
> > > > > >
> > > > > > "freddy" wrote:
> > > > > >
> > > > > > > Deathwing00,
> > > > > > >
> > > > > > > Anyone troubleshooting this problem should be able to read and interpret
> > > > > > > Windows error reports. I don't know whether anyone here can do that, but
> > > > > > > time will tell. I searched the Internet on BCCode 1000008e and found the
> > > > > > > following explanation (at the link, read down for full explanation):
> > > > > > >
> > > > > > > http://www.pcreview.co.uk/forums/thread-439539.php
> > > > > > >
> > > > > > > Of course, reading all that information does not provide the solution to
> > > > > > > your specific issue. It does, however, suggest that the problem is
> > > > > > > associated with a driver issue. Which driver is hard to tell without further
> > > > > > > troubleshooting, but one has to know how to go about doing troubleshooting.
> > > > > > >
> > > > > > > One can start troubleshooting by trying certain steps to see what happens.
> > > > > > > For example, download and install all updates available at the Microsoft
> > > > > > > update site, if you haven't already done that. You might get a fix by luck
> > > > > > > that way.
> > > > > >
> > > > > > Fully up to date.
> > > > > >
> > > > > > >
> > > > > > > In addition, check Device Manager to see whether some indication of a
> > > > > > > problem is disclosed there. If there is, you can use the procedures in
> > > > > > > Device Manager to updating drivers. That is, Device Manager can search for
> > > > > > > updated drivers.
> > > > > > >
> > > > > >
> > > > > > It says all drivers are up and running fine.
> > > > > >
> > > > > > > Another approach is to determine whether the external hard drive requires a
> > > > > > > driver to function properly. Some external devices need special drivers,
> > > > > > > apart from the normal USB port drivers, and some don't. For example, your
> > > > > > > hard drive may have an integrated controller requiring a driver, but I have
> > > > > > > no knowledge whether it does or not.
> > > > > > >
> > > > > >
> > > > > > The vendor says there is no need for any driver. In fact, the driver works,
> > > > > > but it always ends up sooner or later with that blue screen. I also checked
> > > > > > nVidia's website for drivers, but there are none.
> > > > > >
> > > > > > > These comments are just some things to consider. Others may have additional
> > > > > > > information for you.
> > > > > > >
> > > > > >
> > > > > > Thank you. I'll try to post the details of the blue screen later on.
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > freddy
> > > > > > >
> > > > > > >
> > > > > >

Deathwing00,

Thanks, I'll file that information away for future reference. How did you
come to the realization that you needed a hub to get around this problem? In
my mind, that step is not intuitive, but then the solution for these sort of
problems seldom are.
--
freddy


"Deathwing00" wrote:

> It's a windows vista driver problem with HDD USB disks with the current
> nForce drivers. nVidia on drivers sucks definitely. Next time I go ATI, at
> least ATI gives you new drivers every month and does not suddently drop
> support.
>
> Now that I am using the hub, the calls go through it, not directly to the
> device, and the driver used is for the hub, not for the disk.
>
>
> "freddy" wrote:
>
> > Deathwing00,
> >
> > Like we were saying, you never know. How did you manage to decide to try
> > that solution? I also wonder why that approach solved the crash problem. Any
> > ideas?
> > --
> > freddy
> >
> >
> > "Deathwing00" wrote:
> >
> > > Hey there!!!!
> > >
> > > I finally solved the problem. I bought a simple USB hub and used it to
> > > connect the hard drive to it, instead of directly to the laptop. No more
> > > crashes since then.
> > >
> > > Cheers!
> > >
> > > "freddy" wrote:
> > >
> > > > Deathwing00,
> > > >
> > > > I have some unsigned drivers on my system, and Windows hasn't complained
> > > > about it. So, I don't know under what circumstances you'd get a Windows
> > > > complaint. I had an unusual crash not long ago while performing some routine
> > > > that had nothing to do with what caused the crash. It turned out the driver
> > > > for the Asus motherboard monitor was the bad guy, and I got a crash while not
> > > > using the motherboard monitor. You never know.
> > > >
> > > > When I say that the external USB hard drive crashes, I'm not saying that
> > > > there is anything wrong with the hard drive. Read my comments carefully and
> > > > you'll see that I'm not saying that. I'm just saying you get a crash when
> > > > you try using the HD, and that the cause could be elsewhere, so that one
> > > > can't conclude that the HD or the drivers associated with the HD are at
> > > > fault. This can be complicated stuff.
> > > >
> > > > It's also very speculative in using logic in trying to understand the
> > > > problem, because a lot of this stuff isn't subject to layman's logic.
> > > > Anyway, post back on what unsigned drivers you find. You may get to the
> > > > bottom of this yet.
> > > > --
> > > > freddy
> > > >
> > > >
> > > > "Deathwing00" wrote:
> > > >
> > > > > Hi again and thanks for your reply.
> > > > >
> > > > > Well, it's not that the Hard Drive crashes, it works, it's Vista that
> > > > > BlueScreens. I can confirm you that it is the hard drive the one causing the
> > > > > blue screen because I isolated the problem. If the hard drive is not
> > > > > connected, there are no problems at all.
> > > > >
> > > > > I presume it is either a Windows Vista internal bug (wouldn't be the first
> > > > > one, there are quite a lot to be fixed already), an nVidia driver problem
> > > > > (not so strange, nVidia is slacking a lot with Windows Vista) or a BIOS
> > > > > problem (strange, because on Windows XP SP2 it works fine).
> > > > >
> > > > > I'll check the signatures and will report back, but I recall that when I
> > > > > installed the nVidia drivers, Windows did not complain about an unsigned
> > > > > driver.
> > > > >
> > > > > Thank you once again.
> > > > >
> > > > > "freddy" wrote:
> > > > >
> > > > > > Deathwing00,
> > > > > >
> > > > > > I just recalled a procedure you can use to help troubleshoot your issue.
> > > > > > Proceeding on the premise that a driver is behind your problem, Vista
> > > > > > includes a utility that can identify unsigned drivers. Microsoft asks
> > > > > > vendors to submit their drivers to Microsoft for testing to ensure they work
> > > > > > properly. When the drivers pass this quality check they are called signed
> > > > > > drivers (like signed of on by Microsoft).
> > > > > >
> > > > > > Here is how you can identify the unsigned drivers running on your system:
> > > > > > Click on Start and select Run. In the window that opens, type sigverif.exe
> > > > > > and click on OK. The utility will run and list all unsigned drivers it finds.
> > > > > >
> > > > > > Not all unsigned drivers will cause problems, but some might. The problem
> > > > > > is in determining whether one of them is the bad one.
> > > > > >
> > > > > > Also, your hard drive crashing doesn't necessarily mean that there is
> > > > > > something wrong with the hard drive or with the USB associated drivers. A
> > > > > > problem elsewhere can cause your hard drive to crash, making isolating the
> > > > > > problem a confusing exercise. A problem with NIC drivers, video card
> > > > > > drivers, and any other drivers, can precipitate the issue you are having.
> > > > > >
> > > > > > These comments are only intended to help in understanding the issue.
> > > > > > --
> > > > > > freddy
> > > > > >
> > > > > >
> > > > > > "Deathwing00" wrote:
> > > > > >
> > > > > > > Thanks a lot for your quick reply.
> > > > > > >
> > > > > > > "freddy" wrote:
> > > > > > >
> > > > > > > > Deathwing00,
> > > > > > > >
> > > > > > > > Anyone troubleshooting this problem should be able to read and interpret
> > > > > > > > Windows error reports. I don't know whether anyone here can do that, but
> > > > > > > > time will tell. I searched the Internet on BCCode 1000008e and found the
> > > > > > > > following explanation (at the link, read down for full explanation):
> > > > > > > >
> > > > > > > > http://www.pcreview.co.uk/forums/thread-439539.php
> > > > > > > >
> > > > > > > > Of course, reading all that information does not provide the solution to
> > > > > > > > your specific issue. It does, however, suggest that the problem is
> > > > > > > > associated with a driver issue. Which driver is hard to tell without further
> > > > > > > > troubleshooting, but one has to know how to go about doing troubleshooting.
> > > > > > > >
> > > > > > > > One can start troubleshooting by trying certain steps to see what happens.
> > > > > > > > For example, download and install all updates available at the Microsoft
> > > > > > > > update site, if you haven't already done that. You might get a fix by luck
> > > > > > > > that way.
> > > > > > >
> > > > > > > Fully up to date.
> > > > > > >
> > > > > > > >
> > > > > > > > In addition, check Device Manager to see whether some indication of a
> > > > > > > > problem is disclosed there. If there is, you can use the procedures in
> > > > > > > > Device Manager to updating drivers. That is, Device Manager can search for
> > > > > > > > updated drivers.
> > > > > > > >
> > > > > > >
> > > > > > > It says all drivers are up and running fine.
> > > > > > >
> > > > > > > > Another approach is to determine whether the external hard drive requires a
> > > > > > > > driver to function properly. Some external devices need special drivers,
> > > > > > > > apart from the normal USB port drivers, and some don't. For example, your
> > > > > > > > hard drive may have an integrated controller requiring a driver, but I have
> > > > > > > > no knowledge whether it does or not.
> > > > > > > >
> > > > > > >
> > > > > > > The vendor says there is no need for any driver. In fact, the driver works,
> > > > > > > but it always ends up sooner or later with that blue screen. I also checked
> > > > > > > nVidia's website for drivers, but there are none.
> > > > > > >
> > > > > > > > These comments are just some things to consider. Others may have additional
> > > > > > > > information for you.
> > > > > > > >
> > > > > > >
> > > > > > > Thank you. I'll try to post the details of the blue screen later on.
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > freddy
> > > > > > > >
> > > > > > > >
> > > > > > >