If you have IRQL_NOT_LESS_OR_EQUAL please see my blog: What is an IRQL<http://www.adopenstatic.com/cs/blogs/ken/archive/2006/10/01/causes_2c00_-and-tips-for-debugging_2c00_-a-stop-0x0000000a-_2800_irql_5f00_not_5f00_less_5f00_or_5f00_equal_2900_-bugcheck_2f00_blue-screen-_2d00_-part-1.aspx> and what is a NOT_LESS_OR_EQUAL issue How to debug IRQL_NOT_LESS_OR_EQUAL<http://www.adopenstatic.com/cs/blogs/ken/archive/2006/10/03/Causes_2C00_-and-tips-for-debugging_2C00_-a-STOP-0x0000000A-_2800_IRQL_5F00_NOT_5F00_LESS_5F00_OR_5F00_EQUAL_2900_-bugcheck_2F00_blue-screen-_2D00_-Part-2.aspx> issue How to use Driver Verifier<http://www.adopenstatic.com/cs/blogs/ken/archive/2007/01/09/1005.aspx>
Cheers Ken From: Free, Bob [mailto:[EMAIL PROTECTED] Sent: Saturday, 25 October 2008 11:42 AM To: NT System Admin Issues Subject: RE: Checking what services are firing up and when. Stop 0000000a AKA IRQL_NOT_LESS_OR_EQUAL This Stop message indicates that a kernel-mode process or driver attempted to access a memory address to which it did not have permission to access. The most common cause of this error is an incorrect or corrupted pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has an incorrect value in it, the program tries to access memory that it should not. When this occurs in a user-mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message. If you encounter this error while upgrading to a newer version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. Google Stop 0000000a and there are plenty of suggestions. From: David McSpadden [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2008 11:56 AM To: NT System Admin Issues Subject: RE: Checking what services are firing up and when. Error code 0000000a, parameter1 00000001, parameter2 d000001b, parameter3 00000001, parameter4 8083df4c. ________________________________ From: Bob Fronk [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2008 2:36 PM To: NT System Admin Issues Subject: RE: Checking what services are firing up and when. Turn off automatic reboot so you can see the BSOD. Or is it actually doing a "clean reboot" where it shows it is shutting down? Event viewer says....? Bob Fronk [EMAIL PROTECTED] From: David McSpadden [mailto:[EMAIL PROTECTED] Sent: Friday, October 24, 2008 2:23 PM To: NT System Admin Issues Subject: Checking what services are firing up and when. I have a server that is rebooting itself. Now none of my operators will tell me who loaded what and I really don't care. I need to see what services or driver is causing my reboots about every 5 minutes. I have ran MSConfig and stopped all none windows stuff and it stays up all week. If I let everything run in normal it boots at just about 2 to 5 minutes each time. What can I run that will help me find this animal and remove it or get the correct version loaded. Standard Server 2003 with IIS and File and print services enabled. Data Security is everyone's responsibility ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
