BSOD playing need for speed 13 error 0x03b

Page 1 of 2 12 LastLast

  1. Posts : 237
    64 bit windows 7 home professional SP1
       #1

    random bsod 0x00000019


    help? i also get 0x0124
      My Computer


  2. Posts : 1,454
    Windows 7 ultimate x64
       #2

    EXPLAIN !!!

    And then

    Please use this tool to update your profile specs

    And then use this tool to post all the files here
      My Computer


  3. Posts : 237
    64 bit windows 7 home professional SP1
    Thread Starter
       #3

    BSOD playing need for speed 13 error 0x03b


    it changes almost every time about 4 or 5 times a day. dont know what to do?
      My Computer


  4. Posts : 2,573
    Win7 Ultimate X64
       #4

    Hello skrillek, Welcome to SF

    First off if your OCing in anyway stop, return everything to stock settings for the purposes of testing

    If you havent already, fill in your system specs so we know what we are dealing with
    System Info - See Your System Specs

    Make sure you have read the guide on asking for help with BSOD so you know what we need
    https://www.sevenforums.com/crashes-d...tructions.html

    Run some scans to check against virus or infection
    Anti-rootkit utility TDSSKiller
    Windows Defender Offline

    Just ran your two most recent dumps
    1st one shows error 0xFC BSOD Index
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck FC, {fffff8800ad99ba8, 8000000123b00963, fffff8800ad99a10, 0}
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4336c )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory.  The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff8800ad99ba8, Virtual address for the attempted execute.
    Arg2: 8000000123b00963, PTE contents.
    Arg3: fffff8800ad99a10, (reserved)
    Arg4: 0000000000000000, (reserved)
    Debugging Details:
    ------------------
     
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xFC
    PROCESS_NAME:  NFS13.exe
    CURRENT_IRQL:  2
    TRAP_FRAME:  fffff8800ad99a10 -- (.trap 0xfffff8800ad99a10)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80075b7b50
    rdx=fffffffffffffffd rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800ad99ba8 rsp=fffff8800ad99ba8 rbp=fffff8800ad99ca0
     r8=0000000000000000  r9=00000000000000f0 r10=0000000000000000
    r11=fffff8800ad99af8 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    fffff880`0ad99ba8 0000            add     byte ptr [rax],al ds:00000000`00000000=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff800040704b0 to fffff800040c9fc0
    STACK_TEXT:  
    fffff880`0ad998a8 fffff800`040704b0 : 00000000`000000fc fffff880`0ad99ba8 80000001`23b00963 fffff880`0ad99a10 : nt!KeBugCheckEx
    fffff880`0ad998b0 fffff800`040c80ee : fffffa80`09df0a50 fffffa80`09debbf0 bf800000`bf800000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4336c
    fffff880`0ad99a10 fffff880`0ad99ba8 : fffff800`00000000 00000000`00000000 fffff800`00000002 fffffa80`0645c3f0 : nt!KiPageFault+0x16e
    fffff880`0ad99ba8 fffff800`00000000 : 00000000`00000000 fffff800`00000002 fffffa80`0645c3f0 00000000`037ff189 : 0xfffff880`0ad99ba8
    fffff880`0ad99bb0 00000000`00000000 : fffff800`00000002 fffffa80`0645c3f0 00000000`037ff189 00000000`746c6644 : 0xfffff800`00000000
     
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4336c
    fffff800`040704b0 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4336c
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
    FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+4336c
    BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+4336c
    Followup: MachineOwner
    ---------
    So this leads us to believe its a faulty driver

    2nd dump file states 0x3b error BSOD Index
    and points straight at dxgmms1.sys
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 3B, {c0000005, fffff8800579801f, fffff88008da0090, 0}
    Probably caused by : dxgmms1.sys ( dxgmms1!VidMmSetAllocationPriority+bf )
    Followup: MachineOwner
    ---------
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff8800579801f, Address of the instruction which caused the bugcheck
    Arg3: fffff88008da0090, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    Debugging Details:
    ------------------
     
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP: 
    dxgmms1!VidMmSetAllocationPriority+bf
    fffff880`0579801f 488b08          mov     rcx,qword ptr [rax]
    CONTEXT:  fffff88008da0090 -- (.cxr 0xfffff88008da0090)
    rax=0000000000001000 rbx=0000000000000000 rcx=fffff8a014118a20
    rdx=fffff8a0140b3d00 rsi=fffff8a0140b34a0 rdi=0000000028000000
    rip=fffff8800579801f rsp=fffff88008da0a70 rbp=fffff8a0140b3d00
     r8=0000000028000000  r9=fffff880057a78c0 r10=0000000000000015
    r11=fffff8a012ab5000 r12=fffff880056c0a08 r13=0000000040010440
    r14=000000000000003c r15=0000000074a02450
    iopl=0         nv up ei pl nz na po cy
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010207
    dxgmms1!VidMmSetAllocationPriority+0xbf:
    fffff880`0579801f 488b08          mov     rcx,qword ptr [rax] ds:002b:00000000`00001000=????????????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  NFS13.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff880056ddac4 to fffff8800579801f
    STACK_TEXT:  
    fffff880`08da0a70 fffff880`056ddac4 : 00000000`00000000 fffff880`056a407b 00000000`40010440 fffff880`08da0bb0 : dxgmms1!VidMmSetAllocationPriority+0xbf
    fffff880`08da0b00 fffff880`056e0675 : fffff8a0`12ab5000 fffffa80`07337060 fffffa80`07337060 fffff8a0`12ab5000 : dxgkrnl!DXGDEVICE::SetAllocationPriority+0x304
    fffff880`08da0b50 fffff960`0027047e : 00000000`fffdb000 ffff2405`00000000 00000000`000007d7 00000000`00000000 : dxgkrnl!DxgkSetAllocationPriority+0x1fd
    fffff880`08da0bf0 fffff800`040cf253 : fffffa80`07337060 fffffa80`080de001 fffffa80`00000000 fffffa80`0a9ab750 : win32k!NtGdiDdDDISetAllocationPriority+0x12
    fffff880`08da0c20 00000000`74a5165a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0008e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a5165a
     
    FOLLOWUP_IP: 
    dxgmms1!VidMmSetAllocationPriority+bf
    fffff880`0579801f 488b08          mov     rcx,qword ptr [rax]
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  dxgmms1!VidMmSetAllocationPriority+bf
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: dxgmms1
    IMAGE_NAME:  dxgmms1.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    STACK_COMMAND:  .cxr 0xfffff88008da0090 ; kb
    FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidMmSetAllocationPriority+bf
    BUCKET_ID:  X64_0x3B_dxgmms1!VidMmSetAllocationPriority+bf
    Followup: MachineOwner
    ---------
    0: kd> lmvm dxgmms1
    start             end                 module name
    fffff880`05796000 fffff880`057dc000   dxgmms1    (pdb symbols)          C:\ProgramData\dbg\sym\dxgmms1.pdb\0901C357E9E846EE8C2FBCC8107163201\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Mapped memory image file: C:\ProgramData\dbg\sym\dxgmms1.sys\4CE799C146000\dxgmms1.sys
        Image path: dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Sat Nov 20 09:49:53 2010 (4CE799C1)
        CheckSum:         00047A89
        ImageSize:        00046000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        3.7 Driver
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     dxgmms1.sys
        OriginalFilename: dxgmms1.sys
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    so this seems to be gfx/directx related although the file is question should be updated automatically by win update so its hard to believe its at fault, i would check to ensure your windows is up to date manually and if necessary update gfx drivers manually
    dxgmms1 dxgmms1.sys Sat Nov 20 09:49:53 2010

    also noticed you have a very old driver in your system
    MarvinBus64 MarvinBus64.sys Fri Sep 23 22:17:03 2005
    you need to update or remove this i think it is part of pinnacle studio something or other

    i will run some more of the dumps and post back later
      My Computer


  5. Posts : 237
    64 bit windows 7 home professional SP1
    Thread Starter
       #5

    thank you i will delete some old drivers and i have recently done an malware and virus scan + regirsty i will be getting back to you
      My Computer


  6. Posts : 2,573
    Win7 Ultimate X64
       #6

    that bit where you say + registry is really scary, have you used some junk reg cleaner on it?
    those things should be banned cause more harm than good
      My Computer


  7. Posts : 2,573
    Win7 Ultimate X64
       #7

    OK just gone back through another four dumps with varying error codes
    0xa BSOD Index
    0x19 BSOD Index
    0xFC BSOD Index
    0x124 BSOD Index
    Stop 0x124 - what it means and what to try

    At this point it may be worth running a RAM check try memtest
    RAM - Test with Memtest86+
      My Computer


  8. Posts : 237
    64 bit windows 7 home professional SP1
    Thread Starter
       #8

    thansk your are very helpful ^^ and i know, i hate them but i use ccleaner and added to reputation :)
      My Computer


  9. Posts : 2,573
    Win7 Ultimate X64
       #9

    Hows it going with the BSOD did you run memtest ? if you get any more post the new dumps
      My Computer

  10.    #10

    Code:
    BugCheck D1, {2, b, 1, fffff88004b4dcf1}
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : hardware ( atikmdag+82cf1 )
    Code:
    Usual causes:  Device driver
    Code:
    1: kd> lmvm atikmdag
    start             end                 module name
    fffff880`04acb000 fffff880`05554000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Sep 28 03:14:57 2012 (50650821)
        CheckSum:         00A3EAAC
        ImageSize:        00A89000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Your graphics driver is rather outdated, and as a result I suggest you update the driver from AMD's website:

    1. Download Driver
    2. Start Type: Device Manager
    3. Expand Display Adapters
    4. Right-Click Driver Name, Uninstall
    5. Reboot
    6. Run Driver Sweeper
    7. Reboot
    8. Install Downloaded Driver

    Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

    Driver Sweeper:

    Upload .NFO file:

    Start > Type: msinfo32 > File, Save

    Here are the usual causes of Stop 0x1E:

    Code:
    Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
    Here is the information from the other thread (multiple threads have been created).
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:19.
Find Us