BSOD in Windows 7 Ultimate 64bit UK

[darkhorse]

Hi.

I have problems with BSOD in my Windows 7 Ultimate 64bit UK.
I suspect it is a 1394 Firewire board or it's driver, that causes the problem.

For investigation, I have atatched a photo of the screen, and 2 dmp files.

Hope to get info for it, thanks

 

[zigzag3143]

Hi.

I have problems with BSOD in my Windows 7 Ultimate 64bit UK.
I suspect it is a 1394 Firewire board or it's driver, that causes the problem.

For investigation, I have atatched a photo of the screen, and 2 dmp files.

Hope to get info for it, thanks

Your suspicions are correct. These were caused by your firewire driver. I also noted that Wdf01000.sys was loaded in all of them.

I would
download and install a fresh copy of the firewire driver
run a system file check to verify and repair your system files. (wdf01000.sys)
to do that type cmd in search>right click and run as admin>sfc /scannow (note the space between sfc and "/")

Let us know the result of the SFC as you may need to re-run it

Let us know if you need help

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\New folder (3)\031710-28282-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a59000 PsLoadedModuleList = 0xfffff800`02c96e50
Debug session time: Wed Mar 17 06:39:23.701 2010 (GMT-4)
System Uptime: 0 days 0:16:02.590
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {5, 0, 1401, fffffa8004e44e70}

Probably caused by : 1394ohci.sys ( 1394ohci!IsochRx::WdfEvtNotificationDpc+1ce )

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: 0000000000000005, A framework object handle of the incorrect type was passed to
    a framework object method.
Arg2: 0000000000000000, The handle value passed in.
Arg3: 0000000000001401, Reserved.
Arg4: fffffa8004e44e70, Reserved.

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


BUGCHECK_STR:  0x10D_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88000ef233c to fffff80002acaf00

STACK_TEXT:  
fffff800`00ba2df8 fffff880`00ef233c : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001401 : nt!KeBugCheckEx
fffff800`00ba2e00 fffff880`045b9d06 : fffffa80`052e5158 fffffa80`0528bbb0 00000000`00014000 fffffa80`052e5158 : Wdf01000!imp_WdfDmaTransactionRelease+0x34
fffff800`00ba2e40 fffff880`00f2ef70 : 0000057f`fad74548 fffff800`00ba2f50 00000000`00000000 fffffa80`0528bb70 : 1394ohci!IsochRx::WdfEvtNotificationDpc+0x1ce
fffff800`00ba2ed0 fffff800`02ad65dc : fffff800`02c43e80 fffffa80`0528bab0 fffffa80`0528bab0 fffffa80`0528bb18 : Wdf01000!FxDpc::FxDpcThunk+0x78
fffff800`00ba2f00 fffff800`02ad1065 : 00000000`00000000 fffffa80`04114060 fffff800`00ba2f30 fffff880`00f2eef8 : nt!KiRetireDpcList+0x1bc
fffff800`00ba2fb0 fffff800`02ad0e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`07375ae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
1394ohci!IsochRx::WdfEvtNotificationDpc+1ce
fffff880`045b9d06 488b4d18        mov     rcx,qword ptr [rbp+18h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  1394ohci!IsochRx::WdfEvtNotificationDpc+1ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: 1394ohci

IMAGE_NAME:  1394ohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc30

FAILURE_BUCKET_ID:  X64_0x10D_5_1394ohci!IsochRx::WdfEvtNotificationDpc+1ce

BUCKET_ID:  X64_0x10D_5_1394ohci!IsochRx::WdfEvtNotificationDpc+1ce

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

031710-24211-01.dmp    3/17/2010 11:23:48 AM        0x0000010d    00000000`00000005    00000000`00000000    00000000`00001401    fffffa80`04f4ce70    Wdf01000.sys    Wdf01000.sys+333c                    x64        C:\Users\K\Desktop\New folder (3)\031710-24211-01.dmp    2    15    7600    
031710-28282-01.dmp    3/17/2010 11:40:34 AM        0x0000010d    00000000`00000005    00000000`00000000    00000000`00001401    fffffa80`04e44e70    Wdf01000.sys    Wdf01000.sys+333c                    x64        C:\Users\K\Desktop\New folder (3)\031710-28282-01.dmp    2    15    7600    
032510-28875-01.dmp    3/25/2010 12:08:52 PM        0x0000010d    00000000`00000008    0000057f`fbf65588    00000000`00000003    fffffa80`04f45c40    Wdf01000.sys    Wdf01000.sys+53e1                    x64        C:\Users\K\Desktop\New folder (3)\032510-28875-01.dmp    2    15    7600

 

[darkhorse]

@Ken

I'm very happy for your help, thanks a lot.

I ran the sfc /scannow, but it couldn't find anything to do.
(Look at the attachment)

I tried to find a new driver for the Firewire board, but it seems difficult to find.
It's a Startech PIC1394MD with a Texas Instruments chip TSB43AB23.
(Attachment)

Can you help me with finding a new driver for it ?, and shall I try the sfc /scannow again ?

Erik

 

[darkhorse]

Is there not anything I can do ?.

Erik

 

[darkhorse]

If I cannot find a dmp file in \Windows\minidump\, where is then to be found after a BSOD ?.