tag:blogger.com,1999:blog-7528831701633643336.post6154599166840965262..comments2023-09-22T11:22:56.777-07:00Comments on /dev/dump: Well *That* Didn't Work Out So WellAnonymoushttp://www.blogger.com/profile/15319934747521320351noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-7528831701633643336.post-22697405041544818502010-07-22T03:26:18.026-07:002010-07-22T03:26:18.026-07:00If there was really bad ram in Garret's comput...If there was really bad ram in Garret's computer (which I doubt), I would think that using an OpenSolaris Indiana live CD as a main desktop for a 24 hour period would definitely crash as well. <br /><br />Seeing how OpenSolaris + ZFS likes to use RAM very aggressively and also noting how every time you "pkg install" something from IPS on the live CD you're installing on to a RAM disk and not to a real hard disk drive, it shouldn't take too long running off of that OpenSolaris live CD for the kernel to write some data to that bad spot in RAM and elicit a crash of some sort. <br /><br />That OpenSolaris Indiana live CD environment had once found a weird anomaly on a certain stick of RAM in my desktop computer that memtest did not show at all, and swapping out the stick of Ram solved the problem.Anonymoushttps://www.blogger.com/profile/15416821389128879439noreply@blogger.comtag:blogger.com,1999:blog-7528831701633643336.post-80398560833779878202010-06-07T16:10:31.636-07:002010-06-07T16:10:31.636-07:00Btw, I did test the memory (memtest86+ v4.0). Its...Btw, I did test the memory (memtest86+ v4.0). Its not the memory, as I suspected.<br /><br />That's not to say that I've eliminated all the other hardware as potential problem sources.<br /><br />But I've had no crashes with Ubuntu. (Still not proof that it isn't hardware -- Ubuntu drivers may not exercise hardware in the same way as Windows -- but it changes the statistics.)<br /><br />I still suspect a bad driver somewhere or kernel level software.Anonymoushttps://www.blogger.com/profile/15319934747521320351noreply@blogger.comtag:blogger.com,1999:blog-7528831701633643336.post-57068579499186730502010-06-07T15:01:28.430-07:002010-06-07T15:01:28.430-07:00FWIW, Microsoft does make their own spyware/malwar...FWIW, Microsoft does make their own spyware/malware product, available from microsoft.com/security_essentials. It's actually pretty decent :)kukhuvudhttps://www.blogger.com/profile/02478004461381483085noreply@blogger.comtag:blogger.com,1999:blog-7528831701633643336.post-7317680470896446842010-06-07T09:26:34.290-07:002010-06-07T09:26:34.290-07:00I'll be happy to do that, but I don't know...I'll be happy to do that, but I don't know what the basis for this claim is.<br /><br />I don't know Windows internals specifically, but I *do* know a lot about other operating systems... and the particular error message sounds very much like an IRQ level assertion problem, which would be more characteristic of a driver bug.<br /><br />If it were bad memory, I'd expect to have other problems, more randomly scattered. (Application crashes, other driver crashes, etc.) Consistently crashing the same way with an IRQ assertion problem feels very unlike a memory problem to me.<br /><br />That said, I will run memtest86+ plus soon.Anonymoushttps://www.blogger.com/profile/15319934747521320351noreply@blogger.comtag:blogger.com,1999:blog-7528831701633643336.post-17706665356933181292010-06-07T09:20:49.844-07:002010-06-07T09:20:49.844-07:00IRQL_NOT_LESS_OR_EQUAL almost always indicates a p...IRQL_NOT_LESS_OR_EQUAL almost always indicates a problem with the physical memory installed in your machine; I'd wager this is neither an OS nor a driver problem, but that your physical hardware is busted. Run Memtest86+ to verify.Jeff Goldschrafehttps://www.blogger.com/profile/13021462028802268588noreply@blogger.comtag:blogger.com,1999:blog-7528831701633643336.post-12611647893110907732010-06-05T07:40:10.855-07:002010-06-05T07:40:10.855-07:00That's too bad. I have also had some BSODs in...That's too bad. I have also had some BSODs in the year that I've been running Windows 7, but they were all related to lousy drivers and/or bad USB-based hardware.<br /><br />It's been my primary OS for about nine months and honestly I couldn't be happier with it. Even the wife has said it's way better than Vista...that's saying something when my non-techie wife claims it.<br /><br />I assume you have found the most recent drivers for your gear. I use VirtualBox regularly with one or two OSes running in it on top of Win 7 with no issues. Oh, I should mention that Windows 7 is VERY picky about RAM. I don't know why, but if you have RAM it doesn't like then your system will be a mess of problems.<br /><br />I attempted to supplement my two 2GB sticks of OCZ RAM with two sticks of 2GB no-name RAM and Windows 7 did not like that at all. Windows XP, CentOS 5.4, and Solaris 10 had no trouble with it, oddly enough.<br /><br />Man, this comment was a lot longer than I intended. Hope it was helpful, at least.Robhttps://www.blogger.com/profile/04396918296899389151noreply@blogger.comtag:blogger.com,1999:blog-7528831701633643336.post-13462830553518481852010-06-04T19:00:05.007-07:002010-06-04T19:00:05.007-07:00Yeah, I leave Windows 7 running in a VirtualBox VM...Yeah, I leave Windows 7 running in a VirtualBox VM on my OpenSolaris host and that's about it...not all that impressed given the cost, and how well FOSS desktop OSs work of late.Anonymousnoreply@blogger.com