I would like to report a potential Kprobe2 bug: on systems running Intel RAID (a.k.a. Intel Matrix Storage Manager or IMSM) and equipped with a SATA interface optical drive, launching Kprobe2 (in ASPI driver mode) induces a Intel RAID driver BSOD crash, or Kprobe2 simply hangs (never makes it to the main screen).
After quite a bit of research, I believe the following hardware components are all necessary to reproduce this crash:
- Motherboard with Intel chipset with RAID (Matrix Storage) capability. This includes motherboards based on the following Intel southbridges: ICH5R, ICH6R, ICH7R, ICH7DH.
- Intel southbridge SATA controller in RAID or AHCI mode (not IDE mode); applicable driver is Intel Matrix Storage 5.0 or later
- One or more SATA hard disks. With Intel's Matrix Storage (RAID) driver, the hard disks can be in any of the supported RAID levels (0, 1, 5, Matrix RAID, etc.), or simply in "RAID Ready" mode with a single disk.
- One SATA optical drive connected to one of the Intel SATA ports. The presence of a SATA ODD is critical in reproducing this issue; without it the symptoms completely disappear!
- One LiteOn DVD writer to work with Kprobe2
Tested configuration:
- ASUS P5AD2-E Premium motherboard (Intel 925XE/ICH6R chipset); BIOS 1005; onboard SiliconImage SATA controller & ITE RAID controller disabled
- Intel Pentium 4 660 CPU
- 2 Seagate 400GB SATA hard disks in RAID 1 (mirror) mode; connected to ICH6R SATA ports
- 1 Plextor PX-716SA SATA DVD Writer; connected to ICH6R SATA port
- 1 LiteOn SOHW-1653S DVD Writer; IDE primary master
- Windows XP Professional SP2
- Kprobe2 2.5.1
- Intel Matrix Storage Driver 5.1.0.1022, 5.5.0.1035
The exact crash symptoms are dependent on the Intel Matrix Storage driver version. With version 5.1.0.1022, a BSOD occurs and points to the Intel driver (iastor.sys), with STOP 0x00008086 code. With the latest 5.5.0.1035 version, no BSOD occurs, but Kprobe2 will simply hang at the banner screen and never reach the main screen.
One workaround is to configure Kprobe2 into SPTI mode, as the crash occurs only with Kprobe2 in ASPI mode. The SATA optical drive can be temporarily disconnected from the system, to allow Kprobe2 to launch normally, then switch to SPTI mode and reconnect the SATA optical drive.
I have contacted Intel support with this issue and they said their Matrix Storage driver team analyzed Kprobe2 and discovered it to be issuing an IOCTL function call with invalid parameters, in such a way as to induce the Intel Matrix Storage driver to suffer a BSOD. In the latest 5.5.0.1035 driver, Intel improved IOCTL function call error checking, and fails the bad IOCTL call instead of the driver crashing, but this leads directly to Kprobe2 hanging at the banner screen.
Again, the anomaly appears to be a Kprobe2 (ASPI mode) cornercase related to Intel Matrix Storage with a SATA optical drive connected.
I doubt if there are a lot of folks out there with Intel RAID, SATA ODD and LiteOn DVD burner running Kprobe2, but I hope this information can help people sidestep this nasty crash if they have this kind of hardware configuration.
위 내용을 정리하면 SATA 하드의 AHCI 모드를 사용하면 Kprobe2의 진입 과정에서 홀드 다운된다. Kprobe2를 제대로 사용하려면 SATA ODD의 케이블을 잠시 분리한후 Kprobe2의 설정을 SPTI 모드로 바꿔주고 다시 연결하면 사용이 가능하다는 것이다
디스크 품질 검사를 위해 DVDInfo Pro를 사용하면 에러없이 작동하는걸 알수 있는데 이때 설정 모드를 보면 SPTI 모드로 되어 있음을 알수 있다.
BHA_DVDRAM_Driver_Korean_For_Windows_XP2.zip
XPDrv5026BHAOEMKO.exe
invalid-file