BSOD - Windows Framework Violation Error. Likely Cause: Alesis iO 26 Drivers?

Zeit

New Member
#1
Hello everyone. I just joined. How are you all?
So, my iO 26 has been running fine for a week, then yesterday, I had no sound coming through it while in Cubase, so I closed Cubase. Then I realised I had no sound at all, so I restarted. Then, on boot up... BSOD! A Windows framework violation fatal error. Now every time I go to initialize audio, be it from a video or an mp3; BSOD.
I've managed to connect the iO 26 without the OS crashing, but yeah, I go a bit further and it dies.
I'm running Windows 7 Home Premium 64 bit. I so need help with this! I record an immense amount of music and it is my passion in life, so I really need my computer running like it had been for the first week, which was near flawless, I was highly impressed.
Thanks in advance.

:)
 


Last edited:

Zeit

New Member
#2
I have installed the handy little program BlueScreenView, and it shows me that the problem appears to be with this file wdf01000.sys. I just thought I'd add that, might make it easier for one of you to help me with this problem. Thanks.
 


Trouble

Noob Whisperer
#3
Hello and welcome to the forums.
First make sure your machine is configured properly to facilitate the collection of .dmp files.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
Then:
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Good luck
Randy
 


Zeit

New Member
#4
Thanks for the info. My dmp file saving is already configured, so the rest I will do soon, and post it here.
 


Trouble

Noob Whisperer
#6
Good job and thanks.
Well you gotta love consistency. All eight dump files attached are virtually identical
EXAMPLE:
Code:
.................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10D, {8, 57ffc189fd8, 3, fffffa80053be5e0}
Unable to load image[COLOR=#ff0000][U][B] AlesisFirewire.sys[/B][/U][/COLOR], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]AlesisFirewire.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [U][B][COLOR=#ff0000]AlesisFirewire.sys[/COLOR][/B][/U]
Probably caused by : 1394ohci.sys ( 1394ohci!IsochTx::HandleIsochAttachBuffers+3ce )
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: 0000000000000008, An operation occurred on a DMA transaction object while it
    was not in the correct state.
Arg2: 0000057ffc189fd8, Reserved.
Arg3: 0000000000000003, Reserved.
Arg4: fffffa80053be5e0, 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 fffff88000e713e1 to fffff80002e7cc40
STACK_TEXT:  
fffff880`02f1a228 fffff880`00e713e1 : 00000000`0000010d 00000000`00000008 0000057f`fc189fd8 00000000`00000003 : nt!KeBugCheckEx
fffff880`02f1a230 fffff880`00e6f12c : fffffa80`03e76020 0000057f`fc189fd8 00000000`00001401 fffffa80`053be5e0 : Wdf01000!FxDmaTransactionBase::Initialize+0xf1
fffff880`02f1a290 fffff880`0f01f36e : fffffa80`03e76020 00000000`00000000 fffff880`0f01e980 fffff880`00000001 : Wdf01000!imp_WdfDmaTransactionInitialize+0x278
fffff880`02f1a330 fffff880`0f016c04 : fffffa80`00000005 fffffa80`055eed90 0000057f`00000006 fffff880`02f1a460 : 1394ohci!IsochTx::HandleIsochAttachBuffers+0x3ce
fffff880`02f1a3d0 fffff880`0f016069 : 0000057f`fc585a28 0000057f`faa11618 00000000`00000028 fffffa80`055eb080 : 1394ohci!Isoch::HandleIsochAttachBuffers+0x100
fffff880`02f1a430 fffff880`00eb5047 : fffffa80`03a7a5d0 fffffa80`053be5e0 fffffa80`053be5e0 00000000`00000000 : 1394ohci!Isoch::WdfEvtIoInternalDeviceControl+0x121
fffff880`02f1a4a0 fffff880`00eb499f : fffffa80`055ee9e0 fffffa80`03a7a5d0 fffffa80`055ee9e0 fffffa80`03a7a602 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`02f1a520 fffff880`00eb41ab : fffffa80`055ee9e0 00000000`00000002 00000000`00000000 00000000`00000000 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`02f1a590 fffff880`00eb2f1e : 00000000`00000002 fffffa80`055eb020 fffffa80`055ee9e0 fffffa80`03a7a6f8 : Wdf01000!FxIoQueue::QueueRequestFromForward+0x1f7
fffff880`02f1a5f0 fffff880`00eb3555 : 00000000`00000002 fffffa80`06668880 fffffa80`055eb020 00000000`00000000 : Wdf01000!FxIoQueue::ForwardRequestWorker+0x17a
fffff880`02f1a660 fffff880`00e90cd6 : 00000000`00000000 fffffa80`053be5e0 00000000`00000000 0000057f`faa14fd8 : Wdf01000!FxIoQueue::ForwardRequest+0x185
fffff880`02f1a6d0 fffff880`0f0128c4 : fffffa80`055ee9e0 0000057f`fc585a28 fffffa80`03a7a5d0 fffffa80`055eb3d0 : Wdf01000!imp_WdfRequestForwardToIoQueue+0x12e
fffff880`02f1a720 fffff880`0f012605 : 0000057f`fc585a28 0000057f`faa14fd8 00000000`00000028 fffffa80`055eb3d0 : 1394ohci!Dispatch::DispatchIrbRequest+0xa8
fffff880`02f1a770 fffff880`00eb5047 : fffffa80`03a7a5d0 fffffa80`053be5e0 fffffa80`053be5e0 00000000`00000000 : 1394ohci!Dispatch::WdfEvtIoInternalDeviceControl+0x131
fffff880`02f1a7e0 fffff880`00eb499f : 00000000`00000000 fffffa80`03a7a5d0 fffffa80`055eb020 fffffa80`055eb020 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`02f1a860 fffff880`00eb3f98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`03a7a722 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`02f1a8d0 fffff880`00eb9558 : fffffa80`06791b02 fffffa80`03a7a5d0 fffffa80`06791ae0 fffffa80`03a7a5d0 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`02f1a940 fffff880`00ea3245 : fffffa80`03a7a5d0 00000000`00000000 00000000`00000000 0000057f`fc3366e8 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`02f1a9c0 fffff880`00e8f6d0 : 00000000`00000000 00000000`00000000 0000057f`fc3366e8 fffff880`02f1aa70 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02f1a9f0 fffff880`0f010178 : fffffa80`053be730 fffffa80`03cc9910 fffffa80`06668880 fffffa80`03f7f920 : Wdf01000!imp_WdfRequestSend+0x37c
fffff880`02f1aa40 fffff880`0f0103af : fffffa80`03a06b10 0000057f`fc3366e8 00000002`daa69500 00001f80`00f10201 : 1394ohci!ChildDevice::DispatchIrbRequest+0x60
fffff880`02f1aa90 fffff880`0f00f289 : 0000057f`fc3366e8 0000057f`fa9fb788 00000000`00000028 fffffa80`03f7f920 : 1394ohci!ChildDevice::HandleIrbRequest+0x1db
fffff880`02f1aad0 fffff880`00eb5047 : fffffa80`03cc9910 fffffa80`053be5e0 fffffa80`053be5e0 00000000`00000000 : 1394ohci!ChildDevice::WdfEvtIoInternalDeviceControl+0x141
fffff880`02f1ab40 fffff880`00eb499f : 00000000`00000000 fffffa80`03cc9910 fffffa80`05604870 fffffa80`05604870 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x56f
fffff880`02f1abc0 fffff880`00eb3f98 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`03cc9a62 : Wdf01000!FxIoQueue::DispatchEvents+0x4df
fffff880`02f1ac30 fffff880`00eb9558 : fffffa80`06791c02 fffffa80`03cc9910 fffffa80`06791ae0 fffffa80`03cc9910 : Wdf01000!FxIoQueue::QueueRequest+0x2bc
fffff880`02f1aca0 fffff880`00ea3245 : fffffa80`03cc9910 fffffa80`06791ae0 fffff880`05ba3ec0 fffffa80`03fb0dc0 : Wdf01000!FxPkgIo::Dispatch+0x37c
fffff880`02f1ad20 fffff880`05ba2067 : 00000000`00000246 fffffa80`06791ae0 fffff880`05ba3ec0 00000000`000007ff : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02f1ad50 00000000`00000246 : fffffa80`06791ae0 fffff880`05ba3ec0 00000000`000007ff fffff880`04985104 : [COLOR=#ff0000][U][B]AlesisFirewire[/B][/U][/COLOR]+0x24067
fffff880`02f1ad58 fffffa80`06791ae0 : fffff880`05ba3ec0 00000000`000007ff fffff880`04985104 00000000`00000005 : 0x246
fffff880`02f1ad60 fffff880`05ba3ec0 : 00000000`000007ff fffff880`04985104 00000000`00000005 fffff880`066dc668 : 0xfffffa80`06791ae0
fffff880`02f1ad68 00000000`000007ff : fffff880`04985104 00000000`00000005 fffff880`066dc668 fffffa80`04757c10 : [COLOR=#ff0000][U][B]AlesisFirewire[/B][/U][/COLOR]+0x25ec0
fffff880`02f1ad70 fffff880`04985104 : 00000000`00000005 fffff880`066dc668 fffffa80`04757c10 fffffa80`0416f000 : 0x7ff
fffff880`02f1ad78 00000000`00000005 : fffff880`066dc668 fffffa80`04757c10 fffffa80`0416f000 00000000`00000800 : 0xfffff880`04985104
fffff880`02f1ad80 fffff880`066dc668 : fffffa80`04757c10 fffffa80`0416f000 00000000`00000800 00000000`00000000 : 0x5
fffff880`02f1ad88 fffffa80`04757c10 : fffffa80`0416f000 00000000`00000800 00000000`00000000 00000000`00000801 : 0xfffff880`066dc668
fffff880`02f1ad90 fffffa80`0416f000 : 00000000`00000800 00000000`00000000 00000000`00000801 00000000`00000000 : 0xfffffa80`04757c10
fffff880`02f1ad98 00000000`00000800 : 00000000`00000000 00000000`00000801 00000000`00000000 206d6457`00000000 : 0xfffffa80`0416f000
fffff880`02f1ada0 00000000`00000000 : 00000000`00000801 00000000`00000000 206d6457`00000000 fffffa80`00000000 : 0x800
STACK_COMMAND:  kb
FOLLOWUP_IP: 
1394ohci!IsochTx::HandleIsochAttachBuffers+3ce
fffff880`0f01f36e 413bc5          cmp     eax,r13d
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME:  1394ohci!IsochTx::HandleIsochAttachBuffers+3ce
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: 1394ohci
IMAGE_NAME:  1394ohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a6a8
FAILURE_BUCKET_ID:  X64_0x10D_8_1394ohci!IsochTx::HandleIsochAttachBuffers+3ce
BUCKET_ID:  X64_0x10D_8_1394ohci!IsochTx::HandleIsochAttachBuffers+3ce
Followup: MachineOwner
So I would see what I could do about addressing
AlesisFirewire.sys 5/3/2010 Documents & Downloads don't know much about the product, looks like a third party software product/pluggin for sound production and manipulation.
While you'e at it catch these up also if possible
LVUSBS64.sys 5/9/2007, lv302a64.sys 5/9/2007, LV302V64.SYS 5/9/2007, from her Logitech - Support & Software Downloads looks like a pretty old logitech camera
Rt64win7.sys 2/26/2009 from here Realtek
Good luck and let us know how you're progressing.
Regards
Randy

EDIT: Additionally, just took a look at your current memory settings and it looks like they are a bit out of whack. Looks like your single 4 gig stick of DDR3-1333 (667Mhz) ram which should be using timings like 9, 9, 9, 24. Is being misidentified or improperly set to act like 400 Mhz with settings of 6, 6, 6, 15. Not that it won't in all likelihood continue to work like that but the degree of under clocking is certainly less than optimal. You may want to address this by either setting the BIOS memory configurator to auto or by setting the proper timings manually yourself. Keep the command rate at 2T
 


Last edited:

Zeit

New Member
#7
Thanks a lot, I love this forum, best help ever! Haha. So, I already have the latest Alesis drivers, so I dunno what to do about that. I'm now downloading the Realtek driver, and when that's installed, I will do the memory configuration in the BIOS. After that, I really don't know what to do. I thought I had the latest webcam driver also, I installed one manually, then Windows updated it during Windows Update a few days ago.
 


Trouble

Noob Whisperer
#8
Well according to the dump file the actual driver that is being blamed for the BSOD is
1394ohci.sys
This is generally a native Windows 7 (Microsoft) driver file and is not usually responsible actually.
But if this firewire adapter is either an addon card or integrated onto the motherboard you may want to check with the actual device manufacturer's or motherboard manufacturer's website to see if they have a more current driver since you are definitely using the default microsoft driver.
Code:
1: kd> lmvm 1394ohci
start             end                 module name
fffff880`0f000000 fffff880`0f03e000   1394ohci   (pdb symbols)          c:\symbols\1394OHCI.pdb\39D04E6E457F4C9E8001D7FAF62CDBE51\1394OHCI.pdb
    Loaded symbol image file: 1394ohci.sys
    Mapped memory image file: c:\symbols\1394ohci.sys\4CE7A6A83e000\1394ohci.sys
    Image path: 1394ohci.sys
    Image name: 1394ohci.sys
    Timestamp:       [U][B][COLOR=#ff0000] Sat Nov 20 04:44:56 2010[/COLOR][/B][/U] (4CE7A6A8)
    CheckSum:         0003B054
    ImageSize:        0003E000
    File version:     [U][B][COLOR=#ff0000]6.1.7601.17514[/COLOR][/B][/U]
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:     [U][B][COLOR=#ff0000] Microsoft Corporation[/COLOR][/B][/U]
    ProductName:     [B][U][COLOR=#ff0000] Microsoft® Windows® Operating System[/COLOR][/U][/B]
    InternalName:     1394ohci.sys
    OriginalFilename: 1394ohci.sys
    ProductVersion:   6.1.7601.17514
    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
    FileDescription:  1394 OpenHCI Driver
    LegalCopyright:   © [COLOR=#ff0000][U][B]Microsoft Corporation[/B][/U][/COLOR]. All rights reserved.
 


Zeit

New Member
#9
Ok, will do. Thanks. The memory settings are already at auto by the way, but the patterns are different to what you said they should be still.
 


#10
Do you recommend these at all?... Unibrain Software Download Section
I tried them before when I tried hooking up my firewire interface to my old computer with a different OS.
 


Trouble

Noob Whisperer
#11
Ok, will do. Thanks. The memory settings are already at auto by the way, but the patterns are different to what you said they should be still.
Not sure what to tell you. I'm just going by the information that the manufacturer for your module provides.
http://www.patriotmemory.com/products/specs/Entertainment Line.pdf
 


Trouble

Noob Whisperer
#12
Do you recommend these at all?... Unibrain Software Download Section
I tried them before when I tried hooking up my firewire interface to my old computer with a different OS.
I have no personal experience with those drivers so I cannot make any recommendation pro or con. What has been your own personal experience when you used them previously? Perhaps someone else will have a comment regarding Unibrain products.
 


Zeit

New Member
#13
I'm back with an update. So, I updated my ethernet controller driver. And I installed the alternative firewire drivers from Unibrain. I couldn't get my interface to work with the Unibrain drivers, which is exactly what happened on my previous OS, Vista Ultimate 32 bit. But the interface didn't work at all on that, even with Microsoft drivers. So I switched back permanently to the Microsoft drivers, then I thought I'd un-install the interface's firewire drivers. Since I'd updated the ethernet controller driver I thought maybe it was just old drivers contributing to the blue screen. Soon I re-installed the firewire interface drivers, and now this was about 3 days ago, and I haven't had a crash since! Weird eh! But, like I said earlier, this Alesis interface worked for the first week fine, then the blue screens started, so who knows if this new installation will be stable permanently. Only time will tell. Thanks again for all the help. I'll stay more on top of my drivers from now on and maybe everything will be fine.
 


Last edited:

Zeit

New Member
#14
I just had the first blue screen 5 minutes ago, bah! I'm running out of ideas now.
 


#15
Hello again. So, no one has any further ideas for a solution for this problem? I do feel that it may be a matter of Alesis updating their drivers for 64 bit operating systems, which could be a long, long time, but if anyone else has suggestions... I really need to solve this within the next few months because I am scheduled to produce a demo for some friends and their heavy metal band. Any more help would be greatly appreciated. Thank you.
 


Last edited:

Elmer

Extraordinary Member
#16
You got the latest dump files?
 


#17
Hi Elmer. There are no more dump files. My audio interface hasn't been connected for a while because of the error. I'm sure they would be pretty much identical anyway like Trouble said. I guess I should connect it up and see how it goes for a while eh!
 


Trouble

Noob Whisperer
#18
Have you considered contacting the vendor iO|26 or Contact Alesis and explaining the issue and see if they have any suggestions as to a solution or perhaps a recommendation for either using an older driver package or even maybe a beta driver package that they may be working on. It's not likely you are the only person on the planet with this issue, perhaps they are already familiar with the problem and may have a remedy.
Regards
Randy
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top