• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

The computer has rebooted from a bugcheck

Amused

Elite Member
Had a random restart while the computer was unattanded this morning.

This was the bugcheck in event viewer:

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x006d0079, 0x00000002, 0x00000000, 0x804e6ccb).

6 days ago it did much the same thing, but this was the code:

0x1000008e (0xc0000005, 0x805505a1, 0xa89a38a0, 0x00000000)

Can anyone tell me what this points to?

The system is over 2 years old and it's never done this before.
 
Stop 0xA is a irql_not_less_or_equal.

Very likely cause: bad driver. Often the offending driver will be mentioned in the bugcheck.

less likely causes:
old bios, bad memory (use memory diags)

Start by updating drivers on the system for this one.



Stop 0x8E is a kernel_mode_exception_not_handled.

Again very likely a bad driver. culprit often indicated in the bugcheck. The 0xc0000005 parameter indicates an access violation.

less likely causes:
old bios, bad memory, irq conflicts (unlikely on an acpi system).

Again start by updating drivers on the system.


note that each of these individually indicates a likely driver issue. Definately start there. However cumulatively they could be signs of a hardware issue. *IF* you get a 3rd bugcheck type on the box it would almost certainly be a hardware issue. Until that happens though start by getting updates on the system. If you typically keep your system fully updated and have recently installed a new driver it could have a regression. you can try rolling back one version in that case.

 
Back
Top