BSOD 0xd1 on removing HDs?

[Guest]

Question
I have some NON system drives, hooked up to a Silicon Images 3112
controller.
When I remove 1 drive, the system does a BSOD, stop error 0xd1
(0xa,0x2,0x0,0xa) and DRIVER_IRQL_NOT_LESS_OR_EQUAL shortly after I get to
the desktop.

When I remove both drives, it hangs (locks up) on windows loading screen.

If I disable the 3112 controller in the device manager, and reboot, it locks
at windows loading screen again, so I have to boot into safe mode, re-enable
it, and all is OK.

A repair install will not fix this issue.

I know something is trying to access something on those drives, but nothing
is installed on them, and as I said, they are NOT system drives at all.
I can even remove the drive's drive letters, and as long as both drives are
plugged in, then all is fine.

This means to me that something is either hooking on to the Sil 3112 driver,
or something along those lines, and when it can't find whatever, it crashes
with the above error.

Anyone know a way to find out what is causing the issue? I already tried
different 3112 drivers, and it didn't make a difference.
Note, it does NOT create a minidump, or any dump I tell it to create, so I
can't backtrace with that.

 

[needlove]

Check your BIOS settings. Also try rolling back the driver

 

[Guest]

This is not a BIOS issue, and I already tried different drivers.

 

[needlove]

MS has a driver validation tool. Try that. Maybe assigning a different IRQ
path is needed? Irq not less or equal is a pretty broad error. Do you have
any RAID configurations? Can you check the nonsystem drive on another
computer? What is this nonsystem drive? Is your Sil3112 chip onboard your
motherboard or is it a PCI card? Does msinfo32.exe tell you anything or your
error reporting logs? Ive had irq not less or equal bsod's that didnt create
a minidump and it seems to me there is a way to force the creation of a dump
file using winDbg tool but I dont have that knowledge.

 

[Guest]

A friend of mine fixed the problem. Turns out it was a conflict from another
driver that for some reason was 'locking' those drives on the 3112.

Non system drive means that nothing is installed on it, no programs or
anything of that sort. They are just used for backups.

He did a kernel debug to find the problem.

All works now, I can plug in different drives without the BSOD now.