I have been having random reboots with no BSOD. Sometimes it will just shutdown the monitor and the PC is still running. I can not reset it or power down with the power button. I have to turn off the power switch and wait 10 seconds or so then turn it back on. I got a BSOD screen today.
Info:
· OS - Windows 7 Ultimate SP1
· x64
· What was original installed OS on system? - Windows 7 Ultimate
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? FULL Retail
· Age of system (hardware). Feb 2013
· Age of OS installation - have you re-installed the OS? It's been a long while. Not sure last install date. Probably Feb 2013
· CPU - AMD FX-8120
· Video Card - AMD Radeon HD 7700 Series
· MotherBoard - MSI 970A-G46 (MS-7693)
· Power Supply - brand & wattage - Coolmax ZU Series ZU-1000B 1000W Power Supply - 80 PLUS Bronze, ATX, Modular
· System Manufacturer - Custom Built
· Exact model number (if laptop, check label on bottom) - Custom Built
Okay, so we have a Kernel mode exception which wasn't handled, this caused the bugcheck.
So what was the exception that caused the bugcheck?
Code:
0: kd> [COLOR=Green]!error ffffffffc0000046[/COLOR]
Error code: (NTSTATUS) 0xc0000046 (3221225542) - [COLOR=Red]An attempt to release a mutant object was made by a thread that was not the owner of the mutant object.[/COLOR]
What does this mean?
Well threads use a synchronization mobject called a mutex object, hence the term 'mutant', Only one thread can own the mutant object at a time and is used to prevent threads form accessing shared memory at the same time.
When shared memory is being referenced the thread must acquire ownership from the mutant object then execute the code, when the code being executed has finished the thread releases the mutant object.
Now you can see where the problem is, a thread released the object which it didn't own and therefore caused an exception which wasn't handled, probably because it was unexpected.
There are a few User Mode functions being made, then we see MS2Filter releasing the mutant object which raises a flag saying "whoa, you can't do that", this generates the exception and the bugcheck.
So what is MS2Filter and why did it release the object?
It belongs to the Gamer Mouse with Tilt Wheel and Launch, so we know what it is but it doesn't explain why it happened?
Well the timestamp says a lot of it, it's nearly 4 years old.
Code:
0: kd> [COLOR=Green]lmvm MS2Filter[/COLOR]
start end module name
fffff880`069f0000 fffff880`069fc500 MS2Filter T (no symbols)
Loaded symbol image file: MS2Filter.sys
Image path: MS2Filter.sys
Image name: MS2Filter.sys
Timestamp: [COLOR=Red]Thu Sep 23 10:29:54 2010[/COLOR] (4C9B1E12)
CheckSum: 0001391E
ImageSize: 0000C500
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Thank you very much Jared!
I have checked with the manufacture website and seems to have a new driver dated 2012.
I will update this and post back in a few days/week to make sure it doesn't keep happening.
I haven't had a random power down or Blue screen since I updated this driver.
So far seems to be fixed.
If it comes back I will be sure to update.
Thank you a ton for your help!
I got another BSOD tonight.
This happened when logging off my kids user profile.
Attached is the Mini Dump.
Thanks in advance for any help you could give.
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: [COLOR=Red]ffffffffc0000046[/COLOR], The exception code that was not handled
Arg2: fffff80003b077fc, The address that the exception occurred at
Arg3: fffff88009ab2bec, Parameter 0 of the exception
Arg4: fffff80003c0ee80, Parameter 1 of the exception
Again it's the same erorr, the thread was trying to release a mutant object which it didn't own.
Code:
3: kd> [COLOR=Green]lmvm MS2Filter[/COLOR]
start end module name
fffff880`06691000 fffff880`0669d500 MS2Filter T (no symbols)
Loaded symbol image file: MS2Filter.sys
Image path: MS2Filter.sys
Image name: MS2Filter.sys
Timestamp: [COLOR=Red]Thu Sep 23 10:29:54 2010[/COLOR] (4C9B1E12)
CheckSum: 0001391E
ImageSize: 0000C500
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Looking at the callstack it's caused by the same driver which still has the same old timestamp. You need to update it as stated before.
Unfortunately that's the problem with some mice which requires a specific 3rd party driver.
If updates don't solve the problem then unfortunately the only solution is to remove the mouse. Unless you're a good programmer and you can rewrite the code (which I can't).
capixdev.sys appears to be referencing invalid memory, there's no documentation on google at all about this driver, I'm not sure what it belongs to.
Can you upload your msinfo32 file.
There's basically no information on it either, it's a file system driver so that makes it slightly easier. Can you just disable all start services that aren't required as it will probably be involved with one of them.
Do you use crashplan tray?
Is it needed, I have a feeling it's part of that.
I use crashplan.
The tray may not be needed.
I'll disable it and give it some time.
Thank you.
Status
Not open for further replies.
You have insufficient privileges to reply here.
Related Threads
?
?
?
?
?
Tech Support Forum
4.7M posts
957.9K members
Since 2002
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!