Crashes on 64bit

[JMH]

I suggest you do the following -

1. Memory-download memtestx86 and run for at least 5 passes
2. Run a system file check AGAIN to verify and repair your system files.
Go to search - right click to run as Administrator - type in sfc /scannow. [Make sure you have a space between sfc and / ]

Jan.

 

[CarlCP]

Jan,
I can not re-run sfc by following the instructions of:

[FONT=&quot]Go to search - right click to run as Administrator - type in sfc /scannow. [Make sure you have a space between sfc and / ]*
[/FONT]​

When I right click on sfc from the search and run as administrator[FONT=&quot][/FONT] I get the dialog of "do you want to allow the following program to make the changes to your computer" and then I see the cmd prompt window flash and disappear.
But I can run the cmd window as admin and then run sfc /scannow. I'm hoping that produces the same results.

I did run it again with the same results as last time and I'm attaching the cmd text and the CBS.log

On the subject of [FONT=&quot]memtestx86[/FONT]. I find a variety of [FONT=&quot]memtestx86[/FONT] and memtest86 and memtest86+. Is there one that you can recommend and a link to it.

Appreciate the help
Carl
[FONT=&quot][/FONT]
[FONT=&quot][/FONT]
[FONT=&quot][/FONT]

 

[JMH]

Hi Carl CP,
What was the message you received after running sfc?

Re memtestx86 - use the latest version. Memtest86
Make sure you run for at least 5 passes.

You might also care to run Driver Verifier.
Good luck.

 

[YakSipper]

Your problem is the driver for the M-Audio audio interface. Update that driver from M-Audio's site.

MAudioFastTrackUltra.sys

http://www.m-audio.com/index.php?do...=926320a5a5686189748193dbd6eb7d5f&OS=x91#tabs

Direct link to page = http://www.m-audio.com/index.php?do=support.drivers&f=1064

Direct link to driver itself = http://www.m-audio.com/index.php?do=support.drivers&f=1064&dl=yes

 

[CarlCP]

I'll do that YakSipper. For my interest, in all the dumps, what chuck of information points to that?

4/18 5pm update - It looks like I am running the latest drivers. However I uninstalled and reinstalled.

 

[CarlCP]

JMH,
SFC said that following

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
​

I did run Driver Verifier a week ago and attached the dumps. DT Roberts said that there wasn't anything in them that indicated a problem.
Are you suggesting I run it more?

 

[zigzag3143]

JMH,
SFC said that following

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
​

I did run Driver Verifier a week ago and attached the dumps. DT Roberts said that there wasn't anything in them that indicated a problem.
Are you suggesting I run it more?

CArl is SFC is saying there are files that are damaged and it cannot fix them, I suspect your next step would be a repair install to repair them.

Ken

 

[JMH]

JMH,
SFC said that following

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
​

I did run Driver Verifier a week ago and attached the dumps. DT Roberts said that there wasn't anything in them that indicated a problem.
Are you suggesting I run it more?

CArl is SFC is saying there are files that are damaged and it cannot fix them, I suspect your next step would be a repair install to repair them.

Ken

Thanks Ken for coming to the rescue...

 

[CarlCP]

CArl is SFC is saying there are files that are damaged and it cannot fix them, I suspect your next step would be a repair install to repair them.

Ken

Alright, I admit I haven't seen an new OS since XP but how the heck do you "repair" the files. Are we talking about this?:
http://www.sevenforums.com/tutorials/3413-repair-install.html

 

[JMH]

CArl is SFC is saying there are files that are damaged and it cannot fix them, I suspect your next step would be a repair install to repair them.

Ken

Alright, I admit I haven't seen an new OS since XP but how the heck do you "repair" the files. Are we talking about this?:
http://www.sevenforums.com/tutorials/3413-repair-install.html

Carl that is the one. See how it goes. Let us know.

 

[CarlCP]

Well I finally got some free time (work work work) and I did the Repair install. I then ran SFC with the results of "Windows Resource Protection did not find any integrity violations."
I'll report back with results.

 

[JMH]

Good news thus far.
Thanks for reporting back.

 

[CarlCP]

Oh disappointment. Thought I was looking good. BSOD with the following:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8006FBD060
BCP3: FFFFF80000B9C518
BCP4: FFFFFA800A632A60
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Dump is attached.

 

[zigzag3143]

Oh disappointment. Thought I was looking good. BSOD with the following:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8006FBD060
BCP3: FFFFF80000B9C518
BCP4: FFFFFA800A632A60
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Dump is attached.

This crash was caused by your MAudioFastTrackUltra.sys driver causing a bad power state. Since the driver isnt even digitally signed it isnt rated for win 7> I would see if there is a newer win 7 compatibile driver. If not you can try installing the vista driver in compatibility mode.

Let us know if you need help

Ken

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


Loading Dump File [C:\Users\K\Desktop\050610-20077-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03251000 PsLoadedModuleList = 0xfffff800`0348ee50
Debug session time: Thu May  6 20:53:06.006 2010 (GMT-4)
System Uptime: 1 days 0:54:42.037
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006fbd060, fffff80000b9c518, fffffa800a632a60}

*** WARNING: Unable to verify timestamp for MAudioFastTrackUltra.sys
*** ERROR: Module load completed but symbols could not be loaded for MAudioFastTrackUltra.sys
Probably caused by : MAudioFastTrackUltra.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006fbd060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa800a632a60, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800a632a60

DEVICE_OBJECT: fffffa8008c35a10

DRIVER_OBJECT: fffffa8008576140

IMAGE_NAME:  MAudioFastTrackUltra.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4abcec2a

MODULE_NAME: MAudioFastTrackUltra

FAULTING_MODULE: fffff880069ae000 MAudioFastTrackUltra

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800033301b3 to fffff800032c1600

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`033301b3 : 00000000`0000009f 00000000`00000003 fffffa80`06fbd060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`032cd6a6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c570 fffff800`032cca26 : fffff800`03463290 00000000`0057b84b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`032cd57e : 000000d0`cea8dd2e fffff800`00b9cc58 00000000`0057b84b fffff800`0343ebe8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`032ccd97 : 00000036`7d3ddec2 00000036`0057b84b 00000036`7d3dde85 00000000`0000004b : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`032c9dfa : fffff800`0343be80 fffff800`03449c40 00000000`00000000 fffff880`04833db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_MAudioFastTrackUltra.sys

BUCKET_ID:  X64_0x9F_IMAGE_MAudioFastTrackUltra.sys

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

 

[CarlCP]

Ken,
Interesting that you mentioned that. YakSipper said the same a few weeks back, so I checked my driver and it said it was the latest. So I looked again last night on thier site and found that there IS another driver for both win7 32 and 64bit.
However, I haven't been able to install it. my system always reverts to the 5.x versio that I have instead of the 6.x on thier site. I tried unistalling and reinstalling, I tried disconnecting the device, uninstalling, rebooting, reinstalling and then connecting the device. It stays at the old version. Very strange. I'm wondering if windows is by passing the installation driver and still grabbing thier driver?
Any idea on what might be happening on this. I've never had such an issue installing drivers before.

 

[Jonathan_King]

Try uninstalling the device, and then, without rebooting, install the new one.

 

[CarlCP]

Thanks Jonathan_King, I did that the first thing.
I tried using M-Audio's uninstall routine and then re-installed.
I've tried the upgrade driver from the Device Manager
I've tried uninstall, reboot, reinstall, turn device on
I've never seen an obstinate driver like this.
M-audio hasn't had any reference to this either.
I'm going to keep googling and see what I can come up with.
Anyone else have any idea's please post.
Thanks
Carl

 

[jcgriff2]

Long shot maybe -- try install in SAFEMODE

 

[CarlCP]

Well I really do have the latest driver. It was a problem with me not being observant. File name verses driver name.
M-Audio says it IS for Windows 7

Operating System(s):
Windows XP SP3, Windows Vista 32-Bit SP1, Windows Vista 64-Bit SP1, Windows Vista 32-Bit SP2, Windows Vista 64-Bit SP2, Windows 7 32-Bit, Windows 7 64-Bit
​

If the dump is saying that it's causing a bad power state then I'm kind of in a bind it seems. I'll go back and search their forums and if nothing try to contact support with information. What would be the best info to send them or provide them? The code posted by Ken from the MS Debugger?

 

[CarlCP]

I've been looking around for more information on M-Audio drivers and BSOD, Power State failures and found a link on this site to a program BlueScreenView. http://www.sevenforums.com/software/92-free-great-programs-windows-7-a.html
It says the Power State Failure is with the ntoskrnl.exe.

==================================================
Dump File : 050810-22417-01.dmp
Crash Time : 5/8/2010 10:29:59 AM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`08865060
Parameter 3 : fffff800`00b9c518
Parameter 4 : fffffa80`07ca8550
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16539 (win7_gdr.100226-1909)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\050810-22417-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7600
==================================================
​

I went back and looked at all the dumps from the last couple of months and it's identifying the same issue.
Any thoughts on that? Anyone use that to know it's reliability