Tech Support Forum banner
Status
Not open for further replies.

BSOD and Black Screen

2K views 19 replies 3 participants last post by  LordDWT 
#1 ·
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

Laptop or Desktop?
Desktop.
 

Attachments

See less See more
#7 ·
Sorry for the delay, I got back off holiday today and there's only Patrick covering the threads which can be overwhelming.

Code:
BugCheck 1E, {[COLOR"Red]ffffffffc0000046[/COLOR], fffff80003aff7fc, fffff900c0c25006, fffff80003c06e80}
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.

Code:
fffff880`064759f8 fffff800`03b1d738 : 00000000`0000001e ffffffff`c0000046 fffff800`03aff7fc fffff900`c0c25006 : [COLOR=Blue]nt!KeBugCheckEx[/COLOR]
fffff880`06475a00 fffff800`03b1f790 : fffff880`064764d0 fffff880`064764d0 fffff880`06476310 fffff880`06476570 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`064760a0 fffff800`03ad48fb : fffff880`064764d0 fffffa80`18d23b50 00000000`00000001 00000000`00000000 : [COLOR=Green]nt!KiRaiseException+0x1b4[/COLOR]
fffff880`064761d0 fffff800`03ad1e53 : 00000000`00000000 00000000`00010000 fffff880`00460000 fffff8a0`269b7e96 : [COLOR=Green]nt!NtRaiseException+0x7b[/COLOR]
fffff880`06476310 fffff800`03aff7fc : fffff880`064764d0 fffff880`06476570 00000000`00000001 fffff880`00000004 : [COLOR=Purple]nt!KiSystemServiceCopyEnd+0x13[/COLOR]
fffff880`064764b0 fffff800`03adcfb1 : 00000000`00000008 fffff880`06476ad0 00000000`00000004 00000000`00000000 : [COLOR=Purple]nt!RtlRaiseStatus+0x18[/COLOR]
fffff880`06476a50 fffff880`069f43f0 : fffffa80`00000001 fffffa80`00000001 fffffa80`19754aa0 00000000`00000000 : [COLOR=Red]nt!KeReleaseMutant+0x281[/COLOR]
fffff880`06476b00 fffffa80`00000001 : fffffa80`00000001 fffffa80`19754aa0 00000000`00000000 00000000`00000001 : [COLOR=Red]MS2Filter+0x43f0[/COLOR]
fffff880`06476b08 fffffa80`00000001 : fffffa80`19754aa0 00000000`00000000 00000000`00000001 00000000`00000000 : [COLOR=Cyan]0xfffffa80`00000001[/COLOR]
fffff880`06476b10 fffffa80`19754aa0 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : [COLOR=Cyan]0xfffffa80`00000001[/COLOR]
fffff880`06476b18 00000000`00000000 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR=Cyan]0xfffffa80`19754aa0[/COLOR]
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
You need to update the driver.

Regards,

Jared
 
#13 ·
Code:
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.
 
#15 ·
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).
 
#19 ·
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.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top