Please help diagnose this BSoD: 10d

Hello all - any help with diagnosing this blue screen (which is happening around 2 - 3 times a day) on a new installation of Windows 7 Ultimate would be greatly appreciated.

As far as I can tell I've installed all the drivers necessary (nothing comes up as obviously missing in the Device Manager), all software and Windows Update is up-to-date.

System spec:

OS:Windows 7 Ultimate
CPU:Intel Core 2 Quad Q9400 @ 2.66GHz
Motherboard: Intel DP35DP
Memory: 8GB Corsair 800MHz DDR2 RAM
Graphics Card(s): GeForce GTX 285
Sound Card: external: Presonus Firestudio Mobile; MB audio deactivated
Monitor(s) Displays: Dell 24" LCD
Screen Resolution: 1920 x 1200
Hard Drives:
2 x 500 GB Seagate Barracudda sATA (RAID 0)
2 x 1 TB Seagate Barracudda sATA (RAID 0)
PSU: CoolerMaster 600W SilentPro

-------------------

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 5129

Additional information about the problem:
BCCode: 10d
BCP1: 0000000000000008
BCP2: 0000057FF43A4348
BCP3: 0000000000000003
BCP4: FFFFFA800AFF2E70
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

The blue screen itself gives the generic error message: "The windows driver framework has detected that a violation has occurred".

Attached is the zipped dmp file and the xml system data.

Finally I should mention that I've done memory and disk checks and everything reports as fine.

My only suspicion is that this is caused my Daemon Tools Lite that I have on my PC - I've deactivated this for now and will report back if I get another BSoD (or not).

Many thanks in advance!
Shaun

It is difficult to draw conclusions from just one memory dump. Please upload all of them so we can analyze them.

Here's a link with info on the STOP 0x10D error: BSOD Index

The memory dump blames 1394ohci.sys - the Windows 1394 Open OHCI driver. Here's a link to the whitepaper on this driver in Win7: 1394 Bus Driver in Windows 7

I would suggest updating your FireStudio drivers from this website: http://www.presonus.com/technical-su...vers-software/
The memory dump mentions the PaeFireStudio.sys driver - which is a component of the FireStudio program. If this doesn't stop the BSOD's, I'd suggest removing the FireStudio device and re-enabling the onboard sound until we've finished troubleshooting your issues.

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2007 or earlier:

Code:

adfs.SYS     Thu Jun 26 16:52:37 2008 - Adobe File System Filter driver - http://www.carrona.org/dvrref.html#adfs.SYS
HECIx64.sys  Fri May 11 22:00:20 2007 -   Intel(R) Management Engine Interface - http://www.carrona.org/dvrref.html#HECIx64.sys
osaio.sys    Wed Feb 14 04:20:09 2007 - OSA I/O Port Driver" from Avocent/OSA Technologies (likely a component of an Intel desktop utility) - http://www.carrona.org/dvrref.html#osaio.sys
PxHlpa64.sys Mon Dec 10 18:49:01 2007 -Sonic CD/DVD driver (used by many different CD/DVD programs) -http://www.carrona.org/dvrref.html#PxHlpa64.sys

If you're unable to make use of the debugging functions of the driver here: Microsoft Windows USB Core Team Blog : How to generate and view a 1394 debug log (I can't! :)
Then try running Driver Verifier according to these directions (this presumes that it's another, 3rd party driver that's causing the issues with the 1394ohci.sys driver):

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the BSOD:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Mar 24 10:00:42.618 2010 (GMT-4)
System Uptime: 0 days 0:17:41.290
BugCheck 10D, {8, 57ff43a4348, 3, fffffa800aff2e70}
*** WARNING: Unable to verify timestamp for PaeFireStudio.sys
*** ERROR: Module load completed but symbols could not be loaded for PaeFireStudio.sys
Probably caused by : 1394ohci.sys ( 1394ohci!IsochRx::HandleIsochAttachBuffers+5ea )
BUGCHECK_STR:  0x10D_8
PROCESS_NAME:  System

Thanks for letting us know!
Good luck!