SFC unable to fix errors and BSOD issues - please help

M

Mandragorin

New member
Joined
Sep 4, 2014
Posts
4
Location
Bedfordshire, UK
I hope someone is able to help me. I keep experiencing intermittent BSOD. There doesn't seen to be any pattern to it, it happens when I play games (NWN2, X-rebirth) and when I'm just browsing on the internet, in MS Office or copying files from one disk to another.
I upgraded my graphics card from a radeon hd4890 vapor-x to a sapphire R9 290x Vapor-x (4gb). I did a clean install, removing everything AMD
with windows uninstall and then using driver sweeper, before installing catalyst 14.4. I am currently on catalyst 14.2 which is the version that's on the driver disk that came with the card, but still getting the problem

Here's the latest problem description and dump file attached:
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057

Extra information about the problem
BCCode: 116
BCP1: FFFFFA8011EA94E0B
CP2: FFFFF880046D4D88B
CP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1
Bucket ID: X64_0x116_TdrBCR:2_Tdr:2_IMAGE_atikmpag.sys
Server information: 3bea91a0-6ef1-47dc-a8ed-b950930c81a6

View attachment RM Minidump 090414-35490-01.zip

I also ran sfc /scannow three times rebooting after each occasion. After the third scan there were still errors reported. I'm attaching that CBS log file. Having read previous posts here I have also run the SFC Fix and attaching that txt file also.

View attachment CBS.zip View attachment SFCFix.txt

I hope I have covered everything needed to be able to identify the problem and possible solutions but if you need anymore information please let me know and thanks in advance for any help or pointers to resolving this problem.

 
Hello and welcome to Sysnative :)

You have a lot of file corruptions going on here, which might be caused by a bigger issue of a hardware failure. This could also be the reason for your BSOD. I will get one of the BSOD experts to have look over your dump files to see if it gives an indication of what could be failing.

In the mean time please run a hardware diagnostic with SeaTools. Please do a long text and a short test and post aback with the results.
https://www.sysnative.com/forums/hardware-tutorials/4072-hard-drive-hdd-diagnostics.html
 
I'll help you out with the BSOD issue you're getting.

Code: 
BugCheck [COLOR="#FF0000"]A0000001[/COLOR], {5, 0, 0, 0}

This bugcheck is unknown, and I've seen it a lot recently.
Looking into it though, it seems to be related to amd display drivers.

Code: 
fffff880`0311b718 fffff880`100d47ce : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : [COLOR="#0000FF"]nt!KeBugCheckEx[/COLOR]
fffff880`0311b720 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR="#FF0000"]atikmdag+0x277ce[/COLOR]
fffff880`0311b728 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`1059a000 : [COLOR="#800080"]0xa0000001[/COLOR]
fffff880`0311b730 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`1059a000 00000000`00000000 : [COLOR="#800080"]0x5[/COLOR]

All we can see are the parameters which the bugcheck displays being sent along with the amd driver.

This is mostly likely one of two things, either a bad display driver or the graphics card is failing.
Given you also mention a 0x116 bugcheck I'd say your GPU is failing, we can try changing the driver though.

Without a Kernel dump I can't check your temperatures for you but r9 290x GPUs have been causing a lot of trouble, especially due to overheating.
What temperature is your PC at?

Code: 
1: kd> [COLOR="#008000"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`100ad000 fffff880`10d9d000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="#FF0000"]Fri Dec 06 21:19:43 2013[/COLOR] (52A23F6F)
    CheckSum:         00CA856E
    ImageSize:        00CF0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I suggest updating the driver to the latest version, if that doesn't help then try a beta driver, if that still doesn't help then you could try rolling back further than December last year.
If changing the display driver doesn't help at all in frequency of the blue screens then your GPU is probably failing.
Either that or you have a bad motherboard.
 
Thanks Jared

I've completely uninstalled all AMD files using Driver Fusion (which left a couple of legacy registry files) and then Display Driver Uninstaller. DDU got rid of one of the registry files but left:
hkey_local_machine\system\currentcontrolset\enum\root\legacy_amdacpksd
I wasn't able to delete that file so left it and installed AMD CCC 14.4

I'll report back if I get a BSOD
------------------------------------------------------------------------------

Go The Power

I followed the steps to boot up into SeaTools but it only found my two WD HDD and not my Crucial SSD which is where my OS is.
I have an ASUS P6T Deluxe V2 motherboard and have attached an ASUS U3S6 card via the PCIe slot; to give me USB3 and SATA6 support. My Crucial M4-CT256 SSD is attached to this.
 
It's the same bugcheck, unfortunately, even though it's a Kernel dump there just isn't much information.

Code: 
fffff880`0311b708 fffff880`10029ece : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0311b710 fffff880`100391e0 : 00000000`00000000 fffffa80`0d7fe010 00000000`00000000 00000000`00000000 : atikmdag+0x28ece
fffff880`0311b750 fffff880`10082045 : fffffa80`0f7fb410 00000000`00000000 fffffa80`0f7fbba0 fffff880`0475248b : atikmdag+0x381e0
fffff880`0311b780 fffff880`10083b44 : 00000000`00000002 fffff880`100387a3 00000000`00000000 00000000`00000000 : atikmdag+0x81045
fffff880`0311b800 fffff880`10083c81 : fffffa80`0f89f370 fffff880`0311b971 00000000`00000000 fffffa80`0f7fb410 : atikmdag+0x82b44
fffff880`0311b880 fffff880`10083d4d : 00000000`00000000 00000000`00000000 fffffa80`0ceb8000 fffff880`0474ec63 : atikmdag+0x82c81
fffff880`0311b8c0 fffff880`10083e85 : 00000000`00000000 fffff880`00000000 fffff880`00000000 fffff880`1003cfdf : atikmdag+0x82d4d
fffff880`0311b9d0 fffff880`1008d098 : fffffa80`0f877210 fffffa80`0f885b80 fffffa80`0f875000 fffff880`1008ceb6 : atikmdag+0x82e85
fffff880`0311ba20 fffff880`100808cc : fffffa80`00000000 fffffa80`0f875000 fffff880`0311bb80 00000000`00000001 : atikmdag+0x8c098
fffff880`0311ba70 fffff880`10026c35 : fffffa80`0e93d940 fffffa80`0eb7a780 fffff880`009f50c0 00000003`00000030 : atikmdag+0x7f8cc
fffff880`0311baa0 fffff880`044ef2de : 00000000`00000000 fffff880`009f50c0 fffffa80`0dc751a0 00000000`00000001 : atikmdag+0x25c35
fffff880`0311bad0 fffff800`03087a1c : 00000000`00000000 fffff880`009f50c0 fffffa80`0eb7a780 00000000`00000000 : atikmpag+0x92de
fffff880`0311bb00 fffff880`0431b9c2 : fffff800`03094709 00000000`0027d3ce fffffa80`0dc7d0a8 fffffa80`0e987d02 : nt!KiInterruptDispatch+0x16c
fffff880`0311bc98 fffff800`03094709 : 00000000`0027d3ce fffffa80`0dc7d0a8 fffffa80`0e987d02 fffffa80`0e987d28 : intelppm!C1Halt+0x2
fffff880`0311bca0 fffff800`0308389c : fffff880`009ea180 fffff880`00000000 00000000`00000000 fffff880`0465a588 : nt!PoIdle+0x52a
fffff880`0311bd80 00000000`00000000 : fffff880`0311c000 fffff880`03116000 fffff880`0311bd40 00000000`00000000 : nt!KiIdleLoop+0x2c

Code: 
1: kd> [COLOR="#008000"]u nt!KiInterruptDispatch+0x16c[/COLOR]
nt!KiInterruptDispatch+0x16c:
fffff800`03087a1c 884588          mov     byte ptr [rbp-78h],al
fffff800`03087a1f 488b4e48        mov     rcx,qword ptr [rsi+48h]
fffff800`03087a23 e808df0000      call    nt!KeReleaseSpinLockFromDpcLevel (fffff800`03095930)
fffff800`03087a28 f685f3000000ff  test    byte ptr [rbp+0F3h],0FFh
fffff800`03087a2f 741a            je      nt!KiInterruptDispatch+0x19b (fffff800`03087a4b)
fffff800`03087a31 4c8b4d50        mov     r9,qword ptr [rbp+50h]
fffff800`03087a35 4c8b85e0000000  mov     r8,qword ptr [rbp+0E0h]
fffff800`03087a3c 0fb65588        movzx   edx,byte ptr [rbp-78h]

We can see a spinlock is released and then the interrupt is resumed, the interrupt involves the amd display driver and thats all we know.

This dump file isn't very helpful.

I would say your GPU is failing, do you have another one you can test?
You can try using the Intel integrated graphics as a test.
 
No problem, take your time.
Report back if you have any issues.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top