bugcheck

[Guest]

I have a workstation which keeps rebooting. The event log shows an event id
1001 with the description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a
(0x00027387, 0x00000002, 0x00000000, 0x804312f)
I've checked around in various places but can't find anything definitive.
Can anyone interperet this for me? Thanks

 

[Matt Wagner [MSFT]]

Maitakeboy:

The 0x0000000A bugcheck is the IRQL_NOT_LESS_THAN_OR_EQUAL. This generally
occures when a kernel process (such as a driver) attempts to access memory
from another process which had a higher interupt request level (IRQL). A
kernel mode process may only access memory from a process at the same or
lower IRQL.

In your particular case:

The instruction at 0x804312f tried to access location 0x00027387 for a read
operation (0x00000000) but needed to be at IRQL 0x00000002 to successfully
read from the memory location.

Have you installed a new driver on the system, or new any new hardware
recently? If you have, try reverting to an earlier driver, or removing the
recently added hardware.

Matt Wagner
Enterprise Engineering Center
Microsoft Corporation


--
Legal Disclaimer:
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

 

[Guest]

That may be the case in some circumstances, but I've got a situation where 6
systems are rebooting every other day at the same time with this bug check
1001 (yet no other errors around that time). All that was done is SP4 was
applied to these systems, and since that was done, this has started and I've
not been able to find any kind of solution from MS or anywhere else.
Everyone talks about hardware, but I don't see hardware or any IRQ settings,
all of a sudden causing 6 systems to reboot at the same time every other day
(also, machines are absolutely virus and trojan free).

SO, it would be great if you had any thing else I could look for...

thanx,

 

[William C. Meyer]

Hi Jason
I know this may sound off the wall but I had a similar problem a few years
ago and it only happened late Friday afternoons! The problem wound up to be
a power related problem and was caused by a late overload on lines and
caused low voltage spikes that caused everything to reboot. They repaired a
transformer and it solved the problem. I not have UPS units on all of my
systems.

 

[Guest]

Uggghhh, this is frustrating!!!

I only wish that were the case here...it just seems to me too much of a
concidence that the day SP4 was pushed to about 700+ systems, these 6 or 7
systems began doing the reboot thing every other day...starting on, you
guessed it, a Friday...

I'm inclined to have the desktop support staff just reaaply SP4 and be done
with it as this issue does not appear to impact any systems beyond this 6 or 7