Constant BSOD on older comp (GPU side grade)


  1. Posts : 20
    Windows 10
       #1

    Constant BSOD on older comp (GPU side grade)


    The only thing I've changed on my old PC was that I went from a GTX 970 to a AMD R9 380 4GB. So what I've done is completely formatted the system, and reinstalled Windows 10 64bit, and all the drivers. Windows 10 likes to auto-install GPU drivers, so what I did was uninstall those, and install the latest AMD drivers. I was receiving the same BSOD error pre-format and post-format. I'm trying to determine is it's just a bad GPU and needs to be RMA'ed.

    I'm posting the last two dump, one from just here recently, and one from yesterday. Only thing I've done today is reinstall USB3 drivers for the motherboard, off manufacturers website. This system ran just fine with the GTX 970, which required more power, than this R9 380. I don't think PSU is an issue, as it's a non-modular 750 watt. I did unplug card from mobo, and re-seated it, also, same with 12v 6pin rails, unplugged/plugged back in. Also, I'd like to point out, these BSODs seem to be random, but it has been while GTA 5 is running. I tried letting the game idle, even up to hour, but it doesn't seem to do anything, unless you're playing for awhile, then randomly, I'll get some reference error, but not enough time to read before the BSOD pops up and restarts comp. Comp was built in March 2010.

    MSI p55-GD85 mobo
    2x8GB Adata DDR3 ram
    Intel i7-860
    Intel 180GB SSD (Win 10 64 bit install)
    Crucial 120GB SSD (games only)
    Last edited by undead77; 27 Dec 2015 at 19:44.
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #2

    Hi undead77,

    Welcome to the 10forums.

    I'm very sorry for the huge delay.

    I have looked at your mainboard for supported GPU's and I couldn't find the AMD R9 380 in the list.
    Attachment 56884
    MSI USA
    Last edited by axe0; 04 Jan 2016 at 02:50.
      My Computers


  3. Posts : 20
    Windows 10
    Thread Starter
       #3

    The board is a P55-GD85. It worked pretty well with the Gigabyte GTX 970 card, without any issues, which actually requires more power.

    MSI USA


    So can anyone give me any info on what the BSOD log says?
      My Computer


  4. Posts : 14,901
    Windows 10 Pro
       #4

    Can you verify the r9 380 and P55-GD85 are compatible?
    When I look at the test report of GPUs with your provided link I again cannot find the r9 380

    Also update your 'my system specs', there we'll look more then the OP
      My Computers


  5. Posts : 20
    Windows 10
    Thread Starter
       #5

    System specs only let me list one set of specs. I have two computers.

    I cannot verify any compatibility, because the mobo is older now.
      My Computer


  6. Posts : 14,901
    Windows 10 Pro
       #6

    Only the specs of the system having problems please :)
      My Computers


  7. Posts : 20
    Windows 10
    Thread Starter
       #7

    Updated. Can you read that BSOD log?
      My Computer


  8. Posts : 14,901
    Windows 10 Pro
       #8

    I already had done that.
    Below you can see vidmm, meaning video memory, the reason why I asked.
    Code:
    2: kd> k
    Child-SP          RetAddr           Call Site
    ffffd001`8c7d7ef8 fffff800`af84c62a nt!KeBugCheckEx
    ffffd001`8c7d7f00 fffff800`cff674f7 nt!ExFreePool+0xb0a
    ffffd001`8c7d7fe0 fffff800`cff68325 dxgmms2!VIDMM_RECYCLE_MULTIRANGE::SplitAt+0xd7
    ffffd001`8c7d8040 fffff800`cff66471 dxgmms2!VIDMM_RECYCLE_HEAP::Allocate+0x8d
    ffffd001`8c7d8080 fffff800`cff564f0 dxgmms2!VIDMM_RECYCLE_HEAP_MGR::Allocate+0xa1
    ffffd001`8c7d8100 fffff800`cff59679 dxgmms2!VIDMM_GLOBAL::OpenLocalAllocation+0x5a8
    ffffd001`8c7d8200 fffff800`cff49a91 dxgmms2!VIDMM_GLOBAL::OpenOneAllocation+0x1f9
    ffffd001`8c7d8370 fffff800`cff49423 dxgmms2!VIDMM_PAGE_TABLE_BASE::CreateVidMmObjects+0x1b5
    ffffd001`8c7d8490 fffff800`cff4883e dxgmms2!VIDMM_PAGE_TABLE::InitializePageTable+0xcf
    ffffd001`8c7d84d0 fffff800`cff4b33f dxgmms2!CreatePageTable+0x86
    ffffd001`8c7d8500 fffff800`cff4c3e8 dxgmms2!VIDMM_PAGE_DIRECTORY::CommitVirtualAddressRange+0x73f
    ffffd001`8c7d86b0 fffff800`cff52bee dxgmms2!CVirtualAddressAllocator::CommitVirtualAddressRange+0x338
    ffffd001`8c7d8800 fffff800`cff573a7 dxgmms2!VIDMM_GLOBAL::PageInOneAllocation+0x4de
    ffffd001`8c7d8910 fffff800`cff75290 dxgmms2!VIDMM_GLOBAL::ProcessDeferredCommand+0xd37
    ffffd001`8c7d8a90 fffff800`af623125 dxgmms2!VIDMM_WORKER_THREAD::Run+0xa80
    ffffd001`8c7d8d50 fffff800`af761906 nt!PspSystemThreadStartup+0x41
    ffffd001`8c7d8da0 00000000`00000000 nt!KiStartSystemThread+0x16

    Looking at the dxdiag file there are a few Windows Error Reports, these are from a bluescreen 0x117 which are usually caused by GPU related stuff (drivers, improper seating, damaged card, damaged slot, dust, etc).
    Code:
    +++ WER3 +++:
    Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 117
    P2: ffffe00020413010
    P3: fffff800da04ce98
    P4: 0
    P5: 0
    P6: 10_0_10586
    P7: 0_0
    P8: 256_1
    P9: 
    P10:
      My Computers


 

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

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




Windows 10 Forums