I won't try and explain exactly what that means as there are plenty of explanations of IRQ levels on the web but basically all of the applications that you actually see on your screen run in what is known as "user mode" where as device drivers and some system services run in "kernel mode".
User mode processes must always be run at IRQL 0, only code running in kernel mode can be executed when the IRQL is raised above 0, and your BSOD was basically caused by some kernel mode code finished and returning control back to user mode code before the IRQL had been lowered back to 0.
So I would say this is probably due to a bug in some third party driver code, but its possible it could be caused by a hardware problem and the driver just isn't handling it very well. So like I said you need to examine the crash dump which is basically a copy of everything that was held in memory at the time of the BSOD in WinDbg to see which driver or system file it was that was actually executing when the blue screen was triggered.
Also in the install wizard, untick everything apart from "Debugging Tools For Windows" otherwise it will take forever to download and install. Thanks,, I am installing it now.. I read similar things online, just wanted to confirm with the real experts.
Let me get the software installed and take a look at the dump file,. Oh and they've changed the wording of that page I linked you to and made it quite confusing. OK no worries : I've just added some notes to the previous post too but you've probably already got past that point in the install now anyway - EDIT: Ah I see you've seen it already. Oh and one more thing - once you've got WinDbg installed you need to specify the Microsoft Symbol server so that it can download information about the Windows modules that were loaded in memory in the crash dump you are opening.
Then close WinDbg and click Yes when prompted to save. I was like.. I got further, but have no idea what this means now.. Microsoft R Windows Debugger Version 6. All rights reserved. Type ". Page d6faf not present in the dump file. Makes sense I guess but I was hoping it would be the actual culprit driver itself that was going to be the last thing to run rather than a general system program.
It might be worth running the "! Just type it in without the quote marks to the command box at the bottom of the window and press enter then wait for a while and post the output when its finished.
Thanks, that is what I was thinking, that it had to do with the ntkrnlmp. OO OK.. I do have that installed, but need to remove it and install Vipre in place of it, but have not been able to send the server thru a reboot. I will have to schedule that. Sorry for freaking out, but i had that server already crash hard once, and its still 9 months later on a temp server But then again, I don't make the calls.
I may virtualize it, but need to make sure that won't cause issues first. I can't see it being an issue, but I have had people say not to do it. We run almost all 40 of ours servers as virtual servers, though there are some rare scenarios where its not possible or might cause problems, I'd be surprised if you can't just virtualize it. But anyway yeah, I think you should just uninstall MSE and install your replacement software as soon as possible. I know you don't want to have to reboot the server but maybe tell people its either that or they run the risk of the server just shutting itself down randomly again and that could potentially loose their work.
I totally aggree.. I am already trying to schedule a downtime of the entire network to get some maintenance done on it, which i have been wanting to do for a while. I need to get one of my UPS' batteries replaced i have the batteries already that run my 1 and only Hyper-V server, which contains most of my servers.
I need to get all servers up to date. If you are interested, please email redistpm microsoft. Need more help? Expand your skills. Get new features first. A subscription to make the most of your time. Try 1 month free. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help.
Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical.
Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:.
Archived Forums. Windows Server General Forum. Sign in to vote.
0コメント