Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8004e958f8, 0, 0}
Probably caused by : AuthenticAMD
Followup: MachineOwner
EDIT: I've noticed that this dump file in bluescreen viewer also shows except ntoskrnl.exe now shows dump_ataport.sys in red color, i think that was labeled red in one previous dump too.
Screenshot here is screenshot of the bsod and it blames dump_atiport.sys
This is why I asked you to update your chipset drivers especially the SATA/AHCI driver. I posted the link above. In fact checking the motherboard support page there are some later versions here (2014):
MSI Global. In fact update as much as you can including bios.
EDIT2: I was curious and opened the dump file in windows debugger and saw that it says the same
Probably caused by : AuthenticAMD
All this means is that the issue originated from an AMD component as opposed to an Intel one. It doesn't tell us why it crashed.
Bugcheck 124 This type of bugcheck can be caused by numerous things as i explained above. You need to check everything, go through the system with a fine toothcomb and make sure everything is updated.
In fact the actual type of Bugcheck 124 you have is called a machine check exception.
Normal causes for MCE errors include overheating and/or incorrect hardware installation. Specific manually-induced causes include:
- overclocking (which normally increases heat-output)
- poorly-fitted heatsink/computer fans (the same problem can happen with excessive dust in the CPU fan)
- an overloaded internal or external power-supply (fixable by upgrading)
Computer
software can also cause MCE errors (normally by corrupting data which programs read or write). For example, software performing read or write operations from or to non-existent memory regions can lead to confusion for the processor and/or the system bus.[
citation needed] Accessing memory marked off-limits by
UEFI may cause MCE errors.
[3]
Reference: I went back to your original zip file and checked the drivers and indeed many are very old. In fact looking at the dump file I'd have said that Service pack 1 for windows 7 was missing but looking at the systems number it looks installed. Do you use windows update?
It also looks like you have AMD's Overdrive installed? If so please remove as this can cause bsod's.
Try installing the Service pack again as your drivers simply don't look right. All those drivers which are dated 2009 should be dated 2012 especially if the service pack is installed... Odd.
Here's the link for the service pack, if it's already installed try a repair:
Download Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932) from Official Microsoft Download Center Run a chkdsk:
The How-To Geek Guide to Using Check Disk in Windows 7, 8, or 10 Look in the start menu for command prompt, right click on it and run as admin. Type:
sfc /scannow
Press enter and await results. This will, if possible, repair corruption within the os.
If the bsod continues after the above changes then try the driver verifier. If it causes a bsod loop on start up boot into safe mode and turn it off.
How do I fix a Blue Screen in Windows using Driver Verifier? Lastly the fact that you see artifacts during gaming does not bode well especially if the card is not overheating. Is it possible you could check the card in a friends machine?
