Richard knight
New Member
- Joined
- Nov 10, 2014
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800fa36cb6, fffff88005925e88, fffff880059256e0}
Probably caused by : atikmdag.sys ( atikmdag+a06cb6 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41284, fffff980146b6001, 3458, fffff780c0000000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )
Followup: MachineOwner
nevermind its running now in regular start up *Fingers Crossed*!The dump files sent were almost exactly like the ones you sent earlier. Once again many different bugchecks including the above Bugcheck 1A means a severe memory management error has occurred. Just because the RAM is new doesn't mean it can't be bad. So try testing the new RAM (which I notice is exactly the same model as your old RAM) with Memtest86 making sure you test for at least 12hrs. Some errors won't appear until the 12th hour so it's critical RAM is tested for at least that long.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41284, fffff980146b6001, 3458, fffff780c0000000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 ) Followup: MachineOwner
You may also need to consider that the RAM is fine and it's a slot that's bad.
HECIx64.sys Mon Jul 02 23:14:58 2012: Intel Management Engine Interface. I also notice you didn't upgrade your Intel drivers
Did you run the GPU test?
Okay soo i stopped most of the BSOD's but now when im watching a youtube video or doing normal things, steam, browsing internet,etc. the screen goes blank. I know windows is still running in the background as i can hear it, also when i unplug the hdmi from my tv and plug it back in the picture comes back but its a BSOD.Hi,
it's possible. It's also possible that the Intel drivers may bear some relation too.. Did you update them? Also it's odd your GPU didn't complete the test I asked you to run.
Try running the burn-in test on Furmark:
http://www.ozone3d.net/benchmarks/fur/
You could also try uninstalling the GPU driver using this application as it also removes old leftover bits n bobs:
http://www.wagnardmobile.com/DDU/
Download an install the latest whql driver here:
http://support.amd.com/en-us
Windows does have it's own memory testing app but it can often miss errors and the best app for the job is Memtest86. The latest version of which can be found here:
http://www.memtest.org/
To run Memtest86 you need to either burn a copy of it to disk or use a USB stick. If you look down the page you'll eventually find the latest version and it's associated downloads. If your burning to disk choose the pre-compiled iso zip. If your using a USB method then the corresponding download is the auto installer for a USB stick.
Once you have Memtest86 on the media you selected you'll then need to enter your bios and change the boot order so that the machine will boot from either the disk or stick you have Memtest86 on.
Run the test for at least 12hrs if possible unless it becomes clear that there is a issue. If there is a problem with the RAM you'll see the errors pop up in red so you can't miss them.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D5, {fffff9800be2afa8, 0, fffff8800f1514db, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+c94db )
Followup: MachineOwner