[Kicktar]

I have had three crashes today, minidumps attached.

I had removed Alcohol and Kaspersky, just not their start menu folders. I'll stop using DriverMax and ASUS AI. Only reason I had ASUS AI was for the temp readings anyway.

All three of those crashes were after updating the driver, unfortunately.

Attached Files

•  Minidump.zip   60.35KB   236 downloads

[Advertisements]

Two of the 3 errors were caused by the ntoskrnl and the one was caused by the atikmdag.sys
This would be the video driver. Either driver is outdated or corrupted.

[rshaffer61]

Two of the 3 errors were caused by the ntoskrnl and the one was caused by the atikmdag.sys
This would be the video driver. Either driver is outdated or corrupted.

[xBlueRobot]

BugCheck 124, {0, fffffa80020ab8f8, 0, 0}

Probably caused by : AuthenticAMD

0: kd> !errrec fffffa80020ab8f8
===============================================================================
Common Platform Error Record @ fffffa80020ab8f8
-------------------------------------------------------------------------------
Record Id     : 01ce99036b73d525
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 8/14/2013 15:32:08 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa80020ab978
Section       @ fffffa80020aba50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100f43
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa80020ab9c0
Section       @ fffffa80020abb10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 43 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa80020abb10

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa80020aba08
Section       @ fffffa80020abb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f

Here's the largest problem, the bugcheck was raised by a Machine Check Exception, and the WHEA error reporting service reports a generic timeout error, which basically means the CPU found a problem but couldn't relate it to a hardware component.

I've checked your other dumps, and the graphics card driver, seems to be up to date and the latest WHQL version. As a result, I would recommend running Furmark for a few hours, do not let the temperature exceed 80*C. I recommend monitoring the temperatures with GPU-z.

0: kd> lmvm atikmdag
start             end                 module name
fffff880`07812000 fffff880`083c5000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Wed Apr 24 17:37:45 2013 (51780A59)
    CheckSum:         00B65445
    ImageSize:        00BB3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

[Kicktar]

Well, the temp got up to 80°C within five or six minutes, though it was starting to slow down at around 75°.

[xBlueRobot]

It could potentially be a overheating issue, have you checked inside the case for any dust accumulation?

Edited by xBlueRobot, 16 August 2013 - 04:14 PM.

[Kicktar]

I'm not sure what would count as accumulated, but there is a decent amount of dust. I'm guessing it's not so simple as using a feather duster?

[rshaffer61]

A can of compressed air. When blowing it out do not allow the fan on the cpu to turn freely as it may cause damage to the bearings. One other thing is to not turn the can upside down because it will cause condensation. Blow out all vents, fans, PSU and motherboard.

[Kicktar]

Cleared out most of the dust, and later bluescreened. Minidump attached.

Attached Files

•  minidump.zip   26.18KB   240 downloads

[rshaffer61]

It still is saying a possible driver issue, hard drive issue or lastly a possible hidden infection. We have looked at everything else and I'm beginning to believe we need to check the last option out.

I'll wait till XBlueRobot responds before suggesting anything else.

[Kicktar]

Anything I can try in the mean time?

[rshaffer61]

I myself think you should have the system looked at by one of our malware techs to make sure there is no hidden infection. You can link this topic in the new topic so the tech can see everything we have tried and the results. I am including the instructions below for you to start a malware topic if you want to get started with that. We will put this topic on hold till you have been given the all clear from the malware tech. The last option we would have is a format and fresh install of everything.


I suspect that you have some malware on your computer causing issues that we are not able to solve through means we can use here in the Tech Forums. I suggest you read the 'Start Here' topic found HERE. With these self-help tools you have a high chance of fixing the problems on your own. If you are still having problems after following Step 3 of the guide, continue with Step 4 and 5 and post in the Malware Forum. If you are unable to run any programs, Please create a topic stating what you have tried so far and that you are unable to run any programs. Also, Please do NOT post the logs in this thread.

If you are still having issues after the malware expert gives you a clean bill of health, Please return to THIS thread and we will pursue other options to help you solve your current problem(s).
Add a link to this topic so that malware tech can see what steps have been taken here

[Kicktar]

A little confused. First, both of the first two links go to the same spot, but that might be intentional. Second, I don't see any self help tools, and it seems like step three almost has to go with steps four and five.

Also, I think I mentioned this before, but I had this issue before getting the SSD, and then did a fresh install onto the SSD. So unless I'm missing something, the format and fresh install of everything wouldn't help, but like I said, I might just be missing something.

Edited by Kicktar, 28 August 2013 - 03:05 PM.

[rshaffer61]

Actually the Start Here gives you the instructions to get the logs needed for the malware tech. The second should take you to the actual malware forum to start your topic but I just checked and you are right. HERE is the correct link to the malware forum. Even though the issue was happening before that doesn't mean you may not have a hidden infection. Depending on your installed software, programs and internet surfing habits the infection if there is one could have returned.

[Kicktar]

Thought I should report what ended up working. I lowered the voltage and frequency of the memory, and now there are no more crashes. Unfortuneately, it also seems to have accentuated the low memory problem, but if my computer works, I can live with that. It seems to be an issue with my motherboard, since when I googled the problem of having multiple memory sticks in the computer, a post with my motherboard was the first result.

Thanks for y'all's help, even if it didn't end up working.