W wheat89 New member Joined Sep 3, 2014 Posts 3 Sep 3, 2014 #1 So, whenever i try to watch a movie or little vid, my system crashes. It has been doing this since i bought it and i never managed to fix it. I reinstalled windows many many times and updated the drivers more than i can count. It's really ironic that i runs crysis without any struggles but cant handle a youtube vid or sometimes even gif xD I would be a very happy man i you can help me. Kind regards. Nino OS - Windows 7 x64 Original OS, Retail version About 4 years Reinstalled OS couple times few years ago System info in picture I think Corsair 600watts psu System is home built desktop Attachments Bsod.zip 2 MB · Views: 2
So, whenever i try to watch a movie or little vid, my system crashes. It has been doing this since i bought it and i never managed to fix it. I reinstalled windows many many times and updated the drivers more than i can count. It's really ironic that i runs crysis without any struggles but cant handle a youtube vid or sometimes even gif xD I would be a very happy man i you can help me. Kind regards. Nino OS - Windows 7 x64 Original OS, Retail version About 4 years Reinstalled OS couple times few years ago System info in picture I think Corsair 600watts psu System is home built desktop
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Sep 3, 2014 #2 It looks like your display driver is causing problems, evidenced by the bugcheck, the fact that you can run crysis and not youtube videos and the error code in the bugcheck seems to emphasize this. Code: BugCheck 116, {fffffa800bd2a4e0, fffff88004303cf0, 0, 2} Code: FAULTING_IP: atikmpag+acf0 fffff880`04303cf0 4055 push rbp It's adding data onto the stack which is causing a fault, it seems that its causing a hang in the display driver and hence the bugcheck. Code: fffff880`03fe9308 fffff880`0425ccbc : 00000000`00000116 fffffa80`0bd2a4e0 fffff880`04303cf0 00000000`00000000 : nt!KeBugCheckEx fffff880`03fe9310 fffff880`0425c9c6 : fffff880`04303cf0 fffffa80`0bd2a4e0 fffffa80`05ea2a80 fffffa80`07958010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`03fe9350 fffff880`053a8f07 : fffffa80`0bd2a4e0 00000000`00000000 fffffa80`05ea2a80 fffffa80`07958010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`03fe9380 fffff880`053d6d7e : fffffa80`ffffffff 00000000`0006f7fb fffff880`03fe94d0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`03fe9460 fffff880`053bcbb1 : fffffa80`07c61000 ffffffff`feced300 00000000`00000002 00000000`000000aa : dxgmms1!VidSchWaitForCompletionEvent+0x196 fffff880`03fe94a0 fffff880`053bfaaf : 00000000`00000001 00000000`00000000 fffffa80`07733e40 fffff8a0`01588dc0 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9 fffff880`03fe95a0 fffff880`053be1a0 : fffff8a0`01588dc0 00000000`00000000 fffffa80`07c61000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7 fffff880`03fe95e0 fffff880`053be0f6 : 00000000`00000000 00000000`00000001 fffffa80`07c61000 fffff880`053bca1e : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34 fffff880`03fe9770 fffff880`053c7642 : fffffa80`07788930 00000000`00000001 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e fffff880`03fe97e0 fffff880`053c73eb : fffff8a0`01588dc0 00000000`00001000 fffffa80`07788930 fffff8a0`01588dc0 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a fffff880`03fe9830 fffff880`053c6d8f : fffff8a0`01588dc0 fffffa80`07c61c80 00000000`00000000 fffffa80`07c61c80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b fffff880`03fe9890 fffff880`053ba76c : fffffa80`07c61000 fffffa80`07c61000 fffffa80`07c61c80 fffffa80`07c61000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf fffff880`03fe98d0 fffff880`053b7133 : 00000000`00000000 00000000`00000000 00000000`0000001d fffffa80`07c61000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc fffff880`03fe9910 fffff880`053d165d : 00000000`00000000 fffff8a0`0ace7550 fffffa80`00000000 fffffa80`05c2bbc0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f fffff880`03fe9ae0 fffff880`053d1398 : fffff880`009ed040 fffff880`053d0d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`03fe9cd0 fffff880`053d0e96 : 00000000`00000000 fffffa80`07d50610 00000000`00000080 fffffa80`07958010 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`03fe9d00 fffff800`0356e166 : 00000000`03766d68 fffffa80`07c32b60 fffffa80`0552d840 fffffa80`07c32b60 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`03fe9d40 fffff800`032a9486 : fffff880`009e8180 fffffa80`07c32b60 fffff880`009f30c0 fffff880`01215534 : nt!PspSystemThreadStartup+0x5a fffff880`03fe9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 We can see the DirectX video scheduler preparing a DMA buffer, it then begins to remove allocations followed by setting up a paging buffer which looks to be the source of the crash. Code: 6: kd> lmvm atikmdag start end module name fffff880`04826000 fffff880`05399000 atikmdag (deferred) Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Fri Mar 29 02:27:04 2013 (5154FBF8) CheckSum: 00B25604 ImageSize: 00B73000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 I recommend an update for your display driver, download the latest version.
It looks like your display driver is causing problems, evidenced by the bugcheck, the fact that you can run crysis and not youtube videos and the error code in the bugcheck seems to emphasize this. Code: BugCheck 116, {fffffa800bd2a4e0, fffff88004303cf0, 0, 2} Code: FAULTING_IP: atikmpag+acf0 fffff880`04303cf0 4055 push rbp It's adding data onto the stack which is causing a fault, it seems that its causing a hang in the display driver and hence the bugcheck. Code: fffff880`03fe9308 fffff880`0425ccbc : 00000000`00000116 fffffa80`0bd2a4e0 fffff880`04303cf0 00000000`00000000 : nt!KeBugCheckEx fffff880`03fe9310 fffff880`0425c9c6 : fffff880`04303cf0 fffffa80`0bd2a4e0 fffffa80`05ea2a80 fffffa80`07958010 : dxgkrnl!TdrBugcheckOnTimeout+0xec fffff880`03fe9350 fffff880`053a8f07 : fffffa80`0bd2a4e0 00000000`00000000 fffffa80`05ea2a80 fffffa80`07958010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2 fffff880`03fe9380 fffff880`053d6d7e : fffffa80`ffffffff 00000000`0006f7fb fffff880`03fe94d0 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b fffff880`03fe9460 fffff880`053bcbb1 : fffffa80`07c61000 ffffffff`feced300 00000000`00000002 00000000`000000aa : dxgmms1!VidSchWaitForCompletionEvent+0x196 fffff880`03fe94a0 fffff880`053bfaaf : 00000000`00000001 00000000`00000000 fffffa80`07733e40 fffff8a0`01588dc0 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9 fffff880`03fe95a0 fffff880`053be1a0 : fffff8a0`01588dc0 00000000`00000000 fffffa80`07c61000 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::SetupForBuildPagingBuffer+0xd7 fffff880`03fe95e0 fffff880`053be0f6 : 00000000`00000000 00000000`00000001 fffffa80`07c61000 fffff880`053bca1e : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegmentInternal+0x34 fffff880`03fe9770 fffff880`053c7642 : fffffa80`07788930 00000000`00000001 00000000`00000001 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::UnmapVideoApertureSegment+0x13e fffff880`03fe97e0 fffff880`053c73eb : fffff8a0`01588dc0 00000000`00001000 fffffa80`07788930 fffff8a0`01588dc0 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapApertureRange+0x7a fffff880`03fe9830 fffff880`053c6d8f : fffff8a0`01588dc0 fffffa80`07c61c80 00000000`00000000 fffffa80`07c61c80 : dxgmms1!VIDMM_APERTURE_SEGMENT::UnmapTemporaryResource+0x9b fffff880`03fe9890 fffff880`053ba76c : fffffa80`07c61000 fffffa80`07c61000 fffffa80`07c61c80 fffffa80`07c61000 : dxgmms1!VIDMM_APERTURE_SEGMENT::ReleaseTemporaryResource+0xcf fffff880`03fe98d0 fffff880`053b7133 : 00000000`00000000 00000000`00000000 00000000`0000001d fffffa80`07c61000 : dxgmms1!VIDMM_GLOBAL::EvictTemporaryAllocations+0xbc fffff880`03fe9910 fffff880`053d165d : 00000000`00000000 fffff8a0`0ace7550 fffffa80`00000000 fffffa80`05c2bbc0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x69f fffff880`03fe9ae0 fffff880`053d1398 : fffff880`009ed040 fffff880`053d0d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`03fe9cd0 fffff880`053d0e96 : 00000000`00000000 fffffa80`07d50610 00000000`00000080 fffffa80`07958010 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`03fe9d00 fffff800`0356e166 : 00000000`03766d68 fffffa80`07c32b60 fffffa80`0552d840 fffffa80`07c32b60 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`03fe9d40 fffff800`032a9486 : fffff880`009e8180 fffffa80`07c32b60 fffff880`009f30c0 fffff880`01215534 : nt!PspSystemThreadStartup+0x5a fffff880`03fe9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 We can see the DirectX video scheduler preparing a DMA buffer, it then begins to remove allocations followed by setting up a paging buffer which looks to be the source of the crash. Code: 6: kd> lmvm atikmdag start end module name fffff880`04826000 fffff880`05399000 atikmdag (deferred) Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Fri Mar 29 02:27:04 2013 (5154FBF8) CheckSum: 00B25604 ImageSize: 00B73000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 I recommend an update for your display driver, download the latest version.
W wheat89 New member Joined Sep 3, 2014 Posts 3 Sep 6, 2014 #3 Well the problem is that i did that a lot, in every possible way, updates, full reinstalls but it keeps happening
Well the problem is that i did that a lot, in every possible way, updates, full reinstalls but it keeps happening
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Sep 6, 2014 #4 Try a beta driver or different later drivers. It's difficult to find a good driver sometimes. Do you have another card you can try?
Try a beta driver or different later drivers. It's difficult to find a good driver sometimes. Do you have another card you can try?
W wheat89 New member Joined Sep 3, 2014 Posts 3 Sep 6, 2014 #5 Well i have an old 4890 but that ones likely more defect than this one
Jared Sysnative Staff, BSOD Kernel Dump Expert Joined Feb 3, 2014 Posts 1,591 Sep 6, 2014 #6 It's always worth a try, there isn't many bad ideas when it comes to troubleshooting.