What cause the crash?

[pboong]

After peaceful months of using, it happened twice lately.

Need someone to help me to check what is it going on tho..

much appreciated.

 

[zigzag3143]

After peaceful months of using, it happened twice lately.

Need someone to help me to check what is it going on tho..

much appreciated.

Thos crash was caused by your firewire driver ( 1394ohci.sys) I would uninstall it, download a new copy and install.

Let us know if that doesnt fix it[/I]

Ken

 

[Tews]

This crash was caused by your 1394 firewire controller/driver.. download the latest version from your motherboards' website and reinstall...

View attachment 61382

 

[pboong]

Do I go to Device Manager> Firewire > Uninstall it?

Then I reboot, go back there and update it? Is it possible?

Or can I just update it?

Edit:
Did that and my Firewire does not appear on my device manager already. so how to 'call' it out?
Just realise it is a PCI card.

Edit 2:
Found and on latest driver as like before.
Finger crossing

 

[pboong]

Thought I have it re installed and running smoothly until just now, it happened again.

This time, I start up my torrent, open MSE for full scan and it just went BSOD.

Please advise.
Thanks.

 

[zigzag3143]

Thought I have it re installed and running smoothly until just now, it happened again.

This time, I start up my torrent, open MSE for full scan and it just went BSOD.

Please advise.
Thanks.

Same thing as last time your 1394 firewire driver. (1394ohci.sys)


You might also want to run a system file check to verify and repair your system files.

To do that type cmd in search>right click and run as admin>
sfc /scannow (note the space between the sfc and "/")

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\032210-29687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e1c000 PsLoadedModuleList = 0xfffff800`03059e50
Debug session time: Mon Mar 22 11:50:21.526 2010 (GMT-4)
System Uptime: 5 days 1:23:36.401
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {8, 57ff40e6308, 3, fffffa8004fdb600}

Unable to load image \SystemRoot\System32\Drivers\Saffire.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Saffire.sys
*** ERROR: Module load completed but symbols could not be loaded for Saffire.sys
Probably caused by : 1394ohci.sys ( 1394ohci!IsochRx::HandleIsochAttachBuffers+5ea )

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

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

WDF_VIOLATION (10d)
The Kernel-Mode Driver Framework was notified that Windows detected an error 
in a framework-based driver. In general, the dump file will yield additional 
information about the driver that caused this bug check.
Arguments:
Arg1: 0000000000000008, An operation occurred on a DMA transaction object while it
    was not in the correct state.
Arg2: 0000057ff40e6308, Reserved.
Arg3: 0000000000000003, Reserved.
Arg4: fffffa8004fdb600, Reserved.

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


BUGCHECK_STR:  0x10D_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88000ecc3e1 to fffff80002e8df00

STACK_TEXT:  
fffff800`043eb278 fffff880`00ecc3e1 : 00000000`0000010d 00000000`00000008 0000057f`f40e6308 00000000`00000003 : nt!KeBugCheckEx
fffff800`043eb280 fffff880`00eca12c : fffffa80`0bf19cf0 0000057f`f40e6308 00000000`00001401 fffffa80`04fdb600 : Wdf01000!FxDmaTransactionBase::Initialize+0xf1
fffff800`043eb2e0 fffff880`0fe81dce : fffffa80`0bf19cf0 00000000`00000000 fffff880`0fe811d8 00000000`00000000 : Wdf01000!imp_WdfDmaTransactionInitialize+0x278
fffff800`043eb380 fffff880`0fe7b847 : fffffa80`00000004 fffffa80`05073890 00000000`00000000 fffff800`043eb4b0 : 1394ohci!IsochRx::HandleIsochAttachBuffers+0x5ea
fffff800`043eb420 fffff880`0fe7ace5 : 0000057f`fc05b658 0000057f`faf8cb18 00000000`00000028 fffffa80`03fa4a08 : 1394ohci!Isoch::HandleIsochAttachBuffers+0xc7
fffff800`043eb480 fffff880`00f10047 : fffffa80`03fa49a0 fffffa80`04fdb600 fffffa80`04fdb600 00000000`00000000 : 1394ohci!Isoch::WdfEvtIoInternalDeviceControl+0x121
fffff800`043eb4f0 fffff880`00f0f99f : fffffa80`050734e0 fffffa80`03fa49a0 fffffa80`050734e0 fffffa80`03fa4a02 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff800`043eb570 fffff880`00f0f1ab : fffffa80`050734e0 00000000`00000002 00000000`00000000 00000000`00000000 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff800`043eb5e0 fffff880`00f0df1e : 00000000`00000002 fffffa80`0506c8d0 fffffa80`050734e0 fffffa80`03fa4ac8 : Wdf01000!FxIoQueue::QueueRequestFromForward+0x1f7
fffff800`043eb640 fffff880`00f0e555 : fffff800`03006e02 fffff780`00000320 fffffa80`0506c8d0 fffff800`02e965f7 : Wdf01000!FxIoQueue::ForwardRequestWorker+0x17a
fffff800`043eb6b0 fffff880`00eebcd6 : 00000000`00000000 fffffa80`04fdb600 00000000`00000000 00000000`00000000 : Wdf01000!FxIoQueue::ForwardRequest+0x185
fffff800`043eb720 fffff880`0fe77440 : fffffa80`050734e0 0000057f`fc05b658 fffffa80`03fa49a0 fffffa80`0506cc80 : Wdf01000!imp_WdfRequestForwardToIoQueue+0x12e
fffff800`043eb770 fffff880`0fe77181 : 0000057f`fc05b658 0000057f`faf93728 00000000`00000028 fffffa80`0506cc80 : 1394ohci!Dispatch::DispatchIrbRequest+0xa8
fffff800`043eb7c0 fffff880`00f10047 : fffffa80`03fa49a0 fffffa80`04fdb600 fffffa80`04fdb600 fffffa80`0840b4c0 : 1394ohci!Dispatch::WdfEvtIoInternalDeviceControl+0x131
fffff800`043eb830 fffff880`00f0f99f : 00000000`00000000 fffffa80`03fa49a0 fffffa80`0506c8d0 fffffa80`0506c8d0 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff800`043eb8b0 fffff880`00f0ef98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`03fa4af2 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff800`043eb920 fffff880`00f14558 : fffffa80`0a403202 fffffa80`03fa49a0 fffffa80`0a403160 fffffa80`03fa49a0 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff800`043eb990 fffff880`00efe245 : fffffa80`03fa49a0 00000000`00000000 00000000`00000000 0000057f`f596dbb8 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff800`043eba10 fffff880`00eea6d0 : 00000000`00000000 00000000`00000000 0000057f`f596dbb8 fffff800`043ebac0 : Wdf01000!FxDevice::Dispatch+0xa9
fffff800`043eba40 fffff880`0fe74d0c : fffffa80`04fdb750 fffffa80`0a692440 fffffa80`0b195020 fffffa80`0c218bb0 : Wdf01000!imp_WdfRequestSend+0x37c
fffff800`043eba90 fffff880`0fe74f2b : fffffa80`07f97120 0000057f`f596dbb8 00000000`00000000 00000000`00000000 : 1394ohci!ChildDevice::DispatchIrbRequest+0x60
fffff800`043ebae0 fffff880`0fe73f0d : 0000057f`f596dbb8 0000057f`f705d3a8 00000000`00000028 fffffa80`0c218bb0 : 1394ohci!ChildDevice::HandleIrbRequest+0x1c3
fffff800`043ebb20 fffff880`00f10047 : fffffa80`0a692440 fffffa80`04fdb600 fffffa80`04fdb600 fffffa80`0afe9000 : 1394ohci!ChildDevice::WdfEvtIoInternalDeviceControl+0x141
fffff800`043ebb90 fffff880`00f0f99f : 00000000`00000000 fffffa80`0a692440 fffffa80`08fa2c50 fffffa80`08fa2c50 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff800`043ebc10 fffff880`00f0ef98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`0a692592 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff800`043ebc80 fffff880`00f14558 : fffffa80`0a403202 fffffa80`0a692440 fffffa80`0a403160 fffffa80`0a692440 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff800`043ebcf0 fffff880`00efe245 : fffffa80`0a692440 fffffa80`0a403160 fffff880`0b8ca900 fffffa80`08531d00 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff800`043ebd70 fffff880`0b8c8a17 : 00000000`00000246 fffffa80`0a403160 fffff880`0b8ca900 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9
fffff800`043ebda0 00000000`00000246 : fffffa80`0a403160 fffff880`0b8ca900 00000000`000007ff 000000ee`824ffd41 : Saffire+0x24a17
fffff800`043ebda8 fffffa80`0a403160 : fffff880`0b8ca900 00000000`000007ff 000000ee`824ffd41 fffffa80`0594c960 : 0x246
fffff800`043ebdb0 fffff880`0b8ca900 : 00000000`000007ff 000000ee`824ffd41 fffffa80`0594c960 fffff800`02f8e687 : 0xfffffa80`0a403160
fffff800`043ebdb8 00000000`000007ff : 000000ee`824ffd41 fffffa80`0594c960 fffff800`02f8e687 fffffa80`07ee7000 : Saffire+0x26900
fffff800`043ebdc0 000000ee`824ffd41 : fffffa80`0594c960 fffff800`02f8e687 fffffa80`07ee7000 fffffa80`0afb3000 : 0x7ff
fffff800`043ebdc8 fffffa80`0594c960 : fffff800`02f8e687 fffffa80`07ee7000 fffffa80`0afb3000 00000000`00000000 : 0xee`824ffd41
fffff800`043ebdd0 fffff800`02f8e687 : fffffa80`07ee7000 fffffa80`0afb3000 00000000`00000000 00000000`00000000 : 0xfffffa80`0594c960
fffff800`043ebdd8 00000000`00000000 : fffffa80`00000000 fffffa80`08531d00 fffffa80`07f97120 fffffa80`041a8590 : nt!PnpRequestDeviceAction+0x217


STACK_COMMAND:  kb

FOLLOWUP_IP: 
1394ohci!IsochRx::HandleIsochAttachBuffers+5ea
fffff880`0fe81dce 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  1394ohci!IsochRx::HandleIsochAttachBuffers+5ea

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: 1394ohci

IMAGE_NAME:  1394ohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc30

FAILURE_BUCKET_ID:  X64_0x10D_8_1394ohci!IsochRx::HandleIsochAttachBuffers+5ea

BUCKET_ID:  X64_0x10D_8_1394ohci!IsochRx::HandleIsochAttachBuffers+5ea

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

 

[pboong]

Thanks zigzag3143.

I just did that and hope it had been fixed after repairing....

 

[pboong]

I have a feeling that it could be the same error from FireWire.

I did as been advised from you all tho.

Could it be my FireWire card have some issue on it that I need to buy a new one?

 

[nickle]

You are using the generic driver from Microsoft (1394ohci.sys). See highlighted in code box:

2: kd> lmvm 1394ohci
start             end                 module name
fffff880`10b7a000 fffff880`10bb8000   1394ohci   (pdb symbols)          c:\websymbols\1394OHCI.pdb\B5D1CCE1A5D840ECBB90BD717B6CDFD21\1394OHCI.pdb
    Loaded symbol image file: 1394ohci.sys
    Mapped memory image file: c:\websymbols\1394ohci.sys\4A5BCC303e000\1394ohci.sys
    Image path: \SystemRoot\system32\DRIVERS\1394ohci.sys
    Image name: 1394ohci.sys
    Timestamp:        Mon Jul 13 20:07:12 2009 (4A5BCC30)
    CheckSum:         000397AE
    ImageSize:        0003E000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    [COLOR=Blue]CompanyName:      Microsoft Corporation[/COLOR]
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     1394ohci.sys
    OriginalFilename: 1394ohci.sys
    ProductVersion:   6.1.7600.16385
   [COLOR=Blue] FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)[/COLOR]
    FileDescription:  1394 OpenHCI Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

You might want to try removing the card and then reinstalling in case there is a loose connection.

Also see if the maufacturer of the card has an updated version of the driver.

If you have not already done so, run the Win 7 Upgrade Advisor to see if your card is completely compatible with Win 7: http://www.microsoft.com/downloads/details.aspx?FamilyID=1B544E90-7659-4BD9-9E51-2497C146AF15&displaylang=en.

Youy card does not appear in your system specs.

 

[pboong]

You are using the generic driver from Microsoft (1394ohci.sys). See highlighted in code box:

2: kd> lmvm 1394ohci
start             end                 module name
fffff880`10b7a000 fffff880`10bb8000   1394ohci   (pdb symbols)          c:\websymbols\1394OHCI.pdb\B5D1CCE1A5D840ECBB90BD717B6CDFD21\1394OHCI.pdb
    Loaded symbol image file: 1394ohci.sys
    Mapped memory image file: c:\websymbols\1394ohci.sys\4A5BCC303e000\1394ohci.sys
    Image path: \SystemRoot\system32\DRIVERS\1394ohci.sys
    Image name: 1394ohci.sys
    Timestamp:        Mon Jul 13 20:07:12 2009 (4A5BCC30)
    CheckSum:         000397AE
    ImageSize:        0003E000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    [COLOR=Blue]CompanyName:      Microsoft Corporation[/COLOR]
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     1394ohci.sys
    OriginalFilename: 1394ohci.sys
    ProductVersion:   6.1.7600.16385
   [COLOR=Blue] FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)[/COLOR]
    FileDescription:  1394 OpenHCI Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

You might want to try removing the card and then reinstalling in case there is a loose connection.

Also see if the maufacturer of the card has an updated version of the driver.

If you have not already done so, run the Win 7 Upgrade Advisor to see if your card is completely compatible with Win 7: Download details: Windows 7 Upgrade Advisor

Youy card does not appear in your system specs.

Thanks.

I didn't know it is using Microsoft driver.

This card is bought from a shop and it is a no-name brand to me. I just plug in, search for new card installed, and update it.

It is no wonder why all my audio suddenly froze until I turn my soundcard off as it is running via FW. Once I turn it off, everything is back to normal.

Previously, I had removed the driver and reinstalled it.

This time, I shall remove the driver, plug out and in of the card, hopefully that it will works.

If it fail again, I have no idea what to do next tho.

Should I purchase a branded Firewire PCI card with good support?
(I did a update scan on my FW and it claimed to be on it's latest firmware)

 

[nickle]

You could leave the card out and if bsods go away then you know it's the card.

 

[pboong]

That will be hard. It does not happen occasionally, it is more of as-and-when situation.