Bugcheck 0x162 - KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE

[jcgriff2]

Came upon 0x162 for the first time today.

Info on 0x162 from carrona.org - BSOD Index

KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE

OP has 50 dumps; 85 total BSODs that started on 13 Feb 2015.

In addition to the 0x162, other kernel related bugchecks -

0x133 - DPC_WATCHDOG_VIOLATION
0x139 - KERNEL_SECURITY_CHECK_FAILURE
0x1 - APC_INDEX_MISMATCH (internal kernel error)

... + the usual "exception bugchecks" like 0x1e (0xc5,,,) + others like 0x50, 0xa, 0xd1, 0x7f (0x8,,,), etc...

https://www.sysnative.com/forums/bsod-crashes-kernel-debugging/13981-several-bsods.html#post103121

I'm thinking hardware failure or perhaps infection. Anyone have any other ideas?

Corruption of some kind is evident as systeminfo reported:

Code:
System Locale:            [COLOR=#ff0000] el;„¢¢ž¤ ¡á[/COLOR]
Input Locale:              [COLOR=#ff0000]el;„¢¢ž¤ ¡á[/COLOR]
Time Zone:                 (UTC+02:00) [COLOR=#ff0000]€Ÿã¤˜, �¦¬¡¦¬¨â©«[/COLOR]

System language is Greek, but that obviously is not [the language] Greek. It does look like Greek, though!

Thanks,

John

 

[usasma]

It's all Greek to me (yuck yuck!!!)
Seriously, it's appears to be Greek, but Google translate said some was Icelandic. Still didn't make any sense to me.
It looks like the standard text associated with BSOD errors¸blah blah blah STOP error: 0x00000050 (0xfffff901409e4000, 0x0000000000000001, 0xfffff96000147b48, 0x0000000000000000). Memory dump created: C:\Windows\MEMORY.DMP. Minidump named this: 042915-160312-01.

locale: el is Greek

Characters can come out messed up if using different languages - but they can also be messed up due to hardware problems.
This looks like hardware, but you can have them run Driver Verifier "just in case"

 

[x BlueRobot]

That bugcheck is possibly related to some form of synchronization failure. From what I can gather, it is related to a bug in Windows 8.1. Have you checked for any updates?

OSR's ntdev List: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE in W8.1

 

[Jared]

That bugcheck is possibly related to some form of synchronization failure. From what I can gather, it is related to a bug in Windows 8.1. Have you checked for any updates?

OSR's ntdev List: KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE in W8.1

AFAIK, it's a syncrhonisation issue with mutexes and how they are boosted. I'm not 100% sure on what boosting it does, it's difficult to find anything on it.

 

[x BlueRobot]

I couldn't find much about it either, just other threads relating to the bugcheck.

 

[jcgriff2]

The weird symbols appearing + a few "unknown module" PCB leaves me with the opinion of kernel corruption caused by unknown hardware failure.

 

[Patrick]

0x162 is an 8.1 bug check only, as prior to 8.1, if this issue happened, there was no bug check.

Think of Windows before tablets (i.e 8), and when you froze due to a DPC hanging or an ISR going without being serviced, you hung inevitably possibly forever or until it was serviced, which wasn't always possible. When tablets launched, so did 8, and a bug check was invited (0x133) so if it ever happened on a tablet device, you didn't have to do an ACPI reset and just bug checked instead.

 

[Rogue7]

Has this been resolved because I am getting this cluster of Bsod's and it keeps hinting at a hardware failure. I just ordered a new psu in hopes it might be that but aside from that I am completely lost. any help at all is greatly appreciated!

hopefully the scan might help.