- Thread Author
- #1
Hi,
i hope you guys can help me. i got a motu 828 mk II FireWire lately and it crashes with BSOD and the following symptoms:
1) windows 7 BSOD on boot right after the windows logo before the login screen with a BSOD if i switch the Motu interface on when switching on the PC.
2) when i switch on the motu after windows has completely booted, tehre is no no problem in the first place but might come later
3) windows 7 BSOD sometimes randomly during editing audio-settings or switching programs
4) windows 7 BSOD when i shut down the PC and do not turn off the MOTU before shutting down
5) I have also a "electro-statical" pop when booting the MOTU.
find attached the W7F Diagnosis-zipLink Removed
Link Removed
i hope you guys can help me. i got a motu 828 mk II FireWire lately and it crashes with BSOD and the following symptoms:
1) windows 7 BSOD on boot right after the windows logo before the login screen with a BSOD if i switch the Motu interface on when switching on the PC.
2) when i switch on the motu after windows has completely booted, tehre is no no problem in the first place but might come later
3) windows 7 BSOD sometimes randomly during editing audio-settings or switching programs
4) windows 7 BSOD when i shut down the PC and do not turn off the MOTU before shutting down
5) I have also a "electro-statical" pop when booting the MOTU.
find attached the W7F Diagnosis-zipLink Removed
Link Removed
- Joined
- Mar 22, 2010
- Messages
- 3,046
The zip file with the reports and memory dumps appears corrupted. Please:
- rerun the app, then rezip the folders/reports and upload them again
- upload the zipped archive to a free file-hosting service and post a link to it here.
While waiting for a reply, check the MOTU device on another computer to see if it causes errors there.
- rerun the app, then rezip the folders/reports and upload them again
- upload the zipped archive to a free file-hosting service and post a link to it here.
While waiting for a reply, check the MOTU device on another computer to see if it causes errors there.
- Thread Author
- #3
actually i do not have an SSD installed at all.
the harddrives is actually 3 partitions all on the same drive which is a:
Samsung Spinpoint F1 750GB, 32MB Cache, SATA II (HD753LJ) Preisvergleich | Geizhals Österreich
the power supply is a:
Enermax PRO82+ 425W ATX 2.3 (EPR425AWT) Preisvergleich | Geizhals Österreich
i think i've put the system together beginning of 2009ish.
the harddrives is actually 3 partitions all on the same drive which is a:
Samsung Spinpoint F1 750GB, 32MB Cache, SATA II (HD753LJ) Preisvergleich | Geizhals Österreich
the power supply is a:
Enermax PRO82+ 425W ATX 2.3 (EPR425AWT) Preisvergleich | Geizhals Österreich
i think i've put the system together beginning of 2009ish.
- Thread Author
- #4
- Joined
- Mar 22, 2010
- Messages
- 3,046
- Thread Author
- #6
- Joined
- Mar 22, 2010
- Messages
- 3,046
Third try was the charm! It opened and all the reports are present and readable!
Have you tried the MOTU on another computer?
There are enough signs here that I have to wonder about this installation. Should this be a pirated copy of Windows, please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.
Please provide the MGADiag report according to these instructions (from this post: Product Key Number - Uninstall and Deactivate in Windows - Page 3 - Windows 7 Help Forums ):
Your BIOS dates from 2009. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.
You have a Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter:
Out of 20 memory dumps there were 7 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).
You can get a head start on the hardware diagnostics if you'd like - they are located here: Link Removed
Most of the memory dumps blame either the MOTU (Motufwa64.sys) or the Windows Firewire driver (1394ohci.sys). Also, there's also a hal.dll entry present in the stack text - usually indicative of hardware or compatibility issues.
So, removing the MOTU is the first order of business. If that stops the BSOD's, then you've likely found the culprit. To completely rule it out - see if it causes BSOD's on another system.
Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :
VMNetSrv.sys Wed Jan 16 06:52:01 2008 (478DEFE1)
Microsoft Virtual Machine Network Services Driver
Link Removed
Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Link Removed
vmm.sys Tue Apr 7 09:25:54 2009 (49DB5462)
Virtual Machine Monitor driver - Microsoft Virtual PC 2004
Link Removed
Analysis:
The following is for informational purposes only.
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
DirectIo64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
Have you tried the MOTU on another computer?
There are enough signs here that I have to wonder about this installation. Should this be a pirated copy of Windows, please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.
Please provide the MGADiag report according to these instructions (from this post: Product Key Number - Uninstall and Deactivate in Windows - Page 3 - Windows 7 Help Forums ):
To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - Link Removed )
Once saved, run the tool.
Click on the Continue button, which will produce the report.
To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
Your BIOS dates from 2009. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.
You have a Realtek RTL8187 Wireless 802.11b/g 54Mbps USB 2.0 Network Adapter:
I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.
Out of 20 memory dumps there were 7 different BSOD error codes. The differing error codes are usually symptomatic of a lower level problem within the system. They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (3rd party hardware/drivers)
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Link Removed or Link Removed ).
You can get a head start on the hardware diagnostics if you'd like - they are located here: Link Removed
Most of the memory dumps blame either the MOTU (Motufwa64.sys) or the Windows Firewire driver (1394ohci.sys). Also, there's also a hal.dll entry present in the stack text - usually indicative of hardware or compatibility issues.
So, removing the MOTU is the first order of business. If that stops the BSOD's, then you've likely found the culprit. To completely rule it out - see if it causes BSOD's on another system.
Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :
VMNetSrv.sys Wed Jan 16 06:52:01 2008 (478DEFE1)
Microsoft Virtual Machine Network Services Driver
Link Removed
Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
Link Removed
vmm.sys Tue Apr 7 09:25:54 2009 (49DB5462)
Virtual Machine Monitor driver - Microsoft Virtual PC 2004
Link Removed
Analysis:
The following is for informational purposes only.
Code:
[FONT=lucida console]**************************Sat Jul 20 06:03:29.603 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\072013-31437-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:59.009[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1c130 )[/B]
BugCheck [B]A, {fffffa844909ff58, 2, 0, fffff80002c1a3da}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffffa844909ff58, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c1a3da, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_1394ohci+1c130[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul 17 18:56:46.395 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071813-27984-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:53.739[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!PspReaper+b0 )[/B]
BugCheck [B]C2, {7, 109b, 5cc000d, fffffa800917cb00}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 0000000005cc000d, Memory contents of the pool block
Arg4: fffffa800917cb00, Address of the block of pool being deallocated
BUGCHECK_STR: 0xc2_7
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xc2_7_nt!PspReaper+b0[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul 17 18:54:42.791 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071813-22828-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:14:44.135[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1e815 )[/B]
BugCheck [B]D1, {80000007, 2, 0, fffff88000eaf687}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000080000007, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000eaf687, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xD1_1394ohci+1e815[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul 17 18:38:50.727 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071813-19406-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:06:56.071[/B]
*** WARNING: Unable to verify timestamp for Motufwa64.sys
*** ERROR: Module load completed but symbols could not be loaded for Motufwa64.sys
Probably caused by :[B]Motufwa64.sys ( Motufwa64+31a2b )[/B]
BugCheck [B]1000007E, {ffffffff80000003, fffff88008309a2b, fffff8800a578278, fffff8800a577ad0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffff88008309a2b, The address that the exception occurred at
Arg3: fffff8800a578278, Exception Record Address
Arg4: fffff8800a577ad0, Context Record Address
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x7E_Motufwa64+31a2b[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul 17 18:30:47.094 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071813-19687-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:04:01.438[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1e815 )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_1394ohci+1e815[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul 17 18:25:35.051 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071813-20093-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 4:16:47.395[/B]
*** WARNING: Unable to verify timestamp for Motufwa64.sys
*** ERROR: Module load completed but symbols could not be loaded for Motufwa64.sys
Probably caused by :[B]Motufwa64.sys ( Motufwa64+4b473 )[/B]
BugCheck [B]7F, {8, 80050031, 6f8, fffff8800aae2473}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8800aae2473
BUGCHECK_STR: 0x7f_8
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x7f_8_Motufwa64+4b473[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 15 19:53:05.320 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071613-20843-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 3:42:57.726[/B]
*** WARNING: Unable to verify timestamp for Motufwa64.sys
*** ERROR: Module load completed but symbols could not be loaded for Motufwa64.sys
Probably caused by :[B]Motufwa64.sys ( Motufwa64+13a5d )[/B]
BugCheck [B]1000009F, {4, 258, fffffa8006d27660, fffff80004004510}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8006d27660, The thread currently holding on to the Pnp lock.
Arg4: fffff80004004510, nt!TRIAGE_9F_PNP on Win7
BUGCHECK_STR: 0x9F
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x9F_4_Motufwa64+13a5d[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 15 16:08:57.743 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071513-45921-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:28:48.113[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+14217 )[/B]
BugCheck [B]D1, {8, 2, 1, fffff88002c14217}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88002c14217, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xD1_1394ohci+14217[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 9 16:12:15.258 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070913-24515-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:30:05.665[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1e8b8 )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_1394ohci+1e8b8[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 9 15:40:58.912 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070913-22609-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:20:02.318[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+14371 )[/B]
BugCheck [B]A, {fffff80802210c40, 2, 0, fffff80002ce206a}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffff80802210c40, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ce206a, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_1394ohci+14371[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 9 15:19:52.364 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070913-21750-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:29.786[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1e8b8 )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_1394ohci+1e8b8[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 9 15:07:01.338 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070913-25734-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:44:39.682[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1e7f4 )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_1394ohci+1e7f4[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 9 14:21:13.322 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070913-21421-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:09:53.666[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+14371 )[/B]
BugCheck [B]A, {fffff807f9ef5c40, 2, 0, fffff80002cd206a}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: fffff807f9ef5c40, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cd206a, address which referenced memory
BUGCHECK_STR: 0xA
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xA_1394ohci+14371[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 9 14:10:15.428 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070913-22843-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:23.834[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1e8b8 )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0x1E_1394ohci+1e8b8[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 9 13:44:46.106 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070913-21687-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:53.512[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1e8b8 )[/B]
BugCheck [B]1E, {0, 0, 0, 0}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
BUGCHECK_STR: 0x1E
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: explorer.exe
FAILURE_BUCKET_ID: [B]X64_0x1E_1394ohci+1e8b8[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Jul 8 17:40:44.810 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\070813-29078-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 0:00:33.154[/B]
*** ERROR: Module load completed but symbols could not be loaded for 1394ohci.sys
Probably caused by :[B]1394ohci.sys ( 1394ohci+1e815 )[/B]
BugCheck [B]D1, {ffffb880085741d8, 2, 0, fffff88000efc896}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: ffffb880085741d8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88000efc896, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: [B]X64_0xD1_1394ohci+1e815[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 17 18:00:11.631 2012 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\071812-21015-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: [B]7601[/B].17835.amd64fre.win7sp1_gdr.120503-2030
System Uptime:[B]0 days 3:59:21.975[/B]
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29dcf )[/B]
BugCheck [B]1A, {5003, fffff70001080000, 1f5c, 1f5e80003eb8}[/B]
BugCheck Info: [B]Link Removed[/B]
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 0000000000001f5c
Arg4: 00001f5e80003eb8
BUGCHECK_STR: 0x1a_5003
PROCESS_NAME: chrome.exe
FAILURE_BUCKET_ID: [B]X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+29dcf[/B]
CPUID: "Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz"
MaxSpeed: 2660
CurrentSpeed: [B]2625[/B]
BIOS Version P1.90
BIOS Release Date 02/05/2009
Manufacturer To Be Filled By O.E.M.
Product Name To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]
3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
Code:
[FONT=lucida console]**************************Sat Jul 20 06:03:29.603 2013 (UTC - 4:00)**************************
[COLOR=RED][B]VMNetSrv.sys Wed Jan 16 06:52:01 2008 (478DEFE1)[/B][/COLOR]
[COLOR=RED][B]Rt64win7.sys Thu Feb 26 04:04:13 2009 (49A65B0D)[/B][/COLOR]
[COLOR=RED][B]vmm.sys Tue Apr 7 09:25:54 2009 (49DB5462)[/B][/COLOR]
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
rtl8187.sys Wed Dec 9 04:16:39 2009 (4B1F6AF7)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
avkmgr.sys Thu Sep 15 09:36:11 2011 (4E71FF4B)
atikmpag.sys Thu Apr 5 21:10:44 2012 (4F7E4294)
atikmdag.sys Thu Apr 5 21:48:25 2012 (4F7E4B69)
avgntflt.sys Tue Apr 24 02:14:35 2012 (4F9644CB)
avipbb.sys Thu Apr 26 06:12:40 2012 (4F991F98)
MFWAMIDI64.sys Thu Sep 6 18:13:53 2012 (50492021)
MFWAWAVE64.sys Thu Sep 6 18:13:57 2012 (50492025)
Motufwa64.sys Thu Sep 6 18:14:09 2012 (50492031)
MotuBus64.sys Thu Sep 6 18:15:37 2012 (50492089)
AtihdW76.sys Thu Feb 14 17:11:09 2013 (511D60FD)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul 17 18:56:46.395 2013 (UTC - 4:00)**************************
MAudioDelta.sys Wed Jan 25 21:32:22 2012 (4F20BB36)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Jul 17 18:54:42.791 2013 (UTC - 4:00)**************************
DirectIo64.sys Mon Aug 13 00:30:24 2012 (502882E0)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 9 16:12:15.258 2013 (UTC - 4:00)**************************
AtihdW76.sys Fri May 11 04:25:40 2012 (4FACCD04)
cpuz136_x64.sys Fri May 10 08:42:51 2013 (518CEB4B)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jul 17 18:00:11.631 2012 (UTC - 4:00)**************************
AtihdW76.sys Thu Feb 23 07:30:12 2012 (4F463154)
[/FONT]
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
Link Removed
DirectIo64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Link Removed
Link Removed
Link Removed
- Thread Author
- #8
hey usasma thank for all your help. in fact i do not get any bluescreen without the motu turned on so ther problem is clearly there.
i've updated all my drivers to latest one and cleaned up my installation and now it is working.
i think the switching firewire to the (legacy) drivers did the trick for me. it is working now and if i have another question i will of course ask you again.
i've updated all my drivers to latest one and cleaned up my installation and now it is working.
i think the switching firewire to the (legacy) drivers did the trick for me. it is working now and if i have another question i will of course ask you again.
Similar threads
- Replies
- 0
- Views
- 60
- Replies
- 0
- Views
- 987