New
#1
BSOD Bug Check Code 0x00000139
Minidump:
Last edited by mihomilo; 23 Sep 2015 at 07:57.
Done
An AMD video driver has been flagged.
Please remove the AMD Catalyst Control Center and only install the drivers.
Code:0: kd> lmvm atikmdag start end module name fffff801`fa950000 fffff801`fbe5a000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Timestamp: Tue Aug 04 05:28:52 2015 (55C03174) CheckSum: 014ADEC6 ImageSize: 0150A000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
After deleting the AMD Catalyst Control Center, I am still getting BSOD. Here are the latest Dump File:
Please scan your system with your AV and Malwarebytes free (Uncheck the trial version in the installation).
Run Furmark to test your GPU. Furmark tutorial
NoteRun Furmark for around 30 minutes
WarningYour GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high
Havent got any BSOD since then, will update u when a new BSOD comes
That may take too long or will be never.
Please let us know how it goes for the next few days :)
I just got a new BSOD 5 mins ago. Here is the new Dumpfile:
Please try following below, after the results are good please run driver verifier
Please do the following:
- Open an admin command prompt
- Copy/paste "sfc/scannow" (without quotes) and press enter
- When it finished reboot your system
- Open again an admin command prompt
- Enter sfc/scannow again
If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation", please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html
NoteDo not run SeaTools on an SSD as the results will be invalid.
Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html
WarningPlease make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.
Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.
NoteYour system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.