• Narag
  • DriverPacks newbie
  • Offline
  • Registered: 2006-11-30
  • Posts: 12

Topic: DELL LSI Logic Adapter with 7.062 - BSOD 0x07B

I get BSOD after first reboot with new MassStorage 7.062, with version 7.04 (I used this before) it worked.

It's DELL Precision 360 with LSI Logic 1020/1030 SCSI Adapter.

What's interesting, with RAID enabled, I get error 0x69xxxx (I can't remember, sorry), with RAID disabled I get usual  0x0000007B error.

It seems the LSI Logic gets driver it doesn't like sad

Thanks

Here are the HWIDs:

PCI\VEN_1000&DEV_0030&SUBSYS_10401028&REV_07\4&1C660DD6&0&18F0: LSI Adapter, Ultra320 SCSI 2000 series, (with 1020/1030)
PCI\VEN_1000&DEV_0030&SUBSYS_10401028&REV_07\4&1C660DD6&0&19F0: LSI Adapter, Ultra320 SCSI 2000 series, (with 1020/1030)
PCI\VEN_10DE&DEV_0338&SUBSYS_01C210DE&REV_A1\4&30651773&0&0008: NVIDIA Quadro FX 3000
PCI\VEN_8086&DEV_100E&SUBSYS_01561028&REV_02\4&1C660DD6&0&60F0: Intel(R) PRO/1000 MT Network Connection
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_C2\3&172E68DD&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_24D0&SUBSYS_00000000&REV_02\3&172E68DD&0&F8: Intel(R) 82801EB LPC Interface Controller - 24D0
PCI\VEN_8086&DEV_24D1&SUBSYS_01561028&REV_02\3&172E68DD&0&FA: Intel(R) 82801EB Ultra ATA Storage Controllers
PCI\VEN_8086&DEV_24D2&SUBSYS_01561028&REV_02\3&172E68DD&0&E8: Intel(R) 82801EB USB Universal Host Controller - 24D2
PCI\VEN_8086&DEV_24D3&SUBSYS_01561028&REV_02\3&172E68DD&0&FB: Intel(R) 82801EB SMBus Controller - 24D3
PCI\VEN_8086&DEV_24D4&SUBSYS_01561028&REV_02\3&172E68DD&0&E9: Intel(R) 82801EB USB Universal Host Controller - 24D4
PCI\VEN_8086&DEV_24D5&SUBSYS_01561028&REV_02\3&172E68DD&0&FD: SoundMAX Integrated Digital Audio
PCI\VEN_8086&DEV_24D7&SUBSYS_01561028&REV_02\3&172E68DD&0&EA: Intel(R) 82801EB USB Universal Host Controller - 24D7
PCI\VEN_8086&DEV_24DB&SUBSYS_01561028&REV_02\3&172E68DD&0&F9: Intel(R) 82801EB Ultra ATA Storage Controllers
PCI\VEN_8086&DEV_24DD&SUBSYS_01561028&REV_02\3&172E68DD&0&EF: Intel(R) 82801EB USB2 Enhanced Host Controller - 24DD
PCI\VEN_8086&DEV_24DE&SUBSYS_01561028&REV_02\3&172E68DD&0&EB: Intel(R) 82801EB USB Universal Host Controller - 24DE
PCI\VEN_8086&DEV_2578&SUBSYS_00000000&REV_02\3&172E68DD&0&00: Intel(R) 82875P/E7210 Memory Controller Hub - 2578
PCI\VEN_8086&DEV_2579&SUBSYS_00000000&REV_02\3&172E68DD&0&08: Intel(R) 82875P Processor to AGP Controller - 2579
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: DELL LSI Logic Adapter with 7.062 - BSOD 0x07B

Hi

I said time will tell, and the time has come, I suppose..

here's a snippet of a long post.
----------------------------------
Because of this finding, we had to make a choice..
In our example, the OEM Dell driver [D-3] has a valid signature unlike the native LSI [L-4].
The same Dell HWIDs were suppored in LSI [L-4].
The Dell driver has also a slightly higher version number (1.21.08.00) and a newer date than the original LSI files.
So? What influenced our choice?
If D-3 is signed, keep it.
If the SYS file size for the one in LSI is different, definatetly keep Dell.
Still more considerations were made.
Is there a choice between unsigned generic versus signed proprietary? Keep signed proprietary.
A choice between Subsys and 'proprietary" subsys? Keep signed 'proprietary" subsys.
The filter (mass INI) must be changed to not use non-signed LSI in [L-4] for hwid signed in [D-3]
One could say that generic HWIDs in signed driver should be kept, and unsigned generics can be tossed away if one has it covered by a signed driver. Then, Dell won. BUT... It actually LOST.
In some cases, one can make an edit to a signed driver's INF, and kill the generic in there, keeping the specified subs. You can do that if this one is proprietary, and the other supports a lot more generic and SUB_sys HWIDs as well.
The LSI driver was not signed, older, and therefore Jaak edited the Mass storage INI for [L-4] so that it did not list DELL's HWIDs.
One "could" go as far as editing its INF as well, but since Dell was newer, it was the DELL's INF that got edited to not support the generic. (Jaak did that because Dell, just like Compaq and other OEMs do, often use proprietary chips. And, the SYS they use, is most likely specific for that proprietary chip. Well, the size was different as well.)
LSI's can most probably handle the generics better than Dell's prorietary sys-file.
Will this be the best solution?
Time will tell.
====================================

When That was written, The LSI was DriverVer=04/12/2004,1.10.00, and everything still worked for you..
And now it has DriverVer=06/13/2005,1.20.18.00, and it no longer works.
So, we'll try fix that..

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: DELL LSI Logic Adapter with 7.062 - BSOD 0x07B

Narag?
oops, wrong txt.

The updated driver in LSI [L-4] actually supported all the HWIDs that the DELL [D-3] had.
D-3 has therefore been deleted.

(keep a copy of the old pack)
you see, if LSI drivers are intended for other chipmasks, it could still be bad, and then you would have to do an INI edit in older pack, where you could disable L-4

(After all, INI edit was made possible for end users, so that they can modify supported drivers for txtmode.)

Last edited by jtdoom (2007-06-29 16:49:50)

The answer was 42?
Kind regards, Jaak.
  • Narag
  • DriverPacks newbie
  • Offline
  • Registered: 2006-11-30
  • Posts: 12

Re: DELL LSI Logic Adapter with 7.062 - BSOD 0x07B

Hi Jaak,

thanks for you answer, but now I'm a bit confused:

the older pack 7.04 doesn't this HWID (PCI\VEN_1000&DEV_0030) even listed in .INI and it still able to install the .

the newer pack 7.062 has this HWID listed in L-4. Wouldn't help if I deleted this HWID from L-4?

Thanks

Narag

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: DELL LSI Logic Adapter with 7.062 - BSOD 0x07B

Hi Narag, compare D-3 and L-4 INI, and their INF in the folder..
In the 7.04 pack, DELL had a newer version (signed) than what LSI (unsigned) had.

in 7.06.x, LSI is newer and signed, and supports all what DELL [D-3] had (plus one more).
Now, during txtmode, two drivers would "fight" for control, and one gets it.
later on, windows GUI starts, and PnP renumerates,
The OTHER can WIN.
BSOD.
Therefore I think it was wiser to delete D-3 (older signed) because it would compete with the new LSI (not only Newer, but newer and signed).

Do you see what I mean?

EDIT
WHY did I tell you to not delete old DriverPacks?
proprietary.. masks...
That new LSI will MOST likely support that chip you have, but there is always that possibility that it rather likes Dell's own brew.
When That happens, then is when you have to edit the INI and disable [L-4] in the older pack, and tell us about it.

Last edited by jtdoom (2007-06-29 21:15:56)

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: DELL LSI Logic Adapter with 7.062 - BSOD 0x07B

If you ever wondered why the entries in INI are NOT always in the alphanumerical order...

in pack 7.04 The DELL would take control and LSI could not have won during txtmode because the overlap was edited out. (it was edited by me, because it was OLDER, and UNSIGNED)

in pack 7.06.bad (the one that did a BSOD) the older DELL was still there and gets loaded befor Lsi so it took control, LSI had all the HWIDs this Dell loaded on but control was already took (-) so... they crashed.
result is that you saw a BSOD either at txtmode or at PnP.

because you reported that it did a BSOD on you, this was a logical step.

The answer was 42?
Kind regards, Jaak.