- Blue Screen Upon Insertion of Lexar Secure II drive
- Posted by jj on November 1st, 2005
My laptop (Dell Inspiron 6000 w/ WinXP SP2) blue screens every time I
insert a Lexar Secure II drive. I have tried about 10 different
drives, and this occurs every time. This occurs with both the 256 MB
and the 512 MB disks. I have tried several other USB flash drives and
they all work fine (Unfortunatly, I don't have any other Lexars to
try). These drives work perfectly on all other computers I have tried.
It is not the software on the disk causing the problem, as it blue
screens before it is able to mount the drive.
The blue screen error is
usbhub.sys
0x00000050 (0xf6ffffe8, 0x00000001, 0xf76f874e, 0x00000000)
Address f76f874e base at f76f7000 date stamp 41107db8
Any help with this would be appreciated,
Thanks
JJ
- Posted by Gerry Cornell on November 2nd, 2005
jj
Is this a brand new Lexar Secure II drive? If not what have you done
about updating drivers?
--
Hope this helps.
Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA
Using invalid email address
Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.
http://dts-l.org/goodpost.htm
~~~~~~~~~~~~~~~~~~~~~~~~
"jj" <joshua.d.johnson@gmail.com> wrote in message
news:1130868915.344949.27330@z14g2000cwz.googlegro ups.com...
> My laptop (Dell Inspiron 6000 w/ WinXP SP2) blue screens every time I
> insert a Lexar Secure II drive. I have tried about 10 different
> drives, and this occurs every time. This occurs with both the 256 MB
> and the 512 MB disks. I have tried several other USB flash drives and
> they all work fine (Unfortunatly, I don't have any other Lexars to
> try). These drives work perfectly on all other computers I have
> tried.
> It is not the software on the disk causing the problem, as it blue
> screens before it is able to mount the drive.
>
> The blue screen error is
>
> usbhub.sys
> 0x00000050 (0xf6ffffe8, 0x00000001, 0xf76f874e, 0x00000000)
> Address f76f874e base at f76f7000 date stamp 41107db8
>
> Any help with this would be appreciated,
>
> Thanks
>
> JJ
>
- Posted by jj on November 2nd, 2005
I found out the problem. The registry key
HKLM/System/CurrentControlSet/Control/UsbFlags/IgnoreHwSerNumXXXXXXXX
had somehow got set to a dword. I believe this may have happened
because too many different drives (around 30 to 40) with the same
product ID had been inserted in the same computer, but I am not sure.
- Posted by Gerry Cornell on November 2nd, 2005
jj
How did find out the problem?
--
Regards.
Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA
Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
"jj" <joshua.d.johnson@gmail.com> wrote in message
news:1130943775.736561.124740@g49g2000cwa.googlegr oups.com...
>I found out the problem. The registry key
> HKLM/System/CurrentControlSet/Control/UsbFlags/IgnoreHwSerNumXXXXXXXX
> had somehow got set to a dword. I believe this may have happened
> because too many different drives (around 30 to 40) with the same
> product ID had been inserted in the same computer, but I am not sure.
>
- Posted by jj on November 2nd, 2005
By searching online for about 6 hours with every combination of words
that I could think of. I found it in a forum post somewhere in a
non-English language (German if I remember correctly) and made the best
that I could from an automatic translator.
- Posted by Gerry Cornell on November 2nd, 2005
jj
I am impressed.
--
Regards.
Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA
Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
"jj" <joshua.d.johnson@gmail.com> wrote in message
news:1130960563.186706.142380@f14g2000cwb.googlegr oups.com...
> By searching online for about 6 hours with every combination of words
> that I could think of. I found it in a forum post somewhere in a
> non-English language (German if I remember correctly) and made the
> best
> that I could from an automatic translator.
>
