Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

M-audio Vs. Winxp Problem


  • Please log in to reply
1 reply to this topic

#1 Tommboy

Tommboy

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:11:30 PM

Posted 13 June 2006 - 11:32 AM

Hello!

I have a problem with my USB soundcard - M-AUDIO QUATTRO USB INTERFACE.
Problem is when I'am using Nuendo and Reason, sometimes I get a blue screen. And that happens
when I don't play anything on Nuendo :thumbsup: I have opened minidumb.dmb with windows debugging
tool but I cannot find anything to fix that...I have already send dumb file to M-AUDIO but they didn't
replay me of course :flowers: SO IF ANYBODY KNOWS HOW TO READ THOSE DUMB FILES PLEASE
IF YOU CAN HELP ME!!!!



THIS IS COPY-PASTE FROM DUMB FILE OPENED IN WINDBG.EXE:



Microsoft ® Windows Debugger Version 6.6.0003.5
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [D:\WINDOWS\Minidump\Mini061306-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a5a0
Debug session time: Tue Jun 13 16:41:05.845 2006 (GMT+2)
System Uptime: 0 days 1:17:15.447
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
........................................................................................................................
Loading User Symbols
Loading unloaded module list
...........................
Unable to load image MA763001.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for MA763001.sys
*** ERROR: Module load completed but symbols could not be loaded for MA763001.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000047, 8051d356, 8054fd40, 0}

Probably caused by : MA763001.sys ( MA763001+fdc )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000047, The exception code that was not handled
Arg2: 8051d356, The address that the exception occurred at
Arg3: 8054fd40, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000047 - An attempt was made to release a semaphore such that its maximum count would have been exceeded.

FAULTING_IP:
nt!KeSetSystemTime+191
8051d356 e922ccfcff jmp nt!MiRemoveNode+0x16f (804e9f7d)

TRAP_FRAME: 8054fd40 -- (.trap ffffffff8054fd40)
ESP EDITED! New esp=805500f0
ErrCode = 00000000
eax=00000000 ebx=00008000 ecx=00000002 edx=82a0da98 esi=829bedf0 edi=00008001
eip=8051d356 esp=8054fdb4 ebp=80550104 iopl=0 nv up ei pl zr na po nc
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000246
nt!KeSetSystemTime+0x191:
8051d356 e922ccfcff jmp nt!MiRemoveNode+0x16f (804e9f7d)
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from f245efdc to 8051d356

STACK_TEXT:
80550104 f245efdc 829bedf0 00000008 00000001 nt!KeSetSystemTime+0x191
WARNING: Stack unwind information not available. Following frames may be wrong.
80550118 8294e9e8 8296b120 8294e860 82d26530 MA763001+0xfdc
00000000 00000000 00000000 00000000 00000000 0x8294e9e8


STACK_COMMAND: kb

FOLLOWUP_IP:
MA763001+fdc
f245efdc ?? ???

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: MA763001+fdc

MODULE_NAME: MA763001

IMAGE_NAME: MA763001.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 3f425dab

FAILURE_BUCKET_ID: 0x8E_MA763001+fdc

BUCKET_ID: 0x8E_MA763001+fdc

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

[/b]bye

Tommy

BC AdBot (Login to Remove)

 


#2 Snapper

Snapper

  • Members
  • 550 posts
  • OFFLINE
  •  
  • Location:Newfoundland
  • Local time:07:30 PM

Posted 13 June 2006 - 06:21 PM

i've never used a usb sound card, but according to what i read quickly, (and it was a large read, lol) your drivers are not starting, while you wait for another solution, why dont you try this>
1.go into your system's bios setting>on reboot, hit (usually) del, f-1, f-2, key, one of these is usually the key to get into thebios. once there, look for "onboard devices", should be in advanced tab. disable the onboard sound. bios versions are different, so keep an eye out for "onboard devices"

2.uninstall and re-install the drivers> check the internet for an updated driver version.

3. check for windows updates, good idea anyway.

hope this helps you, if not, post back.
Google...Google.....browse..read




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users