random bsods on 8.1

azraelle

New Member
Messages
2
I checked ram with hci test and cpu stability with prime95, everything went smoothly and without errors. But i got 2 bsods afterwards when i tried to type url in firefox.
 

My Computer

System One

  • OS
    8.1
    Computer type
    PC/Desktop
Hello and welcome to the forum.


Code:
Loading Dump File [C:\Users\USER\Downloads\SF_15-10-2013\SF_15-10-2013\101413-4812-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff803`fde14000 PsLoadedModuleList = 0xfffff803`fe0db9b0
Debug session time: Mon Oct 14 18:53:58.645 2013 (UTC + 6:00)
System Uptime: 0 days 5:29:55.300
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


Use !analyze -v to get detailed debugging information.


BugCheck 7F, {8, fffff803ffb18e70, fffff803ffb02f80, fffff80002841574}


*** WARNING: Unable to verify timestamp for MAudioMobilePreII.sys
*** ERROR: Module load completed but symbols could not be loaded for MAudioMobilePreII.sys
Probably caused by : MAudioMobilePreII.sys ( MAudioMobilePreII+13663 )


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


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


UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: fffff803ffb18e70
Arg3: fffff803ffb02f80
Arg4: fffff80002841574


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




BUGCHECK_STR:  0x7f_8


CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT


PROCESS_NAME:  System


CURRENT_IRQL:  2


LAST_CONTROL_TRANSFER:  from fffff803fdf6fbe9 to fffff803fdf640a0


STACK_TEXT:  
fffff803`ffb18d28 fffff803`fdf6fbe9 : 00000000`0000007f 00000000`00000008 fffff803`ffb18e70 fffff803`ffb02f80 : nt!KeBugCheckEx
fffff803`ffb18d30 fffff803`fdf6dcf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff803`ffb18e70 fffff800`02841574 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb4
fffff803`ffb02f80 fffff800`028414a0 : ffffe000`00b2ba60 fffff800`028523e0 ffffe000`02169110 00000000`00000000 : usbccgp!DispatchPdoUrb+0x64
fffff803`ffb03080 fffff800`028401eb : fffff800`028523a0 00000000`00000001 ffffe000`03026760 ffffe000`00b2ba60 : usbccgp!DispatchPdoInternalDeviceControl+0x80
fffff803`ffb030e0 fffff800`02ae8663 : ffffe000`00000000 ffffe000`03026768 ffffe000`03026768 00000000`c000009a : usbccgp!USBC_Dispatch+0x1db
fffff803`ffb031a0 ffffe000`00000000 : ffffe000`03026768 ffffe000`03026768 00000000`c000009a ffffe000`021e82e0 : MAudioMobilePreII+0x13663
fffff803`ffb031a8 ffffe000`03026768 : ffffe000`03026768 00000000`c000009a ffffe000`021e82e0 fffff800`02ae8b74 : 0xffffe000`00000000
fffff803`ffb031b0 ffffe000`03026768 : 00000000`c000009a ffffe000`021e82e0 fffff800`02ae8b74 ffffe000`021e82e0 : 0xffffe000`03026768
fffff803`ffb031b8 00000000`c000009a : ffffe000`021e82e0 fffff800`02ae8b74 ffffe000`021e82e0 00000000`c0000a00 : 0xffffe000`03026768
fffff803`ffb031c0 ffffe000`021e82e0 : fffff800`02ae8b74 ffffe000`021e82e0 00000000`c0000a00 ffffe000`0216a640 : 0xc000009a
fffff803`ffb031c8 fffff800`02ae8b74 : ffffe000`021e82e0 00000000`c0000a00 ffffe000`0216a640 ffffe000`021e82e0 : 0xffffe000`021e82e0
fffff803`ffb031d0 ffffe000`021e82e0 : 00000000`c0000a00 ffffe000`0216a640 ffffe000`021e82e0 00000000`00000000 : MAudioMobilePreII+0x13b74
fffff803`ffb031d8 00000000`c0000a00 : ffffe000`0216a640 ffffe000`021e82e0 00000000`00000000 00000000`00000000 : 0xffffe000`021e82e0
fffff803`ffb031e0 ffffe000`0216a640 : ffffe000`021e82e0 00000000`00000000 00000000`00000000 ffffffff`c000000d : 0xc0000a00
fffff803`ffb031e8 ffffe000`021e82e0 : 00000000`00000000 00000000`00000000 ffffffff`c000000d fffff803`fde57118 : 0xffffe000`0216a640
fffff803`ffb031f0 00000000`00000000 : 00000000`00000000 ffffffff`c000000d fffff803`fde57118 ffffe000`00b2ba60 : 0xffffe000`021e82e0




STACK_COMMAND:  kb


FOLLOWUP_IP: 
MAudioMobilePreII+13663
fffff800`02ae8663 ??              ???


SYMBOL_STACK_INDEX:  6


SYMBOL_NAME:  MAudioMobilePreII+13663


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: MAudioMobilePreII


IMAGE_NAME:  MAudioMobilePreII.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  519e0c21


FAILURE_BUCKET_ID:  0x7f_8_MAudioMobilePreII+13663


BUCKET_ID:  0x7f_8_MAudioMobilePreII+13663


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


0: kd> lmvm MAudioMobilePreII
start             end                 module name
fffff800`02ad5000 fffff800`02b49000   MAudioMobilePreII T (no symbols)           
    Loaded symbol image file: MAudioMobilePreII.sys
    Image path: \SystemRoot\system32\DRIVERS\MAudioMobilePreII.sys
[COLOR=#0000ff]    Image name: MAudioMobilePreII.sys[/COLOR]
[COLOR=#0000ff]    Timestamp:        Thu May 23 18:31:29 2013 (519E0C21)[/COLOR]
    CheckSum:         0007368D
    ImageSize:        00074000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - Disk Check
3. Troubleshoot applications by a clean boot - How to perform a Clean Boot Windows 8
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure
 

My Computer

System One

  • OS
    Windows 7 Home Premium 64 Bit
    Computer type
    PC/Desktop
I'll try and rollback to previous maudio driver version, although manufactured stated that this release supports win8. I've checked disk, system files and ram already, ram was OCed to 1600 and was causing bsods sometimes so i returned to stable 1300.
 

My Computer

System One

  • OS
    8.1
    Computer type
    PC/Desktop
Back
Top