Windows 7: Frequent & Random BSOD, Bugcheck code: 0x9F (0x3...)

As the title suggests, my BSODs seem to be random. They come while typing email, writing a word document, or doing nothing. I cannot associate it with any particular activity, software, action, button-click, etc. No recent software changes that I know of. I think that I have all of my drivers up to date.



Windows_NT6_BSOD_jcgriff2.zip attached.

System Info:
Windows 7 Home Premium, x64, SP1
- This is the original OS installed, OEM (self-built system)
- Approximately 1 year old

Here is some information extracted from WhoCrashed:

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4285980672 total
VM: 2147352576, free: 1940242432

Sample WhoCrashed report (all are nearly identical - only the last three parameters in the 0x9F code change):

On Mon 8/29/2011 6:04:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082911-31839-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8004CC1060, 0xFFFFF80004028518, 0xFFFFFA8003921820)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Virtually every single one of these was related to The MAudioFastTrackUltra.sys is the driver for M-Audio Fast Track Ultra.


I would remove it, at least to test. If there is an update and it is an absolute essential be sure to re-install the newest driver in compatibility mode.

Thats what I'm seeing as well.

Thank you so much for reviewing! I'll see how it turns out....

Well, it looks like y'all figured it out. I removed the M-Audio hardware & software, and the issues seem to have disappeared.

THANK YOU!