locked
BSOD Windows 8.1 System Service Exception (memory_corruption) RRS feed

  • Question

  • Hello,

    I have a new computer with AMD processor and AMD Radeon R9 graphic card.

    Several times a day, usually when I play a game I receive BSOD on Win 8.1 (with latest updates + http://support.microsoft.com/kb/2818604 microcode Update for AMD procs+ latest AMD drivers).

    Here from the dump:

    FOLLOWUP_IP:
    nt!MiGetVadWakeList+180
    fffff802`48257740 488b11          mov     rdx,qword ptr [rcx]

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt!MiGetVadWakeList+180

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  52718d9c

    IMAGE_VERSION:  6.3.9600.16452

    STACK_COMMAND:  .cxr 0xffffd00029a0eaf0 ; kb

    IMAGE_NAME:  memory_corruption

    BUCKET_ID_FUNC_OFFSET:  180

    FAILURE_BUCKET_ID:  0x3B_nt!MiGetVadWakeList

    BUCKET_ID:  0x3B_nt!MiGetVadWakeList

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0x3b_nt!migetvadwakelist

    FAILURE_ID_HASH:  {89f10555-061f-eab8-c95d-da0ab622d7bc}

    Followup: MachineOwner

    Full DUMP and last 2 mini dumps here :

    https://skydrive.live.com/redir?resid=D618163590ABA072!3129&authkey=!AMS2YI4mfjMRRfc&ithint=folder%2c.dmp

    Any input will he appreciated! Thanks!

    I think it`s maybe the AMD drivers.. but have no idea how to further address this issue..

    Monday, December 30, 2013 5:58 PM

Answers

  • These crashes were related to memory management. (probably caused by a driver)

    Please run these tests to verify your memory and find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

    1-Memtest. (You can read more about running memtest here)
    2-Driver verifier (for complete directions see our wiki here)

    Advice offered in good faith. It is your decision to implement same. Wanikiya and Dyami - Team ZigZag

    • Proposed as answer by ZigZag3143x Sunday, January 12, 2014 5:19 AM
    • Marked as answer by ZigZag3143x Sunday, January 19, 2014 1:09 PM
    Monday, December 30, 2013 6:31 PM
  • Serinia

    Verifier was enabled it did not "catch" the offending driver but it was related toUsbport.sys with description USB 1.1 & 2.0 Port Driver from company Microsoft Corporation belonging to product Microsoft® Windows® Operating System.

    I would change the set of drivers being examined to "all" and upload those DMPS.

    I would also, with verifier turned off (verifier /reset), run a system file check

    Please run a system file check (SFC)

    All instructions are in our Wiki article below...
    Should you have any questions please ask us.


    Wanikiya and Dyami--Team Zigzag


    • Edited by ZigZag3143x Sunday, January 5, 2014 6:00 PM
    • Proposed as answer by Yolanda Zhu Monday, January 6, 2014 11:38 AM
    • Marked as answer by ZigZag3143x Sunday, January 12, 2014 9:01 PM
    Sunday, January 5, 2014 5:58 PM
  • Updating firmware for the R9 290 Card with the latest drivers from AMD + 8.1 drivers update works now. I didn`t have a crash in the last month anymore. Apparently there was a hardware problem with the chips on the R9 290+290x cards which was addressed by the latest firmware release.

    • Marked as answer by Silvana Deac Friday, February 21, 2014 8:44 AM
    Friday, February 21, 2014 8:44 AM

All replies

  • These crashes were related to memory management. (probably caused by a driver)

    Please run these tests to verify your memory and find which driver is causing the problem.  

    If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

    1-Memtest. (You can read more about running memtest here)
    2-Driver verifier (for complete directions see our wiki here)

    Advice offered in good faith. It is your decision to implement same. Wanikiya and Dyami - Team ZigZag

    • Proposed as answer by ZigZag3143x Sunday, January 12, 2014 5:19 AM
    • Marked as answer by ZigZag3143x Sunday, January 19, 2014 1:09 PM
    Monday, December 30, 2013 6:31 PM
  • From the dump file, it seems that the BSOD occurred when you play witcher2 and IE

    Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION

    http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

    According to the link, this issue may occur due to graphics drivers, I suggest you reinstall the driver for a test. If issue persists, try Driver verifier metioned by JMH3143 to find the fault driver.

    Regards


    Yolanda
    TechNet Community Support

    Tuesday, December 31, 2013 11:03 AM
  • Hello,

    Thanks,

    Reinstalled AMD Drivers -issue still persists.

    Updated Firmware for the 290 Card.

    This particular error went away, however I still receive BSOD with another message which is related to Direct X?

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffffae0088bace0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
     bit 0 : value 0 = read operation, 1 = write operation
     bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8038d27851a, address which referenced memory

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


    READ_ADDRESS:  fffffae0088bace0

    CURRENT_IRQL:  2

    FAULTING_IP:
    nt!MiUnlinkPageFromLockedList+35a
    fffff803`8d27851a 483301          xor     rax,qword ptr [rcx]

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  AV

    PROCESS_NAME:  witcher2.exe

    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

    TRAP_FRAME:  ffffd0002a526f40 -- (.trap 0xffffd0002a526f40)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00024053d0000000 rbx=0000000000000000 rcx=fffffae0088bace0
    rdx=00fffff000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8038d27851a rsp=ffffd0002a5270d0 rbp=ffffd0002a527138
     r8=fffffa800cbd0e60  r9=000000000024053d r10=0000000000000000
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    nt!MiUnlinkPageFromLockedList+0x35a:
    fffff803`8d27851a 483301          xor     rax,qword ptr [rcx] ds:fffffae0`088bace0=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff8038d3607e9 to fffff8038d354ca0

    STACK_TEXT: 
    ffffd000`2a526df8 fffff803`8d3607e9 : 00000000`0000000a fffffae0`088bace0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`2a526e00 fffff803`8d35f03a : 00000000`00000000 fffffa80`08c1e880 ffffd000`2a526f00 ffffd000`2a526f40 : nt!KiBugCheckDispatch+0x69
    ffffd000`2a526f40 fffff803`8d27851a : ffffc000`0fe7e201 fffff803`8d98e1e9 00000000`00000000 ffffa09c`b7fb0f31 : nt!KiPageFault+0x23a
    ffffd000`2a5270d0 fffff803`8d3e9e85 : e3b00002`eb4d8b04 00000000`00000000 00000000`00000000 fffff680`00000004 : nt!MiUnlinkPageFromLockedList+0x35a
    ffffd000`2a527160 fffff803`8d311b6e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff680`001a2010 : nt!MiActOnPte+0x529
    ffffd000`2a5271c0 fffff803`8d3074c1 : 00000000`343d0000 ffffe000`06f2a900 00000000`343d0000 00000000`01000000 : nt!MiWalkVaRange+0x34a
    ffffd000`2a527340 fffff803`8d5bba86 : 00000000`00000000 00000000`0010a000 00000000`00000000 7fffffff`fffffffc : nt!MiResetVirtualMemory+0x79
    ffffd000`2a527380 fffff803`8d3604b3 : fffff900`00000020 00000000`00000080 00000000`000000c0 00000001`ffffffff : nt!NtAllocateVirtualMemory+0xba6
    ffffd000`2a527580 fffff803`8d358900 : fffff800`015db414 ffffe000`06f2a900 ffffd000`2a5277c8 ffffc000`021cd880 : nt!KiSystemServiceCopyEnd+0x13
    ffffd000`2a527788 fffff800`015db414 : ffffe000`06f2a900 ffffd000`2a5277c8 ffffc000`021cd880 ffffe000`04bc4460 : nt!KiServiceLinkage
    ffffd000`2a527790 fffff800`015d7e10 : ffffe000`00000404 ffffc000`00000000 00000000`0010a000 00000000`343d0000 : dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo+0x88
    ffffd000`2a5277f0 fffff800`015d7b39 : ffffd000`2a527960 fffff800`014127dc ffffc000`0878d6a8 ffffc000`1172c8b0 : dxgmms1!VIDMM_GLOBAL::ReclaimOneAllocation+0x290
    ffffd000`2a5278f0 fffff800`01419f3d : ffffe000`009fa260 00000000`00000001 ffffe000`029ba000 ffffe000`003dbc50 : dxgmms1!VIDMM_GLOBAL::ReclaimAllocation+0x69
    ffffd000`2a527930 fffff800`014717e9 : ffffc000`0878d640 ffffd000`2a5279f0 ffffd000`2a527b00 ffffc000`10829230 : dxgkrnl!VIDMM_EXPORT::VidMmReclaimAllocation+0x45
    ffffd000`2a527960 fffff800`01471425 : ffffc000`10362000 ffffc000`10362000 00000000`00000001 00000000`1f590000 : dxgkrnl!DXGDEVICE::ReclaimAllocations+0x199
    ffffd000`2a5279c0 fffff803`8d3604b3 : ffffe000`06926080 ffffc000`10362000 ffffc000`10362000 ffffe000`0678aa60 : dxgkrnl!DxgkReclaimAllocations+0x1b5
    ffffd000`2a527a80 00000000`77cc77ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`1f49e818 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77cc77ba


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo+88
    fffff800`015db414 4863d8          movsxd  rbx,eax

    SYMBOL_STACK_INDEX:  a

    SYMBOL_NAME:  dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo+88

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME:  dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  5277b2b7

    IMAGE_VERSION:  6.3.9600.16455

    BUCKET_ID_FUNC_OFFSET:  88

    FAILURE_BUCKET_ID:  AV_dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo

    BUCKET_ID:  AV_dxgmms1!VIDMM_PROCESS_HEAP::ResetUndo

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:av_dxgmms1!vidmm_process_heap::resetundo

    FAILURE_ID_HASH:  {7c538bc2-031b-7ae2-d86c-aa05a5a8b9ff}

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

    0: kd> lmvm dxgmms1
    start             end                 module name
    fffff800`0159a000 fffff800`015fb000   dxgmms1    (pdb symbols)          c:\symbols\dxgmms1.pdb\7B195D90422146629D865602E8D4B39B1\dxgmms1.pdb
        Loaded symbol image file: dxgmms1.sys
        Image path: \SystemRoot\System32\drivers\dxgmms1.sys
        Image name: dxgmms1.sys
        Timestamp:        Mon Nov 04 16:44:07 2013 (5277B2B7)
        CheckSum:         00063EA3
        ImageSize:        00061000
        File version:     6.3.9600.16455
        Product version:  6.3.9600.16455
        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.3.9600.16455
        FileVersion:      6.3.9600.16455 (winblue_gdr.131103-1206)
        FileDescription:  DirectX Graphics MMS
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

    Saturday, January 4, 2014 4:13 PM
  • Serinia

    Did you run driver verifier & if so what were the results.  We cant use what you are providing in Windbg because we cant access other switches (it is just text)


    Wanikiya and Dyami--Team Zigzag

    Saturday, January 4, 2014 9:56 PM
  • Hi,

    with driver verifier enabled as in the link above (so for all drivers without from MS) I receive a constant BSOD right after windows startup. Dumps are here: https://skydrive.live.com/redir?resid=D618163590ABA072!3197&authkey=!AB-S_8owE8_eOpQ&ithint=folder%2c.dmp

    Seems to be related to USB driver/ I also got BSOD for asuplO.sys

    If you can take a look at these (uploaded full dump + mini dump) would be great.

    Thanks for your patience.

    Sunday, January 5, 2014 5:42 PM
  • Serinia

    Verifier was enabled it did not "catch" the offending driver but it was related toUsbport.sys with description USB 1.1 & 2.0 Port Driver from company Microsoft Corporation belonging to product Microsoft® Windows® Operating System.

    I would change the set of drivers being examined to "all" and upload those DMPS.

    I would also, with verifier turned off (verifier /reset), run a system file check

    Please run a system file check (SFC)

    All instructions are in our Wiki article below...
    Should you have any questions please ask us.


    Wanikiya and Dyami--Team Zigzag


    • Edited by ZigZag3143x Sunday, January 5, 2014 6:00 PM
    • Proposed as answer by Yolanda Zhu Monday, January 6, 2014 11:38 AM
    • Marked as answer by ZigZag3143x Sunday, January 12, 2014 9:01 PM
    Sunday, January 5, 2014 5:58 PM
  • Hi,

    I run SFC and got some errors, then I run DISM for repair and another SFC. After this system was ok, no more corrupt files.

    I enabled driver verifier for all the drivers. I still get before every logon BSOD for the USB Driver..

    Here are the new dumps: https://skydrive.live.com/redir?resid=D618163590ABA072!3226&authkey=!AKVn4RZu4nVHcUU&ithint=folder%2c.dmp

    Monday, January 6, 2014 5:42 PM
  • Serinia

    Does it BSOD with verifier off?

    What do you have attached to USB?  IS there a USB wifi, network, or video card?


    Wanikiya and Dyami--Team Zigzag

    Monday, January 6, 2014 6:04 PM
  • No, it doesn`t BSOD with verifier off.. only on rare occasions and when it does, not really because USBstor.. sometimes I cannot boot at startup but after CRTL ALT DEL win starts successfully.

    I have an USB network adapter (WIFI) card and a Razer TRON Keyboard + Mouse.

    I`ll try to run verifier only for AMD drivers to see if this triggers BSOD in Witcher 2.. since this is what bugs me the most. It happens also for other games, so it`s not game related.

    Tuesday, January 7, 2014 9:01 PM
  • Serinia

    Can you also upload the event viewer logs?

    Please provide us with your Event Viewer administrative logs by following these steps:


    Click Start Menu
    Type eventvwr into Search programs and files (do not hit enter)
    Right click eventvwr.exe and click Run as administrator
    Expand Custom Views
    Click Administrative Events
    Right click Administrative Events
    Save all Events in Custom View As...
    Save them in a folder where you will remember which folder and save as Errors.evtx
    Go to where you saved Errors.evtx
    Right click Errors.evtx -> send to -> compressed (zipped) folder
    Upload the .zip file to skydrive or a file sharing service and put a link to it in your next post
    *
    If you have updated to win 8.1 and you get the error message "the system cannot find the file specified" it is a known problem.  The work around is to edit the registry.  If you are not comfortable doing this DONT.  If you are, backup the key before you do
    Press Win+"R" and input regedit

    Navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete "Microsoft-Windows-DxpTaskRingtone/Analytic"


    Wanikiya and Dyami--Team Zigzag

    Tuesday, January 7, 2014 9:50 PM
  • https://skydrive.live.com/redir?resid=D618163590ABA072!3236&authkey=!ALMzuxjk99kkpF0&ithint=folder%2c.xml

    Can`t save to evtx-> it`s XML

    This doesn`t work. If I delete the whole key I receive an error, if I delete only the values it doesn`t work either: publisher metadata cannot be found in the resource

    > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels. Delete "Microsoft-Windows-DxpTaskRingtone/Analytic

    Thursday, January 9, 2014 5:23 PM
  • Updating firmware for the R9 290 Card with the latest drivers from AMD + 8.1 drivers update works now. I didn`t have a crash in the last month anymore. Apparently there was a hardware problem with the chips on the R9 290+290x cards which was addressed by the latest firmware release.

    • Marked as answer by Silvana Deac Friday, February 21, 2014 8:44 AM
    Friday, February 21, 2014 8:44 AM