BSOD mini dmp what does this mean? Thanks!

Did already test all of my HD's with windows 7 tests but guess I have to with the WD tools (got 3 WD 2 internal 1 external). :S

JeeSSSSUS chrisssssssssssssssttttttt I am going mad now. So all I want to do is use the WD's tool - the new data life guard ones - so I do it all correctly and burn it to a CD - reboot and nothing - a cursor point top left thats it then I try burning another one to a DVD this time it loads but then a blank screen. Then I see that author in the link has had problems too and I gotta use SEAGATE tools WTF why are these companies so shit at all this stuff! Anyway sorry had to rant...you think seagate tools are fine then? Sigh I will use them anyway now....

Jonathan_King said:

Try updating the SATA controller drivers in Device Manager, or the manufacturer's site.

You may also try uninstalling them and rebooting. Be sure to create a restore point first, though.

System Restore Point - Create

Hmm created restore point but I cant find any WD drivers :S WD Support > Downloads > SATA & SAS > WD VelociRaptor I am a bit worried about un-installing the drivers for my system drive - is that what you ment? un install from ata device properties after right clicking hard drive in device manager? Or do you mean the standard ACHI 1.0 serial ATA controller or some other bit? Heres a pic :

Yep I finally found something certain! The power cable to the system HD was dodgy - it was powering off. So I have changed the connection now so it should be stable but I got another BSOD! Basically I was burning a DVD of my work using convertXtodvd 3 it got to 99.9 percent finished and then the dvd started spinning at top speed and just stayed like that for ages. So eventually I had to open task manager and end the process convertXtoDVD but just as I did this it BSOD. Heres the info:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Dom\Desktop\062610-20202-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c50000 PsLoadedModuleList = 0xfffff800`02e8de50
Debug session time: Sat Jun 26 19:10:03.798 2010 (UTC + 1:00)
System Uptime: 0 days 5:09:45.437
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000046, fffff80002ceeef8, fffff8800790a8c0, 0}

Unable to load image \SystemRoot\System32\Drivers\pcouffin.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pcouffin.sys
*** ERROR: Module load completed but symbols could not be loaded for pcouffin.sys
Probably caused by : pcouffin.sys ( pcouffin+9a80 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000046, Exception code that caused the bugcheck
Arg2: fffff80002ceeef8, Address of the instruction which caused the bugcheck
Arg3: fffff8800790a8c0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000046 - An attempt to release a mutant object was made by a thread that was not the owner of the mutant object.

FAULTING_IP:
nt!RtlRaiseStatus+18
fffff800`02ceeef8 488b8424b8010000 mov rax,qword ptr [rsp+1B8h]

CONTEXT: fffff8800790a8c0 -- (.cxr 0xfffff8800790a8c0)
rax=0000000000000000 rbx=00000000c0000046 rcx=fffff8800790a8c0
rdx=0000000000000001 rsi=0000000000000001 rdi=fffff88002fd5180
rip=fffff80002ceeef8 rsp=fffff8800790a800 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffff8800790ae18 r12=0000000000000000 r13=0000000000000000
r14=fffffa8006ea4960 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000286
nt!RtlRaiseStatus+0x18:
fffff800`02ceeef8 488b8424b8010000 mov rax,qword ptr [rsp+1B8h] ss:0018:fffff880`0790a9b8=fffff80002ceeef8
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: ConvertXtoDvd.

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002cc9520 to fffff80002ceeef8

STACK_TEXT:
fffff880`0790a800 fffff800`02cc9520 : fffffa80`084f1d80 fffffa80`084f1c50 fffff880`0404d890 fffff880`04046000 : nt!RtlRaiseStatus+0x18
fffff880`0790ada0 fffff880`0404fa80 : fffff8a0`00000001 fffffa80`00000001 fffffa80`0e369600 00000000`00000000 : nt!KeReleaseMutant+0x260
fffff880`0790ae50 fffff8a0`00000001 : fffffa80`00000001 fffffa80`0e369600 00000000`00000000 00000000`00000000 : pcouffin+0x9a80
fffff880`0790ae58 fffffa80`00000001 : fffffa80`0e369600 00000000`00000000 00000000`00000000 fffff800`02ce7956 : 0xfffff8a0`00000001
fffff880`0790ae60 fffffa80`0e369600 : 00000000`00000000 00000000`00000000 fffff800`02ce7956 fffff8a0`0d4c81b0 : 0xfffffa80`00000001
fffff880`0790ae68 00000000`00000000 : 00000000`00000000 fffff800`02ce7956 fffff8a0`0d4c81b0 fffff8a0`0d4c81b0 : 0xfffffa80`0e369600


FOLLOWUP_IP:
pcouffin+9a80
fffff880`0404fa80 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: pcouffin+9a80

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: pcouffin

IMAGE_NAME: pcouffin.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 457584a2

STACK_COMMAND: .cxr 0xfffff8800790a8c0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_pcouffin+9a80

BUCKET_ID: X64_0x3B_pcouffin+9a80

Followup: MachineOwner
---------


So basically I am wondering its this corrupted due to the power failures to the HD before or am I maybe getting other power failures elsewhere or its totally unrelated etc...the weird thing is that I burnt stuff just before and I did 2 more after and it was fine (after restart). Thanks!