I also have BSOD with the new Firewire Driver.

I will try the Normal operating mode, and see what's going on then.

I run here Windows 7 Ultimate 64 bit, Flex 5000A, PowerSDR 1.18.5

The Firwire board is a Startech PCI1394MP with a Texas chip on it.

Here the debug report:


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


Loading Dump File [E:\Flexradio\BSOD\042110-24273-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\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.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e44e50
Debug session time: Wed Apr 21 19:00:27.227 2010 (UTC + 2:00)
System Uptime: 0 days 0:50:44.240
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, fffffa8004d4a010}

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

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

1: 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: fffffa8004d4a010, Reserved.

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


BUGCHECK_STR:  0x10D_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  thunderbird.ex

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88000e0333c to fffff80002c77600

STACK_TEXT:
fffff880`02d22df8 fffff880`00e0333c : 00000000`0000010d 00000000`00000005 00000000`00000000 00000000`00001401 : nt!KeBugCheckEx fffff880`02d22e00 fffff880`109dcd06 : fffffa80`04a22530 fffffa80`081edd70 00000000`00014000 fffffa80`04a22530 : Wdf01000!imp_WdfDmaTransactionRelease+0x34 fffff880`02d22e40 fffff880`00e3ff70 : 0000057f`f7e12388 00000762`679d719d 00000000`00000000 fffffa80`081edd30 : 1394ohci!IsochRx::WdfEvtNotificationDpc+0x1ce fffff880`02d22ed0 fffff800`02c82cdc : fffff880`009eb180 fffffa80`0002fa46 fffffa80`081edc70 fffffa80`081edcd8 : Wdf01000!FxDpc::FxDpcThunk+0x78 fffff880`02d22f00 fffff800`02c7d765 : 00000598`00000000 fffffa80`03ff5060 00000000`00000000 fffff880`00e3fef8 : nt!KiRetireDpcList+0x1bc fffff880`02d22fb0 fffff800`02c7d57c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5 fffff880`06ebfbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP:
1394ohci!IsochRx::WdfEvtNotificationDpc+1ce
fffff880`109dcd06 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
---------


73s-Erik-OZ4KK


Try this. If the FLEX Firewire driver's operation mode is set for SafeMode1, 
try setting it to Normal.  Win7 and Vista users reported that mode worked 
better whereas Safemode1 worked better for XP.

I don't think this will be the silver bullet, but it is worth a shot since the 
BSoDs are reproducible.


-Tim

-----Original Message-----
From: [email protected] [mailto:[email protected]] 
On Behalf Of Drax Felton
Sent: Wednesday, April 21, 2010 9:55 PM
To: 'Tim (W4TME)'
Cc: [email protected]
Subject: Re: [FlexEdge] Beta FLEX Firewire driver now available - Update


I am getting multiple BSOD's with the new Firewire driver after leaving it run 
for awhile and walking away.
Seems to be LESS stable under Windows 7  HIHI.

Using the Windows Debugger to analyze the crash dump files I am getting the 
text below:
What else do you need?


-Drax KB3X




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


Loading Dump File [C:\Windows\Minidump\042110-21637-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: c:\symbols
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`02e57000 PsLoadedModuleList = 0xfffff800`03094e50 
Debug session time: Wed Apr 21 16:59:13.616 2010 (UTC - 4:00) System Uptime: 0 
days 0:20:40.927 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, fffffa800871be70}

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

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

3: 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: fffffa800871be70, Reserved.

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


BUGCHECK_STR:  0x10D_5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88000e2d33c to fffff80002ec7600

STACK_TEXT:
fffff880`02ffdbc8 fffff880`00e2d33c : 00000000`0000010d 00000000`00000005 
00000000`00000000 00000000`00001401 : nt!KeBugCheckEx fffff880`02ffdbd0 
fffff880`02c4ad06 : fffffa80`092f9d70 fffffa80`092e1ec0 00000000`00014000 
fffffa80`092f9d70 :
Wdf01000!imp_WdfDmaTransactionRelease+0x34
fffff880`02ffdc10 fffff880`00e69f70 : 0000057f`f6d1e238 00000000`00000000 
00000000`00000000 fffffa80`092e1e80 :
1394ohci!IsochRx::WdfEvtNotificationDpc+0x1ce
fffff880`02ffdca0 fffff800`02ed2cdc : fffff880`02fd5180 00000000`f5af2cc8 
fffffa80`092e1dc0 fffffa80`092e1e28 : Wdf01000!FxDpc::FxDpcThunk+0x78 
fffff880`02ffdcd0 fffff800`02ecfdfa : fffff880`02fd5180 fffff880`02fdffc0 
00000000`00000000 fffff880`00e69ef8 : nt!KiRetireDpcList+0x1bc 
fffff880`02ffdd80 00000000`00000000 : fffff880`02ffe000 fffff880`02ff8000 
fffff880`02ffdd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP:
1394ohci!IsochRx::WdfEvtNotificationDpc+1ce
fffff880`02c4ad06 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
---------





-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Tim (W4TME)
Sent: Wednesday, April 21, 2010 1:07 PM
To: [email protected]
Subject: [FlexEdge] Beta FLEX Firewire driver now available - Update

Just a quick follow up.

With the new FLEX Firewire driver testing, we are looking for reports 
specifically related to the following:

1. Distorted audio
2. Situations where PowerSDR freezes or hangs up 3. System crashes that 
generate BSoDs

If you experience any of these conditions, please be *very* descriptive of 
exactly what you were doing when the problem occurred, can it be reproduced and 
if so what are those steps, provide all of the requisite configuration 
information, (PC operating system, processor type, radio hardware, firmware, 
PowerSDR version, running high power, etc...) and anything else that you feel 
is pertinent. More information is better than less.  If you do experience a 
BSoD, a copy of the crash dump will be extremely important in debugging that 
specific problem.

Thanks again for your help in testing the new driver.

-Tim
---


_______________________________________________
Flexedge mailing list
[email protected]
http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz
This is the FlexRadio Systems e-mail Reflector called FlexEdge.  It is used for 
posting topics related to SDR software development and experimentalist who are 
using alpha and beta versions of the software.

_______________________________________________
Flexedge mailing list
[email protected]
http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz
This is the FlexRadio Systems e-mail Reflector called FlexEdge.  It is used for 
posting topics related to SDR software development and experimentalist who are 
using alpha and beta versions of the software.


--
Venlig hilsen - Best regards - Erik Jakobsen
Licensed HAM-RADIO with the callsign OZ4KK
http://www.urbakken.dk
Registered Linux user #114875 with http://counter.li.org


_______________________________________________
Flexedge mailing list
[email protected]
http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz
This is the FlexRadio Systems e-mail Reflector called FlexEdge.  It is used for 
posting topics related to SDR software development and experimentalist who are 
using alpha and beta versions of the software.

Reply via email to