From: Steve F. <ste...@be...> - 2004-09-15 13:31:27
|
Okay, I figured this out and I'll post it here so if others see this happen. The problem is due to the combination of Windows XP SP2 with DEP enabled on an Athlon64 processor. After trying combination after combination and seeing a ton of blue screens, I was able to get coLinux to operate by changing the /NoExecute to be AlwaysOff in my boot.ini. I consider this a little bit of a bug with coLinux, and it's bitten the DivX encoder too on this processor. =20 DEP =3D Data Execution Prevention, which basically enables the flagging = of memory as being non-executable, thereby preventing injected code from being run if pushed in via a buffer overrun. Lots of details are here at Microsoft's site: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr. mspx Something in coLinux isn't playing nice with this, and I end up with a STOP error everytime I start up the app. I tried flagging just the colinux-daemon.exe to be bypassed with this stuff, but it still BSOD'd, probably because of something in the linux.sys because it was not flagged to run without DEP. I had to disable it for the entire OS. This isn't really desirable from a security perspective long term, but short term it really doesn't make my machine less secure than when I was running service pack 1, because SP1 didn't enable this capability in the first place. FWIW, on my work machine, a Pentium4 desktop, this doesn't crash. DEP is enforced by the OS, not relying on the underlying hardware to do it, since DEP isn't available on this processor, and according to the above link: By default, software-enforced DEP only protects limited system binaries, regardless of the hardware-enforced DEP capabilities of the processor. I'm curious if the OS considers linux.sys to be part of the OS or not?=20 I believe the new E64MT Pentium 4 procs have this enabled, so this problem may or may not appear on that platform. With more people moving towards the Athlon64 processors (they are getting cheaper now), this problem might affect more coLinux people in the near future. Thanks, hope this helps others! Steve=20 > -----Original Message----- > From: col...@li...=20 > [mailto:col...@li...] On Behalf=20 > Of Steve Frank > Sent: Saturday, September 11, 2004 3:27 PM > To: col...@li... > Subject: [coLinux-users] Newbie question: linux.sys causing a BSOD >=20 > Hi, I'm getting a STOP error (Blue scree o' death) whenever I=20 > try to start up colinux, with the failure on the linux.sys=20 > driver. I'm on XP > SP2 (and it works on another SP2 machine fine). Immediately=20 > on startup a 0x8e error occurs, so this is a no go. The=20 > system is an Athlon64 with a Via KT800Pro chipset, if that=20 > matters. Any ideas? >=20 > =20 >=20 > Steve >=20 > =20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one=20 > of 170 Project Admins to receive an Apple iPod Mini FREE for=20 > your judgement on who ports your project to Linux PPC the=20 > best. Sponsored by IBM.=20 > Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php=20 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users >=20 |
From: Steve F. <ste...@be...> - 2004-09-16 13:25:58
|
I'd be glad to help out any way I can. Feel free to email me anytime--just let me know what I need to do. =20 Thanks! Steve -----Original Message----- From: Nuno Lucas [mailto:lu...@nl...]=20 Sent: Wednesday, September 15, 2004 4:48 PM To: Steve Frank Cc: col...@li... Subject: Re: [coLinux-users] Newbie question: linux.sys causing a BSOD Hi Steve, Just to let you know you have been noticed and I forwarded your mail to the developers list. This was more or less expected and I'm sorry I didn't catch the SP2/Amd64 magic combination on your first mail, at least to speed the reason finding, if not the short term solution. What I wasn't expecting was the BSoD. That is a serious problem indeed. Dan Aloni, the one who understands all the code (because he wrote it ;), is in Japan right now, doing some lecturers for CoLinux, but I'm sure he will make everything possible to solve your case. The only problem would be for him to get the time to do it. It would be great if you could offer for testing a possible fix, as not everyone has an adequate machine for that :) Best Regards, ~Nuno Lucas Steve Frank, dando pulos de alegria, escreveu : > Okay, I figured this out and I'll post it here so if others see this=20 > happen. >=20 > The problem is due to the combination of Windows XP SP2 with DEP=20 > enabled on an Athlon64 processor. After trying combination after=20 > combination and seeing a ton of blue screens, I was able to get=20 > coLinux to operate by changing the /NoExecute to be AlwaysOff in my boot.ini. >=20 > I consider this a little bit of a bug with coLinux, and it's bitten=20 > the DivX encoder too on this processor. >=20 > DEP =3D Data Execution Prevention, which basically enables the = flagging=20 > of memory as being non-executable, thereby preventing injected code=20 > from being run if pushed in via a buffer overrun. Lots of details are > here at Microsoft's site: > http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr. > mspx >=20 > Something in coLinux isn't playing nice with this, and I end up with a > STOP error everytime I start up the app. I tried flagging just the=20 > colinux-daemon.exe to be bypassed with this stuff, but it still=20 > BSOD'd, probably because of something in the linux.sys because it was=20 > not flagged to run without DEP. I had to disable it for the entire OS. > This isn't really desirable from a security perspective long term, but > short term it really doesn't make my machine less secure than when I=20 > was running service pack 1, because SP1 didn't enable this capability=20 > in the first place. >=20 > FWIW, on my work machine, a Pentium4 desktop, this doesn't crash. DEP=20 > is enforced by the OS, not relying on the underlying hardware to do=20 > it, since DEP isn't available on this processor, and according to the=20 > above > link: By default, software-enforced DEP only protects limited system=20 > binaries, regardless of the hardware-enforced DEP capabilities of the=20 > processor. I'm curious if the OS considers linux.sys to be part of=20 > the OS or not? >=20 > I believe the new E64MT Pentium 4 procs have this enabled, so this=20 > problem may or may not appear on that platform. With more people=20 > moving towards the Athlon64 processors (they are getting cheaper now), > this problem might affect more coLinux people in the near future. >=20 > Thanks, hope this helps others! >=20 > Steve >=20 >=20 >>-----Original Message----- >>From: col...@li... >>[mailto:col...@li...] On Behalf Of Steve=20 >>Frank >>Sent: Saturday, September 11, 2004 3:27 PM >>To: col...@li... >>Subject: [coLinux-users] Newbie question: linux.sys causing a BSOD >> >>Hi, I'm getting a STOP error (Blue scree o' death) whenever I try to=20 >>start up colinux, with the failure on the linux.sys driver. I'm on XP >>SP2 (and it works on another SP2 machine fine). Immediately on=20 >>startup a 0x8e error occurs, so this is a no go. The system is an=20 >>Athlon64 with a Via KT800Pro chipset, if that matters. Any ideas? >> >>=20 >> >>Steve >> >>=20 >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170=20 >>Project Admins to receive an Apple iPod Mini FREE for your judgement=20 >>on who ports your project to Linux PPC the best. Sponsored by IBM. >>Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php=20 >>_______________________________________________ >>coLinux-users mailing list >>coL...@li... >>https://lists.sourceforge.net/lists/listinfo/colinux-users >> >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack=20 > the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder.=20 > More prizes in the weekly Lunch Hour Challenge. > Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Nuno L. <lu...@nl...> - 2004-09-17 02:50:31
|
Steve Frank, dando pulos de alegria, escreveu : > I'd be glad to help out any way I can. Feel free to email me > anytime--just let me know what I need to do. For your information, an explanation of the error code (BugCheck) is here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/ddtools/BCCodes_12795dee-19a9-4461-a135-bbb882b81455.xml.asp It could help to check your system log for the error in question and post it here or in the devel list. I would guess the exception code is: 0xC0000005 - STATUS_ACCESS_VIOLATION, but only you can confirm that. Regards, ~Nuno Lucas |
From: Steve F. <ste...@be...> - 2004-09-17 15:36:57
|
Here's the system log bugcheck: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000008e (0xc0000005, 0xb2834c54, 0xb1d27a88, 0x00000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. 0x8e is KERNEL_MODE_EXCEPTION_NOT_HANDLED and the code is 0xc00000005, just as you suspected. Steve =20 =20 > -----Original Message----- > From: Nuno Lucas [mailto:lu...@nl...]=20 > Sent: Thursday, September 16, 2004 9:50 PM > To: Steve Frank > Cc: col...@li... > Subject: Re: [coLinux-users] Newbie question: linux.sys causing a BSOD >=20 > Steve Frank, dando pulos de alegria, escreveu : > > I'd be glad to help out any way I can. Feel free to email me=20 > > anytime--just let me know what I need to do. >=20 > For your information, an explanation of the error code (BugCheck) is > here: > http://msdn.microsoft.com/library/default.asp?url=3D/library/en- > us/ddtools/hh/ddtools/BCCodes_12795dee-19a9-4461-a135-bbb882b8 > 1455.xml.asp >=20 > It could help to check your system log for the error in=20 > question and post it here or in the devel list. >=20 > I would guess the exception code is: > 0xC0000005 - STATUS_ACCESS_VIOLATION, but only you can confirm that. >=20 > Regards, > ~Nuno Lucas >=20 >=20 |
From: Manuel M. <mar...@ea...> - 2004-09-17 16:56:17
|
Hello, I was following this string in my daily digest. I might have some revelant info about the BSoD in windows. Using a Dell 2ghz Celeron with 128mb of memory, running Win2kPro. Started seeing the same BSoD, for quite some time, I was trying to find out what it was, but My system eventually died. One thing I did notices is that every time that I did IPCONFIG /Release on my windows box, without running coLinux, it gave this stop error. "STOP: 0x0000001e (0xC0000005, (and some other I did not document)), KMODE_EXCEPTION_NOT_HANDLED" the box has an Intel Intergrated Network adapter. Can't remember what the driver is exactly, since I had to ship My PC across country to get re imaged, anyway. It eventually died, BSoD every time it booted up. "STOP: 0x0000007B (Can't Remember the Rest.) INACCESSIBLE_BOOT_DEVICE" |
From: Nuno L. <lu...@nl...> - 2004-09-17 17:52:09
|
Manuel Marquez, dando pulos de alegria, escreveu : > Hello, I was following this string in my daily digest. > I might have some revelant info about the BSoD in windows. > Using a Dell 2ghz Celeron with 128mb of memory, running Win2kPro. > Started seeing the same BSoD, for quite some time, > I was trying to find out what it was, but My system eventually died. > One thing I did notices is that every time that I did IPCONFIG /Release on my windows box, > without running coLinux, it gave this stop error. > "STOP: 0x0000001e (0xC0000005, (and some other I did not document)), > KMODE_EXCEPTION_NOT_HANDLED" > > the box has an Intel Intergrated Network adapter. Can't remember what the driver is exactly, > since I had to ship My PC across country to get re imaged, anyway. > It eventually died, BSoD every time it booted up. > "STOP: 0x0000007B (Can't Remember the Rest.) > INACCESSIBLE_BOOT_DEVICE" I don't think it's related to colinux. You obviously had other problems with your machine (maybe a bad disk?) Anyway, just post here if you find more problems. Regards, ~Nuno Lucas |
From: Daniel S. <dan...@au...> - 2004-09-17 21:23:51
|
Just an FYI, After a BSOD, it is always a good idea to run chkdsk.exe /f on all your drives. Generally, a BSOD will leave errors on your drive. Back in the old days of NT 3.51 and earlier, chkdsk would automatically run after an un-clean shutdown (i.e. BSOD, power loss, etc.) However, now you need to do it manually - which is pretty stupid since you need to get started up to issue the command, then you will need to reboot again to get chkdsk to run on your system disk - (BOGUS). Dan > -----Original Message----- > From: col...@li... [mailto:colinux-users- > ad...@li...] On Behalf Of Manuel Marquez > Sent: Friday, September 17, 2004 12:56 PM > To: Steve Frank; Nuno Lucas > Cc: col...@li... > Subject: Re: [coLinux-users] Newbie question: linux.sys causing a BSOD >=20 > Hello, I was following this string in my daily digest. > I might have some revelant info about the BSoD in windows. > Using a Dell 2ghz Celeron with 128mb of memory, running Win2kPro. > Started seeing the same BSoD, for quite some time, > I was trying to find out what it was, but My system eventually died. > One thing I did notices is that every time that I did IPCONFIG /Release on > my windows box, > without running coLinux, it gave this stop error. > "STOP: 0x0000001e (0xC0000005, (and some other I did not document)), > KMODE_EXCEPTION_NOT_HANDLED" >=20 > the box has an Intel Intergrated Network adapter. Can't remember what the > driver is exactly, > since I had to ship My PC across country to get re imaged, anyway. > It eventually died, BSoD every time it booted up. > "STOP: 0x0000007B (Can't Remember the Rest.) > INACCESSIBLE_BOOT_DEVICE" >=20 >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Steve F. <ste...@be...> - 2004-09-25 15:14:34
|
Did you see my posted workaround? You need to disable the NX capability of SP2 and it will work. =20 -----Original Message----- From: Paradise [mailto:par...@gm...]=20 Sent: Friday, September 24, 2004 9:50 AM To: Steve Frank Cc: col...@li... Subject: Re: [coLinux-users] Newbie question: linux.sys causing a BSOD Me too !!! coLinux v.0.6.2 pre1 crashed (blue screen) on my windows xp pro sp2 (32 bit ver) however it doesnt crash on my athlonxp.... anyone is same as me? or anyone run it on athlon 64 with no problem? cpu: athlon 64 3000+ (s754) mb: gigabyte k8ns pro (nforce3 250) ram: corsair ddr400 cl2.5 512mb it seems doesnt support athlon 64?? On Sat, 11 Sep 2004 15:26:44 -0500, Steve Frank <ste...@be...> wrote: > Hi, I'm getting a STOP error (Blue scree o' death) whenever I try to=20 > start up colinux, with the failure on the linux.sys driver. I'm on XP > SP2 (and it works on another SP2 machine fine). Immediately on=20 > startup a 0x8e error occurs, so this is a no go. The system is an=20 > Athlon64 with a Via KT800Pro chipset, if that matters. Any ideas? >=20 > Steve >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170=20 > Project Admins to receive an Apple iPod Mini FREE for your judgement=20 > on who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php=20 > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users >=20 -- Regards, Paradise |
From: Nuno L. <lu...@nl...> - 2004-09-15 21:47:57
|
Hi Steve, Just to let you know you have been noticed and I forwarded your mail to the developers list. This was more or less expected and I'm sorry I didn't catch the SP2/Amd64 magic combination on your first mail, at least to speed the reason finding, if not the short term solution. What I wasn't expecting was the BSoD. That is a serious problem indeed. Dan Aloni, the one who understands all the code (because he wrote it ;), is in Japan right now, doing some lecturers for CoLinux, but I'm sure he will make everything possible to solve your case. The only problem would be for him to get the time to do it. It would be great if you could offer for testing a possible fix, as not everyone has an adequate machine for that :) Best Regards, ~Nuno Lucas Steve Frank, dando pulos de alegria, escreveu : > Okay, I figured this out and I'll post it here so if others see this > happen. > > The problem is due to the combination of Windows XP SP2 with DEP enabled > on an Athlon64 processor. After trying combination after combination > and seeing a ton of blue screens, I was able to get coLinux to operate > by changing the /NoExecute to be AlwaysOff in my boot.ini. > > I consider this a little bit of a bug with coLinux, and it's bitten the > DivX encoder too on this processor. > > DEP = Data Execution Prevention, which basically enables the flagging of > memory as being non-executable, thereby preventing injected code from > being run if pushed in via a buffer overrun. Lots of details are here > at Microsoft's site: > http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr. > mspx > > Something in coLinux isn't playing nice with this, and I end up with a > STOP error everytime I start up the app. I tried flagging just the > colinux-daemon.exe to be bypassed with this stuff, but it still BSOD'd, > probably because of something in the linux.sys because it was not > flagged to run without DEP. I had to disable it for the entire OS. > This isn't really desirable from a security perspective long term, but > short term it really doesn't make my machine less secure than when I was > running service pack 1, because SP1 didn't enable this capability in the > first place. > > FWIW, on my work machine, a Pentium4 desktop, this doesn't crash. DEP is > enforced by the OS, not relying on the underlying hardware to do it, > since DEP isn't available on this processor, and according to the above > link: By default, software-enforced DEP only protects limited system > binaries, regardless of the hardware-enforced DEP capabilities of the > processor. I'm curious if the OS considers linux.sys to be part of the > OS or not? > > I believe the new E64MT Pentium 4 procs have this enabled, so this > problem may or may not appear on that platform. With more people moving > towards the Athlon64 processors (they are getting cheaper now), this > problem might affect more coLinux people in the near future. > > Thanks, hope this helps others! > > Steve > > >>-----Original Message----- >>From: col...@li... >>[mailto:col...@li...] On Behalf >>Of Steve Frank >>Sent: Saturday, September 11, 2004 3:27 PM >>To: col...@li... >>Subject: [coLinux-users] Newbie question: linux.sys causing a BSOD >> >>Hi, I'm getting a STOP error (Blue scree o' death) whenever I >>try to start up colinux, with the failure on the linux.sys >>driver. I'm on XP >>SP2 (and it works on another SP2 machine fine). Immediately >>on startup a 0x8e error occurs, so this is a no go. The >>system is an Athlon64 with a Via KT800Pro chipset, if that >>matters. Any ideas? >> >> >> >>Steve >> >> >> >> >> >>------------------------------------------------------- >>This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one >>of 170 Project Admins to receive an Apple iPod Mini FREE for >>your judgement on who ports your project to Linux PPC the >>best. Sponsored by IBM. >>Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php >>_______________________________________________ >>coLinux-users mailing list >>coL...@li... >>https://lists.sourceforge.net/lists/listinfo/colinux-users >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: thawte's Crypto Challenge Vl > Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam > Camcorder. More prizes in the weekly Lunch Hour Challenge. > Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |