BSOD while playing games (SC2, Planetside 2, The War Z), 0x00000050

Page 1 of 3 123 LastLast

  1. Posts : 16
    Windows 7 x64
       #1

    BSOD while playing games (SC2, Planetside 2, The War Z), 0x00000050


    I've been experiencing BSOD's while playing games for a few weeks now. The Bug Check String is: PAGE_FAULT_IN_NONPAGED_AREA so my immediate guess was faulty memory. I ran windows Memory checking utility, and ran Memtest86+ for several hours, all without errors. I adjusted the memory timings to 9-9-9-24 as suggested on corsair's site (my memory timings were previously 8-8-8-20 as set with the auto setting on my BIOS). I still have not adjusted the voltage of the memory, I will try that next. All my drivers are up to date as I just re-installed windows yesterday, and downloaded the latest graphics driver from NVidia's site.

    Any ideas?

    System specs:
    Windows 7x64
    ASUS Rampage II GENE LGA 1366 Intel X58 Micro ATX Intel Motherboard
    Intel Core i7-920 Bloomfield 2.66GHz LGA 1366 130W Quad-Core Processor BX80601920 (Overclocked to 2.97 GHz)
    CORSAIR XMS3 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Triple Channel Kit Desktop Memory Model
    CORSAIR Enthusiast Series CMPSU-550VX 550W ATX12V V2.2 SLI Ready CrossFire Ready 80 PLUS Certified Active PFC Compatible
    EVGA 01G-P3-1155-TR GeForce GTS 250 1GB 256-bit GDDR3 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card

    I've uploaded the logs/driver lists, but here's a view of the event viewer:

    Log Name: System
    Source: Microsoft-Windows-Kernel-Power
    Date: 12/13/2012 1:14:03 PM
    Event ID: 41
    Task Category: (63)
    Level: Critical
    Keywords: (2)
    User: SYSTEM
    Computer: xxx-PC
    Description:
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2012-12-13T18:14:03.134806400Z" />
    <EventRecordID>5297</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>Kowalski-PC</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="BugcheckCode">80</Data>
    <Data Name="BugcheckParameter1">0xfffff8b009110858</Data>
    <Data Name="BugcheckParameter2">0x0</Data>
    <Data Name="BugcheckParameter3">0xfffff8800481d135</Data>
    <Data Name="BugcheckParameter4">0x5</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
    </EventData>
    </Event>
    Last edited by Killerwalski; 19 Dec 2012 at 21:09.
      My Computer


  2. Posts : 851
    Windows 8 Professional x64
       #2

    update your direct x drivers

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff8b00f87f530, 1, fffff88004b81983, 5}
    
    
    Could not read faulting driver name
    Probably caused by : dxgmms1.sys ( dxgmms1!VidMmDestroyAllocation+43 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff8b00f87f530, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff88004b81983, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd100
    GetUlongFromAddress: unable to read from fffff80002cbd1c0
     fffff8b00f87f530 Paged pool
    
    FAULTING_IP: 
    dxgmms1!VidMmDestroyAllocation+43
    fffff880`04b81983 4c8908          mov     qword ptr [rax],r9
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  WarZ.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8801141e830 -- (.trap 0xfffff8801141e830)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8b00f87f530 rbx=0000000000000000 rcx=fffffa8007ec1000
    rdx=fffff8a000f1f980 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004b81983 rsp=fffff8801141e9c0 rbp=fffffa8007ec1000
     r8=fffff8a007503980  r9=fffff8a00f87f530 r10=0000000000000000
    r11=fffff88002dd1120 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe cy
    dxgmms1!VidMmDestroyAllocation+0x43:
    fffff880`04b81983 4c8908          mov     qword ptr [rax],r9 ds:fffff8b0`0f87f530=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a348af to fffff80002a8dfc0
    
    STACK_TEXT:  
    fffff880`1141e6c8 fffff800`02a348af : 00000000`00000050 fffff8b0`0f87f530 00000000`00000001 fffff880`1141e830 : nt!KeBugCheckEx
    fffff880`1141e6d0 fffff800`02a8c0ee : 00000000`00000001 fffff8b0`0f87f530 00000000`00000000 fffff8a0`0f87f530 : nt! ?? ::FNODOBFM::`string'+0x437c1
    fffff880`1141e830 fffff880`04b81983 : fffffa80`0a479010 fffff880`1141ea10 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`1141e9c0 fffff880`04ac406f : 00000000`00000000 00000000`00000000 fffff8a0`09180000 00000000`00000174 : dxgmms1!VidMmDestroyAllocation+0x43
    fffff880`1141e9f0 fffff880`04ad6784 : fffff8a0`0a95af70 00000000`00000000 00000000`00000000 fffff8a0`09180068 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x5eb
    fffff880`1141eae0 fffff880`04abb815 : 00000000`fffffeda fffff8a0`0bb02980 fffff880`1141eca0 fffffa80`07ea8000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
    fffff880`1141eb50 fffff880`04ad78f2 : fffffa80`08a4d060 fffffa80`08a4d060 00000000`fffdb000 fffff8a0`09180000 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
    fffff880`1141eb80 fffff960`001a04ea : 00000000`00000020 00000000`00000000 00000000`000007da 00000000`75296244 : dxgkrnl!DxgkDestroyDevice+0x1f6
    fffff880`1141ebf0 fffff800`02a8d253 : fffffa80`08a4d060 fffff880`1141eca0 00000000`fffdb000 fffffa80`09df1b50 : win32k!NtGdiDdDDIDestroyDevice+0x12
    fffff880`1141ec20 00000000`752b144a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0009dfc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x752b144a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VidMmDestroyAllocation+43
    fffff880`04b81983 4c8908          mov     qword ptr [rax],r9
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  dxgmms1!VidMmDestroyAllocation+43
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VidMmDestroyAllocation+43
    
    BUCKET_ID:  X64_0x50_dxgmms1!VidMmDestroyAllocation+43
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 16
    Windows 7 x64
    Thread Starter
       #3

    Done. Will give it a few sessions tomorrow and see if that helped =)
      My Computer


  4. Posts : 851
    Windows 8 Professional x64
       #4

    If it bsod upload the new dumps
      My Computer


  5. Posts : 16
    Windows 7 x64
    Thread Starter
       #5

    Thank you for your help, it is much appreciated. I will post again with the new dumps if another crash occurs. Thank you again, bagavan.

    For what it's worth, before my fresh windows install yesterday, I am 99% sure I had the latest directX drivers installed, and still had similar BSOD's.
      My Computer


  6. Posts : 851
    Windows 8 Professional x64
       #6
      My Computer


  7. Posts : 16
    Windows 7 x64
    Thread Starter
       #7

    Yes, I did.
      My Computer


  8. Posts : 851
    Windows 8 Professional x64
       #8

    Post back new dumps if it BSOD`s
      My Computer


  9. Posts : 16
    Windows 7 x64
    Thread Starter
       #9

    Seems to have happened again. This time it's a "MEMORY_MANAGEMENT" Error. I was AFK when it happened, wasn't playing any games or anything.
      My Computer


  10. Posts : 851
    Windows 8 Professional x64
       #10

    Perform this and post back

    RAM - Test with Memtest86+

    Errors might be found after 7 passes.

    Do it overnight

    Also run this

    SFC /SCANNOW Command - System File Checker
      My Computer


 
Page 1 of 3 123 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 22:47.
Find Us