[coLinux-devel] [ colinux-Bugs-1239020 ] BSOD[DRIVER_IRQL_NOT_LESS_OR_EQUAL] after removing coLinux

[SourceForge.net <no...@so...>]

Bugs item #1239020, was opened at 2005-07-16 00:19
Message generated for change (Comment added) made by xuefer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1239020&group_id=98788

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: BSOD[DRIVER_IRQL_NOT_LESS_OR_EQUAL] after removing coLinux

Initial Comment:
Hi,   (Please, don't notice my faulty English)

I've very recently used "stable-coLinux-20050524.exe" 
(Snapshot of version 0.6.3-pre13) successfully on an up-
to-date Windows XP SP2 Edition Family on a 32-bit-
AMD-processor machine.
When I installed it, I also chose to install the TAP 
component proposed by the wizard.
So, I used the tap0801co driver (for File Sharing, 
Internet, Cygwin/X, ...).

But recentlty I decided to remove coLinux and at the 
first reboot that occured after its deinstallation, I got a 
BlueScreenOfDeath on early startup.
This BSOD said
  DRIVER_IRQL_NOT_LESS_OR_EQUAL  <--- very 
probably that
or
  IRQL_NOT_LESS_OR_EQUAL
or
  DRIVER_IRQ_NOT_LESS_OR_EQUAL
or
  IRQ_NOT_LESS_OR_EQUAL
(I haven't quoted it down.)

I was then able to start Windows in Failsafe Mode only 
(both with or without network support).
Furthermore, I noticed that removing coLinux seem to 
let several remaining rubbishes : tap0801co.sys and 
much data in the registry about both linux.sys, the 
colinux driver and the TAP driver.
I infered that the removing process leaved Windows in 
an inconsistent state : its registry talking about missing 
drivers or what ???
I didn't manage to fix the problem, even by removing(*) 
tap0801.sys and the suspicious Registry data.
(*) Note that I was not able to remove the 
LEGACY_COLINUX reistry key.
I was obliged to reinstalled Windows XP :-(

I hope this report could help developers.

Sincerely,
Anonymous ANONYMAT


----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2007-03-16 19:30

Message:
Logged In: YES 
user_id=185131
Originator: NO

using bridge without any tun-tap for colinux (tap device is still
installed on winxp). it works good so far, no blue screen any more. maybe i
should file another bug.

----------------------------------------------------------------------

Comment By: Xuefer (xuefer)
Date: 2007-03-11 17:33

Message:
Logged In: YES 
user_id=185131
Originator: NO

i get same message, not at host system boot but when i tap some keys on
keyboard, this happen rarely. it seems relatived to tun-tap as i never use
it before and didn't have such problem. i'll try to use bridge

----------------------------------------------------------------------

Comment By: George P Boutwell (gboutwel)
Date: 2006-09-03 02:18

Message:
Logged In: YES 
user_id=30412

I'm going to close this.  I'll keep in mind that a possible
check for coLinux files in-use/coLinux instance running when
uninstalled could be the problem.  I'll, also, see if there
is some cruft left over after an uninstall and see if the
coLinux uninstaller can be improved to ensure that it there
isn't anything left over unless something really bad happens.


----------------------------------------------------------------------

Comment By: grv (grv575)
Date: 2005-08-18 14:52

Message:
Logged In: YES 
user_id=724100

I've gotten the IRQ_NOT_LESS_EQUAL_TO bsod from bad network
drivers (for my ethernet card).  So it's likely something
fishy with the deinstallation of the TAP virtual network
connection.  If someone can reproduce, does uninstalling the
TAP driver first (or stopping and disabling the driver
service) fix things?  maybe uninstall the pcap install first
as well?



----------------------------------------------------------------------

Comment By: grv (grv575)
Date: 2005-08-18 14:49

Message:
Logged In: YES 
user_id=724100

I've gotten the IRQ_NOT_LESS_EQUAL_TO bsod from bad network
drivers (for my ethernet card).  So it's likely something
fishy with the deinstallation of the TAP virtual network
connection.  If someone can reproduce, does uninstalling the
TAP driver first (or stopping and disabling the driver
service) fix things?  maybe uninstall the pcap install first
as well?



----------------------------------------------------------------------

Comment By: George P Boutwell (gboutwel)
Date: 2005-07-28 22:27

Message:
Logged In: YES 
user_id=30412

That's really interesting...  I've ran the install and
uninstall several times and I'm not able to duplicate this
problem...

You can remove the LEGACY_COLINUX registry key without
reinstalling Windows by running colinux-daemon
--remove-driver (of course you'd have to get a copy of that
file to run without having it installed)  colinux-deamon
--remove-driver is run as part of the Uninstall of colinux,
but if for some reason that failed, that registry key would
still exist, but the file wouldn't, it would cause your
problem.  But again, I'm not able to duplicate this situation.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1239020&group_id=98788