Getting BSOD from random stuff

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Tim Roejgaard, Apr 12, 2015.

  1. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    Hi, I started getting BSOD while playing Path of Exile, but lately its happening to what appears to be random. I get BSOD when alt tabbing between some games, and even right before the PC is about to shut down.

    Please help, I have attached 3 dump files, so maybe its the same problem everytime or various ones. If anyone need other information about anything just ask.

    Thank you.
     

    Attached Files:

  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff80003530433, fffff88007da3da0, 0}
    
    Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+e3 )
    
    Followup: MachineOwner
    
    Code:
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s
    Hi,
    of the three dump files sent, one related to NTFS errors (Bugcheck 24), another to memory management (Bugcheck 1A) and the above. The above bugcheck can be caused by drivers, faulty system service and hardware. The accompanying exception code means data held in the memory couldn't be read because either it or the memory was corrupted.
    Looking at the Call Stack I also see mention of system service handler and it might be worth checking the event logs to see if anything in particular has been playing up. In any case try running a system file scan. You can do this by right clicking on command prompt, choose properties and run as administrator. Type:
    sfc /scannow
    Press enter and await results.

    Your drivers are in need of updating:
    You can update both graphics and chipset (sata driver) here:
    http://support.amd.com/en-us/download/desktop?os=Windows%207%20-%2064

    Rt64win7.sys Tue Aug 23 14:55:41 2011: Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet
    http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

    RTKVHD64.sys Tue Jun 19 09:50:56 2012: Realtek HD Audio.
    http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=14&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

    If after making the above changes you still get the bsod then you need to test your RAM.
    Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
    http://www.memtest.org/

    To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
    Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
    Run the test for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.

    Post any new dump files.
     
  3. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    Thank you very much I will start from the top of the list trying to solve this issue. I haven't done anything yet but I thought I wanted to post the lastest BSOD dump file anyway.
     

    Attached Files:

  4. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 3B, {c0000005, fffff80003534433, fffff88009440da0, 0}
    
    Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+e3 )
    
    Followup: MachineOwner
    
    Hi Tim,
    as you can see it's the same again. Try the above suggestions and see how you go..
     
  5. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    Heh well I don't really understand much from this bugcheck analysis, but I did install the drivers you linked(I belive). So let's hope that was the problem, it has been a while since last time I did anything regarding driver update.

    Again thank you very much for the kind and fast help, I will post any new BSOD dump files.
     
  6. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Ok Tim sounds good. I'll await your next post if there should be one..
     
  7. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    Here I am again, is it the RAM?
     

    Attached Files:

  8. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Code:
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffffffffffffffff, 2, 1, fffff800034bf5a2}
    
    Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
    
    Followup: MachineOwner
    

    Hi,
    this bugcheck is issued if invalid memory is accessed. This can be caused by the installation of faulty device drivers, system service or bios. It is also possible that you might have some faulty RAM.
    Driver wise you still need to update the driver highlighted below:

    amd_sata.sys Wed Apr 11 15:40:24 2012: AMD SATA driver.

    You can update both graphics and chipset (sata driver) here: (you must update your chipset drivers. These are found under 'optional downloads'. Update everything apart from the RAID driver)
    http://support.amd.com/en-us/download/desktop?os=Windows 7 - 64

    TVicPort64.SYS Wed Mar 30 10:12:54 2005: Do you have a TV card installed on your system?

    Also please find command prompt, right click on it and run as administrator. Type:
    sfc /scannow
    Press enter and await results.

    Please follow the advice above and run Memtest86.
     
  9. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    Okay so now I think I've downloaded and updated everything.

    I'm not sure about this?


    This passed with no errors or anything wrong.



    And the memtest86, I've been running it for about 7½ hours at this point, with 4 passes and 0 errors. Stop or keep going?
    Also does it help if I say the BSOD usually happens while playing Path of exile?
    I'm awaiting further instructions :)
     
  10. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    Latest BSOD happend when I exited Path of Exile, and it has happened before.
     

    Attached Files:

  11. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {ffffffffffffffff, 2, 1, fffff80003501202}
    
    Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 )
    
    Followup: MachineOwner
    
    Hi,
    This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

    The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS. Have you made any recent changes regarding updates or drivers? Have you used anything like a registry cleaner or similar?
    You originally said the bsod was random although you say it happens more when you play the game. It could be that something on your machine dislikes the game and as it's browser based (?) I wonder if your Eset may have an issue with it. (all speculation of course.)

    Have you tested other games to make sure it's just this game that causes the bsod?

    I also see your running AMD overdrive? If your overclocking then stop.

    The above was highlighted simply because of the date. It's ancient and needs to be updated. Check your device manager or installed programs to try and determine what it is.

    When testing RAM 7.5 hrs is not enough and as specified above you need to run memtest86 for at least 12hrs. The reason is because some errors won't appear until after that amount of time has passed. Leave it on overnight if that helps any.

    Please update your chipset
    You can update both graphics and chipset (sata driver) here: (you must update your chipset drivers. These are found under 'optional downloads'. Update everything apart from the RAID driver)
    http://support.amd.com/en-us/download/desktop?os=Windows 7 - 64

    If the bsod still continues then let's try and flush the driver out (if it is driver related) by using the driver verifier. The guide below will show you how to go on and please post the dump files after:
    http://www.reviversoft.com/blog/2013/09/using-driver-verifier-to-fix-a-blue-screen-of-death/
     
  12. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    Yes, I have Ccleaner installed and around the time I was getting many BSOD I did run a duplicator remover of some sort.

    I don't think I'm overclocking since I have no idea how to do it. And from what I have been reading it's not something that happens by it self.

    I will run memtest86 again for 12+ hrs again ASAP.

    About the chipset (sata driver), I don't know what to do, I have clicked on the link you posted and installed it.

    I did this just now and the dump file I have uploaded should be from that.

    Sorry for being such a noob, I just play games man.
     

    Attached Files:

  13. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C1, {fffff980a6298ff0, fffff980a629806f, c9c018, 32}
    
    Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGDEVICE::DestroyAllocations+5eb )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff980a6298ff0, address trying to free
    Arg2: fffff980a629806f, address where one bit is corrupted
    Arg3: 0000000000c9c018, (reserved)
    Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC1_32
    
    SPECIAL_POOL_CORRUPTION_TYPE:  32
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  PathOfExileSte
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff800035502a3 to fffff800034bda40
    
    STACK_TEXT: 
    fffff880`097261c8 fffff800`035502a3 : 00000000`000000c1 fffff980`a6298ff0 fffff980`a629806f 00000000`00c9c018 : nt!KeBugCheckEx
    fffff880`097261d0 fffff800`035c8d23 : 00000000`00000000 00000000`00000001 00000000`00000003 00000000`00000001 : nt!MiCheckSpecialPoolSlop+0x83
    fffff880`09726210 fffff800`035f4985 : 00000000`00000174 00000000`6d4d6956 00000000`0019b458 00000000`00000000 : nt!MmFreeSpecialPool+0x1d3
    fffff880`09726350 fffff880`1232e06f : 00000000`00000000 00000000`00000000 fffff8a0`02236000 00000000`00000001 : nt!ExAllocatePoolWithTag+0x16bd
    fffff880`09726400 fffff880`123408b8 : fffff8a0`02236000 00000000`00000000 00000000`00000000 fffff8a0`02236068 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x5eb
    fffff880`097264f0 fffff880`12325815 : fffff980`fffffeda fffff980`614c8f40 fffff8a0`02236000 fffffa80`0a630000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
    fffff880`09726560 fffff880`12363fee : fffffa80`06c96300 fffffa80`0a630000 fffff980`614c8f40 fffff980`614c8fc0 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
    fffff880`09726590 fffff880`12363984 : fffff900`c4d38cd0 00000000`00000000 00000000`00000001 fffff900`c4d38cd0 : dxgkrnl!DXGPROCESS::Destroy+0xba
    fffff880`09726640 fffff960`000c7914 : 00000000`00001088 fffff900`c4d38cd0 00000000`00000000 fffff900`c4d38cd0 : dxgkrnl!DxgkProcessCallout+0x268
    fffff880`097266d0 fffff960`000c7017 : 00000000`00000000 fffff880`09726ae0 fffffa80`083eab50 00000000`00000001 : win32k!GdiProcessCallout+0x244
    fffff880`09726750 fffff800`037920bd : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`083eab00 : win32k!W32pProcessCallout+0x6b
    fffff880`09726780 fffff800`03776d1d : 00000000`cfffffff 00000000`00000001 00000000`78457300 fffffa80`0895a060 : nt!PspExitThread+0x4d1
    fffff880`09726880 fffff800`034b123a : 00000000`0000000b fffff880`60000000 00000000`00000008 fffff800`034e9650 : nt!PsExitSpecialApc+0x1d
    fffff880`097268b0 fffff800`034b1580 : 00000000`00000246 fffff880`09726930 fffff800`03776c90 00000000`00000001 : nt!KiDeliverApc+0x2ca
    fffff880`09726930 fffff800`034bcd77 : fffff880`09726b60 fffff800`034c7e42 00000000`0000002a 00000000`73762450 : nt!KiInitiateUserApc+0x70
    fffff880`09726a70 00000000`73762e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`04aeec28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73762e09
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP:
    dxgkrnl!DXGDEVICE::DestroyAllocations+5eb
    fffff880`1232e06f 4d8b5d30        mov     r11,qword ptr [r13+30h]
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  dxgkrnl!DXGDEVICE::DestroyAllocations+5eb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgkrnl
    
    IMAGE_NAME:  dxgkrnl.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  539e411c
    
    IMAGE_VERSION:  6.1.7601.18510
    
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_dxgkrnl!DXGDEVICE::DestroyAllocations+5eb
    
    BUCKET_ID:  X64_0xC1_32_VRF_dxgkrnl!DXGDEVICE::DestroyAllocations+5eb
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xc1_32_vrf_dxgkrnl!dxgdevice::destroyallocations+5eb
    
    FAILURE_ID_HASH:  {eeff9e28-9d03-f893-3d2e-8ece8903a34d}
    
    Followup: MachineOwner
    
    Hi,
    The above dump file basically means a driver is writing to an incorrect place. It looks like the graphics were involved too. Check your Vram using this app:
    http://mikelab.kiev.ua/index_en.php?page=PROGRAMS/vmt_en

    atikmdag.sys Fri Nov 21 02:30:27 2014: AMD GPU driver. Try removing this driver using DDU (display driver uninstaller):
    http://www.wagnardmobile.com/DDU/
    Install the latest beta driver from AMD:
    http://support.amd.com/en-us

    Regarding testing the RAM. Sometimes you simply cannot run memtest86 long enough to catch the errors. In cases like these the best way to check for a dodgy stick is to run the machine on one stick at a time. Play the game and if the machine bsod's then swap sticks and try again. See if there is a stick which does bsod and one that doesn't.

    Above you don't say whether the bsod's started after the duplicator remover was ran or you ran the duplicator because of it. If they started after you ran the duplicator remover (registry cleaners are simply not needed with windows and cause more issues than they fix) then chances are you've removed something that was needed.

    TVicPort64.SYS Wed Mar 30 10:12:54 2005: Do you have a TV card installed on your system?
     
  14. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    I did this 1 time, and found no error, do I need to run it for 12hrs like memtest86?

    Did this too, the AMD auto detect and install program said I have latest updates.

    What do you mean? What stick? And how do I run my PC on one stick?

    Also I was running the duplicator remover every now and then, because I thought it would free some space and remove unnecessary files. So I dont exactly remember what happend first. But I belive I ran the Ccleaner and then all turned to shit. So yeah I probably removed something I needed.


    Not that I know of, so I don't think so.
     
  15. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    BSOD after last changes.
     

    Attached Files:

  16. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1A, {41284, 148bc001, 0, fffff70001080000}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+b0 )
    
    Followup: MachineOwner
    
    I was referring to sticks of RAM. You'll need to open up the pc and remove a stick of RAM. Follow the advice above regarding testing. If your unsure on how to remove sticks of RAM then try running Memtest86 again but run it for as long as possible 24hrs if need be.

    Yes but you have to search for the beta manually. Even if you don't install the latest beta I'd would consider re-installing the driver again as the last two dump files both mention graphics which may mean the driver is corrupted or the gpu has an issue.

    No. Once is enough.

    If this is the case then you'll need to repair Windows. Do you have an installation disk or a restore point you could go back to?
     
  17. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    Before I go on for a couple of more days, would it resolve the problem if I completly wiped everything and installed Windows from scratch?
     
  18. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Joined:
    Aug 28, 2007
    Messages:
    31,829
    Likes Received:
    1,565
    It may help. Especially as it's suspected that needed data was removed.
     
  19. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    So i reinstalled Windows but I still have some problems.
     
  20. Tim Roejgaard

    Tim Roejgaard New Member

    Joined:
    Apr 12, 2015
    Messages:
    14
    Likes Received:
    0
    And here's the dump file
     

    Attached Files:

Share This Page

Loading...