http://www.windowsitpro.com/authors/author/author/5777272/rsscomment/5777272en-USSun, 27 May 2012 07:12:50 GMTSun, 27 May 2012 07:12:50 GMThttp://www.windowsitpro.com/article/internals-and-architecture/the-blue-screen-of-death#commentsAnchorMon, 09 May 2005 06:54:17 GMT
I have done all the steps mentioned and obtained memory.txt but the file is of 0MB but the actuall user.dmp is of 4MB size. I need this user.dmp fiel in readable format.Pls guide me .. Thanx in Advance kmk]]>kmkMon, 09 May 2005 06:54:17 GMThttp://www.windowsitpro.com/article/internals-and-architecture/the-blue-screen-of-death#commentsAnchorhttp://www.windowsitpro.com/article/internals-and-architecture/the-blue-screen-of-death#commentsAnchorThu, 16 May 2002 14:50:33 GMT
I am looking forward to reading the Blue Screen of Death article because I am having a problem with the KERNEL and DLL. At quick glance I see the article refers to this problem in connection with using Windows NT. I am not using Windows NT and am using Windows ME 2000 on something called an etower by a company called emachines. I will read the article and try to understand it before I start screaming for more help! I’ve been using a computer and the Internet for several years but still have trouble learning what I need to know to keep it working in good order. I do appreciate the Windows&.Net Magazine and really appreciate the response I receive from you tech support person. With this site on my "favorites" I hope to slowly gain some of the knowledge I need. Thanks. RA]]>Ru Aaronson Thu, 16 May 2002 14:50:33 GMThttp://www.windowsitpro.com/article/internals-and-architecture/the-blue-screen-of-death#commentsAnchorhttp://www.windowsitpro.com/article/internals-and-architecture/the-blue-screen-of-death#commentsAnchorFri, 13 Aug 1999 09:53:33 GMT
I was excited to see Mark T. Edmead’s “The Blue Screen of Death” in your June issue. As a consulting partner in a firm that works on nothing but NT internals, I figure a lot of our clients can learn from an article on NT’s infamous blue screen of death.
The only problem is that much of what they’ll learn from this article is wrong. The article is absolutely rife with technical errors. For example, the second sentence in the section headed “What Does This Weird Screen Mean?” reads, “The kernel STOP may mean that a kernel driver ... has illegally accessed the privileged kernel area.” This statement is very close to meaningless, and any meaning I can attach to it is wrong. Kernel drivers are privileged (i.e., they run in kernel mode) and have full access to the kernel area.
Another example? Let’s take Table 1: Kernel Mode Error Conditions. The first entry for IRQL_NOT_LESS_OR_EQUAL tells the reader, “A process attempted to access pageable memory at a process internal request level (IRQL) that was too high.” That statement is one reason for getting this error. But it’s not the reason.
The text continues, “A process can access only objects that have priorities (IRQL) equal to or lower than its own.” This statement is nonsense. Objects don’t have IRQLs. IRQLs are not typically associated with processes (with one exception). The IRQL indicates the CPU state at any point in time, relative to that CPU’s interruptability, preemptability, and dispatchability. That is, the IRQL identifies which devices can interrupt the CPU, whether at the end of a quantum the current thread will be rescheduled, and whether any scheduling operations at all are allowable.
Yikes! I found plenty of other technical problems in the article, too.
I’ve spent lots of time reading blue screens and debugging drivers, so I recognized the problems with this article. How many of your readers can say the same?
--Peter G. Viscarola

Thanks, Peter, for pointing out these problems. We’ll be very careful not to let such errors slip by in the future, and we apologize for any inconvenience these errors may have caused anyone.
--Karen Forster]]>Peter G. Viscarola Fri, 13 Aug 1999 09:53:33 GMThttp://www.windowsitpro.com/article/internals-and-architecture/the-blue-screen-of-death#commentsAnchorhttp://www.windowsitpro.com/article/systems-administrator/essential-windows-nt-system-administration#commentsAnchorWed, 11 Aug 1999 14:05:55 GMT
I’m writing in response to the August review of my book, Essential Windows NT System Administration. The review presents a misleading impression of the purpose, scope, and content of the book. In particular, the review contains three inaccuracies about the book’s content. First, the review asserts that a large portion of the book consists of discussions of Perl and other scripts to automate common tasks. This material is in the book, but it’s not the book’s central focus, as the review suggests. One chapter of the book (and a couple of brief references in other chapters) covers automation. Second, the book is not aimed at or useful to only UNIX users moving to Windows NT. I devoted one appendix to helping UNIX administrators migrate more easily, but I wrote every chapter of the book to be accessible by either UNIX or non-UNIX readers. As the preface clearly states, the book is not intended for administrators who are already NT wizards. It’s aimed at beginning and intermediate NT administrators, including administrators migrating from other operating system (OS) environments and administrators with experience as NT users. Finally, the review states that the book covers only tools for NT systems administration and presents a superficial treatment of the topic in general. Even a quick examination of the book’s contents will reveal this observation to be false. The organization is task-based; every chapter provides background information about the systems administration task under consideration and discusses administrative techniques and procedures in the context of that task. The book covers standard NT features as well as other items (resource kit tools, free software, third-party products, scripts) that an administrator might need to get the job done. All in all, I’m very disappointed and concerned about the misleading impression of the book that results from this review. People can disagree about how well something fulfills the purpose it’s intended for, but as far as this review is concerned, we don’t seem to be looking at the same book.
--AEleen Frisch]]>AEleen Frisch Wed, 11 Aug 1999 14:05:55 GMThttp://www.windowsitpro.com/article/systems-administrator/essential-windows-nt-system-administration#commentsAnchor